Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
jacs-mcp/src/jacs_tools.rs:4173-4201: the test test_tools_list_matches_compiled_features asserted that core tool names were "always present" without feature gates, but the nightly CI runs it with --no-default-features --features mcp which excludes core-tools. The fix wraps each tool family's assertions with the matching #[cfg(feature = "...")] guard. Both --features mcp a
email sigs
jacs signature change
email sigs
bump versions
test cargos
fix flaky trust timestamp tests by adding serial annotation
test_timestamp_unix_epoch_valid_by_default and test_valid_old_timestamp were racing with test_old_timestamp_rejected_when_expiry_enabled which sets JACS_MAX_SIGNATURE_AGE_SECONDS env var, causing spurious failures.