Skip to content

组建5节点集群,需要考虑进程内多个服务端会因为容器而导致对象冲突的问题 #47

组建5节点集群,需要考虑进程内多个服务端会因为容器而导致对象冲突的问题

组建5节点集群,需要考虑进程内多个服务端会因为容器而导致对象冲突的问题 #47

Triggered via push March 23, 2024 00:59
Status Failure
Total duration 37s
Artifacts

test.yml

on: push
build-publish
29s
build-publish
Fit to window
Zoom out
Zoom in

Annotations

1 error and 11 warnings
build-publish
Process completed with exit code 1.
build-publish
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-dotnet@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build-publish: NewLife.MQTT/Models/SubscriptionManager.cs#L24
XML comment has badly formed XML -- 'End tag 'code' does not match the start tag 'string'.'
build-publish: NewLife.MQTT/Models/SubscriptionManager.cs#L25
XML comment has badly formed XML -- 'End tag 'remarks' does not match the start tag 'string'.'
build-publish: NewLife.MQTT/Models/SubscriptionManager.cs#L26
XML comment has badly formed XML -- 'Expected an end tag for element 'code'.'
build-publish: NewLife.MQTT/Models/SubscriptionManager.cs#L26
XML comment has badly formed XML -- 'Expected an end tag for element 'remarks'.'
build-publish: NewLife.MQTT/Clusters/ClusterServer.cs#L74
Nullability of reference types in type of parameter 'reason' of 'void ClusterServer.Stop(string reason)' doesn't match implicitly implemented member 'void IServer.Stop(string? reason)' (possibly because of nullability attributes).
build-publish: NewLife.MQTT/Messaging/MqttMessage.cs#L79
Nullability of reference types in type of parameter 'context' of 'bool MqttMessage.Read(Stream stream, object context)' doesn't match implicitly implemented member 'bool IAccessor.Read(Stream stream, object? context)' (possibly because of nullability attributes).
build-publish: NewLife.MQTT/Messaging/MqttMessage.cs#L105
Nullability of reference types in type of parameter 'context' of 'bool MqttMessage.Write(Stream stream, object context)' doesn't match implicitly implemented member 'bool IAccessor.Write(Stream stream, object? context)' (possibly because of nullability attributes).
build-publish: NewLife.MQTT/MqttCodec.cs#L68
Nullability of type of parameter 'request' doesn't match overridden member (possibly because of nullability attributes).
build-publish: NewLife.MQTT/MqttCodec.cs#L68
Nullability of type of parameter 'response' doesn't match overridden member (possibly because of nullability attributes).
build-publish: NewLife.MQTT/MqttSign.cs#L14
Non-nullable property 'UserName' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.