-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
Wizard restarts on every commit on a staging server #2637
Comments
I looked into it and here are a couple of observations:
@lucasrodes you're the expert, any ideas? Has this ever happened to you? |
We can enable live reload on staging servers and do hard restart on master (where there's a likely code change). |
hi @Marigold, While editing a form on streamlit, fields are not saved in any python variable to the best of my knowledge. So if we wanted them to persist if the streamlit app is re-started, we'd need to re-think some bits of code.
I am not sure I follow on this one. What's the difference between 'live reload' and 'hard restart'? |
As far as I know, streamlit uses "live reload" by default (if you make any code change, it'll reload the app). By "hard restart" I mean restarting the app (which is done via pm2 process manager). |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Streamlit currently restarts every time something is committed to a staging server. But, if you are working on the Wizard (e.g. upgrading indicators or reviewing charts), you may lose work. Would it be possible to avoid the restart?
The text was updated successfully, but these errors were encountered: