Backtestspydanticrun-20261002-175417#13687
populate_by_name (and implicit validate_by_name when validate_by_alias=False) is ignored by @validate_call
Better
Our patch was judged better than the merged fix.
In this judgment, Patch A = our agent, Patch B = the merged fix.
Both patches fix the populate_by_name case. Patch A makes `ConfigWrapper.validate_by_alias` and `validate_by_name` return effective values through a shared `_resolve_validate_by_alias_and_name` helper, and `core_config()` reuses that same helper. Every consumer of the config wrapper, including the arguments schemas, now sees consistent values, which addresses the root cause the issue describes. Patch B instead calls `core_config(title=None)` inside each arguments-schema builder. That also yields the patched value for both scenarios, but it rebuilds the full core config as a side computation, can re-trigger any warnings emitted in `core_config`, and leaves `config_wrapper.validate_by_name` inconsistent for other callers. On tests, Patch A covers both scenarios from the issue (`populate_by_name=True` and the worse `validate_by_alias=False` variant) for both the `arguments` and `arguments-v3` schema types and through `validate_call`, including the expected errors. Patch B tests only `populate_by_name`, does not test the `validate_by_alias=False` case, and adds unrelated churn by rewriting `dict(...)` to `{...}` in existing tests. Patch A is more complete, better tested, and cleaner in scope.
The judge saw only the two patches, labelled A and B in random order, with issue links and version numbers removed. The reasoning above is shown verbatim.
Solve
10m 7s
Wall-clock time in the container
Full test suite
No new failures
12,398 passed · 500 skipped · 12,898 total
Contamination audit
Clean
No sign the agent saw the real fix
Patch size
96vs 39 merged
Changed lines, ours vs merged