Skip to content

fix(tests): merge code_execution category and sync hardcoded config version#12139

Closed
Julientalbot wants to merge 1 commit into
NousResearch:mainfrom
Julientalbot:fix/ci-config-version-and-code-exec-category
Closed

fix(tests): merge code_execution category and sync hardcoded config version#12139
Julientalbot wants to merge 1 commit into
NousResearch:mainfrom
Julientalbot:fix/ci-config-version-and-code-exec-category

Conversation

@Julientalbot

Copy link
Copy Markdown
Contributor

Summary

Two CI regressions are currently breaking every open PR against main:

1. test_no_single_field_categoriescode_execution single-field

hermes_cli/config.py:775 introduces a code_execution category with a single field (mode), violating count >= 2 in tests/hermes_cli/test_web_server.py:369.

Fix: route code_execution through the existing _CATEGORY_MERGE map into terminal (semantic fit: both deal with shell/exec surface).

2. test_config_version_matches_current_schema — stale assertion

_config_version was bumped to 19 in hermes_cli/config.py:805 but tests/tools/test_browser_camofox_state.py:67 still asserts == 18.

Fix: sync the expectation to 19.

Scope

Intentionally minimal — two assertions, no behavior change, no refactor. Unblocks every PR currently failing CI with these two specific errors (including #12120 where this was spotted).

Test plan

  • CI green on this PR
  • Re-run CI on PRs that were stuck on these two tests

…ersion

Two CI regressions currently break every open PR against main:

1. `test_no_single_field_categories` — the `code_execution` category in
   `hermes_cli/config.py` has a single field (`mode`), which violates
   the assertion that all categories must expose at least two fields
   after merging. Route `code_execution` through the existing
   `_CATEGORY_MERGE` map into `terminal` (semantic fit: both deal with
   shell/exec surface).

2. `test_config_version_matches_current_schema` — `_config_version` was
   bumped to 19 in `hermes_cli/config.py` but the assertion in
   `tests/tools/test_browser_camofox_state.py` still hardcodes 18.
   Sync the expectation.

Scope is intentionally limited to the two failing assertions. No
behavior change, no functional refactor.
@Julientalbot

Copy link
Copy Markdown
Contributor Author

Closing — not worth carrying a stale 2-line test fix. Filing away.

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