Opened on 06/22/2015 at 11:43:18 AM
Last modified on 09/17/2019 at 12:27:03 PM
#2705 new defect
Improve notification generation error reporting
Reported by: | Ross | Assignee: | |
---|---|---|---|
Priority: | P3 | Milestone: | |
Module: | Sitescripts | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Platform: | Unknown | |
Ready: | yes | Confidential: | no |
Tester: | Verified working: | no | |
Review URL(s): |
Description
Environment
ABP 2.6.9.3953 / Windows 8.1 x64
How to reproduce
- Create the notification Invalid1 (below) on the server.
- Commit the new notification, observe no errors are logged.
- Visit <ServerAddress>/notification.json
- Observe the newly committed notification is not included.
Test data
Invalid1 (target is wrong format):
severity = information target = adblockplus title.en-US = Other info message.en-US = This is some other info
Observed behaviour
When notification generation fails because of a bad notification file, the errors/problems are not displayed/logged making the problem difficult to debug.
Expected behaviour
Problems with notification files to be displayed or logged.
Attachments (0)
Change History (3)
comment:1 Changed on 06/22/2015 at 11:48:14 AM by Ross
comment:2 Changed on 06/22/2015 at 06:22:45 PM by fhd
- Blocking 2162 removed
- Component changed from Unknown to Sitescripts
- Priority changed from Unknown to P3
- Ready set
comment:3 Changed on 09/17/2019 at 12:27:03 PM by kvas
Dear stakeholders of this ticket,
I'm cleaning up Sitescripts tickets in Trac due to its phase out. This is one of the tickets that I could not myself close or move, so I need your input on it.
Please let me know if this ticket is still relevant for you and we can then discuss where it should be moved. If you think that this ticket is no longer relevant, you can write a comment explaining this or just ignore this message.
If I see now comments in the ticket on October 14, I will close it as rejected.
Best regards,
Vasily
Problems that should/could be logged: