[Java,C#,C++] Support field access order checking #962
ZachBrayci.yml
on: pull_request
Matrix: cpp-clang-2004-build
Matrix: cpp-clang-2204-build
Matrix: cpp-clang-macos-build
Matrix: cpp-gcc-2004-build
Matrix: cpp-gcc-2204-build
Matrix: C++ MSVC (Windows)
Matrix: csharp-build
Matrix: java-build
Matrix: rust-build
Annotations
10 errors and 15 warnings
|
C# 3.1.301:
csharp/sbe-tests/FieldAccessOrderCheckTests.cs#L34
'MultipleVarLength' does not contain a definition for 'CheckEncodingIsComplete' and no accessible extension method 'CheckEncodingIsComplete' accepting a first argument of type 'MultipleVarLength' could be found (are you missing a using directive or an assembly reference?)
|
|
C# 3.1.301:
csharp/sbe-tests/FieldAccessOrderCheckTests.cs#L53
'MultipleVarLength' does not contain a definition for 'CheckEncodingIsComplete' and no accessible extension method 'CheckEncodingIsComplete' accepting a first argument of type 'MultipleVarLength' could be found (are you missing a using directive or an assembly reference?)
|
|
C# 3.1.301:
csharp/sbe-tests/FieldAccessOrderCheckTests.cs#L176
'MultipleVarLength' does not contain a definition for 'CheckEncodingIsComplete' and no accessible extension method 'CheckEncodingIsComplete' accepting a first argument of type 'MultipleVarLength' could be found (are you missing a using directive or an assembly reference?)
|
|
C# 3.1.301:
csharp/sbe-tests/FieldAccessOrderCheckTests.cs#L195
'GroupAndVarLength' does not contain a definition for 'CheckEncodingIsComplete' and no accessible extension method 'CheckEncodingIsComplete' accepting a first argument of type 'GroupAndVarLength' could be found (are you missing a using directive or an assembly reference?)
|
|
C# 3.1.301:
csharp/sbe-tests/FieldAccessOrderCheckTests.cs#L216
'GroupAndVarLength' does not contain a definition for 'CheckEncodingIsComplete' and no accessible extension method 'CheckEncodingIsComplete' accepting a first argument of type 'GroupAndVarLength' could be found (are you missing a using directive or an assembly reference?)
|
|
C# 3.1.301:
csharp/sbe-tests/FieldAccessOrderCheckTests.cs#L235
'GroupAndVarLength' does not contain a definition for 'CheckEncodingIsComplete' and no accessible extension method 'CheckEncodingIsComplete' accepting a first argument of type 'GroupAndVarLength' could be found (are you missing a using directive or an assembly reference?)
|
|
C# 3.1.301:
csharp/sbe-tests/FieldAccessOrderCheckTests.cs#L254
'GroupAndVarLength' does not contain a definition for 'CheckEncodingIsComplete' and no accessible extension method 'CheckEncodingIsComplete' accepting a first argument of type 'GroupAndVarLength' could be found (are you missing a using directive or an assembly reference?)
|
|
C# 3.1.301:
csharp/sbe-tests/FieldAccessOrderCheckTests.cs#L275
'GroupAndVarLength' does not contain a definition for 'CheckEncodingIsComplete' and no accessible extension method 'CheckEncodingIsComplete' accepting a first argument of type 'GroupAndVarLength' could be found (are you missing a using directive or an assembly reference?)
|
|
C# 3.1.301:
csharp/sbe-tests/FieldAccessOrderCheckTests.cs#L324
'GroupAndVarLength' does not contain a definition for 'CheckEncodingIsComplete' and no accessible extension method 'CheckEncodingIsComplete' accepting a first argument of type 'GroupAndVarLength' could be found (are you missing a using directive or an assembly reference?)
|
|
C# 3.1.301:
csharp/sbe-tests/FieldAccessOrderCheckTests.cs#L394
'GroupAndVarLength' does not contain a definition for 'CheckEncodingIsComplete' and no accessible extension method 'CheckEncodingIsComplete' accepting a first argument of type 'GroupAndVarLength' could be found (are you missing a using directive or an assembly reference?)
|
|
Rust beta
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Rust beta
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Rust beta
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Rust beta
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Rust beta
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Rust nightly
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Rust nightly
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Rust nightly
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Rust nightly
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Rust nightly
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Rust stable
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Rust stable
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Rust stable
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Rust stable
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Rust stable
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|