Skip to content

Comments

Setup oxlint#85

Merged
modmuss50 merged 3 commits intoFabricMC:mainfrom
modmuss50:oxlint
Feb 15, 2026
Merged

Setup oxlint#85
modmuss50 merged 3 commits intoFabricMC:mainfrom
modmuss50:oxlint

Conversation

@modmuss50
Copy link
Member

No description provided.

@modmuss50 modmuss50 marked this pull request as ready for review February 15, 2026 15:44
Comment on lines 130 to 134
promises.push(new Promise(async (resolve) => {
while (true) {
const batch = taskQueue.splice(0, batchSize);
promises.push(new Promise((resolve) => {
const processQueue = async () => {
while (true) {
const batch = taskQueue.splice(0, batchSize);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This one is weird. Will the function not get awaited then?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll take a closer look, it wasn't happy about having an async function passed to the Promise constructor.

Copy link
Member Author

@modmuss50 modmuss50 Feb 15, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change here was correct and maintained the same behaviour as before, the processQueue function would not get awaited, but the promise stored in promises would complete correctly when resolve is called. I have refactored this to just have an inline async lambda, removing the need to use new Promise and call resolve.

@modmuss50 modmuss50 requested a review from deirn February 15, 2026 17:51
@modmuss50 modmuss50 merged commit b3d7562 into FabricMC:main Feb 15, 2026
4 checks passed
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

Successfully merging this pull request may close these issues.

2 participants