Neel Virdy
Neel Virdy
**Describe the bug** 1. User A uploads small file, shuttle 1 is selected 2. shuttle 1 gets turned off 3. User A uploads any other file to any shuttle or...
See: https://filecoinproject.slack.com/archives/C016APFREQK/p1671516580176459 the salt and the codepath used to generate the credentials via `./estuary setup` differ from how the register user path does it on estuary-www. the /login endpoint only...
Similar to https://estuary.tech/verify-cid, we should have an endpoint and a page to query a deal id to check deal state according to `lotus`. cc @jlogelin @en0ma @jcace
We shouldn't queue every pinned content to be rechecked on startup. We should only need to queue contents that we may need to make more deals for. Could we track...
Instead of requiring node operators to manually manage datadirs for each shuttle, we can auto-gen the folder as `pinQueue-`. This also communicates that the datadir needs to stay associated to...
Try running a shuttle with a --datadir= value that doesn't exist as a directory yet. You get a /peer.key does not exist error instead of it being created for you....
**Is your feature request related to a problem? Please describe.** Not enough visibility into pin queue size on prod until pinning starts getting backed up. **Describe the solution you'd like**...
blocked on: 1. populating DealStatus in util.Content 2. making zoneId available in util.Content, or changing the /staging-zones/:id param to accept the zone content id instead of the zone id
## What Support the optional `strict` parameter in function definitions, which was released with Structured Outputs. When `strict` is provided, the API requires `additionalProperties` to be provided in the `parameters`...