Serverless Inference API error on new model
When I tested the Serverless Inference API with my new model, I encountered the following error:{'error': "We couldn't connect to 'https://huggingface.co' to load this file, couldn't find it in the cached files and it looks like Saripudin/autotrain-model-datasaur-ZDAzZTc5NmI-NGJmYmVlOWU is not the path to a directory containing a file named config.json.\nCheckout your internet connection or see how to run the library in offline mode at 'https://huggingface.co/docs/transformers/installation#offline-mode'."}Does this mean that Hugging Face has now limited their Serverless API usage?
2024-09-07T09:33:53Z
Currently, HF’s Serverless Inference API is in the midst of a specification change and a massive error coming at the same time.One of the errors has been fixed.Inference API turned off ? Why?Site FeedbackWhay the inference API are turned off ?huggingface.co@John6666 on Hugging Face: "@victor Sorry for the repetitiveness.

I'm not...We’re on a journey to advance and democratize artificial intelligence through open source and open science.huggingface.co@victor on Hugging Face: "🙋 Calling all Hugging Face users! We want to hear...We’re on a journey to advance and democratize artificial intelligence through open source and open science.
2024-09-07T13:47:05Z
Thank you@John6666I’ve tested it and it has been worked normally
2024-09-09T10:37:16Z
I have seen the same errors. Has it been fixed for you?
2024-09-09T10:45:52Z
When I tested in 2 days ago, it was working normally. But it turns out It happen error again now…
2024-09-09T10:48:29Z
There were generally three problems that occurred with HF this time, limited to the image generation AI,Errors that prevented the use of the Serverless Inference API, regardless of the client (can be fixed manually by following the instructions below, and new occurrences are almost never seen).An error that caused very strange server-side responses on some Gradio 3.x systems (still ongoing, no workaround, but spaces that have not been restarted after the problem are safe).Multiple fatal errors in Zero GPU space (the biggest one was fixed a few days ago but still remains)WorkaroundSetting fastapi==0.112.2 in requirements has helped me as a temporary fix.We just releasedgradio==4.43with the same fix. So new Gradio Spaces should work fine now (older ones will need to update thesdk_versionin theREADME.mdfile)Workaround in Zero GPU SpaceLong shit report by me.huggingface.cozero-gpu-explorers/README · About the phenomenon of eternal stacks when...The following glitch occurs when a @spaces.GPU decorator is attached to a function (method) that is not called directly from app.py . If a function with decorators is called directly, it works. How...