await None about jhsingle-native-proxy HOT 3 CLOSED

From memory I think maybe_future will turn non-asyncio futures (e.g. concurrent.futures.Future) into an asyncio future.

Actually the problem isn't as complicated as it sounds - it's really just down to the limitations of the way authentication is built into Tornado, and this is a workaround by the Jupyter team. But it just feels a shame to rewrite some of the Tornado auth just in order to avoid these logs... But I think it will come out as a side effect of other features in the future anyway.

from jhsingle-native-proxy.

Thanks for the report, but actually this is expected behavior!

It is due to a necessary workaround in some of the core JupyterHub code here.

I have some plans to make this redundant though, and in the meantime, I will document it to avoid worrying users.

However, of course this error message should just show up in the logs but not impede the Dashboard. Please could I ask, in your case is there ultimately a problem with the dashboard? (Or did you just notice the error in the logs and it caused concern even though there were no apparent side effects?)

from jhsingle-native-proxy.

Thanks for the reply @danlester

However, of course this error message should just show up in the logs but not impede the Dashboard. Please could I ask, in your case is there ultimately a problem with the dashboard? (Or did you just notice the error in the logs and it caused concern even though there were no apparent side effects?)

Indeed there was at the end no problem to display the dashboard. I saw it looking at the logs.

I remember seeing maybe_future in some jupyter packages. But I don't know if it is appropriate here - and I'm unsure it is compatible with asyncio.

from jhsingle-native-proxy.