oasisprotocol / oasisprotocol/explorer
Search breaks if can't fetch named accounts
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 13
- Forks
- 13
- Avg merge
- 58m
- Merged PRs (30d)
- 2
Description
- open https://explorer.oasis.io/search?q=0x90adE3B7065fa715c7a150313877dF1d33e777D5
- block network requests to https://raw.githubusercontent.com/oasisprotocol/nexus/main/named-addresses/testnet_emerald.json
- refresh
- try to open testnet results
or block https://raw.githubusercontent.com/oasisprotocol/nexus/main/named-addresses/mainnet_sapphire.json and it loads forever
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure from the explorer search URL in the issue while blocking the cited named-addresses JSON requests. Inspect the search result loading and named-account fetch handling; done means testnet results still open and the mainnet case does not load forever when either request is unavailable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100