Skip to content

Comments

Support incremental executionId in runInLoop#227

Merged
matejfalat merged 2 commits intomainfrom
incremental-run-in-loop-execution-id
Feb 20, 2026
Merged

Support incremental executionId in runInLoop#227
matejfalat merged 2 commits intomainfrom
incremental-run-in-loop-execution-id

Conversation

@matejfalat
Copy link
Contributor

Related https://github.com/api3dao/oev-searcher/issues/2663

This PR adds support for incremental executionIds with a custom prefix.

@matejfalat matejfalat requested a review from Siegrift February 19, 2026 16:51
Copy link
Collaborator

@Siegrift Siegrift left a comment

Choose a reason for hiding this comment

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

LGTM with minor comments

/**
* Optional prefix prepended to the incrementing number (e.g. "my-prefix-0").
*/
prefix?: string;
Copy link
Collaborator

Choose a reason for hiding this comment

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

I was thinking we could have also added a start counter. E.g. you want to start from the current timestamp, but then realized you could just specify it as a prefix and also add a separator, e.g. 1771580212- which would make logs more readable.

Copy link
Contributor Author

@matejfalat matejfalat Feb 20, 2026

Choose a reason for hiding this comment

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

Hmm, I mean it's trivial to add start option as well, but I can't really see a use case for it (as you noted, block numbers/timestamps are better in the prefix) 🤷

@matejfalat matejfalat merged commit 1d5a714 into main Feb 20, 2026
5 checks passed
@matejfalat matejfalat deleted the incremental-run-in-loop-execution-id branch February 20, 2026 11:49
@matejfalat matejfalat mentioned this pull request Feb 20, 2026
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