Release 1.12.8 #54
Annotations
10 errors and 13 warnings
build:
Source/NineDofImuWing/Driver/NineDofImuWing.cs#L1
The type or namespace name 'Sensors' does not exist in the namespace 'Meadow.Foundation' (are you missing an assembly reference?)
|
build:
Source/NineDofImuWing/Driver/NineDofImuWing.cs#L2
The type or namespace name 'Hardware' does not exist in the namespace 'Meadow' (are you missing an assembly reference?)
|
build:
Source/NineDofImuWing/Driver/NineDofImuWing.cs#L3
The type or namespace name 'Peripherals' does not exist in the namespace 'Meadow' (are you missing an assembly reference?)
|
build:
Source/NineDofImuWing/Driver/NineDofImuWing.cs#L4
The type or namespace name 'Peripherals' does not exist in the namespace 'Meadow' (are you missing an assembly reference?)
|
build:
Source/NineDofImuWing/Driver/NineDofImuWing.cs#L5
The type or namespace name 'Units' does not exist in the namespace 'Meadow' (are you missing an assembly reference?)
|
build:
Source/NineDofImuWing/Driver/NineDofImuWing.cs#L15
The type or namespace name 'PollingSensorBase<>' could not be found (are you missing a using directive or an assembly reference?)
|
build:
Source/NineDofImuWing/Driver/NineDofImuWing.cs#L15
The type or namespace name 'Acceleration3D' could not be found (are you missing a using directive or an assembly reference?)
|
build:
Source/NineDofImuWing/Driver/NineDofImuWing.cs#L15
The type or namespace name 'AngularVelocity3D' could not be found (are you missing a using directive or an assembly reference?)
|
build:
Source/NineDofImuWing/Driver/NineDofImuWing.cs#L15
The type or namespace name 'MagneticField3D' could not be found (are you missing a using directive or an assembly reference?)
|
build:
Source/NineDofImuWing/Driver/NineDofImuWing.cs#L16
The type or namespace name 'IAccelerometer' could not be found (are you missing a using directive or an assembly reference?)
|
build
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-dotnet@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
build
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
build:
Source/KeyboardWing/Driver/KeyboardWing.cs#L67
Cannot convert null literal to non-nullable reference type.
|
build:
Source/MotorWing/Driver/StepperMotor.cs#L39
Non-nullable field 'portA' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
build:
Source/MotorWing/Driver/StepperMotor.cs#L39
Non-nullable field 'portB' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
build:
Source/MotorWing/Driver/DCMotor.cs#L21
Non-nullable field 'pwmPort' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
build:
Source/MotorWing/Driver/DCMotor.cs#L21
Non-nullable field 'in1' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
build:
Source/MotorWing/Driver/DCMotor.cs#L21
Non-nullable field 'in2' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
build:
Source/MotorWing/Driver/StepperMotor.cs#L14
The field 'StepperMotor.portA' is never used
|
build:
Source/MotorWing/Driver/StepperMotor.cs#L15
The field 'StepperMotor.portB' is never used
|
build:
Source/ServoWing/Driver/ServoWing.cs#L66
Possible null reference argument for parameter 'pin' in 'IPwmPort Pca9685.CreatePwmPort(IPin pin, float dutyCycle = 0.5, bool invert = false)'.
|
build:
Source/ServoWing/Driver/ServoWing.cs#L82
Possible null reference argument for parameter 'pin' in 'IPwmPort Pca9685.CreatePwmPort(IPin pin, float dutyCycle = 0.5, bool invert = false)'.
|
build
.NET 7.0 is no longer supported and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the .NET support policy.
|