SafeElement.LogSafeError doesn't log stacktrace
Bug #329342 reported by
Johannes Rudolph
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Do |
Fix Released
|
Wishlist
|
Unassigned | ||
| Do Plugins |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
As the summary says... without printing a stacktrace, logging only the exception message is quite useless for plugin-developers.
Revision history for this message
| Johannes Rudolph (johannes-rudolph) wrote | #1 |
Revision history for this message
| Chris S. (cszikszoy) wrote | #2 |
| Changed in do-plugins: | |
| status: | New → Invalid |
| Changed in do: | |
| importance: | Undecided → Low |
| Changed in do: | |
| importance: | Low → Wishlist |
Revision history for this message
| Robert Dyer (psybers) wrote | #3 |
| Changed in do: | |
| status: | New → Confirmed |
| Changed in do: | |
| status: | Confirmed → Fix Committed |
| Changed in do: | |
| status: | Fix Committed → Fix Released |
| milestone: | none → 0.8.3 |
To post a comment you must log in.
Not really the place for this. All of the logging methods (safe and unsafe) live in core.