This looks like a known issue:
The progress-checking Space appears to be failing server-side before it can actually evaluate your username, and there is already an open upstream issue (#247) tracking essentially this failure path.
So for this particular error, things like clearing the browser cache, changing browsers, or re-up your model are unlikely to help.
The immediate failure is in the public Check My Progress - Audio Course Space. Its current source tries to read the Unit 7 pass roster from huggingface-course/audio-course-u7-hands-on/usernames.csv
. That access currently fails, and because the Unit 7 check is not isolated from the rest of the startup path, the exception brings down the whole progress checker.
One small but important qualification: I would describe this as “the Space can no longer access the Unit 7 roster”, rather than assuming that the dataset was definitely deleted. Hugging Face’s RepositoryNotFoundError documentation says the same error can also occur when a repository is private and the current credentials do not have access. From outside the maintainer account, those cases are difficult to distinguish.
The good news is that the official Audio Course certification rules still say:
So if you already know that you satisfy three assignments, it is worth trying the official Audio Course Certification Space directly. The public progress checker is useful for self-evaluation, but the certification page performs its own checks.
If that certification Space also returns an error, that likely needs maintainer-side attention as well: there are already recent reports from users claiming 3/4 completion and 4/4 completion who were unable to generate a certificate. A robust fix would probably separate two things:
That second change would help even if the underlying cause turns out to be a token/permission change rather than a deleted repository.
What seems established, and what is still uncertainSo the shortest version is: your screenshot is consistent with an existing Course-side infrastructure problem rather than something you can fix locally. The most useful tracking point is audio-transformers-course issue #247, and if you already satisfy 3/4 assignments, trying the official certification Space directly is the lowest-cost next step. If that also errors, the remaining path appears to require maintainer-side inspection of the private certification/checking infrastructure.