Improved dynamic card scaling #14
forrestcoward
build-and-deploy
3m 16s
Annotations
5 errors and 7 warnings
|
build-and-deploy
Failed to deploy web package to App Service.
|
|
build-and-deploy
Execution Exception (state: PublishContent) (step: Invocation)
|
|
build-and-deploy
When request Azure resource at PublishContent, zipDeploy : Failed to use D:\a\_temp\temp_web_package_7375624835348122.zip as ZipDeploy content
|
|
build-and-deploy
Package deployment using ZIP Deploy failed. Refer logs for more details.
|
|
build-and-deploy
Deployment Failed!
|
|
build-and-deploy
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-dotnet@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
build-and-deploy:
api/MTG.CardGenerator/ImageGenerator.cs#L45
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
build-and-deploy:
api/MTG.CardGenerator/ImageGenerator.cs#L79
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
build-and-deploy:
api/MTG.CardGenerator/GenerateImageFunction.cs#L18
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
build-and-deploy:
api/MTG.CardGenerator/ImageGenerator.cs#L45
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
build-and-deploy:
api/MTG.CardGenerator/ImageGenerator.cs#L79
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
build-and-deploy:
api/MTG.CardGenerator/GenerateImageFunction.cs#L18
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|