Skip to content

Conversation

@raethlein
Copy link
Collaborator

@raethlein raethlein commented Jan 8, 2025

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

  • 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.

@raethlein raethlein added security-assessment-completed Security assessment has been completed for PR change:refactor PR contains code refactoring without behavior change impact:users PR changes affect end users labels Jan 8, 2025
@raethlein raethlein force-pushed the fix/issue-9921-only-emit-log branch from 3d93ba8 to 0abc3d8 Compare January 8, 2025 14:30
Copy link
Collaborator

@lukasmasuch lukasmasuch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

Copy link
Collaborator

@lukasmasuch lukasmasuch Jan 8, 2025

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?

Copy link
Collaborator

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

Copy link
Collaborator Author

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

Copy link
Collaborator Author

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.

@raethlein raethlein force-pushed the fix/issue-9921-only-emit-log branch from 0abc3d8 to 29229ed Compare January 8, 2025 15:10
@raethlein raethlein force-pushed the fix/issue-9921-only-emit-log branch from d115cff to a791c39 Compare January 8, 2025 15:19
@raethlein raethlein merged commit bf4ef5a into develop Jan 8, 2025
32 checks passed
@lukasmasuch lukasmasuch deleted the fix/issue-9921-only-emit-log branch January 8, 2025 15:55
edegp pushed a commit to edegp/streamlit that referenced this pull request Jan 19, 2025
…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.
@jonaslandsgesell
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

change:refactor PR contains code refactoring without behavior change impact:users PR changes affect end users security-assessment-completed Security assessment has been completed for PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants