Couldn't read LoopLock response

[MeijeSibbel]

Couldn't read LoopLock response

[lukechampine]

This is probably due to the timeout code not accounting for the latency to the host. Should definitely be fixed in #31...
Hmm. The stack trace indicates that you're using commit ba043c0b71e4, which doesn't include #31.

[MeijeSibbel]

Closing for now until issue resurfaces.

[MeijeSibbel]

2020-06-13T22:56:37.365Z        WARN    storage/bucket.go:182   failed to upload the content{"path": "/thirty-hosts/1b_2", "request_id": "97a579cddaf044b5933e6ae8c02861f996c228a3", "bucket": "thirty-hosts", "key": "1b_2/null/1", "contractSetName": "85ec97fd-ed66-4984-87ef-6c4295af1034", "error": "failed to sync the pseudo file: could not upload to some hosts: \n5837807c: NewSession: Lock: couldn't read LoopLock response: read tcp 167.71.76.88:42592->93.160.14.233:9982: i/o timeout\nb4c144a6: NewSession: dial tcp 81.98.24.32:9982: i/o timeout"}

[jkawamoto]

This discussion https://github.com/lukechampine/us/pull/95/files#r466051856 relates to this issue.

[MeijeSibbel]

Status update: The LoopLock issue is related to the transaction pool problems on the host side. The issue is currently being investigated.

[MeijeSibbel]

Same idea as #34 (comment), with some host updates in the near future these timeouts should be lowered.