Skip to content
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

Node.js Loaders Team Meeting 2024-01-16 #181

Closed
mhdawson opened this issue Jan 12, 2024 · 2 comments
Closed

Node.js Loaders Team Meeting 2024-01-16 #181

mhdawson opened this issue Jan 12, 2024 · 2 comments
Assignees

Comments

@mhdawson
Copy link
Member

Time

UTC Tue 16-Jan-2024 19:00 (07:00 PM):

Timezone Date/Time
US / Pacific Tue 16-Jan-2024 11:00 (11:00 AM)
US / Mountain Tue 16-Jan-2024 12:00 (12:00 PM)
US / Central Tue 16-Jan-2024 13:00 (01:00 PM)
US / Eastern Tue 16-Jan-2024 14:00 (02:00 PM)
EU / Western Tue 16-Jan-2024 19:00 (07:00 PM)
EU / Central Tue 16-Jan-2024 20:00 (08:00 PM)
EU / Eastern Tue 16-Jan-2024 21:00 (09:00 PM)
Moscow Tue 16-Jan-2024 22:00 (10:00 PM)
Chennai Wed 17-Jan-2024 00:30 (12:30 AM)
Hangzhou Wed 17-Jan-2024 03:00 (03:00 AM)
Tokyo Wed 17-Jan-2024 04:00 (04:00 AM)
Sydney Wed 17-Jan-2024 06:00 (06:00 AM)

Or in your local time:

Links

Agenda

Extracted from loaders-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/node

  • ESM Hook deadlocks since 21.2.0 a3e09b3 #50948

Invited

  • Loaders team: @nodejs/loaders

Observers/Guests

Notes

The agenda comes from issues labelled with loaders-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

@mhdawson mhdawson self-assigned this Jan 12, 2024
@GeoffreyBooth
Copy link
Member

So we still have nodejs/node#50948 to fix, and nodejs/node#50752 is a start at tackling it; and I have a WIP branch at https://github.com/nodejs/node/compare/main…GeoffreyBooth:node:fix-spawning-hooks-thread-wip. I was also recently chatting with @mcollina about it, since I’m too swamped from work for the next few months to devote time to this (and it’s out of my comfort zone, with all the stuff about how Node spawns workers). Anyone have any bandwidth to help with this? This should be the last thing we need to fix in order to move the remaining parts of the API to stable.

@GeoffreyBooth
Copy link
Member

Seems like no attendees today so I’ll cancel.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants