-
Notifications
You must be signed in to change notification settings - Fork 4k
Only show log but don't raise an error when fragment id is not found #10130
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
Conversation
3d93ba8 to
0abc3d8
Compare
lukasmasuch
left a comment
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.
LGTM 👍
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.
nit: can you add a comment here on what happens with the fragment request if an app runs into this? I assume the requested fragment rerun will just be ignored?
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.
Or maybe just add this info to the error message as well
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 have extended the comment above with a small preamble
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.
Oh I have just seen your second comment. Good idea, I have just updated the error message as well.
0abc3d8 to
29229ed
Compare
d115cff to
a791c39
Compare
…treamlit#10130) ## Describe your changes After the discussion in context of this PR: streamlit#9965, we want to show a log instead of raising an error in all cases to keep it simple and not introduce another list / more tech debt. ## GitHub Issue Link (if applicable) ## Testing Plan - Unit Tests (JS and/or Python) - Remove a couple of unit tests that checked for the exception to be thrown --- **Contribution License Agreement** By submitting this pull request you agree that all contributions to this project are made under the Apache 2.0 license.
|
I understand from the PR that a missing fragment is now ignored (instead of raising an error). Would it be possible to actually rerun the missing fragment if it is older than ~10 minutes? Why? When "installing" a Streamlit app from the browser (Chrome, "Add to start screen"), then fragments tend to be missing when the app is opened from the start screen after some 10 minutes after the app was first opened. |
Describe your changes
After the discussion in context of this PR: #9965, we want to show a log instead of raising an error in all cases to keep it simple and not introduce another list / more tech debt.
Changing this surfaced two race conditions that were subsequently tackled in #10132 and #10147
GitHub Issue Link (if applicable)
Testing Plan
Contribution License Agreement
By submitting this pull request you agree that all contributions to this project are made under the Apache 2.0 license.