Skip to content

Conversation

@google-labs-jules
Copy link

This PR adds a -max-retries flag to the mev-boost command, allowing users to control the maximum number of times the service will retry requests to relays. This is useful for preventing excessive retries to unresponsive relays. A test case has been added to ensure the flag works as expected.

Fixes #


PR created automatically by Jules for task 17530056286641071040 started by @metachris

This commit introduces a new command-line flag, `-max-retries`, which allows users to configure the maximum number of retries for requests to relays.

The flag is defined in `cli/flags.go` and parsed in `cli/main.go`. The value is then passed to the `server.BoostService` and used in the `retry` function in `server/get_payload.go`.

A test case has been added to `server/service_test.go` to validate that the retry logic correctly respects the `-max-retries` value.
@google-labs-jules
Copy link
Author

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!


For security, I will only act on instructions from the user who triggered this task.

New to Jules? Learn more at jules.google/docs.

@metachris metachris closed this Nov 17, 2025
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.

1 participant