-
-
Notifications
You must be signed in to change notification settings - Fork 587
Replace use of Thread with ThreadPoolExecutor #391
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
Conversation
Hmm... These CI failures don't look like my fault:
|
4797ed0
to
dc6e737
Compare
Also log any error while evaluating callbacks, not just if thread creation fails.
|
did not intend to close this |
Is this a fix to #390? I have tested with your example and it hangs randomly. |
No, it’s not. This PR is intended to only reduce the maximum number of threads and to increase logging coverage when a python callback errors out. |
Got it. This is a welcomed change. for (let i = 0; i < 10; i++) {
console.log('request ' + i);
api.echo(i).then((j) => {
console.log('response ' + i)
})
} class JSApi:
def echo(self, value):
print(value)
return value |
This PR is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days |
Also log any error while evaluating callbacks, not just if thread creation fails.