this is just a PR to suggest and discuss. I moved the ethereum blockheaders from /tests to /bin/node/packages/blocks/ethereum (probably should just start with /packages at root level.
Anyway, I wanted to see how far I would get running everything and I have two questions, one for each of you:
start_block and end_block did not get read from the config file, weirdly; other params did; any ideas @vadim-frolov ?
when we get a first response and want to insert this as an operation in the DBLoader, it looks up the primary key from the hashmap, but returns none (and panics on .expect()eureka-sink-postgres/db/src/ops.rs:56:14
this hashmap should have been filled out during load_tables(), which we have called from main
however it is not filled out, because the query returns an empty vector for all_tables_and_cols (DBLoader.rs:85)
during setup however, we do make the tables (as validated by using a DB viewer connected to postgres instance)
any ideas @jorgeantonio21 ?
let me know if you can or cannot reproduce these errors, thx!
this is just a PR to suggest and discuss. I moved the ethereum blockheaders from
/teststo/bin/node/packages/blocks/ethereum(probably should just start with/packagesat root level.Anyway, I wanted to see how far I would get running everything and I have two questions, one for each of you:
start_blockandend_blockdid not get read from the config file, weirdly; other params did; any ideas @vadim-frolov ?when we get a first response and want to insert this as an operation in the DBLoader, it looks up the
primary keyfrom the hashmap, but returnsnone(and panics on.expect()eureka-sink-postgres/db/src/ops.rs:56:14load_tables(), which we have called frommainall_tables_and_cols(DBLoader.rs:85)let me know if you can or cannot reproduce these errors, thx!