-
The test is flakey when the test runner is run in parallel
-
"server" and "CLI" are not the same thing, yet we require both on the command line to launch what? A server? A CLI? A client server? A server client? This is bad usability.
-
The indexer isn't correctly initialized if the `startup-blocks` doesn't exist. The domain socket server will never get started meaning it never can accept commands.
```
rm -r $HOME/.mina-indexer/s…
-
This is the only file in the blocks dir: `mainnet-2-3NLyWnjZqUECniE1q719CoLmes6WDQAod4vrTeLfN7XXJbHv6EHH.json`
```sh
target/release/mina-indexer server cli -l ~/mainnet.json -s ~/.mina-indexer/blo…
-
... yet we don't really need mina-rs.
-
Consider the following entry in the genesis ledger:
```javascript
{
"pk": "B62qqDJCQsfDoHJvJCh1hgTpiVbmgBg8SbNKLMXsjuVsX5pxCELDyFk",
"balance": "148837.2",
"delegate": "B62qp8Vq6n4VHq…
-
The issue:
Asking the `mina-indexer` for account information after initialization on mainnet blocks results in a file error
`Error: IO error: While open a file for random read: /mnt/indexer-bloc…
-
The `mina-indexer` server can be run using a YAML configuration file with the `config` subcommand, however, all paths present in that file must be absolute, and cannot use environment variables like `…
-
Using ```mina-indexer --version
mina-indexer 0.1.1```
Trying to understand the process for importing blocks. As I understand the precomputed blocks have to be in a local directory, and that direct…
-
when running the regression testing suite, upon encountering a failure, the local file `mina-indexer.sock` is not removed. The user must then manually remove the file to allow the tests to pass