Last modified: 2014-07-15 19:40:18 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T62154, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 60154 - Logging: Capture stack traces in logging backend
Logging: Capture stack traces in logging backend
Status: RESOLVED FIXED
Product: Parsoid
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: Normal normal
: ---
Assigned To: Maria Pacana
:
Depends on:
Blocks: 49762
  Show dependency tree / graph
 
Reported: 2014-01-16 22:50 UTC by Gabriel Wicke
Modified: 2014-07-15 19:40 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Gabriel Wicke 2014-01-16 22:50:05 UTC 
We can add the capability to capture more structured stack traces in the env.log method later on. This stack overflow post might be useful to get more structured info than the string returned by new Error().stack:

http://stackoverflow.com/questions/13227489/how-can-one-get-the-file-path-of-the-caller-function-in-node-js
Comment 1 Arlo Breault 2014-07-15 19:40:18 UTC 
Looks like this was done in b40ae990535d0c7b4d776d09d9a9e3bdde5e2d21.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links