-
Notifications
You must be signed in to change notification settings - Fork 64
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
QueryFailed #200
Comments
|
Hey @0x009922, thanks for your help so far!! I do appreciate it. Just so that is documented, bellow is a sample response for this Query, even tho I'm certain that the Hash I use does exist. {
"data": {
"tag": "Err",
"content": {
"enum": {
"tag": "QueryFailed",
"content": {
"enum": {
"tag": "Find",
"content": {
"enum": {
"tag": "Transaction",
"content": {
"0": 107,
"1": 77,
"2": 52,
"3": 228,
"4": 68,
"5": 72,
"6": 175,
"7": 190,
"8": 15,
"9": 149,
"10": 233,
"11": 158,
"12": 114,
"13": 117,
"14": 13,
"15": 47,
"16": 54,
"17": 195,
"18": 172,
"19": 142,
"20": 240,
"21": 163,
"22": 146,
"23": 239,
"24": 148,
"25": 26,
"26": 78,
"27": 0,
"28": 179,
"29": 57,
"30": 97,
"31": 151
}
}
}
}
}
}
}
}
} I switched logging to DEBUG and saw this:
The hash is on lower caps, so would always fail. Unless it is just being shown lowercaps in logging, but it's correct when executing the search. (The hash on the log is from a different test I did, it doesn't correspond to the bytes on the response sample above) Where you able to use FindTransactionByHash with v2.0.0-pre-rc.20 and SDK 7.0 ? |
Iroha is ignorant to the hash case and processes it as a sequence of bytes.
I am now having difficulties with this too. Investigating. |
I'm trying to execute a Query using FindTransactionByHash, but I get
QueryFailed
(code 500) as a response.I'm on Iroha version:
v2.0.0-pre-rc.20
with the following library versions:So for instance, If I use hash value
846F5E5498B4FA615B8137C16CD55707DDE349FE79C7A49B07A838F9A
, the code below is how I prepare and execute the query:The text was updated successfully, but these errors were encountered: