test_pop_alerts raised the following error:
File "/home/runner/work/deluge/deluge/deluge/core/alertmanager.py", line 177, in handle_alerts
handler=handler.__qualname__,
File "lib/python3.10/unittest/mock.py", line 645, in __getattr__
raise AttributeError(name)
AttributeError: __qualname__
Mocks don't generate dunder methods like `__qualname__` attribute so
we need to manually specify it.
The bottom options for cancel/apply/ok where confusing for end-users as being checkboxes needing spacebar prepended to activate firstly, before return/enter to activate said previous selection, but changed now to omit. Also fixed not showing canceled options as sticking.
Co-authored-by: Calum Lind <calumlind+deluge@gmail.com>
Closes: https://github.com/deluge-torrent/deluge/pull/445
Change name to gir1.2-appindicator3-0.1. Tested on Ubuntu 22.04.4 LTS
and Ubuntu 20.04.6 LTS.
Replace appindicator3 refs with newer ayatanaappindicator3
Replace broken python-appindicator link with working jammy link.
Closes: https://github.com/deluge-torrent/deluge/pull/459
When setting a language, we set 2 environment variables at run time.
Setting the language back to `System Default`, we don't clean those env
variables.
In the WebUI, the page only reloads, and we still use the env variables
to set the language back to the previous one.
This does not affect GTK.
Closes: https://dev.deluge-torrent.org/ticket/3635
Closes: https://github.com/deluge-torrent/deluge/pull/450
The test_pause_not_pop_alert test passes on Linux but is consistently failing
in CI pipeline for Windows:
AssertionError: Expected 'mock' to not have been called. Called 1 times.
Calls: [call.deferred.cancel(),
call(LtAlertMock(type=1, name='mock_alert1', message='Alert 1'))].
Disabling the test until it can be resolved.
The GTK option for dark theme only provides a preference to use the dark
theme, there is not a similar option for light theme so the settings
should only refer to 'prefer dark theme' and whether it's on or off.
Simplify searching for themes and ensure theme is ordered last.
Ideally themes would be set client-side but seems to be quite tricky to
accomplish with ExtJS.
For me at least, Safari on Mac OS X, the tracker icon significantly
overflows in the Tracker column of the torrent list. (It does show the
correct size in the Trackers filter, though. Different CSS.)
This change causes it to constrain down to the height of the column and
display correctly.
Closes: https://github.com/deluge-torrent/deluge/pull/440
If a dir exists with no contents then the following error occurred:
```
Traceback (most recent call last):
...
File "/usr/lib/python3.10/site-packages/deluge/ui/web/json_api.py", line 608, in _on_got_files
dirinfo['progress'] = sum(progresses) / dirinfo['size'] * 100
builtins.ZeroDivisionError: float division by zero
```
Closes: https://github.com/deluge-torrent/deluge/pull/439
We cannot handle an alert after calling lt.pop_alerts for a subsequent
time since the alert objects are invalidated and with cause a segfault.
To resolve this issue add a timeout to the handler calls and wait in the
alert thread for either the handlers to be called or eventually be
cancelled before getting more alerts.
This is still not an ideal solution and might leave to backlog of alerts
but this is better than crashing the application. Perhaps the timeout
could be tweaked to be shorter for certain alert types such as stats.
Related: https://github.com/arvidn/libtorrent/issues/6437
The change ownership menu item was broken due to Gtk deprecation
changes in commit #bcaaeac.
Fixed by correctly setting the RadioMenuItem group
Refactored to simplify the code
Removed dead or unneeded code
Fixes: https://dev.deluge-torrent.org/ticket/3610
Noticed mismatch with current lt docs and found usage of deprecated
status.paused.
The actual check here is not required we should just attempt to pause
the torrent.
Issue: https://dev.deluge-torrent.org/ticket/3499
The GitHub CI tests on Linux were failing due to ProcessTerminated
> await daemon.kill()
E twisted.internet.error.ProcessTerminated: A process has ended with a probable error condition: process ended by signal 6.
Added a try..except in daemon as a quick solution but might need to
investigate the ProcessOutputHandler.kill method.
We are currently creating a copy of each alert to avoid segfaults when
the next pop_alerts invalidates the lt alert objects we are holding
for handler callbacks.
However these alert copies are not deep enough since need to also
resolve the alert object methods e.g. message() therefore it is still
possible to result in lt segfaults.
The workaround is to check for any handlers not called, give them some
more time and eventually discard if still not handled.
Ref: https://github.com/arvidn/libtorrent/issues/6437
This spawns a thread in alertmanager to call wait_for_alert in a thread.
This reduces latency to deluge responding to events.
And removes all `hasattr` checks in Component
Closes: https://github.com/deluge-torrent/deluge/pull/221
With recent update to pyinstaller 6.0 the libraries are now placed in an
`_internal` folder within the bundle. This has resulted in the failure
to create copies of libssl.
However after examining the new _internal dir it appears that the x64
lib are now created so this step is no longer required.
For new UI features to be added, one should make sure the backend daemon
is supported and add fallback in case it doesn't.
Here we add the ability to get the daemon version from the `Client`
class and also check the version against a desired version.
Closes: https://github.com/deluge-torrent/deluge/pull/427
Add support for v2 torrents in create_torrent, but keep the old
default of only adding the v1 metadata.
Unify the single-file and directory cases to avoid code
duplication.
V2 torrents require files to be piece-aligned. The same for
hybrid v1/v2 ones. To handle both cases of piece-aligned and
non-aligned files, always read the files in piece-aligned
chunks. Re-slice the buffer if needed (for v1-only multi-file
torrents).
Also, had to adapt to progress event. It now depends on the
number of bytes hashed rather than the number of pieces. To
avoid sending and excessive amount of event when handling a
directory with many small files, add a mechanism to limit
event period at 1 per piece_length.
Closes: https://github.com/deluge-torrent/deluge/pull/430
If target=None and add_to_session is True, the torrent will be
directly added to the session without writing the torrent file
to disk. This will allow to programmatically control deluge via
RPC without creating .torrent files all over the place.
Also, make most create_torrent parameters optional.
Tests were stalling in deluge_ui_entry with pytest 7.4.3 likely due to
changes in the way it handles stderr but it is not clean the extact
issue.
For now we will pin the pytest version and look to fix the issue later.
Reference: https://docs.pytest.org/en/stable/changelog.html#pytest-7-4-3-2023-10-24
Preferable to be working with Python scripts for easier development.
This is direct port of the original bash script with the slight
modification to also use pngquant to reduce file size further.
Change the default compression tool to oxipng since it produces smaller
files faster than zopfli.
Add the ECT tool as an option to get maximum compression but is quite
slow to complete.
Using Efficient-Compression-Tool, we managed to reduge image sizes by
Saved 9.45KB out of 241.88KB (3.9065%) without changing visual appearence.
It's a small improvement, but we get something for nothing and that's nice.
ect -keep --allfilters-b --pal_sort=120 -30060 -recurse --mt-file ./
Closes: https://github.com/deluge-torrent/deluge/pull/405
When you set a config directory path (-c) on the command line, and only when,
a file named logging.conf is read to set fine grained log levels.
This allows to have per module/plugin log levels.
A simple logging.conf could be:
-<8 -------------------
deluge:info
deluge.plugin.foo:debug
-----------------------
The file is parsed and the log levels are set in the deluge.log.tweak_logging_levels.
This function set the appropriate logger to the desired level.
Despite the log level is changed, log levels less than ERROR are still not
logged.
The reason is that the log level check is done twice, in the logging.Logger class
and in the logging.Handler class.
The fix is to not set the logging level in the Handler in deluge.log.setup_logger
and let only the logging.Logger check the level.
Closes: https://github.com/deluge-torrent/deluge/pull/428
Calum Lind
Gregorio Litenstein
Martin Hertz
kenstir
Jacob Siverskog
zakary
DjLegolas
Chris Ross
freddy2659
Arkadiusz Bulski
DjLegolas
Radu Carpa
Anthony Ryan
Sébastien Luttringer
Myrmecophaga tridactyla