Jason Cihelka

Thanks @en0ma , made those changes!

> This impacts `collections` api. `collections` api uses a trailing slash to work. Without these, it'll return 404 and can impact the current users. I modified it [here](https://github.com/application-research/estuary/pull/443/files#diff-56307bdb7ded67ebe516f562b90384407b21b2d34e8b5766b42602e1fb9705f0L196) - removed...

Hey @en0ma , I'm starting to investigate this. Still seeing a lot of those `unexpected EOF` messages on estuary deals to my SP node. Any new developments on the source...

@gmelodie That's part of it - we have seen some issues with this exact scenario, but in that case we usually get a `context deadline exceeded` error or something similar....

Might make sense to cache the entire list of all shuttle SP pings on the API so that there's a nice central place to look them up.

We should see this resolved with today's 0.2.0 release ref: https://github.com/application-research/estuary/pull/593 Please let us know if you're still seeing this come up! Thanks to @en0ma for this fix 😄

> > Please let us know if you're still seeing this come up! > > How soon should we see this take effect? Do SPs need to do anything on...

Thanks for the reports guys. I was mistaken - they won't all stop immediately as the algorithm is optimistic (it will try each deal at least one more time, before...

Hey @NightDog ! We recently completed a big re-architecture of some core Estuary systems, which resulted in deals flowing again. There are still some of these `unexpected EOF` deals coming...

Just discovered we already have a database called [estuary-metrics](https://github.com/application-research/estuary-metrics). This could serve as a nice place to store all these raw metrics: I think it might make sense to tweak...