Adding host support for json schemas in claims #1696
Annotations
12 errors and 18 warnings
Build and test (macos-11, 1.14.3, 25)
Command failed: cargo metadata --all-features --format-version 1
|
Build and test (macos-11, 1.14.3, 25)
error: could not find `Cargo.toml` in `/Users/runner/work/wasmcloud-otp/wasmcloud-otp` or any parent directory
|
Build and test (macos-11, 1.14.3, 25)
Error: ENOENT: no such file or directory, opendir '/Users/runner/work/wasmcloud-otp/wasmcloud-otp/target'
|
Build and test (macos-11, 1.14.3, 25)
Process completed with exit code 14.
|
Build and test (windows-2019, 1.14.3, 25)
Command failed: cargo metadata --all-features --format-version 1
|
Build and test (windows-2019, 1.14.3, 25)
error: could not find `Cargo.toml` in `D:\a\wasmcloud-otp\wasmcloud-otp` or any parent directory
|
Build and test (windows-2019, 1.14.3, 25)
Error: ENOENT: no such file or directory, opendir 'D:\a\wasmcloud-otp\wasmcloud-otp\target'
|
Build and test (windows-2019, 1.14.3, 25)
Error: ENOENT: no such file or directory, opendir 'C:\Users\runneradmin\.cargo\registry\index'
|
Build and test (windows-2019, 1.14.3, 25)
Process completed with exit code 1.
|
Build and test (ubuntu-20.04, 1.14.3, 25)
test Performing standard operations on actors can support builtin logging and numbergen invocations (HostCore.ActorsTest)
|
Build and test (ubuntu-20.04, 1.14.3, 25)
Process completed with exit code 2.
|
Build and test (ubuntu-20.04, 1.14.3, 25)
Process completed with exit code 14.
|
Build and test (macos-11, 1.14.3, 25)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2. 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 test (windows-2019, 1.14.3, 25)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2. 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 test (ubuntu-20.04, 1.14.3, 25)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2. 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 test (ubuntu-20.04, 1.14.3, 25)
unused alias ActorSupervisor
|
Build and test (ubuntu-20.04, 1.14.3, 25)
unused alias JetstreamClient
|
Build and test (ubuntu-20.04, 1.14.3, 25)
unused alias Native
|
Build and test (ubuntu-20.04, 1.14.3, 25)
unused alias VirtualHost
|
Build and test (ubuntu-20.04, 1.14.3, 25)
variable "seed" is unused (if the variable is not meant to be used, prefix it with an underscore)
|
Build and test (ubuntu-20.04, 1.14.3, 25)
Nested modules could be aliased at the top of the invoking module.
|
Build and test (ubuntu-20.04, 1.14.3, 25)
Nested modules could be aliased at the top of the invoking module.
|
Build and test (ubuntu-20.04, 1.14.3, 25)
Nested modules could be aliased at the top of the invoking module.
|
Build and test (ubuntu-20.04, 1.14.3, 25)
Nested modules could be aliased at the top of the invoking module.
|
Build and test (ubuntu-20.04, 1.14.3, 25)
Nested modules could be aliased at the top of the invoking module.
|
Build and test (ubuntu-20.04, 1.14.3, 25)
Nested modules could be aliased at the top of the invoking module.
|
Build and test (ubuntu-20.04, 1.14.3, 25)
Nested modules could be aliased at the top of the invoking module.
|
Build and test (ubuntu-20.04, 1.14.3, 25)
Nested modules could be aliased at the top of the invoking module.
|
Build and test (ubuntu-20.04, 1.14.3, 25)
Nested modules could be aliased at the top of the invoking module.
|
Build and test (ubuntu-20.04, 1.14.3, 25)
Nested modules could be aliased at the top of the invoking module.
|