bug(jot-server): Invalid timestamp #184

New issue

Closed

opened 2026-11-06 21:23:35 +00:00 by treadful · 0 comments

treadful commented

2026-11-06 21:23:35 +00:00

Owner

Issue when trying to ban a key:

2026-11-06T21:21:13 ERROR:
         fields > message: Invalid timestamp (1)
                    level: ERROR
            span > method: GET
              span > name: Request
              span > path: /mod/ban/key
       span > remote_addr: socket://127.0.0.1:45730
           span > version: HTTP/1.1
        spans[1] > method: GET
          spans[1] > name: Request
          spans[1] > path: /mod/ban/key
   spans[1] > remote_addr: socket://127.0.0.1:45730
       spans[1] > version: HTTP/1.1
                   target: jot_server::db::sqlite3
                timestamp: 2026-11-06T21:21:13.567517Z

Issue when trying to ban a key: ``` 2026-11-06T21:21:13 ERROR: fields > message: Invalid timestamp (1) level: ERROR span > method: GET span > name: Request span > path: /mod/ban/key span > remote_addr: socket://127.0.0.1:45730 span > version: HTTP/1.1 spans[1] > method: GET spans[1] > name: Request spans[1] > path: /mod/ban/key spans[1] > remote_addr: socket://127.0.0.1:45730 spans[1] > version: HTTP/1.1 target: jot_server::db::sqlite3 timestamp: 2026-11-06T21:21:13.567517Z ```

treadful added the

bug

label

2026-11-06 21:23:35 +00:00

treadful self-assigned this

2026-11-06 21:23:35 +00:00

treadful referenced this issue from a pull request that will close it,

2026-11-06 22:06:37 +00:00

fix(server): until on bans is optional #186

treadful closed this issue

2026-11-07 00:11:25 +00:00