chore: bump release to v1.50.12 - #3968
Merged
Merged
Conversation
Prod runs v1.50.11. This release carries the fixes for the process and memory growth seen on prod-c since 2026-09-07: - #3865 stops the requested backend child. On v1.50.11 `SourceSup.stop_backend_child/2` stops the newest child instead, so a detached backend tree never stops and the attached backend gets killed on every `SourceSupWorker` tick. - #3944 bounds S3 upload stalls with HTTP timeouts and 3 retries instead of ExAws' default 10. - #3945 caps the S3 batcher demand at 100 and acks failed batches, so a stalled bucket no longer pulls the whole queue into GenStage buffers. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YQ8Y8zCvSKUFNPvkwH2WS4
djwhitt
approved these changes
Sep 12, 2026
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
2 participants
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.
Bumps
VERSIONto 1.50.12. Prod runs v1.50.11 on prod-c/e/f/a since 2026-09-07, and prod-b/d/g run v1.50.7.Why now
This release carries the fixes for the process and memory growth on prod-c (213K processes, 46 GB RSS, ~11 GB of binaries pinned under a stale
S3Adaptortree for one source). Local reproduction against thev1.50.11tag confirmed two of the mechanisms; see.plans/2026-09-12_01_process-leak-investigation.md(not in this PR).SourceSup.stop_backend_child/2passes its arguments toEnum.find_value/3in the wrong order and always stops the newest backend child.Supervisor.which_children/1lists newest first. With a detached backend that is not the newest child, everySourceSupWorkertick re-adds the attached backend and then kills it again. Locally: the detached tree survives, and the attached backend is present in 12 of 300 samples. Onmainboth orders pass.main.main(18 MB pinned).Also in
v1.50.11..main: cache warmer fixes (#3913, #3915, #3916), ClickHouse telemetry (#3950, #3952, #3962), read replica read-only connections (#3902), mapper follow-ups, and the anti-slop tooling (#3899).Rollout
Canary first. Watch
:erlang.system_info(:process_count),length(:ets.all())and:erlang.memory(:binary)for 24 h against a non-canary node.🤖 Generated with Claude Code
https://claude.ai/code/session_01YQ8Y8zCvSKUFNPvkwH2WS4