Investigate latest Lightnet Docker image issue

[shimkiv]

Error: Transaction failed with errors:
- {"statusCode":500,"statusText":"Unknown Error: {\"cause\":{\"name\":\"SocketError\",\"code\":\"UND_ERR_SOCKET\",\"socket\":{\"localAddress\":\"::1\",\"localPort\":44662,\"remoteAddress\":\"::1\",\"remotePort\":8080,\"remoteFamily\":\"IPv6\",\"bytesWritten\":41192,\"bytesRead\":8489}}}"}

[shimkiv]

The UND_ERR_SOCKET is typically related to lower-level network communication issues in Node.js environments. This suggests that the problem is occurring at the network connection level rather than being an issue with GraphQL queries or application's business logic.
The localAddress and remoteAddress both being ::1 indicates that the communication is intended to be happening over IPv6 localhost.
GitHub Actions recent changelog does not include any breaking changes.
GitHub status does not show major issues except degraded performance.
Nginx reverse proxy accepts IPv6 comms.
Mina daemon might not accept IPv6 comms.

All this might point to the underlying OS in use. Latest GitHub Actions Ubuntu VM might somehow resolved localhost to IPv6 address that caused the issue.

Retrying GitHub Actions jobs though helped to make CI happy again and it seems this issue is not happening anymore.

Not really sure if we need to do anything else other that monitor it and proceed investigation if it will start to happen more often.

[shimkiv]

Closing for now.

[shimkiv]

It does not happen again...

[shimkiv]

Still no signs of the issue, it seems the root cause was on the GitHub Actions (linux VMs) side.

[shimkiv]

Although it might be related to #658. In which case we need to updated all the localhost entries in o1js GitHub repo with the explicit IPv4 127.0.0.1 reference.