Custom Query (2449 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (274 - 276 of 2449)

Ticket Resolution Summary Owner Reporter
#3409 Fixed Make deluge-console work on Windows for command line automation petersasi
Description
  1. Python does not support and include ncurses on Windows.
  2. Windows-Curses https://pypi.org/project/windows-curses/ can be installed with pip, which adds support for the standard Python curses module on Windows. Uses the PDCurses curses implementation.
  3. Without this patch however it bails out claiming the module 'signal' has no attribute 'SIGWINCH'.
  4. This patch passes on the AttributeError? above.
  5. This makes the below sample commands run and complete as intented:

deluge-console.exe status deluge-console.exe info

#3410 Fixed Interactive deluge-console on windows petersasi
Description
  1. After applying https://dev.deluge-torrent.org/ticket/3409 and adding

pip.exe install windows-curses to the build process non-interactive command line commands complete successfully.

  1. With the attached patch applied deluge-console.exe no longer bails out with the message: "Deluge-console does not run in interactive mode on Windows.".
  2. Instead we just log a debug message and carry on. Now the interactive UI starts, brings up a connection selection window. But does not accept any input.
  3. The log is full of a twisted/internet/selectreactor.py error for win32select: "builtins.OSError: 10038? An operation was attempted on something that is not a socket".
  4. Same twisted error does not show on the logs running the daemon and the GTK3 thin-client on Windows.
  5. I am stuck here, will have to ask for the help of a developer who understands how this twister works with the GTK3 UI on windows but not the curses one - what is different?
  6. Please find the unofficial but working Deluge 2.0.3 and 2.0.4dev38 Windows installers here: https://drive.google.com/drive/folders/1bCwij_GEy8nhqR6EynXYY_Yl7XuWYpVT
#3413 Fixed Sorting by ETA displays wrong zlamm
Description

When sorting by ETA, in the WEBui, infinity is placed at the top. So the current configuration is:

  • Infinity
  • 2m 40s
  • 340d 4h

when it should be:

  • 2m 40s
  • 340d 4h
  • Infinity

Since infinity is the largest number it should be on the bottom.

Note: See TracQuery for help on using queries.