{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiefp3in2gxuwoyqj4ofql3g6hwt4foruaog74mlr3txvlr4c7vmzq",
    "uri": "at://did:plc:pgryn3ephfd2xgft23qokfzt/app.bsky.feed.post/3mh6kgw6kkxp2"
  },
  "path": "/t/python-gradio-space-stuck-in-restarting/173928#post_6",
  "publishedAt": "2026-03-16T11:03:30.000Z",
  "site": "https://discuss.huggingface.co",
  "textContent": "Another of my Python Gradio spaces is now stuck in restarting for four days now despite forcing restart, factory rebuilding, juggling Gradio SDK version back and forth. It stopped originally due to no change of mine whatsoever. I’m running a gradio client program on a raspberry pi at home that pings this space via the API every two hours and it just stopped connecting, and space would not restart.\n\nI’m using only 4 zero cpu spaces if that matters.\n\nThe builds appear to succeed,; image is pushed, and container goes into restarting with this message in the log:\n\n===== Application Startup at 2026-03-16 09:44:20 =====\n\nAt this point I guess all I can do is kill this space and create a new one for the app. (??)",
  "title": "Python Gradio Space stuck in \"restarting\""
}