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
Is your feature request related to a problem? Please describe.
Currently, a message containing SQL statements is sent to an SQS queue so long as parsing the ABI does not fail. However, there is a large amount of ABIs that produce no SQL statements to be run. These should be filtered out and not sent to the queue for further processing as there is no further processing needed.
Describe the solution you'd like
Implement a step to filter these out and prevent them from being sent to the SQS queue.
Describe alternatives you've considered
N/A
Additional context
Should also investigate if getting 0 statements is valid to begin with. Does the contract not implement any methods/events or is this actually a bug?
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently, a message containing SQL statements is sent to an SQS queue so long as parsing the ABI does not fail. However, there is a large amount of ABIs that produce no SQL statements to be run. These should be filtered out and not sent to the queue for further processing as there is no further processing needed.
Describe the solution you'd like
Implement a step to filter these out and prevent them from being sent to the SQS queue.
Describe alternatives you've considered
N/A
Additional context
Should also investigate if getting 0 statements is valid to begin with. Does the contract not implement any methods/events or is this actually a bug?
The text was updated successfully, but these errors were encountered: