Replies: 1 comment
-
This problem is solved by PR #338. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
If we use golang v1.19 or higher versions to compile XDPoSChain, then sync would fail, such as reported by #268 and #324. After troubleshooting I found that the function
sort.Slice
outputs differerent result from golang v1.19 when the stake values are equal.Eg, for below codes when the block number is 516150:
Golang v1.14-v1.18
The address xdcc67c2DEc79da735d6587d8DB3c23271d557196ab is cut off.
Golang v1.19-v1.21
The address xdc065551F0dcAC6f00CAe11192D462db709bE3758c is cut off.
Reason
The release node of golang v1.19 said:
Solution
We can make the sorting results completely determined by the data, such as:
Or:
Beta Was this translation helpful? Give feedback.
All reactions