Skip to content

Conversation

@fanquake
Copy link
Member

@fanquake fanquake force-pushed the security_check_no_more_32bit branch 2 times, most recently from ba9ba60 to 00dd74a Compare April 28, 2020 09:40
@practicalswift
Copy link
Contributor

Concept ACK

Copy link
Member

@laanwj laanwj Apr 30, 2020

Choose a reason for hiding this comment

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

  • Do we want to print stderr to stderr maybe? (in this case, why PIPE it at all)
  • I'm not sure Error opening file is a good error message here. Might want to print the command that failed with the exit status.
  • Launching a command and raising an error on non-zero exit status what subprocess.check_call does. This might be good enough instead of defining our own function.

Copy link
Member Author

Choose a reason for hiding this comment

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

I've swapped to just using subprocess.run.

@laanwj
Copy link
Member

laanwj commented Apr 30, 2020

ACK otherwise, NON_FATAL was always a temporary hack it's good to see it gone.

@fanquake fanquake force-pushed the security_check_no_more_32bit branch from 00dd74a to eacedfb Compare May 14, 2020 12:11
@laanwj
Copy link
Member

laanwj commented May 14, 2020

ACK eacedfb

@laanwj laanwj merged commit 2d7489b into bitcoin:master May 14, 2020
@fanquake fanquake deleted the security_check_no_more_32bit branch May 14, 2020 23:39
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Feb 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants