search

tom-doerr / dalle_flow_streamlit

MIT License
28 stars 8 forks source link

Image variations cause runs to fail #5

Open asukii314 opened 2 years ago

asukii314 commented 2 years ago

Hey there,

I was using the streamlit app fine last night with no issues, but every time I click the Variations button for an image today, it causes the run to fail. (I'm still able to generate the original set of images & upscale one of them, as long as I don't try to generate any variations in between.)

After clicking for variations, the page whites out after a few seconds, displaying just the title ("Image Variations") with a blank white page below & no left-hand sidebar. (Yesterday, I believe it showed the previous round's images at reduced opacity until the new round of images was ready.) I've tried leaving the page as-is for well over 20 minutes in case it was a timing issue, but no luck - seems to stay that way indefinitely.

In case it's related, I noticed periodic network requests from the devtools console, where GET https://share.streamlit.io/api/v1/user would reliably return {"error":"The user is not authenticated"} with status 200. Calls to the status API would consistently return {"status":5,"creatorId":"1V1RA9V2HBR5XREAAJ6MHTMKMSW5RHUAZXF5P7QKCE7YO06FIL","platformStatus":1,"viewerAuthEnabled":false,"streamlitVersion":"1.9.2"}. There were also some calls to datadog, but I assume you're in better shape to monitor those analytics from your end anyway.

Thanks for the tool, by the way! Fantastic resource - here's hoping this is a quick fix. Let me know if there's any other info that would be helpful for me to provide.

asukii314 commented 2 years ago

For a bit more info - might be a red herring, but the whiteout seems to correspond (timing-wise) with a pair of API calls to POST https://api.segment.io/v1/t

tom-doerr commented 2 years ago

There were changes in the backend today, the server was scaled up and there was a huge amount of traffic. I hope it sorts itself out.

asukii314 commented 2 years ago

Still seeing the same issue now (after the restart earlier), for what it's worth...

asukii314 commented 2 years ago

FYI, seems to be resolved now - at least on my end! <3