Skip to content

Use <source> tags in translation prompt to prevent copying source lan… #18

Use <source> tags in translation prompt to prevent copying source lan…

Use <source> tags in translation prompt to prevent copying source lan… #18

Triggered via push March 23, 2026 17:53
Status Failure
Total duration 50s
Artifacts

ci.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 1 warning
test
Process completed with exit code 255.
test
Target "Build" has thrown an exception
test
/home/runner/work/LiveLingo/LiveLingo/src/LiveLingo.Core/Processing/QwenModelHost.cs(32,9): error CS0246: The type or namespace name 'ILlamaServerProcessManager' could not be found (are you missing a using directive or an assembly reference?) [/home/runner/work/LiveLingo/LiveLingo/src/LiveLingo.Core/LiveLingo.Core.csproj]
test
/home/runner/work/LiveLingo/LiveLingo/src/LiveLingo.Core/Processing/QwenModelHost.cs(12,22): error CS0246: The type or namespace name 'ILlamaServerProcessManager' could not be found (are you missing a using directive or an assembly reference?) [/home/runner/work/LiveLingo/LiveLingo/src/LiveLingo.Core/LiveLingo.Core.csproj]
test
/home/runner/work/LiveLingo/LiveLingo/src/LiveLingo.Core/Processing/QwenModelHost.cs(32,9): error CS0246: The type or namespace name 'ILlamaServerProcessManager' could not be found (are you missing a using directive or an assembly reference?) [/home/runner/work/LiveLingo/LiveLingo/src/LiveLingo.Core/LiveLingo.Core.csproj]
test
/home/runner/work/LiveLingo/LiveLingo/src/LiveLingo.Core/Processing/QwenModelHost.cs(12,22): error CS0246: The type or namespace name 'ILlamaServerProcessManager' could not be found (are you missing a using directive or an assembly reference?) [/home/runner/work/LiveLingo/LiveLingo/src/LiveLingo.Core/LiveLingo.Core.csproj]
test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-dotnet@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/