Include error-reason when failining in CryptoVec unix #443
Conversation
This file contains 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
amtelekom
force-pushed
the
cryptovec-unix-errmsg
branch
from
1eb08d5 to
5a883fb
Compare
amtelekom
force-pushed
the
cryptovec-unix-errmsg
branch
from
5a883fb to
8bec932
Compare
amtelekom
force-pushed
the
cryptovec-unix-errmsg
branch
from
2e0f0a1 to
3266f44
Compare
|
LGTM, thank you! |
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.
I've encountered CryptoVec failing on some hosts when running multiple SSH sessions in parallel.
To debug this, we've implemented rudimentary error reporting in CryptoVecs unix implementation to help if errors like this occur.
(For us, it failed due to the Docker engine on those hosts setting
RLIMIT_MEMLOCKtoo low)