Skip to content
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

common-updater-scripts: Handle errors in src hashing #80562

Merged
merged 3 commits into from Feb 20, 2020
Merged

Conversation

jtojnar
Copy link
Contributor

@jtojnar jtojnar commented Feb 19, 2020

Motivation for this change

Previously, when downloading src failed for other reason than hash mismatch, the error ended up in newHash. This made evaluation fail since the error message is not valid hash. Now the failure will make newHash empty.

It is also much cleaner than previously since \K is very cool thing and we no longer grep for legacy messages.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.

@dtzWill
Copy link
Member

dtzWill commented Feb 20, 2020

Woohoo! I've accidentally committed (and then had to fixup) sha25 = "failed to..." more than a few times xD, thanks!

Previously, when downloading src failed for other reason than hash mismatch,
the error ended up in newHash. This made evaluation fail since the error message
is not valid hash. Now the failure will make newHash empty.

It is also much cleaner than previously since \K is very cool thing
and we no longer grep for legacy messages.
SRI hashes (base64 encoded) can contain + sign which is a special character
in extended regular expressions so it needs to be escaped.
@jtojnar
Copy link
Contributor Author

jtojnar commented Feb 20, 2020

I accidentally made it include SRI-like prefix even when the SRI hash was not previously used. That should be fixed now.

I also fixed the issue when SRI hashes containing + were not being replaced by the temporary nil hash due to regex considering it a special character.

@jtojnar jtojnar merged commit cf366dd into master Feb 20, 2020
@jtojnar jtojnar deleted the cus-broken branch February 20, 2020 19:26
dtzWill pushed a commit to dtzWill/nixpkgs that referenced this pull request Feb 21, 2020
common-updater-scripts: Handle errors in src hashing
(cherry picked from commit cf366dd)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants