Skip to content

#281 configurable max-cycles via MAX_CYCLES env var - #281

Open
VasilevNStas wants to merge 1 commit into
zerocracy:masterfrom
VasilevNStas:281-configurable-max-cycles
Open

#281 configurable max-cycles via MAX_CYCLES env var#281
VasilevNStas wants to merge 1 commit into
zerocracy:masterfrom
VasilevNStas:281-configurable-max-cycles

Conversation

@VasilevNStas

Copy link
Copy Markdown
Contributor

baza.rb currently has no way to control the max cycle count without modifying entry.sh.

Makes --max-cycles configurable via MAX_CYCLES environment variable. Falls back to 3 (current default):

./entry.sh job123 /tmp        # 3 cycles
MAX_CYCLES=10 ./entry.sh job123 /tmp  # 10 cycles

@yegor256 please review

Allow baza.rb to control the maximum number of judges update
cycles without modifying entry.sh. Falls back to 3 (current
default) when MAX_CYCLES is not set.
@VasilevNStas
VasilevNStas requested a review from yegor256 as a code owner June 29, 2026 17:25
@VasilevNStas

Copy link
Copy Markdown
Contributor Author

Why this matters

max-cycles=3 is hardcoded. This works for most judges, but some need more cycles to converge (e.g. gradual consensus-building judges) and some would benefit from fewer (e.g. expensive AI judges where you want to fail fast).

Before this PR, changing the cycle count requires forking entry.sh or patching the Docker image — both maintenance nightmares.

After this PR, baza.rb simply sets MAX_CYCLES=10 per job and the same entry.sh handles it. No forks, no patches, no image rebuilds.

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