oopses not published when not using fallback_chain
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-oops-dictconfig |
Fix Committed
|
High
|
Michael Nelson |
Bug Description
Steps to reproduce:
1. Use standard configglue syntax to specify a single publisher without any fallbacks [1]
2. View your settings and that your settings now include default values for other items, specificaly fallback_chain=[] [2]
3. Run your app and cause an oops
Result: oops isn't written to disk.
AFAICT, the reason is that in oops_dictconfig
[1] http://
[2] Eg:
$ ./manage.py settings oopses
OOPSES = {'publishers': [{'inherit_id': False, 'error_dir': '/tmp/my-oopses', 'exchange_name': '', 'routing_key': '', 'vhost': '', 'host': '', 'user': '', 'new_only': False, 'password': '', 'type': 'datedir', 'fallback_chain': []}], 'template': {'reporter': 'DEV'}}
Related branches
- James Westby (community): Approve
-
Diff: 46 lines (+12/-2)3 files modifiedREADME (+1/-1)
oops_dictconfig/dictconfig.py (+1/-1)
oops_dictconfig/tests/test_dictconfig.py (+10/-0)
Changed in python-oops-dictconfig: | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → Michael Nelson (michael.nelson) |
Changed in python-oops-dictconfig: | |
status: | In Progress → Fix Committed |
BTW, the only work-around I could see was to use json for the oopses setting in my configglue config (ie. so it specifically doesn't contain default values for unspecified config options.)