Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error Querying userReserve {id} Field in Protocol V3 Mainnet Subgraph #145

Open
Natkamon opened this issue Dec 25, 2024 · 0 comments
Open

Comments

@Natkamon
Copy link

Describe the bug
When querying historical supply data for the "Protocol V3 Mainnet" subgraph, an error occurs related to the userReserve {id} field on the supplies query. This prevents the query from successfully returning data.

To Reproduce
Query

{
  supplies(first: 1000, skip: 0, orderBy: timestamp, where: {timestamp_gte: 1700611200, timestamp_lt: 1700697600}) {
    id,
    txHash,
    action,
    timestamp,
    pool { id },
    user { id },
    caller { id },
    reserve { id, underlyingAsset, symbol, name },
    userReserve { id },
    referrer { id },
    amount,
    assetPriceUSD
  }
}

Response

{
  "data": null,
  "errors": [
    {
      "message": "Null value resolved for non-null field `userReserve`",
      "locations": [{"line": 22, "column": 3}]
    }
  ]
}

Expected behavior
The query should return a list of data without encountering errors, even if the userReserve {id} field is null or missing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant