Your message dated Sat, 7 Jun 2025 20:20:40 +0000
with message-id 
<27xpaxacdzeejdwlkmfazfizm2dsdqfwr7kfowvid6mucvic2d@nassr6fd4lfi>
and subject line Re: Bug#1106281: broken by ansible 12
has caused the Debian Bug report #1106281,
regarding broken by ansible 12
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.)


-- 
1106281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106281
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ansible-mitogen
Version: 0.3.23-2
Severity: grave
Tags: upstream

Since upgrading ansible, ansible-mitogen fails with:

[ERROR]: [mux  28726] 14:11:13.061278 E mitogen: raw pickle was: 
b'\x80\x02X\'\x00\x00\x00ansible_mitogen.services.ContextServiceq\x00X\x03\x00\x00\x00getq\x01cmitogen.core\nKwargs\nq\x02}q\x03X\x05\x00\x00\x00stackq\x04]q\x05}q\x06(X\x06\x00\x00\x00methodq\x07X\x03\x00\x00\x00sshq\x08X\x06\x00\x00\x00kwargsq\t}q\n(X\x0f\x00\x00\x00check_host_keysq\x0bX\x06\x00\x00\x00ignoreq\x0cX\x08\x00\x00\x00hostnameq\rX\x11\x00\x00\x00w-15.xx.elided.xxq\x0eX\x08\x00\x00\x00usernameq\x0fX\x04\x00\x00\x00rootq\x10X\x0b\x00\x00\x00compressionq\x11\x88X\x08\x00\x00\x00passwordq\x12NX\x04\x00\x00\x00portq\x13NX\x0b\x00\x00\x00python_pathq\x14]q\x15X\x10\x00\x00\x00/usr/bin/python3q\x16aX\r\x00\x00\x00identity_fileq\x17NX\x0f\x00\x00\x00identities_onlyq\x18\x89X\x08\x00\x00\x00ssh_pathq\x19X\x03\x00\x00\x00sshq\x1aX\x0f\x00\x00\x00connect_timeoutq\x1bcansible.module_utils._internal._datatag\n_AnsibleTaggedInt\nq\x1cK\n\x85q\x1d\x81q\x1e}q\x1fX\x15\x00\x00\x00_ansible_tags_mappingq
 
cansible.module_utils._internal._datatag\n_AnsibleTagsMapping\nq!)\x81q"cansible._internal._datatag._tags\nOrigin\nq#h#)\x81q$]q%(NX\x10\x00\x00\x00<Config
 
default>q&NNebssbX\x08\x00\x00\x00ssh_argsq\']q((X\x02\x00\x00\x00-Cq)X\x02\x00\x00\x00-oq*X\x12\x00\x00\x00ControlMaster=autoq+X\x02\x00\x00\x00-oq,X\x12\x00\x00\x00ControlPersist=60sq-eX\x0f\x00\x00\x00ssh_debug_levelq.NX\x0b\x00\x00\x00remote_nameq/NX\x0f\x00\x00\x00keepalive_countq0K\nX\x12\x00\x00\x00keepalive_intervalq1K\x1euuas\x85q2Rq3\x87q4.'
[ERROR]: [mux  28726] 14:11:13.062613 E mitogen.service: Pool(5940, size=32, 
th='mitogen.Pool.5940.0'): while invoking None of None
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/mitogen/service.py", line 616, in 
_on_service_call
    self._validate(msg)
    ~~~~~~~~~~~~~~^^^^^
  File "/usr/lib/python3/dist-packages/mitogen/service.py", line 593, in 
_validate
    tup = msg.unpickle(throw=False)
  File "/usr/lib/python3/dist-packages/mitogen/core.py", line 994, in unpickle
    obj = unpickler.load()
  File "/usr/lib/python3/dist-packages/mitogen/core.py", line 785, in find_class
    return self.find_global(module, func)
           ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/mitogen/core.py", line 895, in 
_find_global
    raise StreamError('cannot unpickle %r/%r', module, func)
mitogen.core.StreamError: cannot unpickle 
'ansible.module_utils._internal._datatag'/'_AnsibleTaggedInt'

[ERROR]: Task failed: mitogen.core.StreamError: cannot unpickle 
'ansible.module_utils._internal._datatag'/'_AnsibleTaggedInt'
  File "/usr/lib/python3/dist-packages/mitogen/service.py", line 616, in 
_on_service_call
    self._validate(msg)
    ~~~~~~~~~~~~~~^^^^^
  File "/usr/lib/python3/dist-packages/mitogen/service.py", line 593, in 
_validate
    tup = msg.unpickle(throw=False)
  File "/usr/lib/python3/dist-packages/mitogen/core.py", line 994, in unpickle
    obj = unpickler.load()
  File "/usr/lib/python3/dist-packages/mitogen/core.py", line 785, in find_class
    return self.find_global(module, func)
           ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/mitogen/core.py", line 895, in 
_find_global
    raise StreamError('cannot unpickle %r/%r', module, func)

fatal: [w-15.xx.elided.xx]: FAILED! => {"changed": false, "msg": "Task failed: 
mitogen.core.StreamError: cannot unpickle 
'ansible.module_utils._internal._datatag'/'_AnsibleTaggedInt'\n  File 
\"/usr/lib/python3/dist-packages/mitogen/service.py\", line 616, in 
_on_service_call\n    self._validate(msg)\n    ~~~~~~~~~~~~~~^^^^^\n  File 
\"/usr/lib/python3/dist-packages/mitogen/service.py\", line 593, in _validate\n 
   tup = msg.unpickle(throw=False)\n  File 
\"/usr/lib/python3/dist-packages/mitogen/core.py\", line 994, in unpickle\n    
obj = unpickler.load()\n  File 
\"/usr/lib/python3/dist-packages/mitogen/core.py\", line 785, in find_class\n   
 return self.find_global(module, func)\n           
~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^\n  File 
\"/usr/lib/python3/dist-packages/mitogen/core.py\", line 895, in _find_global\n 
   raise StreamError('cannot unpickle %r/%r', module, func)"}


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

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

Versions of packages ansible-mitogen depends on:
ii  ansible-core     2.19.0~beta4-1
ii  python3          3.13.3-1
ii  python3-mitogen  0.3.23-2

ansible-mitogen recommends no packages.

ansible-mitogen suggests no packages.

-- no debconf information

-- 
ciao,
Marco

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message ---
Version: 0.3.25~a1-1

Please check if this is still reproducible with 0.3.25~a1-1?

Now it works fine, except for this warning:

Thanks for confrming that. Yes, I had a patch for replacing jsonify earlier (when it was completely gone) but it broke some things. The deprecation warning (and what it takes to not break things) is known upstream.

Stefano

--
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

--- End Message ---

Reply via email to