ci: reopen unit test checks and fix fatal

[Xunzhuo]

Signed-off-by: Xunzhuo [email protected]

What this PR does:

ci: reopen unit test checks and fix fatal

Test cases in below packages:

@echo "===========> Run unit test in sdk/go-sdk"
@echo "===========> Run unit test in components"
@echo "===========> Run unit test in pkg"
@echo "===========> Run unit test in diagnostics"

resolve: #529

[Xunzhuo]

Only this test case failed TestPublishEvent, I did not see this failure #528

[Xunzhuo]

envelope is a map[string]interface{} type, when using jsoniter to marshal it fast, it will cause panic for unsafe map. I did not look into jsoniter codes deeply, but I think when using it to marshal a map, it will cause concurrency fatals?

After fixing this, I think all unit tests passed normally, we can reopen unit test check again. And we can excute make check, make all normally when in local development.

[codecov]

Codecov Report

Merging #546 (eba6443) into main (40b8e8e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #546   +/-   ##
=======================================
  Coverage   60.70%   60.70%           
=======================================
  Files         120      120           
  Lines        6382     6382           
=======================================
  Hits         3874     3874           
  Misses       2139     2139           
  Partials      369      369           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 40b8e8e...eba6443. Read the comment docs.

[seeflood]

LGTM.

[seeflood]

@Xunzhuo I just found this issue with same error json-iterator/go#608
It's beacuse current json-iterator version is incompatible with go 1.18

[Xunzhuo]

@Xunzhuo I just found this issue with same error json-iterator/go#608 It's beacuse current json-iterator version is incompatible with go 1.18

Yes, it should be an issue in jsoniter, but I think layotto is using go 1.14?

[seeflood]

Yes, layotto use 1.14 because mosn use 1.14

[Xunzhuo]

Yes, layotto use 1.14 because mosn use 1.14

I tried to upgrade jsoniter to 1.12, the fatal disappeared. We can keep jsoniter again, since it is with more high performance.

[Xunzhuo]

see eba6443

[seeflood]

lgtm