This repository was archived by the owner on Jun 19, 2024. It is now read-only.
Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 11 commits
- 20 files changed
- 5 contributors
Commits on Feb 23, 2024
-
Reformat the postgres connection URL to work properly with unix socke…
…t connections (#150) I ran into a problem trying to connect `namadexer` to a postgres database using a Unix domain socket rather than a network hostname. This is necessary in order to run the `server` in environments like Google Cloud Run, which exposes connections to Postgresql as a local domain socket. **The problem:** * Google Cloud SQL creates a socket with a path like `/cloudsql/namada:us-central1:namadexer-db-instance` * Setting `DATABASE_HOST=/cloudsql/namada:us-central1:namadexer-db-instance` would produce a connection URL like the following: ``` postgres://postgres:wow@/cloudsql/namada:my-region:namadexer-db-instance:5432/blockchain ``` * This URL is not valid. **The solution:** * There is an alternate form for the postgres URL, like this: ``` postgres://postgres:wow@dummy-hostname:5432/blockchain?host=/cloudsql/namada:my-region:namadexer-db-instance ``` * In this case, the actual `host` can contain `/` and `:` characters just fine. * The `dummy-hostname` in the host part of the URL must be present for the URL to be parsed properly, but is ignored.
-
Commits on Feb 28, 2024
-
feat: data stored as json (#112)
Saving the data in JSON would allow to store all the transaction data in one table making indexing faster but looking for data maybe a little bit slower. It also has the advantage of removing a lot of code.
Commits on Feb 29, 2024
-
Do not set INDEXER_CONFIG_PATH by default in Dockerfile (#149)
This allows the docker image to be configured via env variables instead of a config file. (When `INDEXER_CONFIG_PATH` is set, the application will only use the file and will not attempt to read its config from env vars.) This is useful for environments like Google Cloud Run where it is simpler to set env vars than to mount a file into the container.
Commits on Mar 11, 2024
-
Added a temp solution for the timeout issue. This PR add a timeout of 30secs which will lead to the indexer to crash if it doesn't get an answer from the RPC-JSON. This is temp until the cometbft/tendermint-rs#1380 is merged in lib.
-
Add metrics for indexer_last_get_block_height and indexer_last_save_b…
…lock_height (#154) This adds `gauge` metrics for last height retrieved from RPC and saved to the database for easier monitoring. Similar to the `tendermint_consensus_latest_block_height{chain_id}` metric in the node, these also provide `chain_name` as a label. Example of what this adds to prometheus: ``` # TYPE indexer_last_save_block_height gauge indexer_last_save_block_height{chain_name="shielded_expedition"} 80144 # TYPE indexer_last_get_block_height gauge indexer_last_get_block_height{chain_name="shielded-expedition"} 80246 ``` --------- Co-authored-by: sleepy ramen <rllola80@gmail.com>
Commits on Mar 12, 2024
-
Propagades timeout error (#162)
The enhancement shifts the timeout mechanism from the block producer to the consumer side. This change ensures that if the block producer stalls, the consumer, instead of indefinitely waiting on an empty channel, will encounter a timeout. This timeout triggers an error that is then easily propagated back to the main function. Consequently, this allows the entire indexing process to terminate gracefully, rather than abruptly due to a panic.
-
feat: get transactions per addresses (#161)
This PR add an endpoint to collect all of the transactions related to an address.
Commits on Mar 13, 2024
Commits on Mar 19, 2024
-
feat: added views for ALL the tx type (#167)
This PR create views when the indexer is launched and the time we create the tables to facilitate visualizing an retrieving the data for all different type of tx (see tx_*). The advantage of this approach is that it doesn't take any supplementary space and doesn't need migration while facilitating interaction with the database.
Commits on Mar 21, 2024
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v0.2.0...v1.0.0