Version 8.4.10 build fails with ``Websocket message rejected: Failed to parse time``

[user-1969]

For several months, my builds of fah-client-bastet version 8.4.10 don't work.
When I try to get a workunit, I get a continuous output of:

12:54:02:I2:OUT9:< HTTP/1.1 200 HTTP_OK
12:54:02:I2:REQ10:< GET /api/websocket HTTP/1.1
12:54:02:I2:OUT3:> GET /ws/client HTTP/1.1
12:54:03:I2:OUT3:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
12:54:03:I1:Logging into node account
12:54:03:I1:Account websocket closed: UNACCEPTABLE msg=Websocket message rejected: Failed to parse time '2025-07-14T12:54:01.461Z' with format '%Y-%m-%dT%H:%M:%SZ': Did not parse whole string
12:54:03:I2:OUT11:> GET /machine/AbaNVBG1-6xeVpuqoFQfsjd1Qm4JPnrSwoRMHlvEqww HTTP/1.1
12:54:05:I2:OUT11:< HTTP/1.1 200 HTTP_OK
12:54:05:I2:OUT3:> GET /ws/client HTTP/1.1
12:54:05:I2:OUT3:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
12:54:05:I1:Logging into node account
12:54:06:I1:Account websocket closed: UNACCEPTABLE msg=Websocket message rejected: Failed to parse time '2025-07-14T12:54:01.461Z' with format '%Y-%m-%dT%H:%M:%SZ': Did not parse whole string
12:54:06:I2:OUT12:> GET /machine/AbaNVBG1-6xeVpuqoFQfsjd1Qm4JPnrSwoRMHlvEqww HTTP/1.1
12:54:07:I2:OUT12:< HTTP/1.1 200 HTTP_OK
12:54:07:I2:OUT3:> GET /ws/client HTTP/1.1
12:54:07:I2:OUT3:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
12:54:07:I1:Logging into node account
12:54:08:I1:Account websocket closed: UNACCEPTABLE msg=Websocket message rejected: Failed to parse time '2025-07-14T12:54:01.461Z' with format '%Y-%m-%dT%H:%M:%SZ': Did not parse whole string
12:54:08:I2:OUT13:> GET /machine/AbaNVBG1-6xeVpuqoFQfsjd1Qm4JPnrSwoRMHlvEqww HTTP/1.1

for

[jcoffland]

For some reason your build is adding milliseconds to the time format. I.e. 2025-07-14T12:54:01.461Z. It should be sending 2025-07-14T12:54:01Z. Are you building with the latest cbang?

[user-1969]

CBang is fully updated, and I have just pulled the latest fah-client bastet source code.
I built it, but it still outputs the same message, and doesn't get any work.
I am using Arch Linux on two machines, and Ubuntu 24.04 LTS on another, and they all error like this.
Version 8.4.9 from the webpage works fine, but my builds of 8.4.10 all fail to work.
How can the source code be altered to make it work?

[kbernhagen]

I just built and see that error when I try to config cpus 0 via web control.
The exception maybe also breaks the account connection.

21:07:05:D3:Remote:msg: {
21:07:05:D3:Remote:  "config": {
21:07:05:D3:Remote:    "groups": {
21:07:05:D3:Remote:      "": {
21:07:05:D3:Remote:        "on_idle": false,
21:07:05:D3:Remote:        "cpus": 0,
21:07:05:D3:Remote:        "gpus": {
21:07:05:D3:Remote:          "gpu:09:00:00": {"enabled": false}
21:07:05:D3:Remote:        },
21:07:05:D3:Remote:        "beta": false,
21:07:05:D3:Remote:        "key": 0,
21:07:05:D3:Remote:        "cuda": true,
21:07:05:D3:Remote:        "hip": true,
21:07:05:D3:Remote:        "on_battery": false,
21:07:05:D3:Remote:        "keep_awake": true
21:07:05:D3:Remote:      }
21:07:05:D3:Remote:    }
21:07:05:D3:Remote:  },
21:07:05:D3:Remote:  "cmd": "config",
21:07:05:D3:Remote:  "time": "2025-07-27T21:07:05.327Z"
21:07:05:D3:Remote:}
21:07:05:D3:Websocket:WS6:Websocket message rejected: Failed to parse time '2025-07-27T21:07:05.327Z' with format '%Y-%m-%dT%H:%M:%SZ': Did not parse whole string
21:07:05:I1:Account:Account websocket closed: UNACCEPTABLE msg=Websocket message rejected: Failed to parse time '2025-07-27T21:07:05.327Z' with format '%Y-%m-%dT%H:%M:%SZ': Did not parse whole string
21:07:05:D3:Remote:Closing client 1VWHgg-BctZZ4CRW
21:07:05:D3:App:Removing remote 1VWHgg-BctZZ4CRW
21:07:05:I2:Request:OUT9:> GET /machine/UDO4NT2uhFmrolRJDcflnslFWkD79EYfsLzxF_Bbb4Q HTTP/1.1
21:07:05:I2:Request:OUT9:< HTTP/1.1 200 HTTP_OK
21:07:05:D3:Account:account = {"pubkey": "*redacted*", "user": "calxalot", "team": 1971, "passkey": "*redacted*", "cause": "alzheimers", "node": "node1.foldingathome.org", "mach_name": "Sanctuary"}
21:07:06:I2:Request:OUT6:> GET /ws/client HTTP/1.1
21:07:06:I2:Request:OUT6:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
21:07:06:I1:Account:Logging into node account
21:07:06:D3:Account:received = {"type": "message", "id": "*redacted*", "iv": "*redacted*", "payload": "*redacted*"}

[kbernhagen]

Error also happens when I use lufah.
I can truncate milliseconds from lufah outgoing commands.
This wasn't a problem before.

21:13:38:D3:Remote:msg: {
21:13:38:D3:Remote:  "cmd": "config",
21:13:38:D3:Remote:  "config": {
21:13:38:D3:Remote:    "groups": {
21:13:38:D3:Remote:      "": {"cpus": 0}
21:13:38:D3:Remote:    }
21:13:38:D3:Remote:  },
21:13:38:D3:Remote:  "time": "2025-07-27T21:13:38Z"
21:13:38:D3:Remote:}
21:13:38:D3:Websocket:WS11:Websocket message rejected: Failed to parse time '2024-05-11T08:32:54.712671Z' with format '%Y-%m-%dT%H:%M:%SZ': Did not parse whole string

[kbernhagen]

Ah. Lufah did not send milliseconds there!
Something else is generating that (very old) timestamp.

[kbernhagen]

Weird.
Commands log, restart(account) have no problem.
Commands config, pause, finish all cause the same bogus timestamp error.
Did not test fold.

00:27:39:I2:Request:REQ15:< GET /api/websocket HTTP/1.1
00:27:39:D3:Remote:New client 127.0.0.1
00:27:39:D3:App:Adding remote 127.0.0.1
00:27:39:D3:Remote:msg: {"cmd": "log", "enable": true, "time": "2025-07-28T00:27:39Z"}
00:27:41:D3:Remote:Closing client 127.0.0.1
00:27:41:D3:App:Removing remote 127.0.0.1
00:27:49:I2:Request:REQ16:< GET /api/websocket HTTP/1.1
00:27:49:D3:Remote:New client 127.0.0.1
00:27:49:D3:App:Adding remote 127.0.0.1
00:27:49:D3:Remote:msg: {"state": "pause", "cmd": "state", "time": "2025-07-28T00:27:49Z"}
00:27:49:D3:Websocket:WS16:Websocket message rejected: Failed to parse time '2024-05-11T08:35:01.726641Z' with format '%Y-%m-%dT%H:%M:%SZ': Did not parse whole string
00:27:49:D3:Remote:Closing client 127.0.0.1
00:27:49:D3:App:Removing remote 127.0.0.1
00:27:57:I2:Request:REQ17:< GET /api/websocket HTTP/1.1
00:27:57:D3:Remote:New client 127.0.0.1
00:27:57:D3:App:Adding remote 127.0.0.1
00:27:57:D3:Remote:msg: {"state": "finish", "cmd": "state", "time": "2025-07-28T00:27:57Z"}
00:27:57:D3:Websocket:WS17:Websocket message rejected: Failed to parse time '2024-05-11T08:35:01.726641Z' with format '%Y-%m-%dT%H:%M:%SZ': Did not parse whole string
00:27:57:D3:Remote:Closing client 127.0.0.1
00:27:57:D3:App:Removing remote 127.0.0.1

00:29:45:I2:Request:REQ18:< GET /api/websocket HTTP/1.1
00:29:45:D3:Remote:New client 127.0.0.1
00:29:45:D3:App:Adding remote 127.0.0.1
00:29:45:D3:Remote:msg: {"cmd": "restart", "time": "2025-07-28T00:29:45Z"}
00:29:45:I1:Account:Account websocket closed: NORMAL msg=Account restart
00:29:45:D3:Remote:Closing client pNZS5LKv5Ep1Nryd
00:29:45:D3:App:Removing remote pNZS5LKv5Ep1Nryd
00:29:45:D3:Remote:Closing client 127.0.0.1
00:29:45:D3:App:Removing remote 127.0.0.1
00:29:45:I2:Request:OUT19:> GET /machine/UDO4NT2uhFmrolRJDcflnslFWkD79EYfsLzxF_Bbb4Q HTTP/1.1
00:29:45:I2:Request:OUT19:< HTTP/1.1 200 HTTP_OK
00:29:45:D3:Account:account = {"pubkey": "***", "user": "calxalot", "team": 1971, "passkey": "***", "cause": "alzheimers", "node": "node1.foldingathome.org", "mach_name": "Sanctuary"}
00:29:45:I2:Request:OUT2:> GET /ws/client HTTP/1.1
00:29:46:I2:Request:OUT2:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
00:29:46:I1:Account:Logging into node account
00:29:46:D3:Account:received = {"type": "message", "id": "***", "iv": "***", "payload": "***"}
00:29:46:D3:App:Adding remote pNZS5LKv5Ep1Nryd
00:29:46:D3:Remote:New client pNZS5LKv5Ep1Nryd

00:31:05:I2:Request:REQ20:< GET /api/websocket HTTP/1.1
00:31:05:D3:Remote:New client 127.0.0.1
00:31:05:D3:App:Adding remote 127.0.0.1
00:31:05:D3:Remote:msg: {"state": "finish", "cmd": "state", "time": "2025-07-28T00:31:05Z"}
00:31:05:D3:Websocket:WS20:Websocket message rejected: Failed to parse time '2024-05-11T08:35:01.726641Z' with format '%Y-%m-%dT%H:%M:%SZ': Did not parse whole string
00:31:05:D3:Remote:Closing client 127.0.0.1
00:31:05:D3:App:Removing remote 127.0.0.1

[kbernhagen]

Bogus timestamp differs here.

00:35:36:D3:Remote:msg: {
00:35:36:D3:Remote:  "cmd": "config",
00:35:36:D3:Remote:  "config": {
00:35:36:D3:Remote:    "groups": {
00:35:36:D3:Remote:      "": {"cpus": 2}
00:35:36:D3:Remote:    }
00:35:36:D3:Remote:  },
00:35:36:D3:Remote:  "time": "2025-07-28T00:35:36Z"
00:35:36:D3:Remote:}
00:35:36:D3:Websocket:WS21:Websocket message rejected: Failed to parse time '2024-05-11T08:32:54.712671Z' with format '%Y-%m-%dT%H:%M:%SZ': Did not parse whole string
00:35:36:D3:Remote:Closing client 127.0.0.1
00:35:36:D3:App:Removing remote 127.0.0.1

[kbernhagen]

No error with wus command from web control, even tho it has milliseconds.

00:39:12:D3:Remote:msg: {"enable": true, "cmd": "wus", "time": "2025-07-28T00:39:12.563Z"}

[kbernhagen]

A bogus timestamp error still appears when lufah does not send any.

03:57:28:D3:Remote:New client 127.0.0.1
03:57:28:D3:App:Adding remote 127.0.0.1
03:57:28:D3:Remote:msg: {"state": "finish", "cmd": "state"}
03:57:28:D3:Websocket:WS5:Websocket message rejected: Failed to parse time '2024-05-11T08:35:01.726641Z' with format '%Y-%m-%dT%H:%M:%SZ': Did not parse whole string
03:57:28:D3:Remote:Closing client 127.0.0.1
03:57:28:D3:App:Removing remote 127.0.0.1