You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to index the settle function call handler for being able to decode the AppData.
I faced some issues trying to index that function. I arrived to an error reported 3 years ago.
The error is because of a multidimensional array that is not currently supported by The Graph. We have a parameter that is tuple[][3] that is not supported.
That error prevents the contract of being indexed, because of an error when graph codegen statement is executed. I read the workaround for that and seems to be replacing that tuple multi array and left only a single dimension of it such as: tuple[]
That works and allow us to keep working on the subgraph and indexing the events.
When back to index the settle function call there's no error but nothing was indexed.
I isolate the issue and redeployed for being able to share the error with E&N people.
Krishnanand V P from E&N replied on slack a workaround for being able to index the first part of the parameters until they provide a final solution they're working on.
What he suggested is to change from tuple[][3] to bytes[3] that will index that function call.
The text was updated successfully, but these errors were encountered:
We need to index the settle function call handler for being able to decode the AppData.
I faced some issues trying to index that function. I arrived to an error reported 3 years ago.
The error is because of a multidimensional array that is not currently supported by The Graph. We have a parameter that is
tuple[][3]
that is not supported.That error prevents the contract of being indexed, because of an error when
graph codegen
statement is executed. I read the workaround for that and seems to be replacing that tuple multi array and left only a single dimension of it such as:tuple[]
That works and allow us to keep working on the subgraph and indexing the events.
When back to index the settle function call there's no error but nothing was indexed.
I isolate the issue and redeployed for being able to share the error with E&N people.
Krishnanand V P from E&N replied on slack a workaround for being able to index the first part of the parameters until they provide a final solution they're working on.
What he suggested is to change from
tuple[][3]
tobytes[3]
that will index that function call.The text was updated successfully, but these errors were encountered: