Restic to remote rclone server does not properly retry failed uploads on network outage

Hi restic Team,
First: great piece of Software. When the network stays up everything works really well.
What's the version of restic you used?
Client: restic 0.13.1 compiled with go1.18 on windows/amd64
Server: restic 0.13.1 compiled with go1.18 on linux/arm
rclone:

rclone v1.58.0

os/version: raspbian 11.3
os/kernel: 5.15.32-v7l+ (armv7l)
os/type: linux
os/arch: arm
go/version: go1.17.8
go/linking: static
go/tags: none

cmdline: /usr/bin/rclone serve restic /mydir --addr :8085 --stats 1h --user myuser --pass mypass -vvv --syslog
Almost every time a network outage happens I am losing packs. rclone deletes the partial pack and restic writes to the log that it should retry the pack but it just doesn't. Then I get a corrupted index and subsequent backups depend on the missing pack.
Here is the latest log on both sides, Server public IP was replaced by <IP_ADDRESS> Client public IP with <IP_ADDRESS>:
client log:
Save(<data/712aeadd39>) returned error, retrying after 720.254544ms: client.Post: Post "http://myserver/mydir/data/712aeadd39af26e28cef10f2890fad47698aefca700c2bbdaaa027d11336fed8": readfrom tcp <IP_ADDRESS>:49918-><IP_ADDRESS>:8085: write tcp <IP_ADDRESS>:49918-><IP_ADDRESS>:8085: wsasend: An existing connection was forcibly closed by the remote host.
Save(<data/366e667bb2>) returned error, retrying after 582.280027ms: client.Post: Post "http://myserver/mydir/data/366e667bb22a3a2dfc807daf3e503a9e90f7c1039af6af363ce047c71166bc33": readfrom tcp <IP_ADDRESS>:49920-><IP_ADDRESS>:8085: write tcp <IP_ADDRESS>:49920-><IP_ADDRESS>:8085: wsasend: An existing connection was forcibly closed by the remote host.
Save(<data/00b4bf78a6>) returned error, retrying after 552.330144ms: client.Post: Post "http://myserver/mydir/data/00b4bf78a6e098d50bd6d24d99a3c126cbaa42766679bd03daa057214e93fa64": readfrom tcp <IP_ADDRESS>:49917-><IP_ADDRESS>:8085: write tcp <IP_ADDRESS>:49917-><IP_ADDRESS>:8085: wsasend: An existing connection was forcibly closed by the remote host.
Save(<data/f79a32edf3>) returned error, retrying after 468.857094ms: client.Post: Post "http://myserver/mydir/data/f79a32edf3c1abe3538abe46124a375f2939d6c7e1ae2d4506ff749b7de80354": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/47a478f9a6>) returned error, retrying after 462.318748ms: client.Post: Post "http://myserver/mydir/data/47a478f9a657533af9aa2ce3df77b3ca42ea5d578c00e2f63259240d066a65d6": readfrom tcp <IP_ADDRESS>:49916-><IP_ADDRESS>:8085: write tcp <IP_ADDRESS>:49916-><IP_ADDRESS>:8085: wsasend: An existing connection was forcibly closed by the remote host.
Save(<data/bfa6773a62>) returned error, retrying after 593.411537ms: client.Post: Post "http://myserver/mydir/data/bfa6773a62d0c9eac5bcbc0fda7e87addb9eeb40b7b6cccf8d791eccad58aef8": readfrom tcp <IP_ADDRESS>:49919-><IP_ADDRESS>:8085: write tcp <IP_ADDRESS>:49919-><IP_ADDRESS>:8085: wsasend: An existing connection was forcibly closed by the remote host.
Save(<data/49f62efde4>) returned error, retrying after 282.818509ms: client.Post: Post "http://myserver/mydir/data/49f62efde4da12b614f0cdca23586721d4184089286210b041ce1e91e67d159e": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/8e3630f07a>) returned error, retrying after 328.259627ms: client.Post: Post "http://myserver/mydir/data/8e3630f07a668c5a91cf86fb6c53da2daf2df156d465bb05c578d5876eb0410f": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/de60b0a475>) returned error, retrying after 400.45593ms: client.Post: Post "http://myserver/mydir/data/de60b0a4751fd597fcbb436ef70cc11a1592f7573093637277804b91d9768ddd": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/e29bc6b42c>) returned error, retrying after 298.484759ms: client.Post: Post "http://myserver/mydir/data/e29bc6b42ccbbc9017953b3b712ed374fa456de1707011a73647ec58441b96c2": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/45cebc8f1f>) returned error, retrying after 507.606314ms: client.Post: Post "http://myserver/mydir/data/45cebc8f1fd59db0f2201b1581a7e2503a86cd8b75e66eedba0e7b69d4836f41": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/ad91c0622b>) returned error, retrying after 656.819981ms: client.Post: Post "http://myserver/mydir/data/ad91c0622b310292cd3c2e82b7c63426ca8d418c8a8a04a16e6c6148cc579fe3": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/00b4bf78a6>) returned error, retrying after 535.697904ms: client.Post: Post "http://myserver/mydir/data/00b4bf78a6e098d50bd6d24d99a3c126cbaa42766679bd03daa057214e93fa64": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/49f62efde4>) returned error, retrying after 660.492892ms: client.Post: Post "http://myserver/mydir/data/49f62efde4da12b614f0cdca23586721d4184089286210b041ce1e91e67d159e": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/712aeadd39>) returned error, retrying after 613.543631ms: client.Post: Post "http://myserver/mydir/data/712aeadd39af26e28cef10f2890fad47698aefca700c2bbdaaa027d11336fed8": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/366e667bb2>) returned error, retrying after 587.275613ms: client.Post: Post "http://myserver/mydir/data/366e667bb22a3a2dfc807daf3e503a9e90f7c1039af6af363ce047c71166bc33": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/8e3630f07a>) returned error, retrying after 726.667384ms: client.Post: Post "http://myserver/mydir/data/8e3630f07a668c5a91cf86fb6c53da2daf2df156d465bb05c578d5876eb0410f": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/f79a32edf3>) returned error, retrying after 594.826393ms: client.Post: Post "http://myserver/mydir/data/f79a32edf3c1abe3538abe46124a375f2939d6c7e1ae2d4506ff749b7de80354": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/47a478f9a6>) returned error, retrying after 884.313507ms: client.Post: Post "http://myserver/mydir/data/47a478f9a657533af9aa2ce3df77b3ca42ea5d578c00e2f63259240d066a65d6": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/e29bc6b42c>) returned error, retrying after 538.914789ms: client.Post: Post "http://myserver/mydir/data/e29bc6b42ccbbc9017953b3b712ed374fa456de1707011a73647ec58441b96c2": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/45cebc8f1f>) returned error, retrying after 527.390157ms: client.Post: Post "http://myserver/mydir/data/45cebc8f1fd59db0f2201b1581a7e2503a86cd8b75e66eedba0e7b69d4836f41": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<lock/1897e71612>) returned error, retrying after 430.435708ms: client.Post: Post "http://myserver/mydir/locks/1897e71612fa2615cf6243e2c743878e3c90daccf8bfcf9ad2f9a9736d2d0862": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/de60b0a475>) returned error, retrying after 803.004957ms: client.Post: Post "http://myserver/mydir/data/de60b0a4751fd597fcbb436ef70cc11a1592f7573093637277804b91d9768ddd": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/bfa6773a62>) returned error, retrying after 1.021868578s: client.Post: Post "http://myserver/mydir/data/bfa6773a62d0c9eac5bcbc0fda7e87addb9eeb40b7b6cccf8d791eccad58aef8": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/ad91c0622b>) returned error, retrying after 594.835683ms: client.Post: Post "http://myserver/mydir/data/ad91c0622b310292cd3c2e82b7c63426ca8d418c8a8a04a16e6c6148cc579fe3": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/00b4bf78a6>) returned error, retrying after 896.717884ms: client.Post: Post "http://myserver/mydir/data/00b4bf78a6e098d50bd6d24d99a3c126cbaa42766679bd03daa057214e93fa64": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/e29bc6b42c>) returned error, retrying after 1.409144665s: client.Post: Post "http://myserver/mydir/data/e29bc6b42ccbbc9017953b3b712ed374fa456de1707011a73647ec58441b96c2": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/366e667bb2>) returned error, retrying after 794.905494ms: client.Post: Post "http://myserver/mydir/data/366e667bb22a3a2dfc807daf3e503a9e90f7c1039af6af363ce047c71166bc33": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/712aeadd39>) returned error, retrying after 1.53600189s: client.Post: Post "http://myserver/mydir/data/712aeadd39af26e28cef10f2890fad47698aefca700c2bbdaaa027d11336fed8": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/49f62efde4>) returned error, retrying after 1.346309062s: client.Post: Post "http://myserver/mydir/data/49f62efde4da12b614f0cdca23586721d4184089286210b041ce1e91e67d159e": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.

[SNIP]

Save(<data/6bb4ff33a3>) returned error, retrying after 552.330144ms: client.Post: Post "http://myserver/mydir/data/6bb4ff33a3d2e0dc52bdd15a9ba93b82ce860704af220b73fb4b5a045b166343": readfrom tcp <IP_ADDRESS>:49770-><IP_ADDRESS>:8085: write tcp <IP_ADDRESS>:49770-><IP_ADDRESS>:8085: wsasend: An existing connection was forcibly closed by the remote host.
Save(<data/9262ee30b2>) returned error, retrying after 720.254544ms: client.Post: Post "http://myserver/mydir/data/9262ee30b23c07f47a1b17207358f8e9e651200f1ea4839181ca335927eab2ed": readfrom tcp <IP_ADDRESS>:49780-><IP_ADDRESS>:8085: write tcp <IP_ADDRESS>:49780-><IP_ADDRESS>:8085: wsasend: An existing connection was forcibly closed by the remote host.
Save(<data/043d291a55>) returned error, retrying after 582.280027ms: client.Post: Post "http://myserver/mydir/data/043d291a55603293b45f65dd0337d69f776c7ea7ac9cb293fdb4e792dbff6edf": readfrom tcp <IP_ADDRESS>:49778-><IP_ADDRESS>:8085: write tcp <IP_ADDRESS>:49778-><IP_ADDRESS>:8085: wsasend: An existing connection was forcibly closed by the remote host.
Save(<data/603b768ef8>) returned error, retrying after 468.857094ms: client.Post: Post "http://myserver/mydir/data/603b768ef8c27b5c2eb5e2406dfecb962d022e3e4dbd18b1f6aa49285056bd7b": readfrom tcp <IP_ADDRESS>:49777-><IP_ADDRESS>:8085: write tcp <IP_ADDRESS>:49777-><IP_ADDRESS>:8085: wsasend: An existing connection was forcibly closed by the remote host.
Save(<data/7e4ff8b892>) returned error, retrying after 593.411537ms: client.Post: Post "http://myserver/mydir/data/7e4ff8b892cfe063499587ff6de15875aaa20e3c4cbc49c976df231b9f11a622": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/ac4d5a928e>) returned error, retrying after 462.318748ms: client.Post: Post "http://myserver/mydir/data/ac4d5a928e92eec71d080188bdf835ccfcd90a95a1077b230f4f9942bfa676d1": readfrom tcp <IP_ADDRESS>:49779-><IP_ADDRESS>:8085: write tcp <IP_ADDRESS>:49779-><IP_ADDRESS>:8085: wsasend: An existing connection was forcibly closed by the remote host.
Save(<data/9feab60157>) returned error, retrying after 282.818509ms: client.Post: Post "http://myserver/mydir/data/9feab60157653d57f02c2e70758b3d25ab2d3661c3a76404e6b897460965df35": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/69d6fcc3b2>) returned error, retrying after 328.259627ms: client.Post: Post "http://myserver/mydir/data/69d6fcc3b2c68481cd6ce7843e1cb1952c03c8aa95ca82e2fc04ae4252d8ba1a": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/b78bdcea69>) returned error, retrying after 298.484759ms: client.Post: Post "http://myserver/mydir/data/b78bdcea6999e8d5b9d78d6338cdd0ebbaa880f9c1c7894c8b3d2553fb982fe3": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/50560f7012>) returned error, retrying after 400.45593ms: client.Post: Post "http://myserver/mydir/data/50560f701296361644fdaa72e4e7a85b70b99d08f65d7fa0f7ef8bf9e538a8f0": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/7285831d5f>) returned error, retrying after 507.606314ms: client.Post: Post "http://myserver/mydir/data/7285831d5fec985d3c69074c728e3f6d308a0c157b3e44d9701e67f9bb0b39b2": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/1c73917b11>) returned error, retrying after 656.819981ms: client.Post: Post "http://myserver/mydir/data/1c73917b11ab076607b3121f7ee9329301ce550fb077a0675304afe8d3f916bd": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/6bb4ff33a3>) returned error, retrying after 535.697904ms: client.Post: Post "http://myserver/mydir/data/6bb4ff33a3d2e0dc52bdd15a9ba93b82ce860704af220b73fb4b5a045b166343": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/ac4d5a928e>) returned error, retrying after 660.492892ms: client.Post: Post "http://myserver/mydir/data/ac4d5a928e92eec71d080188bdf835ccfcd90a95a1077b230f4f9942bfa676d1": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/9feab60157>) returned error, retrying after 613.543631ms: client.Post: Post "http://myserver/mydir/data/9feab60157653d57f02c2e70758b3d25ab2d3661c3a76404e6b897460965df35": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/043d291a55>) returned error, retrying after 726.667384ms: client.Post: Post "http://myserver/mydir/data/043d291a55603293b45f65dd0337d69f776c7ea7ac9cb293fdb4e792dbff6edf": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/69d6fcc3b2>) returned error, retrying after 884.313507ms: client.Post: Post "http://myserver/mydir/data/69d6fcc3b2c68481cd6ce7843e1cb1952c03c8aa95ca82e2fc04ae4252d8ba1a": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/b78bdcea69>) returned error, retrying after 538.914789ms: client.Post: Post "http://myserver/mydir/data/b78bdcea6999e8d5b9d78d6338cdd0ebbaa880f9c1c7894c8b3d2553fb982fe3": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/9262ee30b2>) returned error, retrying after 587.275613ms: client.Post: Post "http://myserver/mydir/data/9262ee30b23c07f47a1b17207358f8e9e651200f1ea4839181ca335927eab2ed": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/7e4ff8b892>) returned error, retrying after 594.826393ms: client.Post: Post "http://myserver/mydir/data/7e4ff8b892cfe063499587ff6de15875aaa20e3c4cbc49c976df231b9f11a622": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/50560f7012>) returned error, retrying after 527.390157ms: client.Post: Post "http://myserver/mydir/data/50560f701296361644fdaa72e4e7a85b70b99d08f65d7fa0f7ef8bf9e538a8f0": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/1c73917b11>) returned error, retrying after 645.653563ms: client.Post: Post "http://myserver/mydir/data/1c73917b11ab076607b3121f7ee9329301ce550fb077a0675304afe8d3f916bd": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/603b768ef8>) returned error, retrying after 803.004957ms: client.Post: Post "http://myserver/mydir/data/603b768ef8c27b5c2eb5e2406dfecb962d022e3e4dbd18b1f6aa49285056bd7b": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/7285831d5f>) returned error, retrying after 1.021868578s: client.Post: Post "http://myserver/mydir/data/7285831d5fec985d3c69074c728e3f6d308a0c157b3e44d9701e67f9bb0b39b2": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/9feab60157>) returned error, retrying after 892.253525ms: client.Post: Post "http://myserver/mydir/data/9feab60157653d57f02c2e70758b3d25ab2d3661c3a76404e6b897460965df35": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/6bb4ff33a3>) returned error, retrying after 896.717884ms: client.Post: Post "http://myserver/mydir/data/6bb4ff33a3d2e0dc52bdd15a9ba93b82ce860704af220b73fb4b5a045b166343": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/50560f7012>) returned error, retrying after 1.409144665s: client.Post: Post "http://myserver/mydir/data/50560f701296361644fdaa72e4e7a85b70b99d08f65d7fa0f7ef8bf9e538a8f0": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/ac4d5a928e>) returned error, retrying after 794.905494ms: client.Post: Post "http://myserver/mydir/data/ac4d5a928e92eec71d080188bdf835ccfcd90a95a1077b230f4f9942bfa676d1": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/043d291a55>) returned error, retrying after 1.53600189s: client.Post: Post "http://myserver/mydir/data/043d291a55603293b45f65dd0337d69f776c7ea7ac9cb293fdb4e792dbff6edf": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/9262ee30b2>) returned error, retrying after 1.346309062s: client.Post: Post "http://myserver/mydir/data/9262ee30b23c07f47a1b17207358f8e9e651200f1ea4839181ca335927eab2ed": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/b78bdcea69>) returned error, retrying after 1.151797844s: client.Post: Post "http://myserver/mydir/data/b78bdcea6999e8d5b9d78d6338cdd0ebbaa880f9c1c7894c8b3d2553fb982fe3": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/043d291a55>) returned error, retrying after 891.511453ms: server response unexpected: 500 Internal Server Error (500)
Remove(<lock/4e2a391de5>) returned error, retrying after 329.164139ms: client.Do: Delete "http://myserver/mydir/locks/4e2a391de56d68cea3eb8f3043fa0a37f0296c2a3a4d241576d81f52d198b50f": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/35b8ba9f4a>) returned error, retrying after 553.62672ms: client.Post: Post "http://myserver/mydir/data/35b8ba9f4a54a5af4f72c4fa51245bac946bdffb7149109ebca30b535bed1be8": readfrom tcp <IP_ADDRESS>:49846-><IP_ADDRESS>:8085: write tcp <IP_ADDRESS>:49846-><IP_ADDRESS>:8085: wsasend: An existing connection was forcibly closed by the remote host.
Save(<data/8f5faa6b79>) returned error, retrying after 737.62081ms: client.Post: Post "http://myserver/mydir/data/8f5faa6b793dd5e5711b1b780421fd380158b00a547e394ff34193b167e10127": read tcp <IP_ADDRESS>:49841-><IP_ADDRESS>:8085: wsarecv: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/d86beddf8b>) returned error, retrying after 547.404299ms: client.Post: Post "http://myserver/mydir/data/d86beddf8b4ba50cd9ceafd5245cf9d340963c684b0344830d0a4bc03a5fb482": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/c5193a1fad>) returned error, retrying after 289.726811ms: client.Post: Post "http://myserver/mydir/data/c5193a1fadf7d2bb4241bf69f6ce6e7a17f2375937e5c27ecd9532c82cffa47c": readfrom tcp <IP_ADDRESS>:49834-><IP_ADDRESS>:8085: write tcp <IP_ADDRESS>:49834-><IP_ADDRESS>:8085: wsasend: An existing connection was forcibly closed by the remote host.
Save(<data/882cb6d811>) returned error, retrying after 596.012294ms: client.Post: Post "http://myserver/mydir/data/882cb6d811272bcc04903aeb95b95766b0f3c8935535cbcee3fe20d069ffe23d": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/260c4a6df0>) returned error, retrying after 400.76134ms: client.Post: Post "http://myserver/mydir/data/260c4a6df0468d67add8893d13181695c860470c9fb6ae73d58727b6a762e806": readfrom tcp <IP_ADDRESS>:49836-><IP_ADDRESS>:8085: write tcp <IP_ADDRESS>:49836-><IP_ADDRESS>:8085: wsasend: An existing connection was forcibly closed by the remote host.
Save(<data/16a5aec49b>) returned error, retrying after 279.560325ms: client.Post: Post "http://myserver/mydir/data/16a5aec49b180a6637a6e93c25b21a411999c45db0924b5a4581e81a8a900944": readfrom tcp <IP_ADDRESS>:49844-><IP_ADDRESS>:8085: write tcp <IP_ADDRESS>:49844-><IP_ADDRESS>:8085: wsasend: An existing connection was forcibly closed by the remote host.
Save(<data/8267a58d0e>) returned error, retrying after 520.549928ms: client.Post: Post "http://myserver/mydir/data/8267a58d0ed618b968f178e1de6a04c5712c74cee0fee91447b11e44d819eaef": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/352043466a>) returned error, retrying after 522.077787ms: client.Post: Post "http://myserver/mydir/data/352043466a9e4d1643ced8cbc74ea750e5b7b01e875cf13a80a07621d7adbdb4": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/ae95b7ad6b>) returned error, retrying after 389.253811ms: client.Post: Post "http://myserver/mydir/data/ae95b7ad6bd46f8c56d08981c7cfbaa43269bb0705b57e52f71e4fa811cc3eae": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/82fe514610>) returned error, retrying after 461.576101ms: client.Post: Post "http://myserver/mydir/data/82fe51461089ff2c2e1568b9d6a2501dfe5369dc346424846e18b5a2ab3bebf1": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Remove(<lock/4e2a391de5>) returned error, retrying after 504.949678ms: client.Do: Delete "http://myserver/mydir/locks/4e2a391de56d68cea3eb8f3043fa0a37f0296c2a3a4d241576d81f52d198b50f": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/a13bc49b8e>) returned error, retrying after 515.292858ms: client.Post: Post "http://myserver/mydir/data/a13bc49b8e74eac11ec0cc1d027ed46eda2fe466d47ebcdb425fedd32ca89a00": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/35b8ba9f4a>) returned error, retrying after 565.155375ms: client.Post: Post "http://myserver/mydir/data/35b8ba9f4a54a5af4f72c4fa51245bac946bdffb7149109ebca30b535bed1be8": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Remove(<lock/4e2a391de5>) returned error, retrying after 1.44968053s: client.Do: Delete "http://myserver/mydir/locks/4e2a391de56d68cea3eb8f3043fa0a37f0296c2a3a4d241576d81f52d198b50f": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/c5193a1fad>) returned error, retrying after 586.560746ms: client.Post: Post "http://myserver/mydir/data/c5193a1fadf7d2bb4241bf69f6ce6e7a17f2375937e5c27ecd9532c82cffa47c": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/8f5faa6b79>) returned error, retrying after 1.035407342s: client.Post: Post "http://myserver/mydir/data/8f5faa6b793dd5e5711b1b780421fd380158b00a547e394ff34193b167e10127": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/260c4a6df0>) returned error, retrying after 646.35411ms: client.Post: Post "http://myserver/mydir/data/260c4a6df0468d67add8893d13181695c860470c9fb6ae73d58727b6a762e806": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/882cb6d811>) returned error, retrying after 597.834195ms: client.Post: Post "http://myserver/mydir/data/882cb6d811272bcc04903aeb95b95766b0f3c8935535cbcee3fe20d069ffe23d": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/16a5aec49b>) returned error, retrying after 1.045771297s: client.Post: Post "http://myserver/mydir/data/16a5aec49b180a6637a6e93c25b21a411999c45db0924b5a4581e81a8a900944": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/8267a58d0e>) returned error, retrying after 448.090963ms: client.Post: Post "http://myserver/mydir/data/8267a58d0ed618b968f178e1de6a04c5712c74cee0fee91447b11e44d819eaef": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/352043466a>) returned error, retrying after 430.718249ms: client.Post: Post "http://myserver/mydir/data/352043466a9e4d1643ced8cbc74ea750e5b7b01e875cf13a80a07621d7adbdb4": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/ae95b7ad6b>) returned error, retrying after 1.107687652s: client.Post: Post "http://myserver/mydir/data/ae95b7ad6bd46f8c56d08981c7cfbaa43269bb0705b57e52f71e4fa811cc3eae": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/82fe514610>) returned error, retrying after 541.717062ms: client.Post: Post "http://myserver/mydir/data/82fe51461089ff2c2e1568b9d6a2501dfe5369dc346424846e18b5a2ab3bebf1": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/d86beddf8b>) returned error, retrying after 885.808734ms: client.Post: Post "http://myserver/mydir/data/d86beddf8b4ba50cd9ceafd5245cf9d340963c684b0344830d0a4bc03a5fb482": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Remove(<lock/4e2a391de5>) returned error, retrying after 1.251306712s: client.Do: Delete "http://myserver/mydir/locks/4e2a391de56d68cea3eb8f3043fa0a37f0296c2a3a4d241576d81f52d198b50f": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/a13bc49b8e>) returned error, retrying after 608.641833ms: client.Post: Post "http://myserver/mydir/data/a13bc49b8e74eac11ec0cc1d027ed46eda2fe466d47ebcdb425fedd32ca89a00": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/882cb6d811>) returned error, retrying after 1.611952233s: client.Post: Post "http://myserver/mydir/data/882cb6d811272bcc04903aeb95b95766b0f3c8935535cbcee3fe20d069ffe23d": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/c5193a1fad>) returned error, retrying after 1.39708008s: client.Post: Post "http://myserver/mydir/data/c5193a1fadf7d2bb4241bf69f6ce6e7a17f2375937e5c27ecd9532c82cffa47c": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/35b8ba9f4a>) returned error, retrying after 1.463686923s: client.Post: Post "http://myserver/mydir/data/35b8ba9f4a54a5af4f72c4fa51245bac946bdffb7149109ebca30b535bed1be8": dial tcp: lookup myserver: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
Save(<data/c5193a1fad>) returned error, retrying after 2.076015618s: server response unexpected: 500 Internal Server Error (500)
Save(<data/35b8ba9f4a>) returned error, retrying after 1.152435796s: server response unexpected: 500 Internal Server Error (500)

rclone log:
Jul 18 23:17:06 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/8e3630f07a668c5a91cf86fb6c53da2daf2df156d465bb05c578d5876eb0410f
Jul 18 23:17:06 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/47a478f9a657533af9aa2ce3df77b3ca42ea5d578c00e2f63259240d066a65d6
Jul 18 23:17:06 myserver rclone[490]: Local file system at /mymountpoint: DELETE /mydir/data/00b4bf78a6e098d50bd6d24d99a3c126cbaa42766679bd03daa057214e93fa64
Jul 18 23:17:06 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/f79a32edf3c1abe3538abe46124a375f2939d6c7e1ae2d4506ff749b7de80354
Jul 18 23:17:06 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/45cebc8f1fd59db0f2201b1581a7e2503a86cd8b75e66eedba0e7b69d4836f41
Jul 18 23:17:09 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/locks/1897e71612fa2615cf6243e2c743878e3c90daccf8bfcf9ad2f9a9736d2d0862
Jul 18 23:17:09 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/de60b0a4751fd597fcbb436ef70cc11a1592f7573093637277804b91d9768ddd
Jul 18 23:17:09 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/bfa6773a62d0c9eac5bcbc0fda7e87addb9eeb40b7b6cccf8d791eccad58aef8
Jul 18 23:17:13 myserver rclone[490]: Local file system at /mymountpoint: DELETE /mydir/data/e29bc6b42ccbbc9017953b3b712ed374fa456de1707011a73647ec58441b96c2
Jul 18 23:17:13 myserver rclone[490]: mydir/data/e2/e29bc6b42ccbbc9017953b3b712ed374fa456de1707011a73647ec58441b96c2: Delete request error: object not found
Jul 18 23:17:13 myserver rclone[490]: Local file system at /mymountpoint: DELETE /mydir/data/366e667bb22a3a2dfc807daf3e503a9e90f7c1039af6af363ce047c71166bc33
Jul 18 23:17:13 myserver rclone[490]: Local file system at /mymountpoint: DELETE /mydir/data/712aeadd39af26e28cef10f2890fad47698aefca700c2bbdaaa027d11336fed8
Jul 18 23:17:13 myserver rclone[490]: Local file system at /mymountpoint: DELETE /mydir/data/49f62efde4da12b614f0cdca23586721d4184089286210b041ce1e91e67d159e
Jul 18 23:17:13 myserver rclone[490]: mydir/data/49/49f62efde4da12b614f0cdca23586721d4184089286210b041ce1e91e67d159e: Delete request error: object not found
Jul 18 23:17:13 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/ad91c0622b310292cd3c2e82b7c63426ca8d418c8a8a04a16e6c6148cc579fe3
Jul 18 23:17:13 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/00b4bf78a6e098d50bd6d24d99a3c126cbaa42766679bd03daa057214e93fa64
Jul 18 23:17:13 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/7cb35080934ac059da6c432d0ec452702d8ee68537384ebb2168631e61f48955
Jul 18 23:17:15 myserver rclone[490]: Local file system at /mymountpoint: DELETE /mydir/locks/2609b79d941cc31e95a8a31dfe12e98f360345eff0f8ef2bc636964789b28b35
Jul 18 23:17:15 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/7f2dd6345f67304880310df098de66c3ef57c24d5fc5cc5b5388dfea7bf249a7
Jul 18 23:17:17 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/ddcaf10fe9d2d7c7b595418fa174ab9e7cdc07aac94f63f65ee2e9686b7be0db
Jul 18 23:17:19 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/5b14e80ba4d889746aa3ab45035c069a3a76dc611fca346de7240220c7afcb40
Jul 18 23:17:20 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/366e667bb22a3a2dfc807daf3e503a9e90f7c1039af6af363ce047c71166bc33
Jul 18 23:17:22 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/e29bc6b42ccbbc9017953b3b712ed374fa456de1707011a73647ec58441b96c2
Jul 18 23:17:23 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/49f62efde4da12b614f0cdca23586721d4184089286210b041ce1e91e67d159e
Jul 18 23:17:24 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/712aeadd39af26e28cef10f2890fad47698aefca700c2bbdaaa027d11336fed8
Jul 18 23:17:19 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/5b14e80ba4d889746aa3ab45035c069a3a76dc611fca346de7240220c7afcb40
Jul 18 23:17:20 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/366e667bb22a3a2dfc807daf3e503a9e90f7c1039af6af363ce047c71166bc33
Jul 18 23:17:22 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/e29bc6b42ccbbc9017953b3b712ed374fa456de1707011a73647ec58441b96c2
Jul 18 23:17:23 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/49f62efde4da12b614f0cdca23586721d4184089286210b041ce1e91e67d159e
Jul 18 23:17:24 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/712aeadd39af26e28cef10f2890fad47698aefca700c2bbdaaa027d11336fed8
Jul 18 23:17:25 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/10054764b6ee4edf1abf475451222970ce51f06a09b91299174ae3c0a356fc9f
Jul 18 23:17:28 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/4bc41c7d258c3fdfbc3073a915c1e663535813592ac6460c9a6ef2cb64392d23
Jul 18 23:17:28 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/f2f81a95e64d51e264efbb63aec3ee8d3ff25749bf23bf4758478082b5ce5bb1
Jul 18 23:17:32 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/8686b3a0705c825458132db58c0ff9d77caee3a582762a4655a7855d9e633a77
Jul 18 23:17:32 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/cd9353fc881e139d44f81a2fd295bb19dcf41e21b7b899356a0387ad06e36303
Jul 18 23:17:32 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/3d45690839a80927d5a4206b078cd00c9db4a7a4589749657ddb735b284889e9
Jul 18 23:17:33 myserver rclone[490]: mydir/data/36/366e667bb22a3a2dfc807daf3e503a9e90f7c1039af6af363ce047c71166bc33: Removing partially written file on error: read tcp <IP_ADDRESS>:8085-><IP_ADDRESS>:49920: read: connection timed out
Jul 18 23:17:33 myserver rclone[490]: mydir/data/71/712aeadd39af26e28cef10f2890fad47698aefca700c2bbdaaa027d11336fed8: Removing partially written file on error: read tcp <IP_ADDRESS>:8085-><IP_ADDRESS>:49918: read: connection timed out
Jul 18 23:17:33 myserver rclone[490]: mydir/data/36/366e667bb22a3a2dfc807daf3e503a9e90f7c1039af6af363ce047c71166bc33: Post request put error: read tcp <IP_ADDRESS>:8085-><IP_ADDRESS>:49920: read: connection timed out
Jul 18 23:17:33 myserver rclone[490]: mydir/data/71/712aeadd39af26e28cef10f2890fad47698aefca700c2bbdaaa027d11336fed8: Post request put error: read tcp <IP_ADDRESS>:8085-><IP_ADDRESS>:49918: read: connection timed out
Jul 18 23:17:33 myserver rclone[490]: mydir/data/71/712aeadd39af26e28cef10f2890fad47698aefca700c2bbdaaa027d11336fed8: Post request rcat error: read tcp <IP_ADDRESS>:8085-><IP_ADDRESS>:49918: read: connection timed out
Jul 18 23:17:33 myserver rclone[490]: mydir/data/36/366e667bb22a3a2dfc807daf3e503a9e90f7c1039af6af363ce047c71166bc33: Post request rcat error: read tcp <IP_ADDRESS>:8085-><IP_ADDRESS>:49920: read: connection timed out
Jul 18 23:17:34 myserver rclone[490]: mydir/data/bf/bfa6773a62d0c9eac5bcbc0fda7e87addb9eeb40b7b6cccf8d791eccad58aef8: Removing partially written file on error: read tcp <IP_ADDRESS>:8085-><IP_ADDRESS>:49919: read: connection timed out
Jul 18 23:17:34 myserver rclone[490]: mydir/data/47/47a478f9a657533af9aa2ce3df77b3ca42ea5d578c00e2f63259240d066a65d6: Removing partially written file on error: read tcp <IP_ADDRESS>:8085-><IP_ADDRESS>:49916: read: connection timed out
Jul 18 23:17:34 myserver rclone[490]: mydir/data/bf/bfa6773a62d0c9eac5bcbc0fda7e87addb9eeb40b7b6cccf8d791eccad58aef8: Post request put error: read tcp <IP_ADDRESS>:8085-><IP_ADDRESS>:49919: read: connection timed out
Jul 18 23:17:34 myserver rclone[490]: mydir/data/bf/bfa6773a62d0c9eac5bcbc0fda7e87addb9eeb40b7b6cccf8d791eccad58aef8: Post request rcat error: read tcp <IP_ADDRESS>:8085-><IP_ADDRESS>:49919: read: connection timed out
Jul 18 23:17:34 myserver rclone[490]: mydir/data/47/47a478f9a657533af9aa2ce3df77b3ca42ea5d578c00e2f63259240d066a65d6: Post request put error: read tcp <IP_ADDRESS>:8085-><IP_ADDRESS>:49916: read: connection timed out
Jul 18 23:17:34 myserver rclone[490]: mydir/data/47/47a478f9a657533af9aa2ce3df77b3ca42ea5d578c00e2f63259240d066a65d6: Post request rcat error: read tcp <IP_ADDRESS>:8085-><IP_ADDRESS>:49916: read: connection timed out
Jul 18 23:17:34 myserver rclone[490]: mydir/data/00/00b4bf78a6e098d50bd6d24d99a3c126cbaa42766679bd03daa057214e93fa64: Removing partially written file on error: read tcp <IP_ADDRESS>:8085-><IP_ADDRESS>:49917: read: connection timed out
Jul 18 23:17:34 myserver rclone[490]: mydir/data/00/00b4bf78a6e098d50bd6d24d99a3c126cbaa42766679bd03daa057214e93fa64: Post request put error: read tcp <IP_ADDRESS>:8085-><IP_ADDRESS>:49917: read: connection timed out
Jul 18 23:17:34 myserver rclone[490]: mydir/data/00/00b4bf78a6e098d50bd6d24d99a3c126cbaa42766679bd03daa057214e93fa64: Post request rcat error: read tcp <IP_ADDRESS>:8085-><IP_ADDRESS>:49917: read: connection timed out
Jul 18 23:17:35 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/59b9529d55eca0c9c2636ec0736dde96241b955167e665cd84c424af532ebbd5
Jul 18 23:17:38 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/25cdcb1b6e862bf30403b50603f0861deb75ab90c6fdb216c28d0816acf6e396
Jul 18 23:17:40 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/20259a9357170d5415bddaf3fece85b42593ac3343d33e873cc840c87a8873d5
Jul 18 23:17:41 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/796cc6d269ea161c73e63a117a6aec3d567eae1d9827f041bb175f58b804c72f
Jul 18 23:17:42 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/87f940d2919de148857549a99b4f2fd3a38a122a5cd64ae7e8378a66fa509d69
Jul 18 23:17:42 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/76cffe59208c64c565dca5375da640740236c06ac175a8969fa8d7b97359b442
Jul 18 23:17:45 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/946be8b9d09af69e851e8326110d266416be5fe8dca4858553b7a6d08ef984d0
Jul 18 23:17:47 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/1c650f11eaa2c7beef4eeb767ffd138e881c80f37cd886254115a555e41560b3
Jul 18 23:17:49 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/f0ae56d9ec70aeda14070ed5aab3c9d8a85322abde8ed440c4b98b88b05452e5
Jul 18 23:17:50 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/61fe1867cf5e8272b941e480cea2ed0ff21dc38d2dd930d8c9c1a61227f810ef
Jul 18 23:17:52 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/2374e85628dd8f075f62971389802f318b4581157da4b6b3a0f6c6ec3d9214ca
Jul 18 23:17:53 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/6e6a99ec5e9d419cc5cd83e15c094121600a22edcf573dbc726d0efab5ff01ba
Jul 18 23:18:00 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/ce6f4bd2aae2f0e440103d35c62ebd2efd7ea32c140835ca569ff002bbd700d1

[SNIP]

Jul 18 22:29:40 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/6bb4ff33a3d2e0dc52bdd15a9ba93b82ce860704af220b73fb4b5a045b166343
Jul 18 22:29:41 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/9262ee30b23c07f47a1b17207358f8e9e651200f1ea4839181ca335927eab2ed
Jul 18 22:29:42 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/603b768ef8c27b5c2eb5e2406dfecb962d022e3e4dbd18b1f6aa49285056bd7b
Jul 18 22:31:43 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/69d6fcc3b2c68481cd6ce7843e1cb1952c03c8aa95ca82e2fc04ae4252d8ba1a
Jul 18 22:31:46 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/7e4ff8b892cfe063499587ff6de15875aaa20e3c4cbc49c976df231b9f11a622
Jul 18 22:31:46 myserver rclone[490]: Local file system at /mymountpoint: DELETE /mydir/data/6bb4ff33a3d2e0dc52bdd15a9ba93b82ce860704af220b73fb4b5a045b166343
Jul 18 22:31:46 myserver rclone[490]: Local file system at /mymountpoint: DELETE /mydir/data/9feab60157653d57f02c2e70758b3d25ab2d3661c3a76404e6b897460965df35
Jul 18 22:31:46 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/1c73917b11ab076607b3121f7ee9329301ce550fb077a0675304afe8d3f916bd
Jul 18 22:31:46 myserver rclone[490]: mydir/data/9f/9feab60157653d57f02c2e70758b3d25ab2d3661c3a76404e6b897460965df35: Delete request error: object not found
Jul 18 22:31:47 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/603b768ef8c27b5c2eb5e2406dfecb962d022e3e4dbd18b1f6aa49285056bd7b
Jul 18 22:31:47 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/7285831d5fec985d3c69074c728e3f6d308a0c157b3e44d9701e67f9bb0b39b2
Jul 18 22:31:51 myserver rclone[490]: Local file system at /mymountpoint: DELETE /mydir/data/50560f701296361644fdaa72e4e7a85b70b99d08f65d7fa0f7ef8bf9e538a8f0
Jul 18 22:31:51 myserver rclone[490]: mydir/data/50/50560f701296361644fdaa72e4e7a85b70b99d08f65d7fa0f7ef8bf9e538a8f0: Delete request error: object not found
Jul 18 22:31:51 myserver rclone[490]: Local file system at /mymountpoint: DELETE /mydir/data/ac4d5a928e92eec71d080188bdf835ccfcd90a95a1077b230f4f9942bfa676d1
Jul 18 22:31:51 myserver rclone[490]: Local file system at /mymountpoint: DELETE /mydir/data/043d291a55603293b45f65dd0337d69f776c7ea7ac9cb293fdb4e792dbff6edf
Jul 18 22:31:51 myserver rclone[490]: Local file system at /mymountpoint: DELETE /mydir/data/9262ee30b23c07f47a1b17207358f8e9e651200f1ea4839181ca335927eab2ed
Jul 18 22:31:51 myserver rclone[490]: Local file system at /mymountpoint: DELETE /mydir/data/b78bdcea6999e8d5b9d78d6338cdd0ebbaa880f9c1c7894c8b3d2553fb982fe3
Jul 18 22:31:51 myserver rclone[490]: mydir/data/b7/b78bdcea6999e8d5b9d78d6338cdd0ebbaa880f9c1c7894c8b3d2553fb982fe3: Delete request error: object not found
Jul 18 22:31:51 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/9feab60157653d57f02c2e70758b3d25ab2d3661c3a76404e6b897460965df35
Jul 18 22:31:52 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/6bb4ff33a3d2e0dc52bdd15a9ba93b82ce860704af220b73fb4b5a045b166343
Jul 18 22:31:53 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/8c00b7c606842248a1e63ae67aa2c4f2ab8c3df7283329f53412216cd7f2c998
Jul 18 22:31:56 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/ac4d5a928e92eec71d080188bdf835ccfcd90a95a1077b230f4f9942bfa676d1
Jul 18 22:31:56 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/b78bdcea6999e8d5b9d78d6338cdd0ebbaa880f9c1c7894c8b3d2553fb982fe3
Jul 18 22:32:01 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/58cd75dc47f1bcc6ed225d80b0d71781b00ee3ac43e4e457a31ea071b4911df2
Jul 18 22:32:01 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/50560f701296361644fdaa72e4e7a85b70b99d08f65d7fa0f7ef8bf9e538a8f0
Jul 18 22:32:02 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/9262ee30b23c07f47a1b17207358f8e9e651200f1ea4839181ca335927eab2ed
Jul 18 22:32:09 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/bc781f28f17a00a860479cb6c66bb6a1f635835f84d4ee7f93e9b0b18f6bd011
Jul 18 22:32:09 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/043d291a55603293b45f65dd0337d69f776c7ea7ac9cb293fdb4e792dbff6edf
Jul 18 22:32:12 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/688c47d2197ad00000cd040a38c7179de01f028bb5d67f712a3572b4917793ee
Jul 18 22:32:15 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/7a4fb8d982fe12d4c8bb1cba53cdc8499b09d1608a0cf490065f268dca1a7e90
Jul 18 22:32:17 myserver rclone[490]: mydir/data/92/9262ee30b23c07f47a1b17207358f8e9e651200f1ea4839181ca335927eab2ed: Removing partially written file on error: read tcp <IP_ADDRESS>:8085-><IP_ADDRESS>:49780: read: connection timed out
Jul 18 22:32:17 myserver rclone[490]: mydir/data/60/603b768ef8c27b5c2eb5e2406dfecb962d022e3e4dbd18b1f6aa49285056bd7b: Removing partially written file on error: read tcp <IP_ADDRESS>:8085-><IP_ADDRESS>:49777: read: connection timed out
Jul 18 22:32:17 myserver rclone[490]: mydir/data/04/043d291a55603293b45f65dd0337d69f776c7ea7ac9cb293fdb4e792dbff6edf: Removing partially written file on error: read tcp <IP_ADDRESS>:8085-><IP_ADDRESS>:49778: read: connection timed out
Jul 18 22:32:17 myserver rclone[490]: mydir/data/6b/6bb4ff33a3d2e0dc52bdd15a9ba93b82ce860704af220b73fb4b5a045b166343: Removing partially written file on error: read tcp <IP_ADDRESS>:8085-><IP_ADDRESS>:49770: read: connection timed out
Jul 18 22:32:17 myserver rclone[490]: mydir/data/60/603b768ef8c27b5c2eb5e2406dfecb962d022e3e4dbd18b1f6aa49285056bd7b: Post request put error: read tcp <IP_ADDRESS>:8085-><IP_ADDRESS>:49777: read: connection timed out
Jul 18 22:32:17 myserver rclone[490]: mydir/data/ac/ac4d5a928e92eec71d080188bdf835ccfcd90a95a1077b230f4f9942bfa676d1: Removing partially written file on error: read tcp <IP_ADDRESS>:8085-><IP_ADDRESS>:49779: read: connection timed out
Jul 18 22:32:17 myserver rclone[490]: mydir/data/04/043d291a55603293b45f65dd0337d69f776c7ea7ac9cb293fdb4e792dbff6edf: Post request put error: read tcp <IP_ADDRESS>:8085-><IP_ADDRESS>:49778: read: connection timed out
Jul 18 22:32:17 myserver rclone[490]: mydir/data/92/9262ee30b23c07f47a1b17207358f8e9e651200f1ea4839181ca335927eab2ed: Post request put error: read tcp <IP_ADDRESS>:8085-><IP_ADDRESS>:49780: read: connection timed out
Jul 18 22:32:17 myserver rclone[490]: mydir/data/6b/6bb4ff33a3d2e0dc52bdd15a9ba93b82ce860704af220b73fb4b5a045b166343: Post request put error: read tcp <IP_ADDRESS>:8085-><IP_ADDRESS>:49770: read: connection timed out
Jul 18 22:32:17 myserver rclone[490]: mydir/data/ac/ac4d5a928e92eec71d080188bdf835ccfcd90a95a1077b230f4f9942bfa676d1: Post request put error: read tcp <IP_ADDRESS>:8085-><IP_ADDRESS>:49779: read: connection timed out
Jul 18 22:32:17 myserver rclone[490]: mydir/data/04/043d291a55603293b45f65dd0337d69f776c7ea7ac9cb293fdb4e792dbff6edf: Post request rcat error: read tcp <IP_ADDRESS>:8085-><IP_ADDRESS>:49778: read: connection timed out
Jul 18 22:32:17 myserver rclone[490]: mydir/data/92/9262ee30b23c07f47a1b17207358f8e9e651200f1ea4839181ca335927eab2ed: Post request rcat error: read tcp <IP_ADDRESS>:8085-><IP_ADDRESS>:49780: read: connection timed out
Jul 18 22:32:17 myserver rclone[490]: mydir/data/6b/6bb4ff33a3d2e0dc52bdd15a9ba93b82ce860704af220b73fb4b5a045b166343: Post request rcat error: read tcp <IP_ADDRESS>:8085-><IP_ADDRESS>:49770: read: connection timed out
Jul 18 22:32:17 myserver rclone[490]: mydir/data/60/603b768ef8c27b5c2eb5e2406dfecb962d022e3e4dbd18b1f6aa49285056bd7b: Post request rcat error: read tcp <IP_ADDRESS>:8085-><IP_ADDRESS>:49777: read: connection timed out
Jul 18 22:32:17 myserver rclone[490]: mydir/data/ac/ac4d5a928e92eec71d080188bdf835ccfcd90a95a1077b230f4f9942bfa676d1: Post request rcat error: read tcp <IP_ADDRESS>:8085-><IP_ADDRESS>:49779: read: connection timed out
Jul 18 22:32:17 myserver rclone[490]: mydir/data/04/043d291a55603293b45f65dd0337d69f776c7ea7ac9cb293fdb4e792dbff6edf: Post request put error: chtimes /mymountpoint/mydir/data/04/043d291a55603293b45f65dd0337d69f776c7ea7ac9cb293fdb4e792dbff6edf: no such file or directory
Jul 18 22:32:17 myserver rclone[490]: mydir/data/04/043d291a55603293b45f65dd0337d69f776c7ea7ac9cb293fdb4e792dbff6edf: Post request rcat error: chtimes /mymountpoint/mydir/data/04/043d291a55603293b45f65dd0337d69f776c7ea7ac9cb293fdb4e792dbff6edf: no such file or directory
Jul 18 22:32:17 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/f166664e0737fb8c0d8c8017216bc4396115aaae16a8942db966ffc70873120b
Jul 18 22:32:18 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/a7e7b41c871ddc16696570f5f3985db8c96b85cb8ea0fc503c53766116684194
Jul 18 22:32:18 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/07b8efb3b44920e6c5c841de2342a485d17315d6857a8eba4cd0361c42c7e936
Jul 18 22:32:19 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/de28b2cad3876eee3f751b96dd489f67fa405193f6d2ea446bd7fed7b07d6c6c
Jul 18 22:32:22 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/85ee1977ba3990bbb43b744920019223b3c031a02c31a201e6734b3abe89df54
Jul 18 22:32:24 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/4d449d9e4e537c69f52239bbf383f7eb8e4769313f478ab512a936f8320321cd
Jul 18 22:32:25 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/cde63a1a9acb55abe8364c3ff5b5b7d28907fe89f7cd5178c3c1d43a7a3b5858
Jul 18 22:32:27 myserver rclone[490]: Local file system at /mymountpoint: DELETE /mydir/data/043d291a55603293b45f65dd0337d69f776c7ea7ac9cb293fdb4e792dbff6edf
Jul 18 22:32:27 myserver rclone[490]: mydir/data/04/043d291a55603293b45f65dd0337d69f776c7ea7ac9cb293fdb4e792dbff6edf: Delete request error: object not found
Jul 18 22:32:28 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/2491fe0d4894b03b9793128f62eb295b6b3ea03d116c871669ba2758f159a3b8

