supplementary comment

Author: tianfeng-yang

src/lib/dnssd/Discovery_ImplPlatform.cpp

@@ -629,9 +629,10 @@ bool DiscoveryImplPlatform::IsInitialized()
 
 CHIP_ERROR DiscoveryImplPlatform::ResolveNodeId(const PeerId & peerId)
 {
-    // Resolve requests can only be issued once DNSSD is initialized and there is
-    // no caching currently
-    // When the DNSSD is kInitializing, can also try to resolve.
+    // It only determines that it is not in an uninitialized state, and cannot force initialization to be completed.
+    // There are differences between platforms.
+    // e.g. when a collision occurs on the Linux platform, initialization has not been completed at this time, but you can
+    // still try to parse.
     VerifyOrReturnError(mState != State::kUninitialized, CHIP_ERROR_INCORRECT_STATE);
 
     ChipLogProgress(Discovery, "Resolving " ChipLogFormatX64 ":" ChipLogFormatX64 " ...",

src/platform/Linux/DnssdImpl.cpp

@@ -383,17 +383,14 @@ void MdnsAvahi::HandleClientState(AvahiClient * client, AvahiClientState state)
         break;
     case AVAHI_CLIENT_FAILURE:
         ChipLogError(DeviceLayer, "Avahi client failure");
-        // error happend, we should to restart dnssd.
-        mErrorCallback(mAsyncReturnContext, CHIP_ERROR_FORCED_RESET);
+        mErrorCallback(mAsyncReturnContext, CHIP_ERROR_INTERNAL);
         break;
     case AVAHI_CLIENT_S_COLLISION:
-        ChipLogProgress(DeviceLayer, "Avahi collision, force to reset");
+        ChipLogProgress(DeviceLayer, "Avahi collision");
         StopPublish();
-        mErrorCallback(mAsyncReturnContext, CHIP_ERROR_FORCED_RESET);
-        // Should restart the resolve service of the host.
+        // DNSSD does not need to be restarted, it depends on the system resolve service restarting
         break;
     case AVAHI_CLIENT_S_REGISTERING:
-        // now is registering, we should just StopPublish() without reset
         ChipLogProgress(DeviceLayer, "Avahi registering");
         StopPublish();
         break;