-
-
Notifications
You must be signed in to change notification settings - Fork 422
Added option to disable integrity checks in core install
(for development purposes)
#2740
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+87
−35
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
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@ ## master #2740 +/- ## ========================================== - Coverage 67.67% 67.65% -0.03% ========================================== Files 239 239 Lines 22408 22424 +16 ========================================== + Hits 15165 15170 +5 - Misses 6049 6056 +7 - Partials 1194 1198 +4
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
@cmaglie
cmaglie
added
type: enhancement
Proposed improvement
topic: code
Related to content of the project itself
labels
Oct 29, 2024
@cmaglie
cmaglie
force-pushed
the
core_unsafe_install
branch
from
January 13, 2025 22:01
c06d350
to
4f3d245
Compare
alessio-perugini
alessio-perugini
approved these changes
Jan 14, 2025
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.
Please check if the PR fulfills these requirements
See how to contribute
before creating one)
our contributing guidelines
UPGRADING.md
has been updated with a migration guide (for breaking changes)configuration.schema.json
updated if new parameters are added.What kind of change does this PR introduce?
We have added a new configuration option,
board_manager.enable_unsafe_install,
to allow the installation of platforms/tools that do not pass the checksum test. This option has been added to ease the platform's development phase, relieving the developer from having to regenerate the index every time, and is not intended for use in production environments.What is the current behavior?
If a platform fails the checksum test, it will not be installed:
What is the new behavior?
The checksum test may be skipped:
Does this PR introduce a breaking change, and is titled accordingly?
No
Other information
Fix #1468