thegraph doesn't work for most of the supported networks

[Piliponful]

Describe the bug
URL https://api.studio.thegraph.com/query/14377/semaphore-/v4.5.0 only works for a few networks, namely sepolia, arbitrum-sepolia, scroll-sepolia, gnosis-chiado, gnosis. For all other networks it doesn't work and returns {"message":"Not found"}

Also stemming from that the getGroup function in data package can't properly handle this error and to any client using @semaphore-protocol/data it shows up as runtime(second attached screenshot) and not a proper formated error(Blockchain voting error: TypeError: Cannot read properties of undefined (reading 'groups')).

To Reproduce
Steps to reproduce the behavior:

1. Go to https://api.studio.thegraph.com/query/14377/semaphore-base/v4.5.0/graphql
2. It shows {"message":"Not found"}

Expected behavior
It should open thegraph console where you can enter your graphql query, which would mean the url is valid and working properly. Example of working URL - https://api.studio.thegraph.com/query/14377/semaphore-sepolia/v4.5.0/

Screenshots

[vplasencia]

Hey @Piliponful! The Semaphore subgraph is deployed on multiple networks, but it's only active on a few of them. The others are archived in Subgraph Studio, which doesn't allow all subgraphs to be active simultaneously.

Do you need it active on a specific network? I can unarchive it there.

[vplasencia]

You could also deploy your own subgraph on a specific network and use your URL,

You can follow these steps to deploy your own Semaphore subgraph: https://github.com/semaphore-protocol/semaphore/tree/main/apps/subgraph#deployment

[Piliponful]

Got you. That makes sense. It would be good to mention in readme of data package, would make it clearer for someone like next time. And even better to make a descriptive error when someone tries to use archived network. I can do a PR for that case in coming days.

[Piliponful]

Don't unarchive it just for me because I already use my own subgraph, but thank you!

[vplasencia]

I can do a PR for that case in coming days.

It would be great! Thank you very much!

[LazyDreamingDog]

So the current situation is that the subgraph integrated in version v4.5.0 does not support the Amoy testnet, while the previous v4.2.0 is no longer usable (I tried using the previously integrated code to access matic-amoy but it failed). Additionally, I have a question — I'm not familiar with The Graph: if I want to integrate queries for a group entity (for example, a get_group query) into a Rust project, how should I get started?

[vplasencia]

Hey @LazyDreamingDog! Here is the reason why there are only a few working: #1053 (comment)

Please let us know if you would like to use Amoy so we can unarchive it.

You can query the subgraphs using a GraphQL query. You could do it like a regular POST request. You can also use Rust to generate the query. This TS implementation can help: https://github.com/semaphore-protocol/semaphore/blob/main/packages/data/src/subgraph.ts#L111