Repository navigation
Conversation
Pin CI to OSL aeb83e39 (6.1.1). osl fix renamed serve.limitRequests to serve.rateLimit with the same limits and windows, and the record types to class. Test files that point a sibling's global at test values now do it inside a setup function, because OSL 6 reads a top-level assignment in a sibling file as a second declaration.
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.
Moves the API from OSL 3.0.0 (78deaec4) to the latest OSL, 6.1.1 (aeb83e39).
What changed
aeb83e39. AGENTS.md and README say OSL 6.1.osl fixrenamedserve.limitRequests(n, {window: ms})toserve.rateLimit({requests: n, window: date.minute | date.hour}). All 34 limits keep the same counts and windows. The route dump is identical apart from that spelling.osl fixrenamed the recordtypes toclass. They were already shared, so nothing copies differently.validGitFilePathmeant to refuse NUL bytes with"\x00". OSL 3.0 read that as the textx00, so it refused paths containing "x00" and let NUL through. OSL 6 reads it as NUL.Checks
osl test: 60 passed.osl lsp check main.oslis clean,osl compilepasses, andcheck_conventionspasses.e2e_smoke.py, comparingmainbuilt with OSL 3.0.0 against this branch built with 6.1.1: responses match.Before deploying
aeb83e39cross-compiled for the server (osl-aeb8), notosl-78de.c.ip()only trustsX-Forwarded-Forfrom 127.0.0.0/8 and ::1, and takes the rightmost untrusted address. It never readsX-Real-IP. With cloudflared on the same Mac this works unchanged, and is safer than before (3.0 trusted a spoofable leftmost value). If the proxy is on another host, every visitor would get the proxy's address, so the rate limits would apply site-wide and view dedup would merge visitors. In that case, passserve.new({trustProxy: [...]})inmain.osl. Check withpgrep -fl cloudflaredon the API host." 5".toNum()now gives 5 instead of 0, so numeric query values with surrounding spaces parse. Harmless.Version
1.0.0 → 1.0.1 (patch: toolchain move, no API change).
No screenshots: backend only, nothing visible changes.