160 Commits (ec2e25bdd1eebfe034c3f1f91277fcfd07dc1b55)

Author	SHA1	Message	Date
Alex Garibay	6d61420f32	Address code review feedback	6 years ago
Alex Garibay	b6bc6cc2f8	Add backoff for bad gateway errors	6 years ago
Alex Garibay	76970f6258	Finish documentation and tests for request backoffs	6 years ago
zachdaniel	75c88fac85	WIP: test rolling window and request coordinator	6 years ago
Alex Garibay	1f021a7e1f	Provide default 2nd arg for executing contract functions on Geth (#970)	6 years ago
Amanda Sposito	b86335cf34	Add 'transaction_index' in the fetchers to save at 'internal_transaction' ... Add 'transaction_index' in the fetchers to save at 'internal_transaction'	6 years ago
Sebastian Abondano	2b8ceb4e32	Update block reward contract beneficiary balances ... Why: * "Parity’s consensus engine allows using a smart contract for block reward calculation." - see https://wiki.parity.io/Block-Reward-Contract for details. This means that we need to use `trace_block` (https://wiki.parity.io/JSONRPC-trace-module#trace_block) to fetch the block reward contract beneficiaries and update their balances. Currently this doesn't happen so there are addresses (block contract reward beneficiaries) with inaccurate balances and missing rows in the `address_coin_balances` table. * Issue link: https://github.com/poanetwork/blockscout/issues/767 This change addresses the need by: * Adding `EthereumJSONRPC.fetch_beneficiaries/2` to help us fetch the block reward contract beneficiaries of a given block range. This only works with Parity. * Editing Indexer's dev and prod config by adding `trace_block` config to `:method_to_url`. * Adding `block_reward_contract_beneficiaries` to `Indexer.AddressExtraction` for it to know how to get addresses in this scenario. * Editing `Indexer.Block.Fetcher.fetch_and_import_range/2` to get block reward contract beneficiaries, create their addresses if they don't yet exist, and update their coin balances.	6 years ago
Luke Imhoff	1100f56fa1	Test WebSocketClient with cowboy_websocket_handler ... Allows to properly simulate TCP disconnect.	6 years ago
Luke Imhoff	b1f4696569	Reconnect, rerequest, and resubscribe when websocket disconnects ... * Use struct, `%EthereumJSONRPC.WebSocket.WebSocketClient.Options{}` to hold `web_socket_options`. * `%EthereumJSONRPC.WebSocket.Registration{}` * Record `t:EthereumJSONRPC.request/0` in `%EthereumJSONRPC.WebSocket.Registration{}`, so that the request can be re-requested if the websocket disconnects and reconnects. * Drop server-side `subscription_id` from `%EthereumJSONRPC.WebSocket.Registration{}` as it can retrieved from `request` now. * `EthereumJSONRPC.WebSocket.WebSocketClient` * Track whether the web socket is connected or not, so that requests aren't sent when in the disconnected state. This prevents double-sends as `handle_call` can be called before `onconnect`, which caused that first subscribe to be sent twice. * Instead of the subscriber knowing the server-side subscription id, an opaque `t:reference/0` is used, so that the reference is stable in the subscriber's `%Subscription{}`, but the subscription ID can change on reconnect, which means replacing `subscription_id_to_subscription` in `%WebSocketClient{}` with 3 maps 1. `subscription_id_to_subscription_reference` - used translate server-side, per-connection subscription to the stable reference in `subscription_reference_to_subscription` 2. `subscription_reference_to_subscription_id` - used to convert stable reference to subscription id to unsubscribe. 3. `subscription_reference_to_subscription` - used to get full Subscription, including the subscriber_pid for when subscription messages are delivered or the subscription needs to be resubscribed using the `web_socket_options`. * `ondisconnect`, `:reconnect` immediately. * When disconnecting, tell unsubscribers they were successful. * Hold any json_rpc or subscribe requests to retry on reconnect. * Hold any subscriptions to resubscribe on reconnect. * `onconnect` * re-request the saved json_rpc and subscribe requests. * issue new requests to re-establish the subscriptions that had already succeeded in their subscribe requests. * `%EthereumJSONRPC.Subscription{}` * Replace `id`, which did match the server created ID, with a `t:reference/0`, which allows for indirection and for the server created ID to change on reconnect while the subscriber does not need to care about the reconnections. * `EthereumJSONRPC.WebSocket` * `options` is switched from a Keyword.t to a struct, `t`, so that it is easier to pattern match for the reconnect logic in `WebSocketClient`. * `web_socket_options` is no longer a generic `term` because the code did require it to be a map with a `:web_socket` key for the `t:GenServer.server/0`.	6 years ago
Luke Imhoff	6b53d96075	_optons -> _options	6 years ago
Luke Imhoff	0b5729c144	correclty -> correctly	6 years ago
Luke Imhoff	96d5aea311	Block.SecondDegreeRelation ... The database table block_second_degree_relations contains links between the `uncle_hash` of the uncle and the `nephew_hash` of the block that said `uncle_hash` was an uncle. It also has a `uncle_fetched_at` that is `null` until the `uncle_hash` is confirmed as fetched in the database. This does not contain such a fetcher.	6 years ago
Luke Imhoff	48b302f935	Return uncles from EtherumJSONRPC.Block.elixir_to_params	6 years ago
Luke Imhoff	b32f263eda	Allow status to be nil until internal transactions are indexed ... For pre-Byzantium or Ethereum Classic (which never adopted EIP-658), the status in receipts will be `nil`, but we still want to ensure the status is eventually set, so when setting internal transactions, in addition to setting `internal_transactions_indexed_at` and `created_contract_address_hash`, the `status` will be updated. * If the `status` is already set, leave it as is * If the `status` is not set * If the last internal transaction for a transaction has an error, `status` is `:error` * If the last internal transaction for a transaction has no error, `status` is `:ok`	6 years ago
Luke Imhoff	baa5746a25	Don't infer status for gas and gas_used ... The heuristic of gas == gas_used is an error has been proven to be incorrect with test transactions on Ethereum Classic, so remove it. When the status is not given it will be propagated up as `nil` and must be filled in by the caller using the internal transactions.	6 years ago
Alex Garibay	0a922bb1a3	Display primary address name when available (#610) ... * Display primary address name in overview tile * Display primary address name in links Co-authored-by: Luke Imhoff <Kronic.Deth@gmail.com>	6 years ago
Luke Imhoff	c10b6c218b	Disable another test that times out on Infura	6 years ago
Igor Florian	d460fb8d50	Deal with :bad_gateway errors while querying contracts functions ... We were counting on a specific error standard from ethereum_jsonrpc for formatting the errors from the SmartContract.Reader and we ended up getting an exception because we were getting a different error. There are at least two different error standards returned from ethereum_jsonrpc: 1. ```elixir { :ok, [ %{ id: id, jsonrpc: "2.0", error: %{ code: "12345", message: "<message>" } } ] } ``` 2. ```elixir {:error, {:bad_gateway, "<url>"}} ``` We're now expecting the :bad_gateway error so we can format it properly.	6 years ago
Luke Imhoff	ded4ec4246	Disable tests for Geth that timeout on Infura ... Infura experiencing timeouts with 50 second timeout set.	6 years ago
Stamates	18380efe0a	fix broken tests ... Co-authored-by: Luke Imhoff <luke.imhoff@dockyard.com>	6 years ago
Luke Imhoff	1ad6f068f5	Failing regression test for #638	6 years ago
Luke Imhoff	c4f8b64a96	Cover EthereumJSONRPC.Receipts	6 years ago
Luke Imhoff	9e6198da1b	Cover EthereumJSONRPC	6 years ago
Luke Imhoff	854230f25f	Better error message when receipt cannot be converted to elixir ... Resolves #618 Use the validation pattern of reducing all entries while ok, but then switching to accumulating all errors once any error occurs. Finally, because the fields that identify the receipt precisely, such as the transactionHash or blockNumber may not have an error, include the full receipt the ArgumentError exception.	6 years ago
Felipe Renan	e4a9463584	Add tests to EthereumJSONRPC.execute_contract_functions/3	6 years ago
Luke Imhoff	72bd8d7c68	Ether Mainnet needs a block interval of 25000ms for consistency ... Using the 5000ms for POA leads to timeouts for the subscribe tests.	6 years ago
Luke Imhoff	cddd810a58	Use :websocket_client for EthereumJSONRPC.WebSocket ... :websocket_client can properly use :ssl_verify_hostname.verify_fun/3 for :verify_fun and allow for the handshake to both be secure and pass for infura.	6 years ago
Luke Imhoff	727459ec92	Use `socket`'s Socket.Web for another implementation of WebSockets	6 years ago
Luke Imhoff	c8c53405fc	Subscribe to newHeads for realtime indexer ... Separate Catchup and Realtime indexer's fetching, so that Catchup continues to use the old polling, `EthereumJSONRPC.json_rpc` while Realtime subscribes with `EthereumJSONRPC.subscribe`. Because Realtime gets notified of new blocks through the subscription, it no longer has a Sequence, so Sequence has been removed from `%BlockFetcher{}`. There is also no block concurrency or block batch size for Realtime, so that was removed from `%BlockFetcher{}` too and moved to `%BlockFetcher.Catchup{}`. Because Realtime requires a websocket to be connected, there is now an `Indexer.BlockFetcher.Realtime.Supervisor` that supervises the `Indexer.BlockFetcher.Realtime.WebSocket` and `Indexer.BlockFetcher.Realtime`. `Indexer.BlockFetcher.Realtime` because it is waiting on notifications from is subscription becomes a `GenServer` insteado of a `Task`, so it can be supervised normally. BlockFetcher.Supervisor becomes a normal `Supervisor` of `Catchup.Supervisor` and `Realtime.Supervisor`. As Realtime is using `EthereumJSONRPC.subscribe`, `subscribe_named_arguments` has been added as a sibling of `json_rpc_named_arguments` in the `:indexer` `config`s.	6 years ago
Luke Imhoff	dc5ec15619	Support for Moxing WebSocket	6 years ago
Luke Imhoff	6036dea12d	Websocket json_rpc, subscribe, and unsubscribe against Sokol	6 years ago
Alex Garibay	f81d20fc24	Add support for multiple return types in contracts (#562)	6 years ago
Andrew Cravenho	28e485a5c1	Replace poanetwork/poa-explorer urls with poanetwork/blockscout	6 years ago
Alex Garibay	8b16f81b73	Catalog token transfers and tokens during indexing (#484) ... * Fetch token information asynchronously during indexing * Include token transfers imports in main importer * Extract token transfers when importing blocks while indexing * Move ecto to explorer deps * Update References to the Indexer namespace * Add token insertions with main importer * Import token address/type during block indexing	6 years ago
Luke Imhoff	3427873986	{:ok, nil} -> {:error, :not_found} in handle_get_block_by_tag ... Fixes #490 Compatibility with paritytech/parity-ethereum#8281, which fixed paritytech/parity-ethereum#8028 and made pending return be compliant with Ethereum docs.	6 years ago
Luke Imhoff	e3f7581572	Historical Address Balances	6 years ago
Amanda Sposito	dae9ff2f10	Add support to Pluggable Transport and HTTP transport modules	6 years ago
Amanda Sposito	b8a8f083d2	Add parser function to handle addresses arguments when calling the blockchain	6 years ago
Amanda Sposito	421b8df68c	Add treatment to decode string values from blockchain	6 years ago
Lucas Narciso	4b9bc4a69f	Create EthereumJSONRPC.Encoder ... It deals with encoding and decoding data to be sent to, or that is received from, the blockchain.	6 years ago
Lucas Narciso	e81281edf6	Fix typo in etheream_jsonrpc_test.exs ... Rename it to ethereum_jsonrpc_test.exs	6 years ago
Luke Imhoff	ac841af29f	Split batches on 504 Gateway Timeout ... Under the assumption that gateway timeouts occur because it is taking too long for Sokol nodes to respond to batch requests, 504 Gateway Timeout should be treated the same as 413 Request Entity Too Large: the batch should be split in half and retried. If we still get 504 Gateway Timeouts after this change, we'll need to add a delay before retry.	6 years ago
Luke Imhoff	8f827ecfa6	Use Mox by default for local integration tests ... How to run without Mox is in the root `README.md`. Run all combinations of Variant and Transport on CircleCI to ensure that Mox matches HTTP behavior, so Mox can be used for fast local testing: * Geth, HTTP * Geth, Mox * Parity, HTTP * Parity, Mox Using Mox locally also lessens load on Sokol and the Infura API key the tests use for Geth under the assumption that we do far more local testing than CI testing. May help with #340, but does not fix the root cause, which is now known as `Sequence` not chunking ranges correctly on retry.	6 years ago
Luke Imhoff	834ad23f26	Standardize JSONRPC response ... Restrict response to only those fields supported by the JSON-RPC 2.0 standard, which means that level of keys is validated, so we can indicate that switch to atom keys.	6 years ago
Luke Imhoff	466c1e76f6	Request transport module and options for all JSONRPC calls ... To lessen load on Sokol chain nodes during testing and to allow substituting different transports than HTTP, such as IPC, in the future, pass the transport module and its options to any call to `EthereumJSONRPC.json_rpc`. This will allow us to use a `mox` module in local testing, so we only do true chain integration testing in CircleCI.	6 years ago
Luke Imhoff	d9d9e54dac	Remove problematic test ... Test is rewritten a separate branch, but it is breaking CI tests now, so remove it from this branch and restore with rewrite on other branch.	6 years ago
Luke Imhoff	5ad0ed4571	Use tags to exclude Variant running incompatible tests	6 years ago
Luke Imhoff	3c680ff953	Log, but do not fail tests, when 502 Bad Gateway occurs ... 502 Bad Gateway is an intermittent problem that needs to be fixed by ops when the JSONRPC servers are under heavy load, so they should not fail the test runs.	6 years ago
Luke Imhoff	4ecfb3b409	CircleCI tests for Geth	6 years ago
Luke Imhoff	cac1cab39c	Geth receipts compatibility ... When testing transaction receipt processing using Geth against Ethereum Mainnet, a number of missing features were discovered: * Support for `to` and `from` addresses in receipts * The need to derive status for pre-Byzantium transactions by using the supplied gas from the transaction and the gasUsed in the receipt to check for out-of-gas.	6 years ago