# Please fix SDXL space not loading
**URL:**
**Author:**  [@RussellGibbon](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FRussellGibbon)%5C
**Post date:** [November 24, 2025, 5:36pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fplease-fix-sdxl-space-not-loading%2F170806%2F1 "2025-11-24T17:36:36Z")
Hello at Hugging Face.
Today I have tried to access:
- Space URL: [Stable Diffusion XL on TPUv5e - a Hugging Face Space by google](https://huggingface.co/spaces/google/sdxl)
- My Hugging Face username: Russell Gibbon
- Browser: Firefox on Windows 10
Here is the error message . . .
runtime error
Exit code: 1. Reason: Traceback (most recent call last): File “/home/user/app/app.py”, line 81, in word\_list\_dataset = load\_dataset(“google/word-list-sd”, data\_files=“list.txt”) File “/usr/local/lib/python3.10/site-packages/datasets/load.py”, line 1392, in load\_dataset builder\_instance = load\_dataset\_builder( File “/usr/local/lib/python3.10/site-packages/datasets/load.py”, line 1132, in load\_dataset\_builder dataset\_module = dataset\_module\_factory( File “/usr/local/lib/python3.10/site-packages/datasets/load.py”, line 1025, in dataset\_module\_factory raise e1 from None File “/usr/local/lib/python3.10/site-packages/datasets/load.py”, line 980, in dataset\_module\_factory raise DatasetNotFoundError(f"Dataset ‘{path}’ doesn’t exist on the Hub or cannot be accessed.") from e datasets.exceptions.DatasetNotFoundError: Dataset ‘google/word-list-sd’ doesn’t exist on the Hub or cannot be accessed.
Container logs:
Failed to retrieve error logs: SSE is not enabled
Please can you fix this.
Thank you
Russell Gibbon
---
**Author:**  [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [November 24, 2025, 8:41pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fplease-fix-sdxl-space-not-loading%2F170806%2F2 "2025-11-24T20:41:22Z")
This error indicates that the `google/word-list-sd` dataset repository does not exist. If it genuinely does not exist, you must either prepare an equivalent dataset repository separately or remove the code sections that use this dataset. (From the user’s perspective, it truly does not exist. It could be that it’s set to Private, and the environment variable `HUGGING_FACE_HUB_TOKEN` contains invalid content, preventing access to the Private repository…)
Anyway, Space won’t start unless this is fixed, but I can’t handle it alone. Action by someone at Google or Hugging Face staff is essential. (Contact Hugging Face via [website@huggingface.co](mailto:website@huggingface.co) / Google via [https://huggingface.co/spaces/google/sdxl/discussions](https://huggingface.co/spaces/google/sdxl/discussions))
Also, separately, since the Gradio version is outdated, it’s best to add `pydantic==2.10.6` to `requirements.txt` as a workaround for bugs.
---
**Author:**  [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [November 24, 2025, 8:47pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fplease-fix-sdxl-space-not-loading%2F170806%2F3 "2025-11-24T20:47:37Z")
BTW, [another suspected cause was the inability to load specific dataset reports due to this specification change](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fdataset-scripts-are-no-longer-supported%2F163891%2F2)%2C but based on the error details, I determined it was unrelated this time.
---
**Author:**  [@RussellGibbon](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FRussellGibbon)%5C
**Post date:** [November 24, 2025, 9:02pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fplease-fix-sdxl-space-not-loading%2F170806%2F4 "2025-11-24T21:02:11Z")
Thank you John.
I am not a coder. So “pydantic” database repository etc. it is all Swahili to me.
I have been using this SDXL space almost daily for over the last year. Always, it has loaded perfectly and I have been able to experiment making artistic images with it.
This is the first time that it has done this. I have no clue what to do / how to fix it . . . hence my post.
Thanks for trying to make sense of it.
Fingers crossed that someone who knows what they are doing sees it and does the necessary.
Regards
Russell Gibbon