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
My .NET solution has a project that uses a dotnet tool command to generate code from an OpenApi spec, this works fine in my GH workflows and local environment but fails in the CodeQL action. The CodeQL action attempts to inject invalid parameters to this command. I've found an old PR that attempts to fix a very similar issue #13794, but that does not seem to fix my issue. I think this issue happened on the version v2 of the codeql actions as well.
Thanks for reporting this problem and including as much information as you have -- that's all very helpful! Judging by the build log, it does indeed look like we incorrectly inject the extra arguments here.
I will investigate this a bit further and see if we can get this fixed.
I think the team actually already merged a change last week which should address this in the next CodeQL release (2.16.4). The next release should become available later this week.
Could you try the new version once it becomes available and report back whether the problem is resolved for you then?
My .NET solution has a project that uses a
dotnet toolcommand to generate code from an OpenApi spec, this works fine in my GH workflows and local environment but fails in the CodeQL action. The CodeQL action attempts to inject invalid parameters to this command. I've found an old PR that attempts to fix a very similar issue #13794, but that does not seem to fix my issue. I think this issue happened on the version v2 of the codeql actions as well.dotnet-tools.jsonfile:global.json(This already happened when the project was in .NET 6):SwaggerDefinition.csprojof the project that fails:SwaggerDefinition projectcontent:The error in the CodeQL GH workflow:
codeql.yaml:The project is private and can't be shared, so I can't provide a link to it.
The text was updated successfully, but these errors were encountered: