From b69556c918e2a4a27b047e8de6b02861f04d5a9e Mon Sep 17 00:00:00 2001
From: Jacky Zhao <j.zhao2k19@gmail.com>
Date: Mon, 21 Aug 2023 23:43:32 +0000
Subject: [PATCH] fix: async-mutex not exclusively locking correectly
---
quartz/build.ts | 11 +++++++----
1 files changed, 7 insertions(+), 4 deletions(-)
diff --git a/quartz/build.ts b/quartz/build.ts
index 78437f8..0af39d0 100644
--- a/quartz/build.ts
+++ b/quartz/build.ts
@@ -108,12 +108,13 @@
toRemove.add(filePath)
}
- timeoutIds.forEach((id) => clearTimeout(id))
-
// debounce rebuilds every 250ms
timeoutIds.add(
setTimeout(async () => {
- await buildMutex.acquire()
+ const release = await buildMutex.acquire()
+ timeoutIds.forEach((id) => clearTimeout(id))
+ timeoutIds.clear()
+
const perf = new PerfTimer()
console.log(chalk.yellow("Detected change, rebuilding..."))
try {
@@ -134,6 +135,8 @@
contentMap.delete(fp)
}
+ // TODO: we can probably traverse the link graph to figure out what's safe to delete here
+ // instead of just deleting everything
await rimraf(argv.output)
const parsedFiles = [...contentMap.values()]
const filteredContent = filterContent(ctx, parsedFiles)
@@ -146,7 +149,7 @@
clientRefresh()
toRebuild.clear()
toRemove.clear()
- buildMutex.release()
+ release()
}, 250),
)
}
--
Gitblit v1.10.0