-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Typer 0.12.2 breaks test suite #12617
Comments
Sorry about this! I think fastapi/typer#796 will fix things again. |
Thanks! No worries
When you release a fix do you intend to yank 0.12.2 - no worries either way
just need to figure out whether I need to exclude it in perpetuity or not
…On Tue, Apr 9, 2024 at 4:00 AM Sofie Van Landeghem ***@***.***> wrote:
Sorry about this! I think fastapi/typer#796
<fastapi/typer#796> will fix things again.
—
Reply to this email directly, view it on GitHub
<#12617 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AH4DG2LWWYIR6XSCNSB7OOTY4ONYTAVCNFSM6AAAAABF5ON5DKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBUGM4DANZSGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Typer 0.12.3 just released 🚀 Thanks @svlandeg for the fix! |
It's up to you, of course, but if this bug was only breaking your test suite I think the new release should fix that for you, as the test suite will always install the latest. Other than that, I'd expect this bug to show up only in edge cases, so I'm not sure it's worth yanking for. |
@aaazzam - since this is fixed in Typer 0.12.3, I'm closing this issue. Feel free to let me know if you want it re-opened. |
First check
Bug summary
Typer 0.12.2 breaks OSS test suite, specifically
test_pluralized_subcommands_have_multiple_valid_invocations
in our cli tests.Specifically fastapi/typer#567, which appears to build a list of subcommands for better rendering but in doing so calls max instead of length on an empty array, which throws an error.
Reproduction
Error
No response
Versions
Additional context
No response
The text was updated successfully, but these errors were encountered: