That issue has nothing to do with this problem, it seems.
I’ve found that when debugging with VSCode that any navigation away from the page when still processing the python script produces an exception, specifically a StopException.
I’ve tried catching this globally, and maybe I’m just a python noob, but I can’t find the actual type to catch, and so my exception block can’t distinguish between the StopException and something I actually care about, so I can’t tell the VSCode debugger to only break on uncaught exceptions.
I observed the same, it would be great to know how to avoid that. It’s becoming increasingly difficult to debug with VS Code. (Same happens also Streamlit 3.15)
Thanks for stopping by! We use cookies to help us understand how you interact with our website.
By clicking “Accept all”, you consent to our use of cookies. For more information, please see our privacy policy.
Cookie settings
Strictly necessary cookies
These cookies are necessary for the website to function and cannot be switched off. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms.
Performance cookies
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us understand how visitors move around the site and which pages are most frequently visited.
Functional cookies
These cookies are used to record your choices and settings, maintain your preferences over time and recognize you when you return to our website. These cookies help us to personalize our content for you and remember your preferences.
Targeting cookies
These cookies may be deployed to our site by our advertising partners to build a profile of your interest and provide you with content that is relevant to you, including showing you relevant ads on other websites.