-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ledger produces an invalid flat term #3800
Comments
It is actually consensus that produces this invalid CBOR 😄 All of our roundtrip tests now also validate through FlatTerm since this PR: #3769 So, unless we missed a test for a type defined in ledger, such failures should not be possible |
I'd like to emphasis that I wanted to fix that bug in the |
🤦 Thanks! Let me check that.
🎉 Great news!
:) Sorry, which bug are you referring to? |
I guess it's related to this |
It is actually related to this issue right here: CardanoSolutions/ogmios#314 (comment) In other words I have fixed this issue that you are experiencing, but then it broke people's tools and we had to backport a fix that reintroduced a bug. So there is nothing we can really do, except deprecating the old query (or maybe just the NoteToClient protocol version) that relies on this bug. In any case, I don't think there is really nothing to do about this on the ledger side, thus closing the issue. |
Thanks @lehins. We'll try to workaround this in Consensus. |
Fixes IntersectMBO/ouroboros-network#3099 Sadly some CBOR validity tests need to be skipped due to: - IntersectMBO/cardano-ledger#3800 - IntersectMBO/cardano-ledger#3741 - IntersectMBO/cardano-ledger#3740 This patch introduces an ad-hoc filtering mechanism to fix problems with legacy encoders.
When checking that the CBOR produced by Consensus is valid I ran into the error shown below, which can be reproduced by running:
on this branch.
The text was updated successfully, but these errors were encountered: