Compress trace record data

[twschiller]

Context

• Our traces (and debug logging) snapshots the context when the brick is called
• For extensions with a lot of bricks and/or large values (e.g., from API calls) that can clog up the IDB
• There's needless redundancy between traces
• Tracing/program slice tools for real programming languages work by compressing the trace, e.g., storing diffs between program counters

Implementation Sketch

• In a trace "pre-" section, only include the diff from the previous trace record
• Link each trace record to the previous trace record

[fregante]

I used this in the past: it takes strings, outputs strings

https://github.com/pieroxy/lz-string

[twschiller]

I used this in the past: it takes strings, outputs strings

Thanks, long-term I suspect we'll need to avoid storing the redundant data. But this is worth a quick look to see if it's a helpful stop gap

[github-actions[bot]]

This issue will be closed in 7 days unless the stale label is removed, or a comment is added to the issue.

[github-actions[bot]]

This issue was closed because it has been stale for 7 days with no activity.