Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

1.3.9 release (Mainnet-Staging) #1715

Merged
merged 117 commits into from
Apr 9, 2019
Merged

1.3.9 release (Mainnet-Staging) #1715

merged 117 commits into from
Apr 9, 2019

Conversation

ayrat555
Copy link
Contributor

@ayrat555 ayrat555 commented Apr 8, 2019

Features

  • #1662 - allow specifying number of optimization runs
  • #1654 - add decompiled code tab
  • #1661 - try to compile smart contract with the latest evm version
  • #1665 - Add contract verification RPC endpoint.

Fixes

  • #1669 - do not fail if multiple matching tokens are found
  • #1691 - decrease token metadata update interval
  • #1688 - do not fail if failure reason is atom
  • #1692 - exclude decompiled smart contract from encoding
  • #1684 - Discard child block with parent_hash not matching hash of imported block
  • #1699 - use seconds as transaction cache period measure
  • #1697 - fix failing in rpc if balance is empty
  • #1712 - do not set contract code from transaction input

goodsoft and others added 19 commits April 2, 2019 21:13
Consider a root block `A`, old chain `-- B -- C` and new one `-- B' -- C'`.
Due to asynchronous nature of realtime fetcher it is possible for block
`B` to be imported _later_ than the entire chain `-- B' -- C'`.

In this case we should discard block `C'` and let it be refetched.
When that happens, block `B` gets discarded to make sure block `B'` gets
eventually fetched and the chain becomes consistent.
This worker only handled one of invalid consensus cases, i.e. when a parent
block lost consensus, but the child one didn't.
Even then it worked only when all blocks are reliably and sequentially
imported (certainly not our case), and only once on indexer launch.

Now this particular case is covered by previous commit, and we don't need
this worker at all.
Discard child block with parent_hash not matching hash of imported block
…nsaction-cache

use seconds as transaction cache period measure
…from-transaction-input

do not set contract code from transaction input
@ghost ghost assigned ayrat555 Apr 8, 2019
@ghost ghost added the in progress label Apr 8, 2019
@coveralls
Copy link

coveralls commented Apr 8, 2019

Pull Request Test Coverage Report for Build f60d5f70-1764-48dc-9fd0-61d747f1a696

  • 163 of 199 (81.91%) changed or added relevant lines in 17 files are covered.
  • 1 unchanged line in 1 file lost coverage.
  • Overall coverage increased (+0.2%) to 78.771%

Changes Missing Coverage Covered Lines Changed/Added Lines %
apps/block_scout_web/lib/block_scout_web/views/address_view.ex 2 3 66.67%
apps/ethereum_jsonrpc/lib/ethereum_jsonrpc/contract.ex 0 1 0.0%
apps/explorer/lib/explorer/chain/import/runner/blocks.ex 14 15 93.33%
apps/explorer/lib/explorer/chain/smart_contract.ex 0 1 0.0%
apps/explorer/lib/explorer/smart_contract/verifier.ex 9 10 90.0%
apps/block_scout_web/lib/block_scout_web/controllers/address_decompiled_contract_controller.ex 0 6 0.0%
apps/explorer/lib/explorer/chain/transaction_count_cache.ex 32 38 84.21%
apps/block_scout_web/lib/block_scout_web/controllers/api/rpc/contract_controller.ex 37 44 84.09%
apps/explorer/lib/explorer/chain.ex 11 23 47.83%
Files with Coverage Reduction New Missed Lines %
apps/explorer/lib/explorer/chain.ex 1 86.26%
Totals Coverage Status
Change from base Build bf34e75b-b22c-4b35-9a68-2bcd1fce3f0d: 0.2%
Covered Lines: 4219
Relevant Lines: 5356

💛 - Coveralls

@ayrat555 ayrat555 merged commit 78a241f into staging-mainnet Apr 9, 2019
@ghost ghost removed the in progress label Apr 9, 2019
@ayrat555 ayrat555 deleted the 1.3.9-release branch April 9, 2019 08:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants