Skip to content

Conversation

guidiaz
Copy link
Contributor

@guidiaz guidiaz commented Oct 20, 2025

No description provided.

reverse: options?.reverse
limit: options?.limit || 1,
offset: options?.offset || 0,
reverse: options?.reverse || true
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we use reverse = false, then false || true is always true so reverse can't never be false. We have to check if it's false instead of undefined


promisePoller({
taskFn: () => this.provider.getTransaction(hash),
taskFn: () => this.provider.getTransaction(hash).catch(err => err),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the expected behavior here? if we use .catch(e=>e) we will always return a value instead of handling the error. Example here

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Apparently, promisePoller is not catching eventual exceptions when executing taskFn(), so instead of passing the Exception as an error value to shouldContinue, it was bubbling up the exception and therefore unexpectedly exiting from the "confirmTransaction" workflow.

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

Successfully merging this pull request may close these issues.

2 participants