This repository has been archived by the owner on May 26, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 37
A question about dialWorkerLoop #304
Comments
my git submit log is 5155c770 |
@vyzo, can you help out here? |
hrm thats the second time we gat this, something is amiss.
…On Tue, Dec 21, 2021, 10:37 Marten Seemann ***@***.***> wrote:
@vyzo <https://github.com/vyzo>, can you help out here?
—
Reply to this email directly, view it on GitHub
<#304 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAI4SU3TVMGU2ZQQF3Y63LUSA4DLANCNFSM5KNLECNA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Yes, logically, I don't think you are doing anything with this active, and many of the conditions about it are not valid. So, is this a logic problem or is there something that is not yet done? |
yeah, it's a bug, fixing.
…On Tue, Dec 21, 2021 at 11:08 AM tanqiangyes ***@***.***> wrote:
Yes, logically, I don't think you are doing anything with this ACTIVE, and
many of the conditions about it are not valid. So, is this a logic problem
or is there something that is not yet done?
—
Reply to this email directly, view it on GitHub
<#304 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAI4ST5GA45P6WO3ZISL6DUSA7ZZANCNFSM5KNLECNA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Okay, looking forward to the fix. |
#305 fixes the issue. |
Can you tell us why you have this logic? Because I tried to fix it, but I don't know why you wrote it that way. |
so that we can collect all pending dial results after the request channel has been closed; basically control short-circuits. |
Okay, does this bug affect specific businesses? |
I don't think so, it's a corner case. |
Ok, thanks for the reply. I'm currently learning the libp2p code, and I'm learning a lot, so thanks for your efforts. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In swarm_dial.go the dialWorkerLoop function has an active variable inside, when case res := <-resch:, active--, then in this case will determine active==0, but this time active is not certainly less than 0? I don't see active++ or an assignment operation elsewhere. Please help me solve this problem, thank you.
The text was updated successfully, but these errors were encountered: