Your message dated Wed, 21 May 2025 09:04:10 +0000
with message-id <e1uhfmw-00g3tp...@fasolo.debian.org>
and subject line Bug#1105921: fixed in nbclassic 0.3.2-4
has caused the Debian Bug report #1105921,
regarding python3-nbclassic: Refusing to serve hidden directory, via 404 Error
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1105921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1105921
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-nbclassic
Severity: important

Dear Maintainer,

while trying start a classic notebook from jupyterhub, I got this error message

[D 2025-05-17 08:32:43.583 oauthlib.oauth2.rfc6749.endpoints.token token:112] 
Dispatching grant_type authorization_code request to 
<oauthlib.oauth2.rfc6749.grant_types.authorization_code.AuthorizationCodeGrant 
object at 0x7f9cfee01a90>.
[D 2025-05-17 08:32:43.583 JupyterHub provider:58] authenticate_client 
<oauthlib.Request SANITIZED>
[D 2025-05-17 08:32:43.621 
oauthlib.oauth2.rfc6749.grant_types.authorization_code authorization_code:533] 
Using provided redirect_uri /user/picca/oauth_callback
[D 2025-05-17 08:32:43.621 JupyterHub provider:117] confirm_redirect_uri: 
client_id=jupyterhub-user-picca, redirect_uri=/user/picca/oauth_callback
[D 2025-05-17 08:32:43.621 
oauthlib.oauth2.rfc6749.grant_types.authorization_code authorization_code:301] 
Token request validation ok for <oauthlib.Request SANITIZED>.
[D 2025-05-17 08:32:43.622 JupyterHub provider:345] Saving bearer token 
{'access_token': 'REDACTED', 'expires_in': 1209600, 'token_type': 'Bearer', 
'scope': 'read:users:groups!user access:servers!server=picca/ 
read:users:name!user', 'refresh_token': 'REDACTED'}
[D 2025-05-17 08:32:43.635 JupyterHub provider:205] Deleting oauth code wT2... 
for jupyterhub-user-picca
[I 2025-05-17 08:32:43.650 JupyterHub log:192] 200 POST /hub/api/oauth2/token 
(picca@127.0.0.1) 71.28ms
[D 2025-05-17 08:32:43.657 JupyterHub base:366] Recording first activity for 
<APIToken('gEuc...', user='picca', client_id='jupyterhub-user-picca')>
[I 2025-05-17 08:32:43.665 JupyterHub log:192] 200 GET /hub/api/user 
(picca@127.0.0.1) 11.88ms
[I 2025-05-17 08:32:43.666 ServerApp] Logged-in user picca
[I 2025-05-17 08:32:43.667 ServerApp] Setting new xsrf cookie for 
b'e3f475fdd7ac48f99c702f8ba5d39f8b:4781760833cd6eda1d014f07eb2f352cdadc3de66e9cd241b40346af670fad8b'
 {'path': '/user/picca/'}
[I 2025-05-17 08:32:43.671 ServerApp] 302 GET 
/user/picca/oauth_callback?code=[secret]&state=[secret] -> /user/picca/tree? 
(picca@::ffff:127.0.0.1) 93.66ms
/usr/lib/python3/dist-packages/nbclassic/tree/handlers.py:51: RuntimeWarning: 
coroutine 'AsyncFileContentsManager.dir_exists' was never awaited
  if cm.dir_exists(path=path):
RuntimeWarning: Enable tracemalloc to get the object allocation traceback
/usr/lib/python3/dist-packages/nbclassic/tree/handlers.py:52: RuntimeWarning: 
coroutine 'AsyncFileContentsManager.is_hidden' was never awaited
  if cm.is_hidden(path) and not cm.allow_hidden:
RuntimeWarning: Enable tracemalloc to get the object allocation traceback
[I 2025-05-17 08:32:43.691 NotebookApp] Refusing to serve hidden directory, via 
404 Error


I am wondering if nbclassic is compatible with all the jupyter stack currently 
available in trixie.

Cheers

Fred

-- System Information:
Debian Release: 13.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.12.27-amd64 (SMP w/6 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

--- End Message ---
--- Begin Message ---
Source: nbclassic
Source-Version: 0.3.2-4
Done: Picca Frédéric-Emmanuel <pi...@debian.org>

We believe that the bug you reported is fixed in the latest version of
nbclassic, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1105...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Picca Frédéric-Emmanuel <pi...@debian.org> (supplier of updated nbclassic 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 21 May 2025 10:35:45 +0200
Source: nbclassic
Architecture: source
Version: 0.3.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <team+pyt...@tracker.debian.org>
Changed-By: Picca Frédéric-Emmanuel <pi...@debian.org>
Closes: 1105921
Changes:
 nbclassic (0.3.2-4) unstable; urgency=medium
 .
   * Team upload.
   * Bug fix: "Refusing to serve hidden directory, via 404 Error", thanks
     to Picca Frédéric-Emmanuel (Closes: #1105921).
Checksums-Sha1:
 d0d8851e6651619731aefa8bfdf7d2fbac6ae437 2191 nbclassic_0.3.2-4.dsc
 f2710a1ab785761b356bc33183e18363e60a7a8b 4708 nbclassic_0.3.2-4.debian.tar.xz
Checksums-Sha256:
 c4155d4736494c330c90ff8b603fc6d9fb3337aeadb89502f1eaf267359d88bb 2191 
nbclassic_0.3.2-4.dsc
 c07d0ad4c08d0b08ddb0257273e6a7945e751ca2604bd9cadada94a6106ddc2d 4708 
nbclassic_0.3.2-4.debian.tar.xz
Files:
 f7910354a96c07b5d5d76e9b8887ee80 2191 python optional nbclassic_0.3.2-4.dsc
 b79c106ec27b847fc90abac053bd4fe3 4708 python optional 
nbclassic_0.3.2-4.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQJFBAEBCgAvFiEE2bRTt5m4gw2UXmoKW/VOXhK5ALsFAmgtkaERHHBpY2NhQGRl
Ymlhbi5vcmcACgkQW/VOXhK5ALvxHw/+Nig/hnv9TEJu0mOxlSR0CB3StofmRV4Q
V8Y50UxsfacAYDssDeNgDnMAlBVY/YVQAtZCwEC6D0LF9rrKQGKN1Y/9EbvY5RHK
mrGLY1ATXiGyF1nXK++0VPN61ZtPIdsHRCwEXak1saag6lL5JI71xFCCbXCVNqhU
U7YB86jYZHINWwXHpaDwXgbLcfs+EeSRFF5JxGBiKclbCobCeNvRuw0DKiSxC7wW
XicmfyWd9uALBCbbXVacJiqyATPVBu8YJR2aaBOOKRand4yaU4E0RBzlkicqKNFx
vvikZfy1P1RINoTlbFFQYKuscT/S+l0ph0VUbCjFAS1iuL2D6nLVGaJLoRkqll2+
t2NgykofEaBRUN3mvWtyO5HhyHqoSctW2NpqE1fqnJIs55Dn2O5IoifoLsvFgzUm
8k38E3T/KQfCieZ9zM9H37f4d778aOybXi9eQpxB8Z0C1D5d5il8fy7039XhFjvv
7N+KT30GrTtctB5HauKdYh2lE7aY6BWJ+nXvilr0++X01YGqvL2Xq+e7wh4W2DGD
6mgFIltIuPt6HI3x0Ow0zoqXIqk44PLn3xqACltMuJn7hUOtFxtlA32OiOgSagA1
nbDxC+BIBIK0nz3JJXjNv7JynkWsnHB+DPRMXX10VR4ef99/uK34wlqpwRVTY9kL
dwQELS2o2RM=
=SzwV
-----END PGP SIGNATURE-----

Attachment: pgpp5yzVewunf.pgp
Description: PGP signature


--- End Message ---

Reply via email to