Weekly update 2021-06-11

[frol]

Last week update is here: #4352

Done

• docs
  • Updated indexer tutorial to work with recent master branch and to decrease troubles with a dependency that may occur refactor: Update indexer tutorial to make it work and avoid dependency troubles docs#733 (@khorolets)
  • Re-recorded a video on NEAR Data flow; stay tuned! [DOC] Document the data flowing in NEAR Protocol docs#700 (@khorolets & @amgando)
  • Drafted the documentation of starting a node from a backup Add how to start near node from backup docs#720 (@mhalambek)
• indexer-for-explorer
  • Re-indexed the entire account_changes table on testnet from genesis to apply unique indexes on account_changes table fix: unique indexes in account_changes table should contain update_reason near-indexer-for-explorer#120 (@khorolets)
  • Analysed the ways of fixing the representation of transaction hash collisions in Indexer for Explorer database, and created the plan how to make the DB consistent Some rows are missing because of transaction hash collisions near-indexer-for-explorer#84 (comment) (@telezhnaya)
    • We decided to postpone addressing this issue
  • Fixed privileges in DB by allowing read-only access by default Alter default privileges on select on new tables near-indexer-for-explorer#122 (@telezhnaya)
• operations
  • Created "reindexer" automation to spin up indexer-for-explorer nodes that starts indexing from genesis (archival node is up in 10-15 minutes!) (@khorolets)
• explorer
  • Exposed receipts on Block Details page feat(frontend): Display receipts on Block Details page near-explorer#643 (@shelegdmitriy)
  • Fixed "Result not found" error when searching for deleted users fix(frontend): Fix searching for deleted users near-explorer#656 (@shelegdmitriy)
  • Drafted PR to resolve confusing information on Nodes page Validator nodes screen is confusing near-explorer#646 (@shelegdmitriy)
  • Deprecated the old indexer (JS) implementation and left it in legacy branch: Migrate Explorer to the Indexer for Explorer near-explorer#450 (@frol)
    • mainnet and testnet has been running on Indexer for Explorer for quite a while already
    • betanet and guildnet still need to be upgraded to Indexer for Explorer, so they keep running the legacy version of Explorer, and won't get major updates
• meta
  • Created the draft of postmortem about hash collisions Postmortem about hash collisions docs#746 (@telezhnaya)

Plans

• nearcore
  • Finalize the design and expose error structures from JSON-RPC in JSON nearcore doesn't return structured errors for most use cases of API #2976 (@frol and @khorolets)
  • Introduce a strictly typed version of AccountId type in order to pave the way to type-safe changes in nearcore feat(core): Defined AccountId to hold a contract of being valid #2831 (@miraclx)
• indexer-for-explorer
  • Re-index the entire account_changes table on mainnet from genesis to apply unique indexes on account_changes table fix: unique indexes in account_changes table should contain update_reason near-indexer-for-explorer#120 (@khorolets and @telezhnaya created a dedicated indexer-for-explorer build to make the migration zero-downtime by just swapping two tables once the re-index is complete)
• indexer
  • R&D indexer with Apache Kafka (@khorolets)
• near-cli-rs
  • Adding Ledger Nano S support (@khorolets)
• docs
  • Document the data flowing in NEAR Protocol [DOC] Document the data flowing in NEAR Protocol docs#700 (@khorolets)
  • Write a guide on the localnet development process [DOC] Write a guide on the localnet development process docs#156 (@khorolets)
• explorer
  • Reconsider the way we display next epoch validators, proposals, and low-funded staking pools Validator nodes screen is confusing near-explorer#646 (@shelegdmitriy)
  • Display active access keys on Account Details page Display active access keys on Account Details page near-explorer#509 (@shelegdmitriy)
  • Computed circulating supply should be temporarily saved somewhere between re-deployments feat(backend): add transition logic for circulating supply near-explorer#642 (comment) (@telezhnaya)
• operations
  • Use terrafrom to manage buildkite (@mhalambek)
  • Write more docs about the infrastructure we run with terraform (@mhalambek)