Satellite error (reading from server: read: connection timed out)

Satellite error (reading from server: read: connection timed out)

[idelvall (maintainer)]: The read: connection timed out errors when building on a Satellite were caused by the client stripping the gRPC status code from the error. Fixed and released in v0.7.19: upgrade earthly.

Context from the issue

gh:earthly/earthly#3255: Issue earthly/earthly#3255 (closed, 8 comments): We have been experiencing this failure occasionally, when running in satellites over last days. I've seen this happening both in GH actions as well as locally.

Init 🚀
--------------------------------------------------------------------------------

           satellite | satname is waking up. Please wait...
           satellite | ...amplifying transmission signal...
           satellite | ...testing antennas...
Shareable link: https://ci.earthly.dev/logs?logId=a9f1cc10-4427-4b05-b3ba-9244da7ffd25
Error: error reading from server: read tcp X.X.X.X:Y->100.21.239.443:443: read:...

Issue gh:earthly/earthly#3255: the reporter asked: Issue earthly/earthly#3255 (closed, 8 comments): We have been experiencing this failure occasionally, when running in satellites over last days. I've seen this happening both in GH actions as well as locally.

Init 🚀
--------------------------------------------------------------------------------

           satellite | satname is waking up. Please wait...
           satellite | ...amplifying transmission signal...
           satellite | ...testing antennas...
Shareable link: https://ci.earthly.dev/logs?logId=a9f1cc10-4427-4b05-b3ba-9244da7ffd25
Error: error reading from server: read tcp X.X.X.X:Y->100.21.239.443:443: read:... The verified answer was: [idelvall (maintainer)]: The read: connection timed out errors when building on a Satellite were caused by the client stripping the gRPC status code from the error. Fixed and released in v0.7.19: upgrade earthly. Evidence thread: https://github.com/earthly/earthly/issues/3255