Repository navigation
K13.6: cap demo actions in the database - #141
Merged
Merged
Conversation
Demo starts were limited per serverless instance and fast-forward was unlimited, so a loop could fill the hosted database during judging. Closes #132
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.
Fix 6 from the pre-launch review (availability).
Problem: demo starts were rate-limited per serverless instance only, and Fast-forward (which writes rows every call) had no limit. A simple loop could fill the free Neon database and take the site down during judging.
Fix (on the shared limiter from K13.7, limits in
lib/server/demoLimits.ts):Tests: fast-forward cap with its message; global start cap. 148 total.
Docs: README status, ARCHITECTURE §4.1, ESSENTIALS, project_structure, ROADMAP.
Closes #132