Enehizena Lawrence

@snissn why not replicate it again using same file?

@snissn closing this, as it has been addressed in https://github.com/application-research/estuary/pull/406

@jlogelin can you use the go-car cli util to inspect the blocks for both car files and do a diff

@stuberman are you still experiencing this, so I know if we can close this ticket

> On the verification side, are you thinking a tool that goes through the database, and finds any consistencies? > > So potentially, we can configure some "invariants" that the...

@stuberman I have looked at this, This is a boost issue. I will create an issue in Boost with a possible fix. So basically, Boost HTTP file transfer from Estuary...

> @stuberman I have looked at this, This is a boost issue. I will create an issue in Boost with a possible fix. > > So basically, Boost HTTP file...

Sorry for joining in late. The major causes of this issue are; - Shuttle crash during data transfer - Corrupted data There has been major work to stabilize the infra...

@gmelodie you meant `/health` right? Also, I am not sure adding this endpoint is necessary as it already exists for both primary at https://github.com/application-research/estuary/blob/master/handlers.go#L124 and shuttle at https://github.com/application-research/estuary/blob/master/cmd/estuary-shuttle/main.go#L975. The only...

> @en0ma we should document both the version and the health endpoints @gmelodie how do you mean document them? Also, I think the question we should be asking is how...