tools/stellar-archivist: Fix stellar-archivist dumpxdr command #1331
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DumpXdrAsJson
function is creating shared objects for various XDR types:These objects are later reused inside
for
loop. It seems that previous values are persisted in the shared objects when unmarshaling unions. For example:Note:
AccountId
fields are strkey-encoded for readability. In example aboveLiveEntry
should benull
because bucket entry type is equal1
.This PR recreates empty objects on each iteration.
Should a long term fix be actually added to
go-xdr
(xdr.Unmarshal
)?