Opened 10 years ago

Last modified 3 years ago

#520 new defect

Double entries in upload queue !

Reported by: anonymous Owned by: quinox
Priority: normal Milestone: Release 1.3.0
Component: nicotine Version: 1.2.14
Keywords: upload queue Cc:

Description

There are permanently doubled entries in my upload queue ... a user will be download one file and in my queue there are even more entries for the same file. please fix it.

Attachments (1)

nicotine.JPG (176.3 KB) - added by anonymous 9 years ago.
screenshot of this error

Download all attachments as: .zip

Change History (10)

comment:1 Changed 10 years ago by anonymous

I changed something in the config (transfer tab) ... now the problem does not exist any more. I remember that i switched from round robin to fifo, have unchecked the max. upload slots option and furthermore i increased the upload queue rate from default 10 to 75 kb/s with a fixed 10 kb/s for each upload slot.

now it works fine, i dont change anything of these options again ... never change a running ... :)

Changed 9 years ago by anonymous

Attachment: nicotine.JPG added

screenshot of this error

comment:2 Changed 9 years ago by anonymous

I added an attachment (screenshot) ... the error is occured again :(

comment:3 Changed 9 years ago by anonymous

Thanks for the ticket and the screenshot - this should be solved indeed!

comment:4 Changed 9 years ago by mike-labo

Still the same issue here (1.2.15svn)

comment:5 Changed 9 years ago by anonymous

Okay, so, it's seems that those multiples entries appear when there is a connection problem. "Cannot connect" = one duplicate entry, and so on. So each time nicotine retries and fails, it adds a dupe.

comment:6 Changed 9 years ago by mike-labo

and that was /me

comment:7 Changed 9 years ago by debug

I also have same problem, still, with r135x. Sometimes even more than just doubled entries.

comment:8 Changed 9 years ago by anonymous

yes, we haven't fixed this yet

comment:9 Changed 3 years ago by gfarmerfr

Milestone: Release 1.2.14Release 1.3.0
Note: See TracTickets for help on using tickets.