Workflow updates #30
Annotations
10 warnings
build (ubuntu-24.04):
EmpireCompiler/Program.cs#L45
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 (ubuntu-24.04):
EmpireCompiler/Core/Common.cs#L10
'System.Reflection.Assembly.Location' always returns an empty string for assemblies embedded in a single-file app. If the path to the app directory is needed, consider calling 'System.AppContext.BaseDirectory'.
|
build (ubuntu-24.04-arm):
EmpireCompiler/Program.cs#L45
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 (ubuntu-24.04-arm):
EmpireCompiler/Core/Common.cs#L10
'System.Reflection.Assembly.Location' always returns an empty string for assemblies embedded in a single-file app. If the path to the app directory is needed, consider calling 'System.AppContext.BaseDirectory'.
|
build (macos-15)
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
|
build (macos-15):
EmpireCompiler/Program.cs#L45
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 (macos-15):
EmpireCompiler/Core/Common.cs#L10
'System.Reflection.Assembly.Location' always returns an empty string for assemblies embedded in a single-file app. If the path to the app directory is needed, consider calling 'System.AppContext.BaseDirectory'.
|
build (macos-13)
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
|
build (macos-13):
EmpireCompiler/Program.cs#L45
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 (macos-13):
EmpireCompiler/Core/Common.cs#L10
'System.Reflection.Assembly.Location' always returns an empty string for assemblies embedded in a single-file app. If the path to the app directory is needed, consider calling 'System.AppContext.BaseDirectory'.
|
Artifacts
Produced during runtime
Name | Size | Digest | |
---|---|---|---|
EmpireCompiler-linux-arm64
Expired
|
94 MB |
sha256:4c9374be8c38432eb8f38ff283edcdbd823607b780a9130c5b9ceffbfe32db15
|
|
EmpireCompiler-linux-x64
Expired
|
95.9 MB |
sha256:fb50e3cf86fe56cfdd8ef14d74def6417c8b37e540300d30d1f6c10cff057cb2
|
|
EmpireCompiler-osx-arm64
Expired
|
94.8 MB |
sha256:85b15328aa739e81ea811ffb6d81060ec90994890faa02688cdde9994714bad3
|
|
EmpireCompiler-osx-x64
Expired
|
96.6 MB |
sha256:e2704fe1ebf17f872ae2f51a402a7722f87b8eb784f4afed45ee512672619529
|
|