We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug
My Mocha unit tests hang unless I specify --exit to kill the test process after each suite.
--exit
It looks like this may be because Semaphore leaks some resources.
To Reproduce
Write any test or script that verifies a Semaphore proof. At the end, add:
const foo = (process as any)._getActiveHandles(); console.log(foo);
You'll see that this includes a bunch of mysterious MessagePort handles.
MessagePort
Expected behavior
Should show exactly two handles, corresponding to stdin/stdout.
stdin/stdout
Technologies (please complete the following information):
The text was updated successfully, but these errors were encountered:
Using @semaphore-protocol/{group,identity,proof} version 3.2.3
@semaphore-protocol/{group,identity,proof}
Sorry, something went wrong.
Hello @dcposch! It seems to be related to snarkjs which is used in the @semaphore-protocol/proof package to generate and verify a proof.
snarkjs
@semaphore-protocol/proof
generateProof
#736 (comment)
This issue is related to snarkjs, but Semaphore could provide a function to "terminate" it.
No branches or pull requests
Describe the bug
My Mocha unit tests hang unless I specify
--exit
to kill the test process after each suite.It looks like this may be because Semaphore leaks some resources.
To Reproduce
Write any test or script that verifies a Semaphore proof. At the end, add:
You'll see that this includes a bunch of mysterious
MessagePort
handles.Expected behavior
Should show exactly two handles, corresponding to
stdin/stdout
.Technologies (please complete the following information):
The text was updated successfully, but these errors were encountered: