Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
ERROR: InvalidTransactionBytesError: Failed to deserialize transaction, encountered invalid bytes: Unknown transaction type: 2/0
See original GitHub issueThe forger process sometimes encounters the following error (not relay):
3|ark-forger | [2020-02-11 19:51:11.330] ERROR: InvalidTransactionBytesError: Failed to deserialize transaction, encountered invalid bytes: Unknown transaction type: 2/0
3|ark-forger | at Function.fromBytesUnsafe (/home/ark/.config/yarn/global/node_modules/@arkecosystem/crypto/dist/transactions/factory.js:34:19)
3|ark-forger | at /home/ark/.config/yarn/global/node_modules/@arkecosystem/core-forger/dist/manager.js:147:106
3|ark-forger | at Array.map (<anonymous>)
3|ark-forger | at ForgerManager.getTransactionsForForging (/home/ark/.config/yarn/global/node_modules/@arkecosystem/core-forger/dist/manager.js:147:52)
3|ark-forger | at runMicrotasks (<anonymous>)
3|ark-forger | at processTicksAndRejections (internal/process/task_queues.js:94:5)
3|ark-forger | at async ForgerManager.forgeNewBlock (/home/ark/.config/yarn/global/node_modules/@arkecosystem/core-forger/dist/manager.js:107:30)
3|ark-forger | at async ForgerManager.checkSlot (/home/ark/.config/yarn/global/node_modules/@arkecosystem/core-forger/dist/manager.js:81:17)
Consequently the node fails to forge. This is despite core-magistrate-transactions being installed and loaded in the relay (in the correct order) as confirmed in the logs. This does not seem to occur if the unified core process is used instead of the split forger/relay setup.
Expected Behavior
It should forge magistrate transactions.
Current Behavior
It doesn’t.
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
There is no check transaction type setup - Dynamics GP
Provides a solution to an error that occurs when you upload Safe Pay Transactions in Microsoft Dynamics GP.
Read more >ARK Development Report — February 2020 | by Rok Černec
... #3464 ERROR: InvalidTransactionBytesError: Failed to deserialize transaction, encountered invalid bytes: Unknown transaction type: 2/0.
Read more >Validate Transaction with serialization lib from a Tx Hash
"Deserialization failed in Transaction because: Invalid cbor: not the right type, expected Array' byte received Bytes'".
Read more >Kafka Streams - SerializationException: Unknown magic byte
errors.StreamsException: Deserialization exception handler is set to fail upon a deserialization error. If you would rather have the streaming ...
Read more >Medicare Modernization Act (MMA) Customer Support ... - CMS
submitted to CMS? The following are the top errors being encountered in Plan enrollment transaction files: TR 007 – Invalid Claim Number.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks for reporting and that doesn’t have anything to do with misconfiguration on the user end if it works with the
coreprocess type.https://github.com/ArkEcosystem/core/blob/master/packages/core/src/commands/forger/run.ts#L35-L41 this is missing the magistrate plugin so it can’t work with it if it encounters any magistrate transaction in the split forger.
Will include a fix in the patch release together with other things.
This is just stock Core 2.6 on mainnet with no extra plugins, @kristjank. Happens when forging a business registration tx.