Node.js Diagnostics WorkGroup Meeting 2025-07-10
@mhdawson is already working on this.
Since Jul 7, 2025.
Assessment
This issue has not been assessed yet.
Description
Time
UTC Thu 10-Jul-2025 16:00 (04:00 PM):
| Timezone | Date/Time |
|---|---|
| US / Pacific | Thu 10-Jul-2025 09:00 (09:00 AM) |
| US / Mountain | Thu 10-Jul-2025 10:00 (10:00 AM) |
| US / Central | Thu 10-Jul-2025 11:00 (11:00 AM) |
| US / Eastern | Thu 10-Jul-2025 12:00 (12:00 PM) |
| EU / Western | Thu 10-Jul-2025 17:00 (05:00 PM) |
| EU / Central | Thu 10-Jul-2025 18:00 (06:00 PM) |
| EU / Eastern | Thu 10-Jul-2025 19:00 (07:00 PM) |
| Moscow | Thu 10-Jul-2025 19:00 (07:00 PM) |
| Chennai | Thu 10-Jul-2025 21:30 (09:30 PM) |
| Hangzhou | Fri 11-Jul-2025 00:00 (12:00 AM) |
| Tokyo | Fri 11-Jul-2025 01:00 (01:00 AM) |
| Sydney | Fri 11-Jul-2025 02:00 (02:00 AM) |
Or in your local time:
- https://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Diagnostics%20WorkGroup+Meeting+2025-07-10&iso=20250710T1600
- or https://www.wolframalpha.com/input/?i=04PM+UTC%2C+Jul+10%2C+2025+in+local+time
Links
- Minutes Google Doc: https://docs.google.com/document/d/11k4YNtDjGtuY_TURZqkcEmirKt8A-XvZQhLkCtf6mWk/edit
Agenda
Extracted from diag-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/node
- Port/Duplicate async_hooks tests to use AsyncLocalStore #55712
nodejs/import-in-the-middle
- chore: npm ignore several files used for dev #137
Invited
- Diagnostics team: @nodejs/diagnostics
Observers/Guests
Notes
The agenda comes from issues labelled with diag-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.
Joining the meeting
- link for participants: https://zoom.us/j/466707925
- For those who just want to watch:
- youtube admin page: https://www.youtube.com/my_live_events?filter=scheduled
- Dominant language
- No language data
- Stars
- 550
- Forks
- 69
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nodejs/diagnostics
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
nodejs/diagnostics#648 · 3 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 20/100
nodejs/diagnostics#690 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 20/100
nodejs/diagnostics#689 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 25/100
nodejs/diagnostics#688 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
nodejs/diagnostics#687 ·