User reported query issues about public clusters

[ShookLyngs]

Reports

A user reported some issues when using the spore-demo:

1. New generated public clusters cannot be found in the "my space" page.
2. The "mintable clusters" selector in the "mint spore" modal is always empty.

All these issues are highly likely caused by the spore-graphql, so I'm opening an issue in here.

Locating issues

issue#1

I think the issue#1 is because when querying, the passed address doesn't match the public cluster's address.
This issue needs more attention, reated code is located here:
https://github.com/sporeprotocol/spore-graphql/blob/master/lib/src/data-sources/clusters.ts#L43-L50

issue#2

The issue#2 is cause by a graphql failure when "mintableBy" param is passed, which throws:

{
  "message": "Invalid buffer length: 0, should be 1",
  "locations": [
    {
      "line": 2,
      "column": 3
    }
  ],
  "path": [
    "clusters"
  ],
  "extensions": {
    "code": "INTERNAL_SERVER_ERROR"
  }
}

Related code is located here:
https://github.com/sporeprotocol/spore-graphql/blob/master/lib/src/utils.ts#L58

[ashuralyk]

is there a better and efficient method to check them out?

can you get these parameters while using spore-graphql, so I can debug with them @ShookLyngs

[ShookLyngs]

is there a better and efficient method to check them out?

can you get these parameters while using spore-graphql, so I can debug with them @ShookLyngs

My method was to test them in the spore-demo and check each of those graphql requests.
You can also try to console.log them while testing in the local environment with vitest.