feat: add system restart action to ASV SDR protocol #58
Annotations
1 error and 18 warnings
Deploy
Process completed with exit code 1.
|
Deploy
The following actions uses node12 which is deprecated and will be forced to run on node16: battila7/get-version-action@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Deploy:
src/Asv.Mavlink/Microservices/Ftp/Client/IFtpClient.cs#L116
XML comment has badly formed XML -- 'End tag 'summary' does not match the start tag 'offset'.'
|
Deploy:
src/Asv.Mavlink/Protocol/Messages/common.cs#L2580
XML comment has badly formed XML -- 'An identifier was expected.'
|
Deploy:
src/Asv.Mavlink/Tools/Browser/IMavlinkDeviceBrowser.cs#L20
XML comment has badly formed XML -- 'An identifier was expected.'
|
Deploy:
src/Asv.Mavlink/Microservices/Ftp/Client/IFtpClient.cs#L117
XML comment has badly formed XML -- 'Expected an end tag for element 'path'.'
|
Deploy:
src/Asv.Mavlink/Protocol/Messages/common.cs#L2580
XML comment has badly formed XML -- '0'
|
Deploy:
src/Asv.Mavlink/Microservices/Ftp/Client/IFtpClient.cs#L117
XML comment has badly formed XML -- 'Expected an end tag for element 'summary'.'
|
Deploy:
src/Asv.Mavlink/Tools/Browser/IMavlinkDeviceBrowser.cs#L20
XML comment has badly formed XML -- 'An identifier was expected.'
|
Deploy:
src/Asv.Mavlink/Protocol/Messages/common.cs#L2590
XML comment has badly formed XML -- 'End tag 'summary' does not match the start tag ''.'
|
Deploy:
src/Asv.Mavlink/Tools/Browser/IMavlinkDeviceBrowser.cs#L20
XML comment has badly formed XML -- '8'
|
Deploy:
src/Asv.Mavlink/Protocol/Messages/common.cs#L2591
XML comment has badly formed XML -- 'Expected an end tag for element 'summary'.'
|
Deploy
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/
|
Deploy
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/
|
Deploy
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/
|
Deploy
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/
|
Deploy
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/
|
Deploy
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/
|
Deploy
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/
|