-
-
Notifications
You must be signed in to change notification settings - Fork 143
Conversation
1.55.1 just came out |
@@ -70,7 +70,7 @@ def display_page(pathname): | |||
time.sleep(2) | |||
|
|||
# callback is called twice when defined | |||
self.assertEqual(call_count.value, 2) | |||
self.assertEqual(call_count.value, 1) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What happened here? Is this related to plotly/dash#1385 ? We should fix the comments on these two changed lines once this is understood. Any chance this means plotly/dash#883 or plotly/dash#1049 has incidentally been resolved?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@alexcjohnson Yes. This is caused by plotly/dash#1385.
- The initial callback gets added to the list of requested callbacks
- Before
await wait(0);
resolves thedcc.Location
component renders and triggers asetProps
because its props are not populated / misaligned with the current url (before, the callback would have been executing before the component rendered) - An additional callback is added to the list of requested callbacks
await wait(0);
resolves- There are now two callbacks for
test-url.pathname
and the oldest one gets pruned
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm still seeing plotly/dash#1049 running what I think is the latest version of everything. Is it supposed to be resolved as of this merge?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The boundaries of the problem have changed a little, as evidenced by this test, but it’s definitely not fixed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💃 once the test changes (unrelated to the plotly.js upgrade) are understood and the comments fixed.
No description provided.