-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
core dump collaboration call #402
Comments
Awesome @No9 I will be available after 5th August. My timezone is UTC+2 I can be flexible regarding hours |
I'm UTC-7, although also flexible. |
I'm in +8 right now, but working late, so I overlap with Europe and East Coast US business hours. I'm generally online until at least noon NYC time but another hour or two later is probably fine. |
OK I'm UTC +1 |
Here is my busy/free for that week in UTC+1, anything not colored is fine with me. |
I wouldn't worry about me being in a far off time zone from everyone else. I'm currently overlapping hours completely with Europe and East Coast North America time. I can also overlap with West Coast if that's preferable. My schedule is whatever I make it. 😅 Also, my availability is basically any day. I have very few meetings and they're mostly moveable. |
Sounds great :) |
OK Looks like Tuesday 9th 8pm UTC +1 works. If not we can target 11th or 12th. |
Sounds good to me.
|
I put a slot for the 9th on my agenda. In case you'll create an event, it's my email: [email protected] 👍 |
Anton Whalley is inviting you to a scheduled Zoom meeting. Topic: Core Dump Collaboration Join Zoom Meeting Meeting ID: 826 3225 8155 Dial by your location |
Hi @No9! Unfortunately, I wouldn't be able to participate (this week will be quite busy for me). Would you mind recording the session so I can watch it later? |
Dublin is UTC +1 ? |
Will do @RafaelGSS |
I'll have to skip. That's 1am my current time. Perhaps it could be recorded though? |
I'm on the call 👋 cc @No9 |
(I'm also confused; the zoom invitation says "07:00 PM Dublin", but I thought we were meeting at "8pm UTC +1". Anyway either works for me, just ping me here when we start?) |
Same for me |
OK Sorry about this - I'll open in 30 mins 8pm Dublin |
We're are on the call peeps 👋 |
Thanks @tony-go @kvakil for joining - great to have a bit of momentum in the project. |
Status update: I put up #404 which partially fixes Node v16. Backtrace is fully functional. Unfortunately it breaks Node v14 as written. My next step will be to add a bunch of if-statements based on postmortem metadata to make sure v14 continues working. I hope to get time to do that sometime this week & clean it up for review. |
Good stuff @kvakil - Great to see so much progress. @Qard @tony-go @RafaelGSS @kvakil |
It will be in the middle of the Diagnostics WG Meeting, won't it? https://nodejs.org/calendar. We can use the Diagnostics WG slot as well (this is fully diagnostics related) |
DWG time slot works for me. |
Grand - If everyone else is OK lets go for the DWG |
@Qard @kvakil @tony-go
Following on from the diagnostics session 2022-07-26
It was suggested to have a followup call on backlog items specific to this project and discuss the
debug_helper
approach that Keyhan brought up.If you can support this would you mind putting in your timezone and preferred times in this issue and we can set something up.
The text was updated successfully, but these errors were encountered: