Repository navigation
v0.27.1
Settings reach the read workers in order
v0.27.1 fixes a read-worker bug found by CI right after v0.27.0.
Fixes
- A read worker could keep the old rate limits for up to 5 seconds after a settings change. When a setting changed, each read worker dropped its rate-limit, CORS, email, storage and egress caches as soon as it heard which key changed, before it had read the new value; a request in between rebuilt them from the old one, and the rate limits kept that for their 5-second cache. The caches are now dropped once the new value is in. On v0.27.0 this mostly mattered on Linux, where the workers serve requests themselves.
Upgrade notes
- Nothing to do. The upgrade notes for v0.27.0 apply if you are coming from an earlier version, in particular: reads count toward rate limits again.
Full Changelog: v0.27.0...v0.27.1