result:
load indexes
check all packs
pack 8f5faa6b: does not exist
pack 47a478f9: does not exist
pack 16a5aec4: does not exist
pack 00b4bf78: does not exist
pack ac4d5a92: does not exist
pack 712aeadd: does not exist
pack bfa6773a: does not exist
pack 260c4a6d: does not exist
pack 6bb4ff33: does not exist
pack 366e667b: does not exist
pack 9262ee30: does not exist
pack 603b768e: does not exist
check snapshots, trees and blobs
[4:42] 100.00%  365 / 365 snapshots...
Fatal: repository contains errors

reindex:
loading indexes...
getting pack files to read...
removing not found pack file 00b4bf78a6e098d50bd6d24d99a3c126cbaa42766679bd03daa057214e93fa64
removing not found pack file 9262ee30b23c07f47a1b17207358f8e9e651200f1ea4839181ca335927eab2ed
removing not found pack file 260c4a6df0468d67add8893d13181695c860470c9fb6ae73d58727b6a762e806
removing not found pack file 712aeadd39af26e28cef10f2890fad47698aefca700c2bbdaaa027d11336fed8
removing not found pack file 16a5aec49b180a6637a6e93c25b21a411999c45db0924b5a4581e81a8a900944
removing not found pack file 366e667bb22a3a2dfc807daf3e503a9e90f7c1039af6af363ce047c71166bc33
removing not found pack file 8f5faa6b793dd5e5711b1b780421fd380158b00a547e394ff34193b167e10127
removing not found pack file 6bb4ff33a3d2e0dc52bdd15a9ba93b82ce860704af220b73fb4b5a045b166343
removing not found pack file 603b768ef8c27b5c2eb5e2406dfecb962d022e3e4dbd18b1f6aa49285056bd7b
removing not found pack file bfa6773a62d0c9eac5bcbc0fda7e87addb9eeb40b7b6cccf8d791eccad58aef8
removing not found pack file 47a478f9a657533af9aa2ce3df77b3ca42ea5d578c00e2f63259240d066a65d6
removing not found pack file ac4d5a928e92eec71d080188bdf835ccfcd90a95a1077b230f4f9942bfa676d1
rebuilding index

Let me know if you need anything else. But that is just about all the info I have.

That looks very similar to a data loss issue we have recently fixed in rest-server restic/rest-server#142 (included in rest-server 0.11.0). As you're storing the repository locally, is there a particular reason to use rclone instead of rest-server? Could you give rest-server a try and test whether it fixes your data loss issue?
What appears to happen is the following: when an upload fails, e.g. due to an interrupted network connection, then restic retries the upload again up to 10 times. If all retries fail, then the backup will be canceled, which obviously hasn't happened here. So from restic's point of view the upload was successful in the end. For a retry restic will delete the upload first (not relevant here) and then uploads the file again.
What seems to be happening here is that the interrupted upload is noticed by rclone after the reupload was completed. rclone then cleans up the failed upload by deleting the file, which unfortunately was replaced by the correctly uploaded file in the meantime. This is for example visible in the following log snippet. The three error lines belong to the first (!) POST request.
Jul 18 22:29:40 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/6bb4ff33a3d2e0dc52bdd15a9ba93b82ce860704af220b73fb4b5a045b166343
Jul 18 22:31:46 myserver rclone[490]: Local file system at /mymountpoint: DELETE /mydir/data/6bb4ff33a3d2e0dc52bdd15a9ba93b82ce860704af220b73fb4b5a045b166343
Jul 18 22:31:52 myserver rclone[490]: Local file system at /mymountpoint: POST /mydir/data/6bb4ff33a3d2e0dc52bdd15a9ba93b82ce860704af220b73fb4b5a045b166343
Jul 18 22:32:17 myserver rclone[490]: mydir/data/6b/6bb4ff33a3d2e0dc52bdd15a9ba93b82ce860704af220b73fb4b5a045b166343: Removing partially written file on error: read tcp <IP_ADDRESS>:8085-><IP_ADDRESS>:49770: read: connection timed out
Jul 18 22:32:17 myserver rclone[490]: mydir/data/6b/6bb4ff33a3d2e0dc52bdd15a9ba93b82ce860704af220b73fb4b5a045b166343: Post request put error: read tcp <IP_ADDRESS>:8085-><IP_ADDRESS>:49770: read: connection timed out
Jul 18 22:32:17 myserver rclone[490]: mydir/data/6b/6bb4ff33a3d2e0dc52bdd15a9ba93b82ce860704af220b73fb4b5a045b166343: Post request rcat error: read tcp <IP_ADDRESS>:8085-><IP_ADDRESS>:49770: read: connection timed out

This has to be fixed on the rclone side, probably by ensuring that only one operation / upload happens at a time for each file.

The repository is off-site on an external drive connected to a Raspberry Pi 4 (myserver). From rclone's view that is local, I guess.
I thought rclone had the same features as rest-server and it was easy to set up and already available as an ARM binary so I just used that.
I will try with rest-server and report back after the next network failure.
Thanks for the quick reply!

Having this same issue. Errors like crazy trying to upload to a source thats usually fine. Then problems restoring the snapshot. It keeps saying Fatal...

Great news. This time the network outage was on the server side and the backup completed successfully anyways.
rest-server seems to work much better.
Logs:
Save(<data/5fee0bf383>) returned error, retrying after 552.330144ms: client.Post: Post "http://[server]/data/5fee0bf383f8e491f2152aef5417dc9f05696a581e1c72c39abe944677956d2b": readfrom tcp <IP_ADDRESS>:64870->[server]: write tcp <IP_ADDRESS>:64870->[server]: wsasend: An existing connection was forcibly closed by the remote host.
Save(<data/fe5b5da6ad>) returned error, retrying after 720.254544ms: client.Post: Post "http://[server]/data/fe5b5da6ad2d2bd30f70ae9c30bdcf535872ed7a828c446849d69f6ffb8add2a": readfrom tcp <IP_ADDRESS>:64863->[server]: write tcp <IP_ADDRESS>:64863->[server]: wsasend: An existing connection was forcibly closed by the remote host.
Save(<data/2c48217f3f>) returned error, retrying after 582.280027ms: client.Post: Post "http://[server]/data/2c48217f3f991e85d2709905c6de11a11085bbd484f26e79a214a4c9ec2a93b5": readfrom tcp <IP_ADDRESS>:64874->[server]: write tcp <IP_ADDRESS>:64874->[server]: wsasend: An existing connection was forcibly closed by the remote host.
Save(<data/47ecd05e28>) returned error, retrying after 468.857094ms: client.Post: Post "http://[server]/data/47ecd05e287e8537eccfa42bed3fa615cdee49bf2a5c26fda382709462567af1": readfrom tcp <IP_ADDRESS>:64873->[server]: write tcp <IP_ADDRESS>:64873->[server]: wsasend: An existing connection was forcibly closed by the remote host.
Save(<data/b4e004bb36>) returned error, retrying after 462.318748ms: client.Post: Post "http://[server]/data/b4e004bb36bdf320f8bed795b3e7311e3984668e37c1604e118d582b4e680f45": readfrom tcp <IP_ADDRESS>:64869->[server]: write tcp <IP_ADDRESS>:64869->[server]: wsasend: An existing connection was forcibly closed by the remote host.
Save(<data/3a792f4d28>) returned error, retrying after 593.411537ms: client.Post: Post "http://[server]/data/3a792f4d28f1be28af594f943af08683d37e4979ce4149c9835cfbeaf715f39c": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/8c504497d5>) returned error, retrying after 282.818509ms: client.Post: Post "http://[server]/data/8c504497d539079b8d0b0d337cd3999e5a8ce5f04c1cd1154da77893e990205a": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/5706094b9d>) returned error, retrying after 328.259627ms: client.Post: Post "http://[server]/data/5706094b9da4e0b0532fd09c7c02ea74e7490d8996e9976c51f7e3fdfed9496c": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/40f3bf0838>) returned error, retrying after 298.484759ms: client.Post: Post "http://[server]/data/40f3bf0838ffbc639848f67f558d74af4fbfb7ac2481aaffc4b6eb57f7420491": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/ba3ad68799>) returned error, retrying after 400.45593ms: client.Post: Post "http://[server]/data/ba3ad6879973eaeaf984d6e1d5a4da4e35535d6df1a3e2ddf339e63aa5bc14e6": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<index/fb75010116>) returned error, retrying after 507.606314ms: client.Post: Post "http://[server]/index/fb75010116fb0a6b738ae93f43460e193780016a33ad398a9b178a993f29a2cf": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/85c297d655>) returned error, retrying after 656.819981ms: client.Post: Post "http://[server]/data/85c297d655d81105410002d0bbe630622cf18d8579a2045001407096fbc4e338": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/5fee0bf383>) returned error, retrying after 535.697904ms: client.Post: Post "http://[server]/data/5fee0bf383f8e491f2152aef5417dc9f05696a581e1c72c39abe944677956d2b": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/fe5b5da6ad>) returned error, retrying after 613.543631ms: client.Post: Post "http://[server]/data/fe5b5da6ad2d2bd30f70ae9c30bdcf535872ed7a828c446849d69f6ffb8add2a": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/2c48217f3f>) returned error, retrying after 660.492892ms: client.Post: Post "http://[server]/data/2c48217f3f991e85d2709905c6de11a11085bbd484f26e79a214a4c9ec2a93b5": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/5706094b9d>) returned error, retrying after 726.667384ms: client.Post: Post "http://[server]/data/5706094b9da4e0b0532fd09c7c02ea74e7490d8996e9976c51f7e3fdfed9496c": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/3a792f4d28>) returned error, retrying after 594.826393ms: client.Post: Post "http://[server]/data/3a792f4d28f1be28af594f943af08683d37e4979ce4149c9835cfbeaf715f39c": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/8c504497d5>) returned error, retrying after 587.275613ms: client.Post: Post "http://[server]/data/8c504497d539079b8d0b0d337cd3999e5a8ce5f04c1cd1154da77893e990205a": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/47ecd05e28>) returned error, retrying after 884.313507ms: client.Post: Post "http://[server]/data/47ecd05e287e8537eccfa42bed3fa615cdee49bf2a5c26fda382709462567af1": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/b4e004bb36>) returned error, retrying after 538.914789ms: client.Post: Post "http://[server]/data/b4e004bb36bdf320f8bed795b3e7311e3984668e37c1604e118d582b4e680f45": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/ba3ad68799>) returned error, retrying after 527.390157ms: client.Post: Post "http://[server]/data/ba3ad6879973eaeaf984d6e1d5a4da4e35535d6df1a3e2ddf339e63aa5bc14e6": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<index/fb75010116>) returned error, retrying after 645.653563ms: client.Post: Post "http://[server]/index/fb75010116fb0a6b738ae93f43460e193780016a33ad398a9b178a993f29a2cf": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/40f3bf0838>) returned error, retrying after 803.004957ms: client.Post: Post "http://[server]/data/40f3bf0838ffbc639848f67f558d74af4fbfb7ac2481aaffc4b6eb57f7420491": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/85c297d655>) returned error, retrying after 1.021868578s: client.Post: Post "http://[server]/data/85c297d655d81105410002d0bbe630622cf18d8579a2045001407096fbc4e338": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/5fee0bf383>) returned error, retrying after 892.253525ms: client.Post: Post "http://[server]/data/5fee0bf383f8e491f2152aef5417dc9f05696a581e1c72c39abe944677956d2b": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/fe5b5da6ad>) returned error, retrying after 896.717884ms: client.Post: Post "http://[server]/data/fe5b5da6ad2d2bd30f70ae9c30bdcf535872ed7a828c446849d69f6ffb8add2a": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/b4e004bb36>) returned error, retrying after 1.409144665s: client.Post: Post "http://[server]/data/b4e004bb36bdf320f8bed795b3e7311e3984668e37c1604e118d582b4e680f45": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/2c48217f3f>) returned error, retrying after 794.905494ms: client.Post: Post "http://[server]/data/2c48217f3f991e85d2709905c6de11a11085bbd484f26e79a214a4c9ec2a93b5": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/5706094b9d>) returned error, retrying after 1.53600189s: client.Post: Post "http://[server]/data/5706094b9da4e0b0532fd09c7c02ea74e7490d8996e9976c51f7e3fdfed9496c": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/47ecd05e28>) returned error, retrying after 1.151797844s: client.Post: Post "http://[server]/data/47ecd05e287e8537eccfa42bed3fa615cdee49bf2a5c26fda382709462567af1": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/3a792f4d28>) returned error, retrying after 1.346309062s: client.Post: Post "http://[server]/data/3a792f4d28f1be28af594f943af08683d37e4979ce4149c9835cfbeaf715f39c": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/8c504497d5>) returned error, retrying after 594.340968ms: client.Post: Post "http://[server]/data/8c504497d539079b8d0b0d337cd3999e5a8ce5f04c1cd1154da77893e990205a": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/ba3ad68799>) returned error, retrying after 740.619312ms: client.Post: Post "http://[server]/data/ba3ad6879973eaeaf984d6e1d5a4da4e35535d6df1a3e2ddf339e63aa5bc14e6": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<index/fb75010116>) returned error, retrying after 1.24566012s: client.Post: Post "http://[server]/index/fb75010116fb0a6b738ae93f43460e193780016a33ad398a9b178a993f29a2cf": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/40f3bf0838>) returned error, retrying after 1.659646822s: client.Post: Post "http://[server]/data/40f3bf0838ffbc639848f67f558d74af4fbfb7ac2481aaffc4b6eb57f7420491": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/85c297d655>) returned error, retrying after 651.885326ms: client.Post: Post "http://[server]/data/85c297d655d81105410002d0bbe630622cf18d8579a2045001407096fbc4e338": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<lock/f9fb8dca8c>) returned error, retrying after 547.404299ms: client.Post: Post "http://[server]/locks/f9fb8dca8c4a928b5637918c33e4fa5d1e8d4fc0464605fb9ed91062fd435f67": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/fe5b5da6ad>) returned error, retrying after 943.516099ms: client.Post: Post "http://[server]/data/fe5b5da6ad2d2bd30f70ae9c30bdcf535872ed7a828c446849d69f6ffb8add2a": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/5fee0bf383>) returned error, retrying after 2.011541491s: client.Post: Post "http://[server]/data/5fee0bf383f8e491f2152aef5417dc9f05696a581e1c72c39abe944677956d2b": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/5706094b9d>) returned error, retrying after 1.352569524s: client.Post: Post "http://[server]/data/5706094b9da4e0b0532fd09c7c02ea74e7490d8996e9976c51f7e3fdfed9496c": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/2c48217f3f>) returned error, retrying after 1.136136777s: client.Post: Post "http://[server]/data/2c48217f3f991e85d2709905c6de11a11085bbd484f26e79a214a4c9ec2a93b5": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/8c504497d5>) returned error, retrying after 1.756856005s: client.Post: Post "http://[server]/data/8c504497d539079b8d0b0d337cd3999e5a8ce5f04c1cd1154da77893e990205a": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/b4e004bb36>) returned error, retrying after 1.762012529s: client.Post: Post "http://[server]/data/b4e004bb36bdf320f8bed795b3e7311e3984668e37c1604e118d582b4e680f45": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/47ecd05e28>) returned error, retrying after 1.313731612s: client.Post: Post "http://[server]/data/47ecd05e287e8537eccfa42bed3fa615cdee49bf2a5c26fda382709462567af1": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/ba3ad68799>) returned error, retrying after 1.55781934s: client.Post: Post "http://[server]/data/ba3ad6879973eaeaf984d6e1d5a4da4e35535d6df1a3e2ddf339e63aa5bc14e6": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/85c297d655>) returned error, retrying after 1.739113395s: client.Post: Post "http://[server]/data/85c297d655d81105410002d0bbe630622cf18d8579a2045001407096fbc4e338": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<index/fb75010116>) returned error, retrying after 1.271599594s: client.Post: Post "http://[server]/index/fb75010116fb0a6b738ae93f43460e193780016a33ad398a9b178a993f29a2cf": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/3a792f4d28>) returned error, retrying after 1.319761679s: client.Post: Post "http://[server]/data/3a792f4d28f1be28af594f943af08683d37e4979ce4149c9835cfbeaf715f39c": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<data/40f3bf0838>) returned error, retrying after 2.174520794s: client.Post: Post "http://[server]/data/40f3bf0838ffbc639848f67f558d74af4fbfb7ac2481aaffc4b6eb57f7420491": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Save(<lock/f9fb8dca8c>) returned error, retrying after 646.35411ms: client.Post: Post "http://[server]/locks/f9fb8dca8c4a928b5637918c33e4fa5d1e8d4fc0464605fb9ed91062fd435f67": dial tcp [serveripv6]: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

Jul 20 21:12:02 [server] rest-server[27884]: POST [backupdir]/data/0d7187af707da00f22fc00bbcd1ae6ab9430d89c73c7d7fac250b940f17ca53c
Jul 20 21:12:02 [server] rest-server[27884]: saveBlob()
Jul 20 21:12:04 [server] rest-server[27884]: POST [backupdir]/data/1c6a5a0b50db54caf1e7f0c25bb6e330eb03e02e600c8a18f96417c9d9a07b9a
Jul 20 21:12:04 [server] rest-server[27884]: saveBlob()
Jul 20 21:12:06 [server] rest-server[27884]: POST [backupdir]/data/5fee0bf383f8e491f2152aef5417dc9f05696a581e1c72c39abe944677956d2b
Jul 20 21:12:06 [server] rest-server[27884]: saveBlob()
Jul 20 21:12:09 [server] rest-server[27884]: POST [backupdir]/data/b4e004bb36bdf320f8bed795b3e7311e3984668e37c1604e118d582b4e680f45
Jul 20 21:12:09 [server] rest-server[27884]: saveBlob()
Jul 20 21:12:10 [server] rest-server[27884]: POST [backupdir]/data/47ecd05e287e8537eccfa42bed3fa615cdee49bf2a5c26fda382709462567af1
Jul 20 21:12:10 [server] rest-server[27884]: saveBlob()
Jul 20 21:12:10 [server] rest-server[27884]: POST [backupdir]/data/2c48217f3f991e85d2709905c6de11a11085bbd484f26e79a214a4c9ec2a93b5
Jul 20 21:12:10 [server] rest-server[27884]: saveBlob()
Jul 20 21:12:11 [server] rest-server[27884]: POST [backupdir]/data/fe5b5da6ad2d2bd30f70ae9c30bdcf535872ed7a828c446849d69f6ffb8add2a
Jul 20 21:12:11 [server] rest-server[27884]: saveBlob()
Jul 20 21:14:48 [server] rest-server[27884]: read tcp [server]->[client]:64869: read: connection timed out
Jul 20 21:14:48 [server] rest-server[27884]: ERROR: read tcp [server]->[client]:64869: read: connection timed out
Jul 20 21:14:48 [server] rest-server[27884]: read tcp [server]->[client]:64870: read: connection timed out
Jul 20 21:14:48 [server] rest-server[27884]: ERROR: read tcp [server]->[client]:64870: read: connection timed out
Jul 20 21:14:48 [server] rest-server[27884]: read tcp [server]->[client]:64873: read: connection timed out
Jul 20 21:14:48 [server] rest-server[27884]: ERROR: read tcp [server]->[client]:64873: read: connection timed out
Jul 20 21:14:48 [server] rest-server[27884]: read tcp [server]->[client]:64874: read: connection timed out
Jul 20 21:14:48 [server] rest-server[27884]: ERROR: read tcp [server]->[client]:64874: read: connection timed out
Jul 20 21:14:48 [server] rest-server[27884]: read tcp [server]->[client]:64863: read: connection timed out
Jul 20 21:14:48 [server] rest-server[27884]: ERROR: read tcp [server]->[client]:64863: read: connection timed out
Jul 20 21:19:02 [server] rest-server[27884]: DELETE [backupdir]/data/85c297d655d81105410002d0bbe630622cf18d8579a2045001407096fbc4e338
Jul 20 21:19:02 [server] rest-server[27884]: POST [backupdir]/data/fe5b5da6ad2d2bd30f70ae9c30bdcf535872ed7a828c446849d69f6ffb8add2a
Jul 20 21:19:02 [server] rest-server[27884]: POST [backupdir]/data/5fee0bf383f8e491f2152aef5417dc9f05696a581e1c72c39abe944677956d2b
Jul 20 21:19:02 [server] rest-server[27884]: DELETE [backupdir]/data/3a792f4d28f1be28af594f943af08683d37e4979ce4149c9835cfbeaf715f39c
Jul 20 21:19:02 [server] rest-server[27884]: deleteBlob()
Jul 20 21:19:02 [server] rest-server[27884]: saveBlob()
Jul 20 21:19:02 [server] rest-server[27884]: saveBlob()
Jul 20 21:19:02 [server] rest-server[27884]: DELETE [backupdir]/index/fb75010116fb0a6b738ae93f43460e193780016a33ad398a9b178a993f29a2cf
Jul 20 21:19:02 [server] rest-server[27884]: deleteBlob()
Jul 20 21:19:02 [server] rest-server[27884]: deleteBlob()
Jul 20 21:19:02 [server] rest-server[27884]: remove /[backupmount]/[backupdir]/data/85/85c297d655d81105410002d0bbe630622cf18d8579a2045001407096fbc4e338: no such file or directory
Jul 20 21:19:02 [server] rest-server[27884]: remove /[backupmount]/[backupdir]/index/fb75010116fb0a6b738ae93f43460e193780016a33ad398a9b178a993f29a2cf: no such file or directory
Jul 20 21:19:02 [server] rest-server[27884]: remove /[backupmount]/[backupdir]/data/3a/3a792f4d28f1be28af594f943af08683d37e4979ce4149c9835cfbeaf715f39c: no such file or directory
Jul 20 21:19:03 [server] rest-server[27884]: DELETE [backupdir]/data/40f3bf0838ffbc639848f67f558d74af4fbfb7ac2481aaffc4b6eb57f7420491
Jul 20 21:19:03 [server] rest-server[27884]: POST [backupdir]/data/2c48217f3f991e85d2709905c6de11a11085bbd484f26e79a214a4c9ec2a93b5
Jul 20 21:19:03 [server] rest-server[27884]: saveBlob()
Jul 20 21:19:03 [server] rest-server[27884]: deleteBlob()
Jul 20 21:19:03 [server] rest-server[27884]: POST [backupdir]/data/5706094b9da4e0b0532fd09c7c02ea74e7490d8996e9976c51f7e3fdfed9496c
Jul 20 21:19:03 [server] rest-server[27884]: saveBlob()
Jul 20 21:19:03 [server] rest-server[27884]: remove /[backupmount]/[backupdir]/data/40/40f3bf0838ffbc639848f67f558d74af4fbfb7ac2481aaffc4b6eb57f7420491: no such file or directory
Jul 20 21:19:03 [server] rest-server[27884]: DELETE [backupdir]/locks/f9fb8dca8c4a928b5637918c33e4fa5d1e8d4fc0464605fb9ed91062fd435f67
Jul 20 21:19:03 [server] rest-server[27884]: deleteBlob()
Jul 20 21:19:03 [server] rest-server[27884]: remove /[backupmount]/[backupdir]/locks/f9fb8dca8c4a928b5637918c33e4fa5d1e8d4fc0464605fb9ed91062fd435f67: no such file or directory
Jul 20 21:19:04 [server] rest-server[27884]: POST [backupdir]/data/47ecd05e287e8537eccfa42bed3fa615cdee49bf2a5c26fda382709462567af1
Jul 20 21:19:04 [server] rest-server[27884]: saveBlob()
Jul 20 21:19:09 [server] rest-server[27884]: POST [backupdir]/data/ba3ad6879973eaeaf984d6e1d5a4da4e35535d6df1a3e2ddf339e63aa5bc14e6
Jul 20 21:19:09 [server] rest-server[27884]: saveBlob()
Jul 20 21:19:11 [server] rest-server[27884]: POST [backupdir]/data/8c504497d539079b8d0b0d337cd3999e5a8ce5f04c1cd1154da77893e990205a
Jul 20 21:19:11 [server] rest-server[27884]: saveBlob()
Jul 20 21:19:13 [server] rest-server[27884]: POST [backupdir]/data/b4e004bb36bdf320f8bed795b3e7311e3984668e37c1604e118d582b4e680f45
Jul 20 21:19:13 [server] rest-server[27884]: saveBlob()

I will do a complete verification of all files next but it looks good now.

@MichaelEischer can we port our changes from rest-server to rclone? As far as I remember the code there is pretty similar. Ping @ncw

@fd0 in principle yes. However, judging from the discussion in https://github.com/rclone/rclone/issues/6329 that would require quite a bit of internal changes in rclone.


Error: seedMultibase required

Hi.
If I follow the instructions to run the tests, they fail with:
  eddsa-rdfc-2022 (create)
    ❌ "before all" hook in "eddsa-rdfc-2022 (create)"
    Error: seedMultibase required

This seems to be set by the environment variable KEY_SEED_DB. I have no idea what this could be.

KEY_SEED_DB is a base58 key seed used to sign the zcaps on our endpoint, my apologies about this we are looking into making the suites more resilient, unfortunately I don't think we can give you a KEY_SEED for the issuer and verifier endpoints, but we might be able to make the test ignore DB if there is no key seed set.

Thanks for the information. With the key seed, I can also run some 78% of tests successfully.
Unfortunately, I think I'm still missing something. I was hoping for a way to just execute local tests, see https://github.com/w3c/vc-test-suite-implementations#testing-locally
So something like create localImplementationsConfig.cjs and then only calls to localhost are done. Is a functionality like that planned?

@HelgeKrueger You should be able to run the tests only against local implementations. After adding the config file, you can update the tags in the test suite (https://github.com/w3c/vc-di-eddsa-test-suite/blob/main/tests/10-rdfc-create.js#L16, https://github.com/w3c/vc-di-eddsa-test-suite/blob/main/tests/20-rdfc-verify.js#L14 and https://github.com/w3c/vc-di-eddsa-test-suite/blob/main/tests/30-rdfc-interop.js#L10) that is used to filter implementations to use a specific tag that is in your config file. See - https://github.com/w3c/vc-test-suite-implementations/pull/10/files

Thanks! I got it working now.


📊 forests: primary forest share

@spoonerf
what's the status of this PR?
(no urgency, just doing some 🧹)


Update Step 1-03 exercise to match instructions

While working through exercise 1-03, I noticed that the updateRemaining() function was already implemented. This change makes the starter code consistent with the instructions so that students will write the function body as described.
One option I considered here was deleting the function entirely (including the declaration, instead of just the body). Students do have to write the entire function declaration for the addTodo() function in the next step though, and I figured easing them into writing full functions would build momentum. (I teach this stuff to high school students too, and that gradual buildup sometimes matters for novices.) Happy to change this if you all don't agree, though. 😄
Thanks for open-sourcing this!

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: ronaldsmartin sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Thanks. I noticed that too yesterday as we ran through it.


[FLINK-16490] Add a minimal Python SDK

Background
The JVM based stateful functions implementation, has a RequestReply extension (a protocol and an implementation) that allows calling into any HTTP endpoint that implements that protocol.
Although it is possible to implement this protocol independently, we should provide a minimal library for the Python programing language, that:

Allows users to define and declare their functions in a convenient way
Dispatch an invocation request sent from the JVM to the appropriate function previously declared

A mini tutorial
define and declare a function
from statefun import StatefulFunctions

functions = StatefulFunctions()

@functions.bind("demo/greeter")
def greet(context, message: LoginEvent):
    print("Hey " + message.user_name)

This code, declares a function with a FunctionType("demo", "greeter") and binds the greet Python instance to it.
Expose it with a request reply handler
from statefun import RequestReplyHandler

handler = RequestReplyHandler(functions)

Use the handler within your favorite HTTP serving framework
For example Flask
@app.route('/statefun', methods=['POST'])
def handle():
    response_data = handler(request.data)
    response = make_response(response_data)
    response.headers.set('Content-Type', 'application/octet-stream')
    return response

if __name__ == "__main__":
    app.run()

This creates an HTTP server that accepts requests from the Stateful Functions cluster and
dispatches it to the handler.
The reaming thing would be to declare this function type in a module.yaml
functions:
     function:
         meta:
            kind: http
            type: demo/greeter
         spec:
            endpoint: http://<end point url>/statefun
           states:
              - foo
              - bar
             -  baz

Currently supported features:
A Context classes has the following attributes/methods

Method
Description

send(self, typename: str, id: str, message: Any)
send a message to any function with the function type of the form <namespace>/<type> and the message is a google.protobuf.Any

pack_and_send(self, typename: str, id: str, message)
the same as above, but it would pack the protobuf message in an Any

reply(self, message: Any)
send a message to the invoking function

pack_and_reply(self, message)
the same as above, but would pack to an Any

send_after(self, delay: timedelta, typename: str, id: str, message: Any)
send a message after a delay

pack_and_send_after(self, delay: timedelta, typename: str, id: str, message)
the same as above, but would pack the message to an Any

send_egress(self, typename, message: Any)
emit a message to an egress with a typename of the form <namespace>/<name>

pack_and_send_egress(self, typename, message)
the same as above.

Eager state registration
The request reply protocol, requires that the state names would be registered at module.yaml
under the state: section (see the example above). The state values could be absent (None or a google.protobuf.Any and they can be generally obtained via the context parameter:
@functions.bind("demo/greeter")
def greet(context, message: LoginEvent):
    session = context['session']
    if not session:
       session = start_session(message)
       context['session'] = session
    ...

How to test

create the virtual environment

python3 -m venv venv
source venv/bin/activate

Run unit tests

python3 -m unittest tests

Create the distribution
With Docker
./build-distribution.sh
With venv
python3 -m pip install wheel
python3 setup.py sdist bdist_wheel

+1, LGTM. Thanks for addressing the comments @igalshilman.
I've tested this by:

Built the distribution and pip installed with the .whl locally.
Locally running the Python unit tests with the instructions mentioned in this PR
Used the Python SDK in realistic deployments using AWS Lambda + AWS ECS. Have an end to end deployment running, so in general I think functionality wise this is in good shape.

As discussed offline, I'll merge only the SDK for now, and leave the k8s example as a follow-up.


index.ts file not being created when a component is created

Please provide us with the following information:

OS?
Linux flow 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Versions.
$ ng --version
angular-cli: 1.0.0-beta.16
node: 6.6.0
os: linux x64
Repro steps.
ng g c TestComponent
Mention any other details that might be useful.
I no longer see index.ts file?

Thanks! We'll be in touch soon.

index.ts files are no longer generated since the move to NgModule. At the moment if you want to use barrels you have to manage them yourself.

Would be nice to have a switch :) for those who don't want to do it manually.

The CLI follows the style-guide, and the recommendation changed to not have index.ts files overall.
Reexporting is still useful, and we still generate ./src/index.ts and ./src/shared/index.ts on ng new, but we don't do that for other generators.

hi @filipesilva
Could you provide the source of where in the style-guide shows index.ts is recommended not to have? I'd like to know more detail about it. Thanks.

@speed-of-light it is not that the style guide recommends that one does not use index.ts files, but rather that it used to recommend you have it and now it doesn't.


the head of the cow is lower and looks so weird and unconfortable 😂

dude wtf XD please fix that weird bug i don't feel right looking ma cows like that XD
is funny tho

(the cows didn't look like this before installing the mod)

They shouldn't either with this mod installed, what version is this on? And what other mods do you have installed?

Since I can't reproduce this and there has been no further information this issue, I will close it for now. Feel free to re-open it once you're ready to provide more information. (:


Fixes #504 Validates the .workflow file

Added various validation rules to the normalize function in Workflow class to validate the .workflow file structure.

Hello @JayjeetAtGithub! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file cli/popper/gha.py:

Line 37:80: E501 line too long (86 > 79 characters)
Line 53:80: E501 line too long (99 > 79 characters)
Line 59:80: E501 line too long (85 > 79 characters)
Line 63:80: E501 line too long (86 > 79 characters)
Line 67:80: E501 line too long (86 > 79 characters)
Line 72:1: W293 blank line contains whitespace