Skip to content

Fix CI#197

Merged
str4d merged 1 commit into
mainfrom
fix-lints
Aug 20, 2025
Merged

Fix CI#197
str4d merged 1 commit into
mainfrom
fix-lints

Conversation

@oxarbitrage
Copy link
Copy Markdown
Contributor

@oxarbitrage oxarbitrage commented Aug 19, 2025

I think it would be beneficial for external reviewers and contributors if the CI passed, even at the cost of temporarily reducing coverage. Coverage can be restored once the necessary conditions are met again. Right now, it’s difficult to tell whether a PR is introducing new lints, since the failing checks are effectively ignored.

@oxarbitrage oxarbitrage marked this pull request as ready for review August 19, 2025 14:49
Copy link
Copy Markdown
Collaborator

@str4d str4d left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed 3a6d0cb. I'm ACK on the lint silencing, and NACK on the CI change.

}

#[allow(dead_code)]
pub(crate) async fn encrypt_and_store_legacy_seed(
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I NACKed this change in #109 because at the time I thought that what is now #152 would be merged shortly, meaning that this change (and the other it proposed) was creating unnecessary work. Ironically we are now in a position where #152 is likely to be merged shortly, but I'm now less averse to this change as long as we do indeed remember to do the additional work to revert it once #152 merges.

Comment thread .github/workflows/ci.yml Outdated
os: ubuntu-latest
rustflags: '--cfg zcash_unstable="nu7"'
# TODO: Enable NU7 tests when zebra-chain used revision supports it.
#rustflags: '--cfg zcash_unstable="nu7"'
Copy link
Copy Markdown
Collaborator

@str4d str4d Aug 19, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change I disagree with. It is entirely expected that these test cases be allowed to fail and the PR can still be merged; that is why the required-checks job doesn't check this one. It would be no different if macOS or Windows builds started failing; we would permit PRs that break Zallet on those platforms to be merged because they are not (currently) target platforms.

The current test failure is actually a Zebra bug: Zebra should be using #[cfg(zcash_unstable="nu7")] annotations on NU7-specific code instead of commenting them out.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense, thanks. Deferred the feature issue to Zebra. ZcashFoundation/zebra#9811

Copy link
Copy Markdown
Collaborator

@str4d str4d left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK 1602d6c

@str4d str4d merged commit a281d7d into main Aug 20, 2025
19 of 20 checks passed
@str4d str4d deleted the fix-lints branch August 20, 2025 12:13
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.

2 participants