Actions
Bug #7968
closedLogs are not outputed for visualization errors
Status:
Rejected
Priority:
Immediate
Assignee:
-
Category:
Bridge
Target version:
-
Start date:
02/10/2017
Due date:
% Done:
0%
Estimated time:
Detected in build:
svn
Platform:
Published in build:
Description
An interface shows an 'unknown error' while visualizing an error trace, but any debug information are not performed.
Files
Updated by Evgeny Novikov about 7 years ago
- Category changed from Tasks generation to Bridge
- Assignee set to Vladimir Gratinskiy
- Priority changed from Normal to Immediate
Logs are extremely useful for debugging errors.
Updated by Vladimir Gratinskiy about 7 years ago
- Status changed from New to Feedback
Visualizing error trace can be failed with "Unknown error" only if the javascript that sends requests is broken.
Updated by Evgeny Novikov about 7 years ago
- Status changed from Feedback to Rejected
- Assignee deleted (
Vladimir Gratinskiy)
So, the reason of this deviant behavior was outdated JavaScript.
Actions