Analytics query fails and crashes indexer

[n1tranquilla]

Query:

query InternalCommands($limit: Int, $sort_by: FeetransferSortByInput!, $query: FeetransferQueryInput!) {
  feetransfers(limit: $limit, sortBy: $sort_by, query: $query) {
    fee
    blockHeight
  }
}

Variables:

{
  "limit": 10000000,
  "sort_by": "BLOCKHEIGHT_DESC",
  "query": {
    "canonical": true,
    "blockHeight_gte": 358604,
    "blockHeight_lte": 359604
  }
}

[Isaac-DeFrain]

I’ll look into this

On Sat, Oct 12, 2024 at 12:19 PM Nathan Tranquilla @.***> wrote:

Query:

query InternalCommands($limit: Int, $sort_by: FeetransferSortByInput!, $query: FeetransferQueryInput!) { feetransfers(limit: $limit, sortBy: $sort_by, query: $query) { fee blockHeight } }

Variables:

{ "limit": 10000000, "sort_by": "BLOCKHEIGHT_DESC", "query": { "canonical": true, "blockHeight_gte": 358604, "blockHeight_lte": 359604 } }

— Reply to this email directly, view it on GitHub https://github.com/Granola-Team/mina-indexer/issues/1623, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKBBZUFCVSMLN5A3EFVIYZTZ3FY3XAVCNFSM6AAAAABP2VP6U2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGU4DGMZUGY2DSMY . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[n1tranquilla]

The limit is too high. I didn't think it mattered. But I think we should bound the limit based on the two heights, if they are both supplied.

[n1tranquilla]

I'll work around this issue in the front end by lowering the limit.

[n1tranquilla]

This is still an issue.