feat(api): first action handlers

[merklefruit]

• after feat(db): added SQL db abstraction; minor nits; config file parsing #5
• closes Implement Action handling #3

[mempirate]

Quick note: for any actions on the registry state (reading / writing), the idea is to first call handle.wait_for_sync().await, to ensure that the DB has been synced at the start of the epoch before doing any DB operations. I feel like this will eliminate some race conditions

[merklefruit]

Quick note: for any actions on the registry state (reading / writing), the idea is to first call handle.wait_for_sync().await, to ensure that the DB has been synced at the start of the epoch before doing any DB operations. I feel like this will eliminate some race conditions

I see, it makes sense! However as it currently stands this comes with the drawback that if we are still syncing the API will just hang until it is synced. The only good alternative I see is to perhaps return an error saying that the registry is still syncing and to try again later. Wdyt?

[mempirate]

Yeah that's the drawback indeed. I think waiting for a second (hopefully not more than that) might be a better option no? Or we return HTTP Too Early, which would require the client to retry.

[merklefruit]

I like the timeout option, and didn't know about that specific HTTP code. nice!

[mempirate]

We could also do this at registration time (& at sync time for external sources) and save them in the DB. We might actually have to do that anyway to check if the validator is valid.

[mempirate]

#11

[merklefruit]

addressed in #12

[mempirate]

Why is this an Option?

[mempirate]

Oh I see, if None we return everything. I think we should disambiguate with list_registrations, list_validators, list_operators instead (which take no arguments)

[merklefruit]

done in latest commit