-
Notifications
You must be signed in to change notification settings - Fork 33
Requests do not reliably execute on page load #24
Comments
Just checked on |
Hm.. I'm not sure what could be going on here. Could you create a reproducable example? I'll prioritize the fix once we can reliably reproduce. |
(even if the reproducible example has like 50 inputs, it will still be helpful) |
Looks like it was caused by this logic path: Dropdown (with no default) -> pathname -> other components. Still not sure why the behavior changed between On another note, I am able to get an unreliable example with anywhere between 20 and 50 inputs, but it only shows up sometimes. I have not been able to make a reliable example. For example, on one server run, the 2nd and 5th components of 30 may not update, and when restarting the server, they may all update. Seems like that may just be more of a server performance issue. Probably reasonable to just close this. |
@mjclawar - I'll close this for now, but if you continue seeing it and can reproduce it, please re-open! Thanks :) |
Hey @chriddyp! So we're having a new issue with
dash-renderer==0.11.0
that was not on older versions. I think this is related to plotly/dash#133 and #22.We are trying to render something like 40 components on page load. However, only about 20 of them actually even make a request on page load for data.
Logic with
0.8.0
pathname
.pathname
isNone
, we throw aValueError
, and the request to /_dash-update-component returns a 500.pathname
then updates to/my/new/url/10
, and requests to /_dash-update-component return the correct data based on the url.This is good enough and works, although leaves an "Updating" in the browser title.
Logic with
0.11.0
pathname
pathname
isNone
, we throw aValueError
, and the first request to /_dash-update-component returns a 500. We noted that the first request is always the same, and always returns a 500.pathname
then updates to/my/new/url/10
, and about 20 requests to /_dash-update-component return the correct data based on the url. We noted that these are always the same requests and always return the correct data.dash-renderer
thinks that all requests completed successfully.Notes
If useful, I can try and make a dummy example of this. It does, however, based on previous issues and the change made for
0.11.0
seem to be related to the event scheduler (and the dummy example may have to be quite large to mimic this issue).For now, we have to stay on older versions of
dash-renderer
since the behavior in0.11.0
is not desirable.The text was updated successfully, but these errors were encountered: