Bug 902069
| Summary: | [abrt] fedmsg-notify-0.4.0-1.fc18: decoder.py:384:raw_decode:ValueError: No JSON object could be decoded | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Matthew Miller <mattdm> | ||||||||
| Component: | fedmsg-notify | Assignee: | Luke Macken <lmacken> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 18 | CC: | jsmith.fedora, lmacken, pfrields, rbean | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | abrt_hash:659b0c3b2a776dfdc64d22f28fa1b592cf4186a0 | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2013-03-02 19:56:13 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
Created attachment 683772 [details]
File: backtrace
Created attachment 683773 [details]
File: core_backtrace
Created attachment 683774 [details]
File: environ
I think the following pull request should fix the issue: https://github.com/lmacken/fedmsg-notify/pull/4 fedmsg-notify-0.5.0-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/fedmsg-notify-0.5.0-1.fc18 Package fedmsg-notify-0.5.0-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing fedmsg-notify-0.5.0-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-2823/fedmsg-notify-0.5.0-1.fc18 then log in and leave karma (feedback). fedmsg-notify-0.5.0-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. |
Description of problem: I changed an option from off to on. (Notable: All options initially shown as off, but I'm getting a firehose of all notifications.) Version-Release number of selected component: fedmsg-notify-0.4.0-1.fc18 Additional info: cmdline: /usr/bin/python /usr/bin/fedmsg-notify-daemon dso_list: python-libs-2.7.3-13.fc18.x86_64 executable: /usr/bin/fedmsg-notify-daemon kernel: 3.7.2-201.fc18.x86_64 uid: 18281 Truncated backtrace: decoder.py:384:raw_decode:ValueError: No JSON object could be decoded Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/fedmsg_notify/daemon.py", line 122, in settings_changed for filter in filters] File "/usr/lib64/python2.7/json/__init__.py", line 326, in loads return _default_decoder.decode(s) File "/usr/lib64/python2.7/json/decoder.py", line 366, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) File "/usr/lib64/python2.7/json/decoder.py", line 384, in raw_decode raise ValueError("No JSON object could be decoded") ValueError: No JSON object could be decoded Local variables in innermost frame: s: 'announce FAS Bodhi git unhandled fedoratagger Wiki logger Pkgdb compose meetbot' self: <json.decoder.JSONDecoder object at 0x1e5df10> idx: 0