You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
________________________________
From: github-actions[bot] ***@***.***>
Sent: Saturday, October 26, 2024 1:01:33 PM
To: domaindrivendev/Swashbuckle.AspNetCore ***@***.***>
Cc: wizofaus ***@***.***>; Author ***@***.***>
Subject: Re: [domaindrivendev/Swashbuckle.AspNetCore] [Bug]: Swashbuckle hangs generating swagger.json for certain public Controller functions not intended as endpoints (Issue #3047)
This issue is stale because it has been open for 60 days with no activity. It will be automatically closed in 14 days if no further updates are made.
—
Reply to this email directly, view it on GitHub<#3047 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABI5UAJ5PAY4HRFBOCIQKCLZ5LZX3AVCNFSM6AAAAABNDEO5DWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZZGE3TIOBWGI>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
Describe the bug
I had a function on a controller with a signature
public async Task LookupOrCreateFoo(ScanFooResponse scanFooResponse, IProfileOperations profileOperations, Func<Task<byte[]>> getInvoice)
that just by the virtue of existing caused the swagger middle ware that generates swagger.json to hang.
It appears specifically it's hanging inside DefaultApiDescriptionProvider.OnProvidersExecuting( ) so it may even be a .NET bug.
Removing "public" from the signature fixed it (it didn't need to be public).
Expected behavior
Shouldn't hang.
Actual behavior
Attempt to request swagger.json is never responded to.
Steps to reproduce
No response
Exception(s) (if any)
No response
Swashbuckle.AspNetCore version
6.7.2
.NET Version
8.0
Anything else?
Didn't happen prior to upgrading to .NET 8/Swashbuckle 6.7.2
Had observed previously when I had a public OnActionExecuting( ) function in a controller too.
The text was updated successfully, but these errors were encountered: