Fix spec for t:ExUnit.Callbacks.child_spec_overrides/2 #15006
Merged
+1
−5
Conversation
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
whatyouhide
added a commit
that referenced
this pull request
Dec 9, 2025
Member
Author
|
Done, pushed this commit over to the |
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.
Found out about this here: https://github.com/getsentry/sentry-elixir/actions/runs/20060145541/job/57534823122
I'm aware of #14611 but I think in this case it might just be borked. We can totally pass things like
:idand whatnot here, after all the implementation is just forwarding cleanly toSupervisor.child_spec/2. Ideally we'd remove this type altogether but I’m trying to be considerate of breaking changes (ExUnit.Callbacks.child_spec_overrides/0is public API and released).