Package Details: yt-dlp-git 2025.03.21.r6.g9d5e6de-1

Git Clone URL: https://aur.archlinux.org/yt-dlp-git.git (read-only, click to copy)
Package Base: yt-dlp-git
Description: A youtube-dl fork with additional features and fixes (git)
Upstream URL: https://github.com/yt-dlp/yt-dlp
Licenses: Unlicense
Conflicts: yt-dlp
Provides: yt-dlp
Submitter: katt
Maintainer: katt
Last Packager: katt
Votes: 47
Popularity: 1.60
First Submitted: 2021-08-08 15:20 (UTC)
Last Updated: 2025-03-24 15:45 (UTC)

Dependencies (25)

Required by (150)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 .. 10 Next › Last »

gesh commented on 2024-08-27 00:00 (UTC) 

ERROR: test_close_server_keeps_handlers_running (tests.asyncio.test_server.ServerTests.test_close_server_keeps_handlers_running)
Server waits for connection handlers to terminate.
----------------------------------------------------------------------
FAIL: test_close_waits_for_close_frame (tests.asyncio.test_connection.ServerConnectionTests.test_close_waits_for_close_frame)
close waits for a close frame (then EOF) before returning.
----------------------------------------------------------------------
FAIL: test_keepalive (tests.asyncio.test_connection.ServerConnectionTests.test_keepalive)
keepalive sends pings at ping_interval and measures latency.
----------------------------------------------------------------------

if I build on my system, and

ERROR: test_close_server_keeps_handlers_running (tests.asyncio.test_server.ServerTests.test_close_server_keeps_handlers_running)
Server waits for connection handlers to terminate.
----------------------------------------------------------------------

in a clean chroot (at least, as of last week, don't have the time to check if it's better now)

frankspace commented on 2024-08-26 23:28 (UTC)

@gesh, what problem are you running into? I tried playing with building a version 13.0 of python-websockets, too, and found that every single test fails whether I try to build it in a chroot or not, but as a test, I also tried to build the existing PKGBUILD for version 12.0 and got the same result. Maybe something else is breaking websockets compilation?

katt commented on 2024-08-21 17:03 (UTC)

@gesh Thanks for the heads up, I always build in a chroot so wouldn't have caught it.

gesh commented on 2024-08-21 14:30 (UTC) (edited on 2024-08-21 14:44 (UTC) by gesh)

Note the latest upstream commit bumped the websockets dep to 13.0. This causes websocket tests to hang, in particular test/test_socks.py::TestSocks4Proxy::test_socks4_no_auth[Websockets-ws]. I'm currently building a python-websockets13 to check if that fixes things, but until then upstream recommendation was to disable the test for now. EDIT: I've run out of time for today -- the obvious edit to the published extra/python-websockets doesn't build. Hopefully its packager will have the new version up soon.

diff --git a/PKGBUILD b/PKGBUILD
index 3e48039..db2fcc7 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -47,7 +47,7 @@ build() {

 check() {
     cd "${pkgname%-git}"
-    python -m pytest -v -Werror -m "not download"
+    python -m pytest -v -Werror -m "not download" -k 'not Websockets'
 }

 package() {

bashonly commented on 2024-04-29 23:41 (UTC)

The failing test won't be patched upstream until the next stable release.

If you don't want to wait, you could update the PKGBUILD to have it pass -Werror to pytest:

diff --git a/PKGBUILD b/PKGBUILD
index face841..5cc2eb3 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -47,7 +47,7 @@ build() {

 check() {
     cd "${pkgname%-git}"
-    pytest -v -m "not download"
+    pytest -v -Werror -m "not download"
 }

 package() {

Upstream will be making the same adjustment to its Makefile test recipes: https://github.com/yt-dlp/yt-dlp/pull/9765/commits/c36cac6b546973b7262f658d14a55403e6968ba0

Note that this PKGBUILD change will not be necessary after the next stable upstream release; I just thought I'd offer this here as a workaround for users who want to install without skipping the check

matejdro commented on 2024-04-28 05:23 (UTC)

Test fails for me on a recent version:

_________________________________________________________________________________________________________________________________________ TestInfoExtractor.test_search_nextjs_data _________________________________________________________________________________________________________________________________________

self = <test.test_InfoExtractor.TestInfoExtractor testMethod=test_search_nextjs_data>

    def test_search_nextjs_data(self):
        data = '<script id="__NEXT_DATA__" type="application/json">{"props":{}}</script>'
        self.assertEqual(self.ie._search_nextjs_data(data, None), {'props': {}})
        self.assertEqual(self.ie._search_nextjs_data('', None, fatal=False), {})
        self.assertEqual(self.ie._search_nextjs_data('', None, default=None), None)
        self.assertEqual(self.ie._search_nextjs_data('', None, default={}), {})
>       with self.assertRaises(DeprecationWarning):
E       AssertionError: DeprecationWarning not raised

test/test_InfoExtractor.py:1915: AssertionError
--------------------------------------------------------------------------------------------------------------------------------------------------- Captured stderr call ----------------------------------------------------------------------------------------------------------------------------------------------------
WARNING: [Dummy] unable to extract next.js data; please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U
===================================================================================================================================================== warnings summary ======================================================================================================================================================
test/test_InfoExtractor.py::TestInfoExtractor::test_search_nextjs_data
  /home/matej/.cache/yay/yt-dlp-git/src/yt-dlp/test/test_InfoExtractor.py:1916: DeprecationWarning: using `default='{}'` is deprecated, use `default={}` instead
    self.assertEqual(self.ie._search_nextjs_data('', None, default='{}'), {})

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html

It looks like upstream issue: https://github.com/yt-dlp/yt-dlp/issues/9763

gesh commented on 2024-03-31 12:41 (UTC)

Missing optdepend: curl_cffi (added 52f5be1f1e0dc45bb397ab950f564721976a39bf), used 'for impersonating browser requests. This may be required for some sites that employ TLS fingerprinting.'

However, I recall it being a pain to install in practice, so perhaps wait until the stable package adds it (so that by then, the installation path will stabilize)?

katt commented on 2024-03-13 17:48 (UTC)

@Alad I cannot reproduce this, neither in chroot or outside it. The package in arch's repos is on the same commit and they don't have that as a dep either.

Alad commented on 2024-03-13 11:32 (UTC) (edited on 2024-03-13 11:35 (UTC) by Alad)

test_websockets.py fails:

edit: I suppose python-websockets >=12.0 is required

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
test/test_websockets.py:78: in create_ws_websocket_server
    return create_websocket_server()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

ws_kwargs = {}

    def create_websocket_server(**ws_kwargs):
>       import websockets.sync.server
E       ModuleNotFoundError: No module named 'websockets.sync'

test/test_websockets.py:68: ModuleNotFoundError

« First ‹ Previous 1 2 3 4 5 6 7 .. 10 Next › Last »