cardano-graphql
cardano-graphql copied to clipboard
Cannot return null for non-nullable field TransactionMetadata.value
{
blocks(where: {_and: [{number: {_gte: 6123430}}, {number: {_lt: 6123615}}]}, order_by: {number: asc}) {
number
hash
size
epochNo
fees
transactionsCount
opCert
slotInEpoch
slotNo
forgedAt
slotLeader {
description
hash
}
protocolVersion
vrfKey
transactions {
blockIndex
hash
size
deposit
fee
totalOutput
invalidBefore
invalidHereafter
includedAt
metadata {
key
value
}
inputs {
address
value
sourceTxHash
sourceTxIndex
sourceTransaction {
block {
number
}
}
tokens {
quantity
asset {
assetName
decimals
description
fingerprint
name
policyId
ticker
}
}
}
outputs {
address
index
value
tokens {
quantity
asset {
assetName
decimals
description
fingerprint
name
policyId
ticker
}
}
}
withdrawals {
address
amount
}
mint {
quantity
asset {
assetName
decimals
description
fingerprint
name
policyId
ticker
}
}
}
}
}
returns error
message => Cannot return null for non-nullable field TransactionMetadata.value.
I have the same issue with block 6123581.
cardano_fullnode_version: "1.30.1"
cardano_fullnode_db_sync_version: "11.0.4"
cardano_fullnode_db_explorer_api_version: "3.1.2"
cardano_fullnode_graphql_version: "6.0.0"
cardano_fullnode_ogmios_version: "v4.1.0-mainnet"
Hi, I'm facing this issue: Error: ClientError: Cannot return null for non-nullable field Token.asset Some of block numbers are 8208751, 8216194
Same problem here. any updates?
Same here with v7.0.2. It looks release 8.0.0 has changes related to asset table. Could graphql v8.0.0 solve or mitigate this issue?
I assume this is related to data synchronization of cardano-graphql. Is there any chance using cardano-graphql-background can mitigate this issue?
Getting the similar issue with v8.0.0. It looks like assets were not syncing to the latest and clearly it takes like forever to sync. https://github.com/input-output-hk/cardano-graphql/issues/801#issuecomment-1475303136
This is still an issue v8.0.0, is still on anyone's radar? @rhyslbw @johnalotoski ?
I'm having this issue too
on v8.0.0. having this issue also