build: Patch boost install checksum mismatch error #57658
Merged
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
dcalhoun
added
[Type] Build Tooling
Apply the workaround provided by the React Native community to address a checksum mismatch error that occurs when installing `boost`. The error originates from issues with the `boost` host, JFrog. facebook/react-native#42180
dcalhoun
force-pushed
the
fix/patch-boost-install-checksum-mistmatch-error
branch
from
ebc14a7 to
7c3b686
Compare
dcalhoun
changed the title
dcalhoun
added
the
Mobile App - Automation
Member
|
It appears the CI is currently failing due to the patch being corrupt or not installable. Investigating... |
derekblank
force-pushed
the
fix/patch-boost-install-checksum-mistmatch-error
branch
from
23a2c71 to
d3421bb
Compare
|
Size Change: 0 B Total Size: 1.69 MB ℹ️ View Unchanged
|
derekblank
force-pushed
the
fix/patch-boost-install-checksum-mistmatch-error
branch
from
0b957a9 to
e37d869
Compare
Member
|
Upgrading to There are two remaining non-required CI failures for checking Node.js versions on windows-latest (#), but they may not be related. It may be just as straightforward to wait until the RN 0.71 patch itself is introduced, rather than upgrade patch-package for the whole Gutenberg repo. I do think there is value in upgrading patch-package from 6.2.2 to 8.0.0 as was done in this PR, as eventually we would run into this bug again if ever using multiple patches in the future. |
Contributor
For reference, the fix for the
I agree, we might run in a similar situation in the future, so I'd also advocate upgrading |
fluiddot
approved these changes
Jan 9, 2024
Contributor
fluiddot
left a comment
fluiddot
left a comment
There was a problem hiding this comment.
LGTM 🎊 !
There are two remaining non-required CI failures for checking Node.js versions on windows-latest (#), but they may not be related.
Yep, they seem unrelated to the changes introduced in this PR, so I've re-run them. Once they succeed, we could merge the PR.
Contributor
All CI checks passed, I'll proceed with the merge to prevent the CI job |
Member
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What?
Fix a install error for
boost.Why?
The error prevents successful project builds both locally and on CI servers.
How?
Apply the workaround provided by the React Native community to address a
checksum mismatch error that occurs when installing
boost. The errororiginates from issues with the
boosthost, JFrog.facebook/react-native#42180
Testing Instructions
Verify CI tasks succeed.
Testing Instructions for Keyboard
N/A, no user-facing changes.
Screenshots or screencast
N/A, no user-facing changes.