-
-
Notifications
You must be signed in to change notification settings - Fork 367
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
Error opening new comm #1059
Comments
Some more data:
|
Ouch, hope I don’t have to eat my laptop. |
yeah, dunno... but can confirm that pinning to |
Happy to take another look after the weekend, thanks for reporting! |
Sorry for this, this is caused a lot of pain already. |
@bollwyvl I think this is fixed in #1056 (comment) but I am not sure, since I cannot reproduce this :( Could you try running that branch? Or maybe you have ideas on how to reproduce this locally. |
I'm seeing some more issues... will try to create another reproducer and open a new issue. |
With the
6.19.x
line, i'm seeing this in this gist.Rolling back to
6.17.1
does not show this behavior.The
target_name: "comm"
is suspect. Having a further look, but this seemed like a useful minimum reproducer to explore further.The text was updated successfully, but these errors were encountered: