DC++ does not send it's own INF when connecting to ADC hub in response to SID ( sometimes ).
Bug #185549 reported by
Pietry
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| DC++ |
Fix Released
|
Low
|
Unassigned | ||
Bug Description
@Since version 0.69 or even earlier
When connecting on some ADC hub on localhost, DC++ does not send it's own INF. Don't know whats the cause, but the state remains in IDENTIFY and does not move on . I only experienced it on localhost.
| Changed in dcplusplus: | |
| importance: | Undecided → Low |
Revision history for this message
| Pseudonym (404emailnotfound) wrote | #1 |
| Changed in dcplusplus: | |
| status: | New → Fix Committed |
| Changed in dcplusplus: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
I remember seeing something similar when connecting to a machine located in the same room. It seems it breaks if the latency is low enough, which made me guess it was some sort of thread timing issue. For me, though, it only happened when I would do a manual reconnect. After the hub timed me out and dropped the connection, and the auto-reconnect ran, it logged in fine.
Note: I haven't tried this recently, this was happening about a year ago. (I was also using BCDC++. Shhhh...)