API references seem to have been broken

[Sibasish07]

Describe the bug
The API references seem to have been broken after the release of v0.9.14.2.

Expected behavior
The links to the API references in pygsti for example: {class}pygsti.protocols.StandardGST throw a class reference target not found error

Environment:

• pyGSTi version v0.9.14.2
• python version 3.12.11
• OS Windows 11 Home 64-bit

[rileyjmurray]

Hi, @Sibasish07! Thanks for reporting. I believe this is a documentation issue and I've marked it accordingly. If it's not, can you please post a screenshot of the problem?

[coreyostrove]

Not sure if this is related at all, but fwiw I just checked readthedocs and it looks like that is broken. The latest build of the document looks to have completed successfully per the logs, so it'll take some digging to track that down.

Update: I noticed the runtime for the doc generation was shorter than usual, and found that the latest build logs was lines like this for all of the source files:

[AutoAPI] Reading files... [ 99%] /home/docs/checkouts/readthedocs.org/user_builds/pygsti/checkouts/latest/pygsti/circuits/circuitparser/init.py
WARNING: Unable to read file: /home/docs/checkouts/readthedocs.org/user_builds/pygsti/checkouts/latest/pygsti/circuits/circuitparser/slowcircuitparser.py

So something wonky is going on.

[Sibasish07]

Hey, yes indeed the docs are broken. That is what I wanted to flag as well. We have references to the pygsti documentation in the documentation of our package and getting errors building the docs as the references seem to be missing.

This is what comes up, when I try to go to Module Index