Transaction Details 404 page

[acravenho]

If a transaction does not exist yet, we should not show a standard 404 page. Instead, we should show the TX details page but with a message stating that our node hasn't picked up the transaction yet and the page will update automatically when it does.

1. If the user is on the correct route for the transaction details page but the tx hash is not found in the DB, we should show the normal transaction details page but with a message stating to please be patient while our nodes search for the transaction.
2. We should subscribe to both pending transactions and incoming blocks to find the transaction hash.
3. If the tx hash is found, refresh the page to show either the pending state or collated state.

Aceptance Criterias

• Verify the TxHash in order to identify if the hash is or not valid and show to the user the correct page behavior:

  • For invalid hashes:
    • Show a warning message when the TxHash is invalid;
      • Message example: Etherscan;
  • For pending transactions:
    • Show the TxDetails Page when it's valid but doesn't exist. Suggested sentence: Please be patient while our nodes search for the transaction.
    • Show a spinner for the pending transactions;
    • Show complementary information about the pending transaction process;
      • Information Example: Etherscan

• As soon as the txHash get processed the Hash's TxDetail Page needs to be refreshed with it's current state.

Tasks

• Change controller to not redirect to the 404 page and insert the transaction hash when it is valid;
  • Send the hash to the realtime indexer to be indexed;
  • Alter view to show message of "Transaction not indexed yet."
• Subscribe to pending "transactions" and "incoming blocks" websockets so when the transaction is indexed show in the view;
• When the transaction hash is invalid show message: "Transaction hash invalid."

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

This issue now has a funding of 75.0 DAI (75.0 USD @ $1.0/DAI) attached to it as part of the Ethereum Community Fund via ECF Web 3.0 Infrastructure Fund fund.

• If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
• Want to chip in? Add your own contribution here.
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $49,724.89 more funded OSS Work available on the Gitcoin Issue Explorer

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

Work has been started.

These users each claimed they can complete the work by 7 months, 1 week from now.
Please review their action plans below:

1) gusilverflame has been approved to start work.

• create the templates for when the hash is invalid and when the transaction is not found
• add to the controllers the cases when those new templates will be rendered
• make the not found one auto refresh when the transaction is finally indexed

Learn more on the Gitcoin Issue Details page.

[aj07]

@acravenho I am facing setup issue for default configurations mentioned on Readme file (step 3). Is there any chat channel where we can connect you or with your team?

[acravenho]

@aj07 Can you please provide more information on the issue? Depending upon which OS you're using and how you configured Postgres. If you installed Postgres using Homebrew you're most likely going to remove the username and password from apps/explorer/config/dev.secret.exs.

[acravenho]

@aj07 You can join our Gitter chat located here https://gitter.im/poanetwork/blockscout if you would like to ask any questions.

[acravenho]

@aj07 You can join our Gitter chat located here https://gitter.im/poanetwork/blockscout if you would like to ask any questions.

[aj07]

I followed https://www.postgresql.org/download/linux/ubuntu/

apt-get install postgresql-10

I will ping on gitter

[acravenho]

You have to provide us with the exact error message otherwise we don't have any idea how to help.

[gitcoinbot]

@aj07 Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• warning (3 days)
• escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

@aj07 due to inactivity, we have escalated this issue to Gitcoin's moderation team. Let us know if you believe this has been done in error!

• warning (3 days)
• escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[aj07]

@gitcoinbot I am working on this

[brwatanabe]

@acravenho

Questions

• Could we use a layout similar to that one we applied to the 404 block page?
  • If necessary, we could add a spinner as for the pending txs.
  • Also, we could add more information for the user, like Etherscan does here
• What to do with invalid hashes? Etherscan shows a message for the user as seen here;
• We should subscribe to both pending transactions and incoming blocks to find the transaction hash.
  • In this case, should the system prioritize the searched transaction to get it processed faster than usual?

[acravenho]

@brwatanabe

1. Yes, let's use a similar layout to the 404 block page, but with a spinner 👍 More information is always better, let's go for it.
2. Yes, let's show a similar message as Etherscan for invalid hashes.
3. Both pending and incoming blocks should be subscribed to. The realtime indexer should already be prioritizing this transaction. I'm not sure that there is much more that we can do to index it faster.

[gitcoinbot]

@aj07 Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• warning (3 days)
• escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[mkosowsk]

@GuSilverFlame please apply for work on the Gitcoin detail page and you will be approved :)

[mkosowsk]

@GuSilverFlame you have been approved, please submit your work and you will be paid out. Thanks! 👍

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

Work for 75.0 DAI (75.0 USD @ $1.0/DAI) has been submitted by:

1. @GuSilverFlame

@mkosowsk please take a look at the submitted work:

• PR by @GuSilverFlame

---

• Learn more on the Gitcoin Issue Details page
• Want to chip in? Add your own contribution here.
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $47,482.34 more funded OSS Work available on the Gitcoin Issue Explorer

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

The funding of 75.0 DAI (75.0 USD @ $1.0/DAI) attached to this issue has been approved & issued to @GuSilverFlame.

• Learn more on the Gitcoin Issue Details page
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $47,407.34 more funded OSS Work available on the Gitcoin Issue Explorer