You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ostracon version (use ostracon version or git rev-parse --verify HEAD if installed from source):
ABCI app (name for built-in, URL for self-written if it's publicly available):
Environment:
OS (e.g. from /etc/os-release):
Install tools:
Others:
What happened:
Finschia TypedEvent is unmarshalled by proto marhsaller. This marshaller add 0x22(") at both ends for some data (e.g. uint64, string). Finschia unmarshal this data by JSON unmarshaller and it lefts double quote in original data. (e.g. "1" instead of 1). So we need to query like lbm.fbridge.v1.EventTransfer.seq='\"1\"' but current query parser doesn't support this case.
What you expected to happen:
Have you tried the latest version: yes
How to reproduce it (as minimally and precisely as possible):
Generate TypedEvent and try to query using TxSearch
Logs (paste a small part showing an error (< 10 lines) or link a pastebin, gist, etc. containing more of the log file):
Config (you can paste only the changes you've made):
node command runtime flags:
Please provide the output from the http://<ip>:<port>/dump_consensus_state RPC endpoint for consensus bugs
Anything else we need to know:
The text was updated successfully, but these errors were encountered:
Ostracon version (use
ostracon version
orgit rev-parse --verify HEAD
if installed from source):ABCI app (name for built-in, URL for self-written if it's publicly available):
Environment:
What happened:
Finschia TypedEvent is unmarshalled by proto marhsaller. This marshaller add 0x22(") at both ends for some data (e.g. uint64, string). Finschia unmarshal this data by JSON unmarshaller and it lefts double quote in original data. (e.g. "1" instead of 1). So we need to query like
lbm.fbridge.v1.EventTransfer.seq='\"1\"'
but current query parser doesn't support this case.What you expected to happen:
Have you tried the latest version: yes
How to reproduce it (as minimally and precisely as possible):
Generate TypedEvent and try to query using TxSearch
Logs (paste a small part showing an error (< 10 lines) or link a pastebin, gist, etc. containing more of the log file):
Config (you can paste only the changes you've made):
node command runtime flags:
Please provide the output from the
http://<ip>:<port>/dump_consensus_state
RPC endpoint for consensus bugsAnything else we need to know:
The text was updated successfully, but these errors were encountered: