Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No child spawner exists yet - cannot get progress yet #53

Open
rcthomas opened this issue Jul 13, 2022 · 0 comments
Open

No child spawner exists yet - cannot get progress yet #53

rcthomas opened this issue Jul 13, 2022 · 0 comments
Labels

Comments

@rcthomas
Copy link
Contributor

rcthomas commented Jul 13, 2022

I think this exception is harmless, but it shows up a lot in my log and I'm wondering if there might be an alternate approach to what this exception does:

    Traceback (most recent call last):
      File "/usr/local/lib/python3.8/dist-packages/tornado/web.py", line 1704, in _execute
        result = await result
      File "/usr/local/lib/python3.8/dist-packages/jupyterhub/apihandlers/users.py", line 737, in get
        async for event in events:
      File "/usr/local/lib/python3.8/dist-packages/jupyterhub/utils.py", line 570, in iterate_until
        yield item_future.result()
      File "/usr/local/lib/python3.8/dist-packages/jupyterhub/spawner.py", line 1146, in _generate_progress
        async with aclosing(self.progress()) as progress:
      File "/usr/local/lib/python3.8/dist-packages/wrapspawner/wrapspawner.py", line 152, in progress
        raise RuntimeError("No child spawner yet exists - can not get progress yet")
    RuntimeError: No child spawner yet exists - can not get progress yet

This exception was added in #21 to prevent hitting a recursion limit. Is throwing an exception the only way out of that?

@rcthomas rcthomas added the bug label Jul 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant