Repository navigation
Conversation
etcwilde
requested review from
cmcgee1024,
justice-adams-apple and
shahmishal
as code owners
November 11, 2026 18:50
I've heard a few offhand reports that something is causing a cycle in the Swiftly proxy mechanism, often related to clang and linking. I haven't been able to reproduce the cycle to determine what it's coming from so I'm adding tracking to see what tool calls are resulting in the cycle.
etcwilde
force-pushed
the
ewilde/track-swiftly-cycle
branch
from
November 12, 2026 00:31
b9d87ce to
1f01b2a
Compare
cmcgee1024
approved these changes
Nov 12, 2026
justice-adams-apple
approved these changes
Nov 12, 2026
This branch has not been deployed
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.
I've heard a few offhand reports that something is causing a cycle in the Swiftly proxy mechanism, often related to clang and linking. I haven't been able to reproduce the cycle to determine what it's coming from so I'm adding tracking to see what tool calls are resulting in the cycle.