Closed dingxiangfei2009 closed 2 years ago
Thanks for the report. I'll be updating the Ogmios dependency shortly so will test this out to see if it's been resolved already.
Hello. Could you please provide your GraphQL service for me to use? SubmitTransaction also ran into problems. this issue: https://github.com/input-output-hk/cardano-graphql/issues/606,
Hello @rhyslbw, I see that Ogmios is updated to 4.1.0
. This issue persists with the same error message.
Thanks for the update @dingxiangfei2009, I'll dig into this further.
@rhyslbw I have a question. In the current plan, do transaction submissions through cardano-graphql
accept only Alonzo transaction bodies or accept transaction bodies from Alonzo and earlier eras for backward compatibility?
If indeed all Shelley-compatible transaction submissions should be acceptable, CardanoSolutions/ogmios#131 will enable such support.
Looks like this issue will be resolved once the latest ogmios
is used. :+1:
Thanks for the contributions @dingxiangfei2009, we'll get this updated ASAP
I have exactly the same error. I tried the latest v6.2.0 in testnet, but it seems like the same issue remains. Why does this error happen when using docker? No problem is found at wss://ogmios-api.testnet.dandelion.link
.
{
"transaction": "84a40081825820fa1fe8bf72a4c4608181865b106950e1caa4f83ae2d9df53d0a49ea9e461457a01018282581d60247f3006b36b3b39f5e3cf5135df39e74e773d3860d6d6e4639099b41a000f42408258390030b1d8b9642d2072c03c2af4b42c887a23df8c56482ee2763e9083999d6732b5ca23796d8710ab1268dfa50c8bfc613c4973aca7bef2dedc1a01ac4392021a0002ae8a031a02f89627a100818258209c264a4c9a43a3711de00d60e201a4a75f24aefe19dfbab30c6776d3bdb5b5b6584043581e3be1af1d429dfb144c59056512a45b7acdae93ff3c60716511670727f385d6f6b373c80b7224aecc1dd51ba031dfae7f6d36231d20ccb3a1e3a6f4bc00f5f6"
}
@masa-matt v6.2.0 is still using the old ogmios @ v4.1.0
@dingxiangfei2009 I'm afraid, but v6.2.0 seems to be using ogmios @ v5.1.0. https://github.com/input-output-hk/cardano-graphql/releases/tag/6.2.0
I've faced with the same issue:
errors: [
{
message: 'Deserialization failed in Transaction.metadata because: Expected null, found other type',
locations: [ { line: 4, column: 3 } ],
path: [ 'submitTransaction' ],
extensions: {
code: 'INTERNAL_SERVER_ERROR',
exception: {
stacktrace: [
'Error: Deserialization failed in Transaction.metadata because: Expected null, found other type',
' at Object.<anonymous> (/app/packages/api-cardano-db-hasura/dist/executableSchema.js:77:43)',
' at Generator.throw (<anonymous>)',
' at rejected (/app/packages/api-cardano-db-hasura/dist/executableSchema.js:6:65)',
' at runMicrotasks (<anonymous>)',
' at processTicksAndRejections (internal/process/task_queues.js:95:5)'
]
}
}
}
]
Is there a plan to solve this issue? Does the v6.2.0 mainnet also have this problem?
Hey guys could you please give an update on the state of this issue?
The next version will be using Ogmios v5.5.0
, which supports the Babbage era. Transactions need to be constructed using era-compatible libraries, although the original report indicates it wasn't the case.
Environment
Environment set up with
docker-compose
. Version is5.1.0
.When building and running, the environment variable
NETWORK=testnet
is set.Platform
Platform version:
Runtime
Runtime version:
Steps to reproduce the bug
Execute this query,
With this query parameter:
Note that the hexdecimal representation of this transaction is the following.
It returns this error:
What is the expected behavior?
This is a valid transaction, as it was successfully submitted to the
testnet
usingcardano-cli
.The expected response shall contain the transaction ID
20e65fbbbb08e6085853b828d52bed364e19e50a35d7d9e241e9f43a0fd4aa2f
.