Details
-
New Feature
-
Resolution: Done
-
None
-
Medium
-
Empty show more show less
Description
Todo:
Adding the Snapshot-History to the RootCause-messages helps to understand what happened during editing and thus how to solve bugs, that by other means can not be reproduced and solved.
Thoughts and ideas:
- Option 1: logConsoleOutput is true => console.log of each step of the Snapshot-History
- many logs: performance?
(https://stackoverflow.com/questions/11426185/will-console-log-reduce-javascript-execution-performance) - therootcause: memory usage?
(therootcause's tracking of each move of the user seems not to limit their memory, so why should this happen for some more snapshot-history-steps?)
- many logs: performance?
- Option 2: capture function arguments
- DONE: Option 3: addLogEntry()
Attachments
Issue Links
- relates to
-
TRANSLATE-3118 Rework Richtext Editor
- In Progress
Activity
| Link | New: This issue relates to TRANSLATE-3118 [ TRANSLATE-3118 ] |
| Workflow | Original: MittagQI Workflow [ 28413 ] | New: MittagQI Workflow with Peer [ 35720 ] |
| Summary | Original: Add Snapshots to RootCause-messages | New: Add segment editing history (snapshots) to JS debugging (rootcause) |
| Fix Version/s | New: translate5 - 3.3.0 [ 11001 ] |
| Status | Original: Test Ready [ 10005 ] | New: Done [ 10000 ] |
| Description |
Original:
h2. Todo: Adding the Snapshot-History to the RootCause-messages helps to understand what happened during editing and thus how to solve bugs, that by other means can not be reproduced and solved. h2. Thoughts and ideas: * Option 1: logConsoleOutput is true => console.log of each step of the Snapshot-History ** many logs: performance? ([https://stackoverflow.com/questions/11426185/will-console-log-reduce-javascript-execution-performance]) ** therootcause: memory usage? (therootcause's tracking of each move of the user seems not to limit their memory, so why should this happen for some more snapshot-history-steps?) * Option 2: capture function arguments ** [https://therootcause.io/blog/solving-tricky-javascript-errors-by-capturing-function-arguments/] * *DONE: Option 3: addLogEntry()* ** [https://app.therootcause.io/#organizations/mittagqi/docs] ** Is the Logger available in our Plugins? ** Does addLogEntry() start a request or just "add" something to the current list? |
New:
h2. Todo: Adding the Snapshot-History to the RootCause-messages helps to understand what happened during editing and thus how to solve bugs, that by other means can not be reproduced and solved. h2. Thoughts and ideas: * Option 1: logConsoleOutput is true => console.log of each step of the Snapshot-History ** many logs: performance? ([https://stackoverflow.com/questions/11426185/will-console-log-reduce-javascript-execution-performance]) ** therootcause: memory usage? (therootcause's tracking of each move of the user seems not to limit their memory, so why should this happen for some more snapshot-history-steps?) * Option 2: capture function arguments ** [https://therootcause.io/blog/solving-tricky-javascript-errors-by-capturing-function-arguments/] * *DONE: Option 3: addLogEntry()* ** [https://app.therootcause.io/#organizations/mittagqi/docs] |
| Description |
Original:
h2. Todo: Adding the Snapshot-History to the RootCause-messages helps to understand what happened during editing and thus how to solve bugs, that by other means can not be reproduced and solved. h2. Thoughts and ideas: * Option 1: logConsoleOutput is true => console.log of each step of the Snapshot-History ** many logs: performance? ([https://stackoverflow.com/questions/11426185/will-console-log-reduce-javascript-execution-performance]) ** therootcause: memory usage? (therootcause's tracking of each move of the user seems not to limit their memory, so why should this happen for some more snapshot-history-steps?) * Option 2: capture function arguments ** [https://therootcause.io/blog/solving-tricky-javascript-errors-by-capturing-function-arguments/] * Option 3: addLogEntry() ** [https://app.therootcause.io/#organizations/mittagqi/docs] ** Is the Logger available in our Plugins? ** Does addLogEntry() start a request or just "add" something to the current list? h2. Next Step * Contact the team of the therootcause. (_done 2019-07-25 IPB; waiting for reply to support@translate5.net_) |
New:
h2. Todo: Adding the Snapshot-History to the RootCause-messages helps to understand what happened during editing and thus how to solve bugs, that by other means can not be reproduced and solved. h2. Thoughts and ideas: * Option 1: logConsoleOutput is true => console.log of each step of the Snapshot-History ** many logs: performance? ([https://stackoverflow.com/questions/11426185/will-console-log-reduce-javascript-execution-performance]) ** therootcause: memory usage? (therootcause's tracking of each move of the user seems not to limit their memory, so why should this happen for some more snapshot-history-steps?) * Option 2: capture function arguments ** [https://therootcause.io/blog/solving-tricky-javascript-errors-by-capturing-function-arguments/] * *DONE: Option 3: addLogEntry()* ** [https://app.therootcause.io/#organizations/mittagqi/docs] ** Is the Logger available in our Plugins? ** Does addLogEntry() start a request or just "add" something to the current list? |
| Status | Original: Done [ 10000 ] | New: Test Ready [ 10005 ] |
| Status | Original: Test Ready [ 10005 ] | New: Done [ 10000 ] |
| Resolution | New: Done [ 6 ] | |
| Status | Original: In Progress [ 3 ] | New: Test Ready [ 10005 ] |