Vincent Lin

Logs like this, right? ``` E0316 03:04:24.034662 678203 message_dispatcher.go:298] "Failed to create objectSync" err="namespaces \"null\" not found" objectSyncName="kube-edge-node.41eaa28d-3285-4b5b-9096-d65d0c9af7fa" resourceNamespace="null" resourceName="xxx" E0316 03:04:43.602839 678203 message_dispatcher.go:298] "Failed to create objectSync" err="namespaces \"null\"...

FYI: https://github.com/kubeedge/kubeedge/issues/4521

> I'll write UT for kubeedge/edge/pkg/edgehub Thanks a ton!

Test in local host and check coverage: go test -v ./... -coverprofile=cover.out gocov convert cover.out | gocov-xml > coverage.xml

Integrating conformance tests framework and the base conformance tests: https://github.com/kubeedge/kubeedge/pull/4411

> i want to work on the `kubeedge/edge/pkg/eventbus.` please assign it to me if no one is working on this Great, sure.

> Hi @vincentgoat, If nobody has picked "kubeedge/edge/devicetwin", then I can write unit tests. Thanks! Great, thanks. By the way, any task without a checkmark will be available for all...

> Hi @vincentgoat! If no one is working on `kubeedge/edge/pkg/eventbus`, I'd like to work on this. Please assign it to me. Thanks @nox1134

I may not have been clear, it is not the master branch of Kubeedge that brings out this issue, it is on my own repository https://github.com/vincentgoat/kubeedge/tree/verifynodecert. I run Fuzzing locally...

When I build KubeEdge with go version 1.18, I got the same error but it works fine with go1.16/go1.17. I'm wondering if the OSS-Fuzz builder takes go1.18 to build fuzzer?...