Feature/modulized generated devices parameters #69
Annotations
7 errors and 11 warnings
|
Build
Process completed with exit code 1.
|
|
Build:
RDMSharpTests/Devices/Mock/MockGeneratedDevice1.cs#L71
The type or namespace name 'StatusMessageModule' could not be found (are you missing a using directive or an assembly reference?)
|
|
Build:
RDMSharpTests/Devices/Mock/MockGeneratedDeviceWithSubDevice1.cs#L97
The type or namespace name 'StatusMessageModule' could not be found (are you missing a using directive or an assembly reference?)
|
|
Build:
RDMSharpTests/Devices/Mock/MockGeneratedDeviceWithSubDevice1.cs#L51
The type or namespace name 'StatusMessageModule' could not be found (are you missing a using directive or an assembly reference?)
|
|
Build:
RDMSharpTests/Devices/Mock/MockGeneratedDevice1.cs#L71
The type or namespace name 'StatusMessageModule' could not be found (are you missing a using directive or an assembly reference?)
|
|
Build:
RDMSharpTests/Devices/Mock/MockGeneratedDeviceWithSubDevice1.cs#L97
The type or namespace name 'StatusMessageModule' could not be found (are you missing a using directive or an assembly reference?)
|
|
Build:
RDMSharpTests/Devices/Mock/MockGeneratedDeviceWithSubDevice1.cs#L51
The type or namespace name 'StatusMessageModule' could not be found (are you missing a using directive or an assembly reference?)
|
|
Complete job
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/setup-dotnet@v4.2.0, actions/upload-artifact@v4.6.0. 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/
|
|
Build:
RDMSharp/RDM/Device/AbstractGeneratedRDMDevice.cs#L109
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build:
RDMSharp/RDM/Device/AbstractGeneratedRDMDevice.cs#L108
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build:
RDMSharp/RDM/Device/AbstractGeneratedRDMDevice.cs#L107
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build:
RDMSharp/RDM/Device/Module/IModule.cs#L11
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build:
RDMSharp/RDM/Device/Module/AbstractModule.cs#L111
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build:
RDMSharp/RDM/Device/Module/AbstractModule.cs#L111
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build:
RDMSharp/RDM/Device/Module/AbstractModule.cs#L69
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build:
RDMSharp/RDM/Device/Module/AbstractModule.cs#L47
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build:
RDMSharp/RDMSharp.cs#L25
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build:
RDMSharp/RDMSharp.cs#L24
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
Loading