Repository navigation
REV feed on a ten-minute cron, staged in steps within the free plan's CPU - #55
Merged
Merged
Conversation
[Medium impact] The PR appears safe to merge; both previously reported issues are addressed. SummarySchedules REV’s official feed every ten minutes while leaving vendor crawls paused. Downloads and staging run in separate steps before publication.
|
…leanup covers a batch written before a failed save
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
REV's official feed was published by hand on 2026-10-27 and nothing refreshed it, because every cron is paused. This schedules REV's feed job only; the four vendor crawls stay off.
CPU. Staging all 976 rows in one run took about 17 ms in a fresh Node process (parse 10 ms, stage 7 ms), over the free plan's 10 ms.
runRevFeednow takes one small step per run:Measured per step on the real feed, one fresh process each: 3.4–7.4 ms; idle runs 0.5–1.1 ms.
Schedule.
*/10 * * * *, mapped to REV incronVendors. An idle run writes nothing, an unchanged check writes one key, and a changed feed costs about 35 KV writes and deletes and goes live about 100 minutes after its download.Safety. A build is dropped, with its batches and saved body, when:
A SKU listed twice keeps its first row. The top-level ETag changes only when staging completes.
Tests: stepped staging, a duplicate SKU, a mostly unusable feed found halfway, abandonment by a manual publish, the three-hour cutoff, and the cron test (only REV scheduled).