Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error when querying events via http

See original GitHub issue

I’m trying to upgrade and switch my fcl config from grpc to http. I’m upgrading from 0.0.79-alpha.3 to 1.0.0-alpha.0. I’m getting an error when I query events on testnet. It was working before the upgrade. Creating this issue at request of Justin.

Request

const result = await fcl.send([
	fcl.getEventsAtBlockHeightRange("A.f3e8f8ae2e9e2fec.ToddTestnet1_NFT.Deposit", 66002791, 66002890),
]);

Error

TypeError: r.forEach is not a function
    at X (/Users/gta/giglabs/portal-api/node_modules/@onflow/transport-http/dist/sdk-send-http.js:1:39489)
    at /Users/gta/giglabs/portal-api/node_modules/@onflow/transport-http/dist/sdk-send-http.js:1:39372
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async processNftDepositEvents (/Users/gta/giglabs/portal-api/built/src/services/events.js:101:24)
    at async checkEvents (/Users/gta/giglabs/portal-api/built/src/services/events.js:90:13)
    at async Timeout.processEvents [as _onTimeout] (/Users/gta/giglabs/portal-api/built/src/services/events.js:34:17)

Config

await fcl
 .config()
 .put("accessNode.api", "https://rest-testnet.onflow.org/")
     .put("decoder.Type", (val: any) => val.staticType);

Issue Analytics

State:
Created a year ago
Comments:13 (5 by maintainers)

Top GitHub Comments

1reaction

vishalchangranicommented, May 10, 2022

The PR has now been merged to master. The change will be deployed to testnet/mainnet on the next testnet/mainnet spork which is on June 8th and 15th respectively. Lemme know if this changes is needed on testnet/mainnet before that and I can port over the change to the current testnet/mainnet.

1reaction

vishalchangranicommented, May 10, 2022

https://github.com/onflow/flow-go/pull/2379 - PR against flow-go master which fixes this issue and makes the REST API consistent with the gRPC API in terms of the maximum block height range.