-
Notifications
You must be signed in to change notification settings - Fork 54
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
ping3 multiprocessing buggy #23
Comments
Hi @joelfranco After investigation, this one is a bug. When using I will make sure that they don't have the same Sorry for the inconvience, and thank you for the feedback. |
i closed it by mistake. Thank you |
Hi @joelfranco I just updated ping3 to 2.6.2. Hopefully it will fix the bug. Thanks |
Hello Kyan,
Yes it worked :-)
Thank you a lot.
joel
Em 09/05/2020 10:34, Kyan escreveu:
…
Hi @joelfranco <https://github.com/joelfranco>
I just updated ping3 to 2.6.2. Hopefully it will fix the bug.
Can you give it a try and tell me if it works?
Upgrade: |python3 -m pip install -U ping3| or |pip3 install -U ping3|
Thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#23 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEMNXTCZ4MAYUOPE733FJ6DRQVLXLANCNFSM4M4NRIMQ>.
|
Hello,
I think that ping3 is buggy when used with multiprocess Process with start method "fork".
Look the code and result:
Result in buggy result (the hosts do not have similar delay times):
But if i insert:
mp.set_start_method('spawn')
it runs fine (actually a.dns.br is blocked):
Is it a bug or an expected result?
Thanks :-)
joel
The text was updated successfully, but these errors were encountered: