Skip to content

move user.v files too #861

move user.v files too

move user.v files too #861

Triggered via push April 22, 2026 10:47
Status Failure
Total duration 2m 12s
Artifacts

ci.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

31 errors and 7 warnings
macos-clang
invalid variable `exists`
macos-clang
assignment mismatch: 2 variables but `check_username()` returns 0 values
macos-clang
unknown method or field: `App.check_username`.
macos-clang
`repo_owner` (no value) used as value
macos-clang
assignment mismatch: 1 variable but `get_username_by_id()` returns 0 values
macos-clang
unexpected `or` block, the function `get_username_by_id` does not return an Option or a Result
macos-clang
the default expression type in the `or` block should be `&App`, instead you gave a value of type `string`
macos-clang
unknown method or field: `App.get_username_by_id`.
macos-clang
unexpected `!`, the function `register_user` does not return a Result
macos-clang
unknown method or field: `App.register_user`
ubuntu-gcc
invalid variable `exists`
ubuntu-gcc
assignment mismatch: 2 variables but `check_username()` returns 0 values
ubuntu-gcc
unknown method or field: `App.check_username`.
ubuntu-gcc
`repo_owner` (no value) used as value
ubuntu-gcc
assignment mismatch: 1 variable but `get_username_by_id()` returns 0 values
ubuntu-gcc
unexpected `or` block, the function `get_username_by_id` does not return an Option or a Result
ubuntu-gcc
the default expression type in the `or` block should be `&App`, instead you gave a value of type `string`
ubuntu-gcc
unknown method or field: `App.get_username_by_id`.
ubuntu-gcc
unexpected `!`, the function `register_user` does not return a Result
ubuntu-gcc
unknown method or field: `App.register_user`
ubuntu-tcc
invalid variable `exists`
ubuntu-tcc
assignment mismatch: 2 variables but `check_username()` returns 0 values
ubuntu-tcc
unknown method or field: `App.check_username`.
ubuntu-tcc
`repo_owner` (no value) used as value
ubuntu-tcc
assignment mismatch: 1 variable but `get_username_by_id()` returns 0 values
ubuntu-tcc
unexpected `or` block, the function `get_username_by_id` does not return an Option or a Result
ubuntu-tcc
the default expression type in the `or` block should be `&App`, instead you gave a value of type `string`
ubuntu-tcc
unknown method or field: `App.get_username_by_id`.
ubuntu-tcc
unexpected `!`, the function `register_user` does not return a Result
ubuntu-tcc
unknown method or field: `App.register_user`
windows-gcc
Process completed with exit code 1.
macos-clang
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
macos-clang
casting `&C.git_object` to `&C.git_commit` is only allowed in `unsafe` code
ubuntu-gcc
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
ubuntu-gcc
casting `&C.git_object` to `&C.git_commit` is only allowed in `unsafe` code
ubuntu-tcc
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
ubuntu-tcc
casting `&C.git_object` to `&C.git_commit` is only allowed in `unsafe` code
windows-gcc
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/