Repository navigation
fix: pin Dash to avoid renderer regression - #185
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Details
Issue #183 was reproduced with Dash 4.2.0 and 4.4.1, where the browser renderer can saturate one CPU core and become unresponsive.
A diagnostic build with Dash 4.0.0 did not reproduce the problem. Upstream source changes place the relevant behavior change between Dash 4.1.0 and 4.2.0.
Dash 4.1.0 is pinned until an upstream release containing the renderer fix is available and verified.
Testing
pytest— 814 passed, 6 skippedruff check .