189 Commits (8489c6db5b8c7da18a02ba38467f1a9b5de6a7f4)

Author	SHA1	Message	Date
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	32535bd73c	Simplify WebSocketClient.respond_to_registration ... All clauses set request_id_to_registration in state to new_request_id_to_registration, so it does not need to be passed. The catchall cause does the equivalent because new_request_id_to_registration was request_id_to_registration already as Map.pop popped nothing.	6 years ago
Konstantin Zolotarev	ff8053d656	fix formatting	6 years ago
Konstantin Zolotarev	3eee0a2944	Fix spacing	6 years ago
Konstantin Zolotarev	0604f7a234	Fixes for pr comments	6 years ago
Konstantin Zolotarev	f89a27adf4	Fixes for ganache integration	6 years ago
Nam Chu Hoai	d17917ce30	Allow unsecure WebSocket connections ... Some setup like ours will have the WebSocket connection in a private network to a local node and thus do not require a secure connection. This change allows to specify ws:// instead of wss:// endpoints as well as reading from the ENV var for the geth config of the indexer Co-authored-by: Luke Imhoff <luke.imhoff@dockyard.com>	6 years ago
Luke Imhoff	5d0c1fc18a	succucessfully -> successfully	6 years ago
Luke Imhoff	8da99addcb	JSONR-RPC -> JSON-RPC	6 years ago
Luke Imhoff	b93377cccd	chainId -> chain_id for elixir variable	6 years ago
Luke Imhoff	64bd973076	suscribed -> subscribed	6 years ago
Luke Imhoff	a4509ed42e	resultscan -> results can	6 years ago
Luke Imhoff	36c939f14a	Ethereums -> Ethereum	6 years ago
Luke Imhoff	fa1c9ac944	passsed -> passed	6 years ago
Luke Imhoff	076d12d905	quanity -> quantity	6 years ago
Luke Imhoff	7eddae586e	transfered -> transferred	6 years ago
Luke Imhoff	480300b542	Ethreums -> Ethereum	6 years ago
Luke Imhoff	6dbb511700	failes -> fails	6 years ago
Luke Imhoff	e20c98949e	econded -> encoded	6 years ago
Luke Imhoff	33c12ca780	Ethererum -> Ethereum	6 years ago
Luke Imhoff	dc669423c2	peformed -> performed	6 years ago
Lokraan	92f99cac22	Ran mix format on code. ... Confirm to CircleCi tests. Was failing due to not updating gettext, javascript lint standards, and an accidental edit in `block_controller.ex` where I added `:block => :required` to `necessity_by_association`. I also updated the query in `Explorer.Chain.address_to_validation_count/1` in order to make it more functional (use built in Ecto queries instead of hand written SQL query.) Conform to code review comments. Instances of "Blocks #{gettext("Validated")}" -> gettext("Blocks Validated") The class for the validation link in the mobile menus was "nav-link" instead of "dropdown-item" so I changed it. Ran `mix gettext.extract --merge` in order to update the gettext("Blocks Validated") Conform to code review. Added `active` classes to the corresponding links on mobile navs. Removed redundant if statements when in the page that required the content. Created a function in `address_view.ex` called `validator?` that accepts the number of validations and returns true if greater than 0. Replaced `if @validation_count > 0` with `if validator?(@validation_count`. "Please add the active class to the dropdown item." Added the `active` class where the page was active on for mobile and desktop navs. Also replaced `nav-item` with `dropdown-item` on the mobile navs where it was necessary.	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	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
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	b7d7ceaaa0	Temporary work-around for #673 value-only transactions ... The gas_used == gas heuristic means failures pre-Byzantium (and on ETC) is only a heuristic: it fails for value-only transactions where ETC submitters are using exactly the transaction base fee (21,000 gas) often. Because this is so common, we'll use this work-around now until we can restructure EthereumJSONRPC and Indexer to verify pre-Byzantium status using Internal Transactions.	6 years ago
Luke Imhoff	d42fbdb06e	Treat "status" => nil the same as no status ... While Geth does not return a status for pre-Byzantium blocks, Parity returns `"status" => nil`, so treat `"status" => nil` as if `"status"` wasn't there.	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
Igor Florian	c2ff17756c	Get TokensBalance in the Blockchain ... We're now able to get the balances from a Address given it's address_hash, block_number and token_contract_address_hash.	6 years ago
Luke Imhoff	9a4a23b5c5	Remove EthereumJSONRPC.WebSocket impl that don't work with Infura ... Don't rebase them out, so that we have the history that we tried to use `socket` and `websockex`, but we couldn't get them to work.	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
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	f2884992a7	Fetch realtime internal transactions and balances synchronously ... Fixes #366 Queuing the internal transactions and balances to be fetched asynchronously for realtime blocks lead to upto 15 minute delay between when a block appeared and the internal transaction was drained from the queue. It is a better user experience to not see the realtime blocks at all than to see them incomplete, so fetch the internal transactions and then the balances before importing the whole tree of data instead of using the catchup asynchronous queues.	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	537f090597	Create Explorer.SmartContract.Reader ... This new module is the main entry point for getting results of a smart contract function. It accepts a smart contract hash and a list of functions names and its arguments (when applicable) in order to execute those functions and return their results. Before actually making the call to the blockchain, the function name is encrypted and the arguments are encoded. The EthereumJSONRPC deals with this, encrypting the name of the function using the Keccak256 algorithm and encoding the arguments based on their type. The call to the blockchain is also made by EthereumJSONRPC. The result is then decoded - as it comes in the same type of encoding that has been sent - by the EthereumJSONRPC lib as well, and returned. The return is a list of results of calling the functions in the blockchain. Note that each function may return more than one result, so for each functions there is a list of results.	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	acdbed2ba7	Support eth_call on EthereumJSONRPC ... It just makes the call, so the smart contract function name should already be encrypted and its arguments already encoded. It supports multiple function calls, by receiving a list of hashs and data, e.g. `[{contract_hash_1, call_data_1}, {contract_hash_2, call_data_2}]`.	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