Node.js Diagnostics WorkGroup Meeting 2026-01-15

Open
#677 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
15/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
node.js
Domain
documentation

Research direction

No files, tests, or implementation entry points are named. This issue records a Diagnostics WorkGroup meeting agenda and links minutes, but provides no concrete change or completion criterion for a contributor.

Written by the indexing model from the issue text.

Description

Time

UTC Thu, Jan 15, 2026, 05:00 PM:

Timezone Date/Time
US / Pacific Thu, Jan 15, 2026, 09:00 AM
US / Mountain Thu, Jan 15, 2026, 10:00 AM
US / Central Thu, Jan 15, 2026, 11:00 AM
US / Eastern Thu, Jan 15, 2026, 12:00 PM
EU / Western Thu, Jan 15, 2026, 05:00 PM
EU / Central Thu, Jan 15, 2026, 06:00 PM
EU / Eastern Thu, Jan 15, 2026, 07:00 PM
Moscow Thu, Jan 15, 2026, 08:00 PM
Chennai Thu, Jan 15, 2026, 10:30 PM
Hangzhou Fri, Jan 16, 2026, 01:00 AM
Tokyo Fri, Jan 16, 2026, 02:00 AM
Sydney Fri, Jan 16, 2026, 04:00 AM

Or in your local time:

Links

Agenda

Extracted from diag-agenda labelled issues and pull requests from the nodejs org prior to the meeting. (Updated daily)

nodejs/node
  • Port/Duplicate async_hooks tests to use AsyncLocalStore #55712

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

Dominant language
No language data
Stars
550
Forks
69
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nodejs/diagnostics

All issues in nodejs/diagnostics

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.