I am getting the following message when attempting to login to a streamlit site and was wondering if this is a problem on my side (my computer) or the site. I have logged in many times with no problems up to now.
Your app is having trouble loading the streamlit_option_menu.option_menu component.
(The app is attempting to load the component from ****, and hasn’t received its "streamlit
" message.)
If this is a development build, have you started the dev server?
If this is a release build, have you compiled the frontend?
I’m having the same issue but with the aggrid component. I run my app through docker containers deployed on a k8s server and all I have a simple script that simply runs streamlit run <filename>.
I noticed in this streamlit tutorial that they download the streamlit component, npm install & stuff (i don’t know front end stuff ), and then hook up their component to a local npm server?
Is that workflow good for production as welll? I.e. can I start the npm server in my docker container and point the component to it to prevent this issue?
I’m not sure you’re on the right track. If you only want to use the streamlit-aggrid component, you don’t need npm stuff. The mentioned tutorial is about developing your own streamlit component.
Yeah I can use the streamlit-aggrid component just fine without the npm stuff, but it keeps giving me the
Your app is having trouble loading the st_aggrtid.agGrid component.
Based on threads that I’ve read, i think this is because it takes too long to load the agGrid component and streamlit throws the warning (that eventually goes away). This warning happens consistently for some of our users which isn’t a great user experience. If I understand how streamlit components work (that’s a big if ), they’re displayed as IFRAMEs which fetch the HTML from a URL on some web server. What I don’t understand is where that web server lives and why it’s taking so long to fetch.
I was hoping that by connecting agGrid to a local instance of the web server (npm?) within the same docker container it could cut down on latency and not cause a time out.
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.