Keyhan Vakil
Keyhan Vakil
Seems like a good suggestion, I'm currently revamping the memory view and I'll make sure to include this.
> I still use llnode constantly, even in its relatively broken state. I would like to find time to contribute to it, but it's been difficult being a one person...
> But maybe could we write down a list of things that could address the broken state of the project and see how could we improve it incrementally? Maybe with...
I commented on nodejs/llnode#399 with some more specific info on why Node 16 backtraces are broken. Anybody can grab it if they'd like; my plan is to pick it back...
Here's a script which does the JSON -> JUnit conversion: https://gist.github.com/kvakil/8ed172559f5bc3c8391ec34065682599 It seems to work on all the cases I tried locally (on Linux: passed, timeout, and failed test cases)....
> Seems like a good forward. Can I suggest you PR it to nodejs/node? I don't know how to hook it up to the CI but someone else no doubt...
I put an example of one eBPF thing I've done in #569, if you're interested.
I'm UTC-7, although also flexible.
[Here is my busy/free for that week in UTC+1](https://airtable.com/shrQIxBA6nSkUCarV/tbldTyua0PFCcQyNO), anything not colored is fine with me.
Sounds good to me.