-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
[BUG] Callback will not render new data until a delay is introduced #2763
Comments
@iamzoltan Can you provide code to reproduce the problem. |
@CNFeffery Do you mean for the unchanging callback? |
@iamzoltan the entire app - ideally simplified to the smallest example that recreates the problem. In order to investigate this bug someone else will need to be able to run code that shows the problem. |
@alexcjohnson I see, I will have to check on that. If there anything I can run to provide you with more information? |
This sounds like a very deep issue - a race condition or some such... which means it's very hard to guess where the root cause lies so debugging really needs a live environment and access to modify the source code. All that to say extra information that's NOT a runnable example is unlikely to be helpful, I'm afraid. |
Alright, I will see if I can send you the code base with some fake data. |
Closing for now as we can't tackle this without a reproducible example (reprex) - if you're able to provide one, please re-open. |
Context
Plotly, gunicorn, nginx, redis cache
Description
I have roughly 15 graphs that use the same signal as input. All of them update as expected, except for one. This one will not update regularly, but will occasionally update. I checked all the data coming into the callback from the cache, and everything is changing as expected, but the graph still does not update. I then decided to try adding a small delay in the callback, after the data was loaded, and that seemed to fix the issue. I know this is not the best solution, but I can't seem to figure out any other way. I even tried to force the frontend to update.
Expected behavior
I expected that the graph would update and render the new data that is coming in.
Any wisdom or advice on the matter is much appreciated.
Thanks for you time!
The text was updated successfully, but these errors were encountered: