Getting an error when showing a dispute by ID #24
Assignees
Labels
bug
Something isn't working
Comments
Merged
glmaljkovich
added a commit
that referenced
this issue
Sep 2, 2021
goaaron
added a commit
that referenced
this issue
Sep 23, 2021
…t blocks...coming up automate the creation of divergent blocks broken fix conflict with sqlalchemy version make the dispute stage an enum all apis v0 and insomnia requests cleanup and documentation on how to run the application remove debugger modify version of ipfshttpclient, change module name from web3 to w3 addendum to readme requirements container file and Makescripts Update README.md multi stage docker build. use poetry inside of docker Build dockerfile added cicd and k8s files run on updated k8s .github paths fix cicd context fix repo name moving some fields to enums. cleanup some async code base frontend for dispute portal foundation redux actions bump webpack, setup base dispute page expose get all disputes list disputes simplify state with zustand merge state updates swap out the stages of the dispute allows frontend to toggle the stages of the dispute swap state in the frontend prior to revalidation. revalidation still hits later sort, filter, visualize uploaded data dispute portal list events Fix rainbow Fix setup when the config file is not yet created Define files to use when publishing package Add bin and cleanup gitignore filter disputes by status (#13) * filter by status * Update README.md Simplify cli (#14) * remove dispute command and show help by default * update README.md * fix usage Add Economics section and fetch network settings (#15) Sort disputes by date (#16) v0.2.0 Add defaultDisplayName to indexer and fisherman (#17) Check thawing period before resolving dispute (#19) Support for multiple ids on show and improved styling (#20) * Support for multiple ids on show and improved styling * Replace treeify with object-treeify Add closing epoch startBlock and poi info (#21) v0.3.0 [#24] Fix show command (#25) v0.3.1 remove conf file testing deployment
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
This is happening with the following command execution:
graph-disputes show 0xbd7a4f1161630edbe505f8df605e4c60e73256687cf5de144f037da6ea614273The text was updated successfully, but these errors were encountered: