Bug 1340943
| Summary: | Pyzor gives backtrace on UTF-8 errors | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Göran Uddeborg <goeran> | ||||
| Component: | pyzor | Assignee: | Jason Tibbitts <j> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 28 | CC: | andreas, j, lucilanga | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | pyzor-1.0.0-16.20180724git2b8d76d.fc27 pyzor-1.0.0-16.20180724git2b8d76d.fc28 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2018-08-02 15:39:54 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
This is just another in a list of utf-8 errors that keep cropping up. Upstream has said that at least some of these are fixed in the current git but there haven't really been many commits not relating to their test suite. I'll import a new git snapshot and we'll see how it goes. This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Still a problem in F26 pyzor-1.0.0-11.20160210gitf16e1b6.fc26.noarch This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The problem remains in F28, pyzor-1.0.0-13.20160210gitf16e1b6.fc28.noarch. pyzor-1.0.0-16.20180724git2b8d76d.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-71652c2fdf pyzor-1.0.0-16.20180724git2b8d76d.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-17a549ab26 So the bottom line is that I'm pretty sure upstream is just gone at this point and there is no real hope for a release in the foreseeable future. I pulled together the latest git snapshot and an open PR for a python3 fix and pushed the result to testing. So far it seems to be better, though it's discouraging that the test suite never found any of these issues. If problems with python 3.7 crop up, I will almost certainly drop this package from Fedora. We can't maintain things downstream endlessly while upstream does nothing. pyzor-1.0.0-16.20180724git2b8d76d.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-17a549ab26 pyzor-1.0.0-16.20180724git2b8d76d.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-71652c2fdf pyzor-1.0.0-16.20180724git2b8d76d.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-17a549ab26 > If problems with python 3.7 crop up, I will almost certainly drop this package
> from Fedora. We can't maintain things downstream endlessly while upstream does
> nothing.
It's a pity, but things like that happen. After all, I'm not prepared to take over upstreams myself, so who am I to complain?
Thanks for your efforts until now!
pyzor-1.0.0-16.20180724git2b8d76d.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report. pyzor-1.0.0-16.20180724git2b8d76d.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report. |
Created attachment 1162964 [details] One triggering message Description of problem: I noticed some of my spamassassin runs gave the following message in the log maj 30 20:42:09 mimmi spamd[6244]: pyzor: check failed: internal error, python traceback seen in response I dug up the message that triggered this, and ran it on the command line. It seems to be yet another instance of Python's problems with non-ascii. Traceback (most recent call last): File "/usr/bin/pyzor", line 429, in <module> main() File "/usr/bin/pyzor", line 152, in main if not dispatch(client, servers, config): File "/usr/bin/pyzor", line 258, in check for digested in get_input_handler(style): File "/usr/bin/pyzor", line 174, in _get_input_msg msg = email.message_from_file(sys.stdin) File "/usr/lib64/python3.5/email/__init__.py", line 54, in message_from_file return Parser(*args, **kws).parse(fp) File "/usr/lib64/python3.5/email/parser.py", line 54, in parse data = fp.read(8192) File "/usr/lib64/python3.5/codecs.py", line 321, in decode (result, consumed) = self._buffer_decode(data, self.errors, final) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xfa in position 1642: invalid start byte Version-Release number of selected component (if applicable): pyzor-1.0.0-8.20160210gitf16e1b6.fc24.noarch system-python-libs-3.5.1-7.fc24.x86_64 How reproducible: Every time for this message, but only some mails trigger the problem of course. Steps to Reproduce: 1. pyzor check < attached-message Actual results: Backtrace as above. Expected results: No crash, just a result from the check.