ion
ion copied to clipboard
Network Explorer hangs after DID not found
Once I get DID not found in the Network Explorer, the page is stuck and I cannot change and search again until after refresh.
Steps:
- Search for:
did:ion:EiClkZMDxPKqC9c-umQfTkR8vvZ9JPhl_xLDI9Nfk38w5w - Success
- Search for
did:ion:EiClkZMDxPKqC9c-umQfTkR8vvZ9JPhl_xLDI9Nfk38w5 - Not Found
- Stuck - cannot search again must refresh
@csuwildcat, can you take a look at this issue?
@joshbooker I am not able to repro that, what exactly did you do? Did you copy/paste, or mod the input with the keyboard?
@csuwildcat thanks for your reply.
I pasted the value in step 1 and it worked then deleted the last chr w keyboard and clicked the button.
Returned not found message then became non-responsive.
Firefox.
GIF REPRO
400 response before hang is: { "code": "did_initial_state_jcs_is_not_json", "message": "Long form initial state should be encoded jcs." }

@joshbooker I do have code in that does not allow the back-to-back submission of the same DID URI, so if you don't change the string, it's not even going to attempt to do another lookup - could that be what this is?
Yeah. It seems you cannot submit the same as the last successful URI regardless of whether they're be back-to-back.
Seems you can submit the same bad URI back-to-back but not the same successful URI again until you submit a different successful URI.
Thanks.
There may still be a bug, because any difference in URI should clear it. Let me test more now that I know the details of the issue.
On Tue, Mar 30, 2021, 5:26 PM Josh Booker @.***> wrote:
Yeah. It seems you cannot submit the same as the last successful URI regardless of whether they're be back-to-back. Seems you can submit the same bad URI back-to-back but not the same successful URI again until you submit a different successful URI. Thanks.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/decentralized-identity/ion/issues/179#issuecomment-810664162, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABAFSSZ2PEFCCMILIHP7JDTGJT2XANCNFSM4ZZZUWHQ .
Seems like the check that prevents back-to-back submissions fails if there is a 404 response, and the UI does not take that search into account. I opened a PR with a suggested (very simple) fix.
I think you're right, after looking at your PR. I'll try to pull and test this weekend, and get it in.
@joshbooker we accepted a PR that covers this, so can you let me know if you still see this happening?
@csuwildcat it's fixed. Case closed. Thanks @grankko.
I'm happy I could help!