-
Notifications
You must be signed in to change notification settings - Fork 4
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
Using blocking network IO to avoid busy-wait #216
Conversation
7d2ce57
to
dd4ed90
Compare
This change also makes the netstring parser more robust to support the way that it's used in the network loop
dd4ed90
to
4a778f8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have you verified that the test suite for the Cryptol Python bindings continues to pass after these changes? (I recall that getting the network code just right for the test suite was very tricky, so it would be good to check to be on the safe side.)
./run_rpc_tests.sh passes |
This updates the `cryptol` Python bindings to require the use of `argo-client-0.0.13` or later, bringing in the performance improvements from GaloisInc/argo#216.
This updates the `saw-client` Python bindings to require the use of `argo-client-0.0.13` or later, bringing in the performance improvements from GaloisInc/argo#216. It also brings in the use of `cryptol-3.2.1`, which is compatible with `argo-client-0.0.13` or later.
This change also makes the netstring parser more robust to support the way that it's used in the network loop