App stuck in the oven when deploying

Community Cloud
11

Since we have a few different people on this thread now, let me just cover bases trying to make sure we’re all in the same spot.

My “App won’t launch” troubleshooting checklist:

  1. For anyone late to the party, there was indeed a system issue that was declared fixed only yesterday, so make sure you’ve tried rebooting your app. If you fall into the case of “it worked perfectly fine before and I didn’t change anything, but a reboot doesn’t fix it” then we may need to enlist staff to see if there are any lingering issues from this. (Alternately it could be a package upgrade, so you might verify locally if your app is breaking with the latest version of Streamlit and maybe try pinning to a previous known good version of Streamlit for your app.)

I’ll note that officially it says the “majority” should be fixed now:

Hey there :wave: @Alexandru_Toader, just looping you in since you seemed to be covering this.

Here’s the extent of my advice I can offer:

  1. Create a very simple test_app.py file with two lines:
import streamlit as st
st.write('test')
  1. Set this as the main app in your Streamlit admin console, then three dots → Reboot your app
  2. If 2 is not a success:
    • Check what your total file size is. If you have a lot of data, try to temporarily remove or trim your largest pieces to see if that is clogging it up. (Although 1GB resource limit is given, I’ve read it may at times grace you with more, so just because something worked before does not eliminate this as a possibility, just fyi.)
    • Check the terminal for any reported errors installing. Report specific errors seen with a link to your repository so we can see your setup files. If an error does not make clear which package might be causing problems, I’d recommend trimming your requirements down and adding things back in to try and locate what is not installing correctly that it can’t launch a one-line Streamlit app. Order of installation could potentially come in to play.
      - We could just be seeing more of the issues carrying over from the weekend, in which case I’ll pass off to staff.
  3. If 2 is a success:
    • This should mean the environment isn’t fundamentally corrupt and you are not starting off with too much content in the resource-limited container.
    • Check your main app for anything that could introduce a large amount of data held in memory that might be pushing it over the limit on the first run.
    • If nothing seems guilty, expand the test app to include all the imports you have within your app and use st.write to display each of their versions just to make sure each of the installed packages you are using are readable.
1 Like