Opened 7 years ago

Closed 7 years ago

Last modified 2 years ago

#3112 closed bug (Fixed)

Setting peer TOS from deluge console is different from setting Peer TOS from WebUI

Reported by: ant3tna Owned by:
Priority: minor Milestone: Future
Component: Console UI Version: 1.3.13
Keywords: deluge console Cc:



Let's say I want to set Peer TOS: 0x88

I will do it 2 different ways a) & b) see examples bellow. Why the result is not the same, one is written as hex 0x88 and other is written as 136 (same decimal value as 0x88)

a) webui:

When I set this from Web UI and later I read core.conf I see that same value: 0x88, also deluge console reads it like 0x88 too.

deluge-console 'connect myuser myuserpass; config peer_tos'

peer_tos: 0x88



myuser@srv:~$ deluge-console 'connect myuser myuserpass; config -s peer_tos 0x88; config peer_tos'
Setting peer_tos to 136..
Configuration value successfully updated.
  peer_tos: 136

Is this a problem ? If not than why don't you follow same nmber base ?

Kind Regards

Change History (3)

comment:1 Changed 7 years ago by Cas

  • Milestone changed from needs verified to 1.3.16

comment:2 Changed 7 years ago by Cas

  • Resolution set to Fixed
  • Status changed from new to closed

Fixed: [bcc7a74725]

comment:3 Changed 2 years ago by Cas

  • Milestone changed from 1.3.16 to Future

Ticket retargeted after milestone deleted

Note: See TracTickets for help on using tickets.