Your message dated Tue, 11 Jan 2022 16:49:12 +0100
with message-id <[email protected]>
and subject line Fixed in 16.2.7+ds
has caused the Debian Bug report #956293,
regarding python3-ceph-argparse: Using anything around INT32_MAX timeout in 
thread.join on a 32 bit system is wrong.
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 [email protected]
immediately.)


-- 
956293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956293
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python3-ceph-argparse
Version: 14.2.7-1~bpo10+1
Severity: important

Dear Maintainer,

Installing ceph nautilus on armhf works after fixing the timeout value in:
/usr/lib/python3/dist-packages/ceph_argparse.py line 1302.
It says:
        timeout = 2 ** 32
which effectively means a timeout of right now on 32 bit python.
Upstream it's not changed at all:
https://github.com/ceph/ceph/blob/master/src/pybind/ceph_argparse.py#L1322
        timeout = (1 << (32 - 1)) - 1
still leads to a situation where the t.join of a few lines further just times 
out immediately:

root@odroid6:~# ceph -s
Traceback (most recent call last):
  File "/usr/bin/ceph", line 1266, in <module>
    retval = main()
  File "/usr/bin/ceph", line 979, in main
    conffile=conffile)
  File "/usr/lib/python3/dist-packages/ceph_argparse.py", line 1319, in 
run_in_thread
    raise Exception("timed out")
Exception: timed out

Changing the timeout to something sane like: 86400.0 (for a day) or even 
365*86400.0 would be better I guess for the position it is used in:
ceph command line.

And thanks for the armhf build, since I never was able to get past the C++ 
errors of size assumptions. Except for this timeout it seems to work.
Since obviously you did extensive work to get past this, this is the last bit I 
think that's needed to get it to work again on 32 bit systems.

-- System Information:
Debian Release: 10.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: armhf (armv7l)

Kernel: Linux 5.4.6-ckxu4+ (SMP w/8 CPU cores; PREEMPT)
Init: systemd

--- End Message ---
--- Begin Message ---
Hi,

I went to look in the upstream code, and that's been fixed.

Cheers,

Thomas Goirand (zigo)

--- End Message ---

Reply via email to