Rongsong Shen
5876716eee
repl_info_limit() now prints an explanatory note when a limit is implicitly host-scoped (is_host_based_limit() > 0 due to a percent-based value on a non-shared resource) but its own configuration doesn't show an explicit per-host scope. The real discriminator turned out to be consumers[CONSUMER_ HOST]->per_consumer, not pointer-nullity as design.md's gloss said -- build_consumer() unconditionally allocates a consumer for all four dimensions, so the struct field is never actually NULL in production. Fixed using the same field is_host_based_limit() itself already falls back to; verified via RED-phase reproduction that the literal design.md condition never fires. design.md corrected to document the real condition. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RLSNJhNoULvVcUhXEFafQC |
||
|---|---|---|
| .. | ||
| autoscaler | ||
| configs | ||
| controller | ||
| docs | ||
| frontend | ||
| harness | ||
| include | ||
| lib | ||
| nixSupport | ||
| scheduler | ||
| schema | ||
| tools | ||
| worker | ||
| xceadmin | ||
| flake.lock | ||
| flake.nix | ||
| meson.build | ||
| meson.options | ||