You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a tracking issue to note that any updates of the curve library fork to upstream version 4.1.2 or later will break on the current nightly toolchain.
The current version of the curve library used for the fork breaks nightly CI starting with the nightly-2024-02-05 toolchain. A recent upstream PR fixes this, but is not backwards compatible.
This means that if the curve library fork is ever updated to include the fix, it will break this repository's nightly CI. The ecosystem's repositories will need to move to stable or at least nightly-2024-02-05 if this happens.
The text was updated successfully, but these errors were encountered:
Description
---
Updates `tari-crypto` and associated dependencies. Bumps the nightly
toolchain. Fixes lints. Removes unused code.
Closes#6138.
Motivation and Context
---
Updates to `tari-crypto` and related dependencies allow for a return to
the upstream curve library. This also requires bumping the nightly
toolchain, which brings fun new lints that need to be fixed. This PR
addresses all of these, and removes unused code.
How Has This Been Tested?
---
Existing tests pass.
What process can a PR reviewer use to test or verify this change?
---
Watch that CI! Ensure that the removed code is unused.
This is a tracking issue to note that any updates of the curve library fork to upstream version 4.1.2 or later will break on the current nightly toolchain.
The current version of the curve library used for the fork breaks nightly CI starting with the
nightly-2024-02-05
toolchain. A recent upstream PR fixes this, but is not backwards compatible.This means that if the curve library fork is ever updated to include the fix, it will break this repository's nightly CI. The ecosystem's repositories will need to move to
stable
or at leastnightly-2024-02-05
if this happens.The text was updated successfully, but these errors were encountered: