Skip to content

Conversation

@nullfunc
Copy link
Contributor

This change will return a response to the /trigger-rebuild end point after starting cache rebuild. Instead of waiting for refresh
to complete. This change also fixes issue where only one thread handles /trigger-rebuild and so other threads aren't aware of cache changes. The timestamp of the cache files are check each time to be the most recent cache.

fixes defang-docs #271
fixes #105

Eric Liu added 3 commits August 12, 2025 16:29
…will allow the next step for multiple threads to check if they have the most recent cached file
@nullfunc nullfunc changed the title fix rebuild rigger fix rebuild trigger response for CI Aug 13, 2025
@nullfunc nullfunc merged commit d6ba9f0 into main Aug 14, 2025
5 checks passed
@nullfunc nullfunc deleted the eric/make-rebuild-run-in-background branch August 14, 2025 16:59
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.

CI fails with 502 /trigger-rebuild will not update in-memory kb for sibling processes

3 participants