-
-
Notifications
You must be signed in to change notification settings - Fork 531
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
Sneaky Race condition using asyncio create_task (reliably reproduced) #6603
Comments
Super helpful, thanks @tomascsantos! |
Sadly my fix caused a bunch of other issues. Will have to tackle this again after the 1.4.1 release. |
I'm so excited to see this fixed! Thanks a ton @philippjfr! I just came across something that feels super similar and I'm wondering if your fix applies to this as well: # my_notebook.ipynb
from time import sleep
c = pn.Column('hi')
display(c)
c.objects = ['hello']
# Show loading message
p1 = figure()
p1.text(x=[0], y=[0], text=['loading'])
c.objects = [pn.pane.Bokeh(p1)]
sleep(1)
# show final figure
p2 = figure()
p2.text(x=[0], y=[0], text=['final figure'])
c.objects = [pn.pane.Bokeh(p2)] This shows loading but I would expect it to show "final figure" ![]() |
Me too, I tried so many times and somehow I hit on the right approach this time. I think that's probably a different issue. Can you open a new issue if you get a chance? |
Sure--#7145 Thank you |
Context
Hey team, I'm back with I think perhaps the same bug as: #6019
I've managed to significantly simplify the minimum reproducible code, and I suspect that the last issue was really caused by this bug as my code was not fixed in the patch that was released to address the previous ticket. (Thank you for trying!)
I've been stuck on panel==1.3.4 because I think this race condition becomes worse starting from 1.3.5 onwards. I saw the awesome changes in 1.4.0 and would love to jump to the latest version.
ALL software version info
panel==1.4.0 (error is much less likely but still possible to reproduce with 1.3.4)
bokeh==3.4.0
Python==3.11.5
param==2.1.0
Description of expected behavior and the observed behavior
The final visible "state" should be "SUCCESS", instead it gets stuck in "LOADING". In the code below, I add some comments indicating how to increase or decrease the likelihood of the race condition appearing. It's tuned right now to fail every time.
Complete, minimal, self-contained example code that reproduces the issue
Screenshots or screencasts of the bug in action
(Not captured in the gif, it does flash to "SUCCESS" briefly

The text was updated successfully, but these errors were encountered: