[GH-ISSUE #520] converting driver.Value type float64 to a uint64: invalid syntax #334

New issue

Closed

opened 2026-03-15 13:56:12 +03:00 by kerem · 2 comments

kerem commented

2026-03-15 13:56:12 +03:00

Owner

Originally created by @matteovivona on GitHub (Jun 12, 2025).
Original GitHub issue: https://github.com/axllent/mailpit/issues/520

After upgrading from version 1.24.0 to 1.26.0, I am experiencing an issue where the dashboard indicates there are new messages, but when I click on "Inbox," no messages are displayed.

Here are some relevant logs:

time="2025/06/12 13:25:36" level=debug msg="[db] storing messages with compression: fastest"
time="2025/06/12 13:25:36" level=debug msg="[db] opening rqlite database http://mailpit-rqlite.mailpit.svc.cluster.local"
time="2025/06/12 13:25:36" level=info msg="[smtpd] starting on [::]:1025 (no encryption)"
time="2025/06/12 13:25:36" level=info msg="[http] starting on [::]:8025"
time="2025/06/12 13:25:36" level=info msg="[http] accessible via http://localhost:8025/"
time="2025/06/12 13:27:36" level=error msg="[db] sql: Scan error on column index 0, name \"Created\": converting driver.Value type float64 (\"1.749734495986e+12\") to a uint64: invalid syntax"
time="2025/06/12 13:27:36" level=debug msg="[db] list INBOX in 2.75599ms"

Could this issue be related to a change made in version 1.25.1??
Switch from unnecessary float64 to uint64 API values for App Information values, message & attachment sizes

Originally created by @matteovivona on GitHub (Jun 12, 2025). Original GitHub issue: https://github.com/axllent/mailpit/issues/520 After upgrading from version 1.24.0 to 1.26.0, I am experiencing an issue where the dashboard indicates there are new messages, but when I click on "Inbox," no messages are displayed. Here are some relevant logs: ``` time="2025/06/12 13:25:36" level=debug msg="[db] storing messages with compression: fastest" time="2025/06/12 13:25:36" level=debug msg="[db] opening rqlite database http://mailpit-rqlite.mailpit.svc.cluster.local" time="2025/06/12 13:25:36" level=info msg="[smtpd] starting on [::]:1025 (no encryption)" time="2025/06/12 13:25:36" level=info msg="[http] starting on [::]:8025" time="2025/06/12 13:25:36" level=info msg="[http] accessible via http://localhost:8025/" time="2025/06/12 13:27:36" level=error msg="[db] sql: Scan error on column index 0, name \"Created\": converting driver.Value type float64 (\"1.749734495986e+12\") to a uint64: invalid syntax" time="2025/06/12 13:27:36" level=debug msg="[db] list INBOX in 2.75599ms" ``` Could this issue be related to a change made in version 1.25.1?? `Switch from unnecessary float64 to uint64 API values for App Information values, message & attachment sizes`

kerem

2026-03-15 13:56:12 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-15 13:56:28 +03:00

Author

Owner

@axllent commented on GitHub (Jun 12, 2025):

Thanks for the report @matteovivona , I strongly suspect you are correct. I will investigate this issue this weekend.

From your report cli output I can see you are using rqlite which is helpful to know. Do you know if this rqlite database had existing messages before the Mailpit upgrade, or would the only messages in there have been after the upgrade?

I will look into this issue in the next day or two to try find the cause and fix.

@axllent commented on GitHub (Jun 12, 2025): Thanks for the report @matteovivona , I strongly suspect you are correct. I will investigate this issue this weekend. From your report cli output I can see you are using rqlite which is helpful to know. Do you know if this rqlite database had existing messages before the Mailpit upgrade, or would the only messages in there have been after the upgrade? I will look into this issue in the next day or two to try find the cause and fix.

kerem commented

2026-03-15 13:56:33 +03:00

Author

Owner

@axllent commented on GitHub (Jun 14, 2025):

Thanks again for reporting this. You were absolutely correct - that commit was responsible for breaking rqlite compatibility, and I have fixed this in the latest release. In addition to this I have also added automated testing specifically against rqlite which should help prevent this kind of problem going unnoticed in the future.

@axllent commented on GitHub (Jun 14, 2025): Thanks again for reporting this. You were absolutely correct - that commit was responsible for breaking rqlite compatibility, and I have fixed this in the [latest release](https://github.com/axllent/mailpit/releases/tag/v1.26.1). In addition to this I have also added automated testing specifically against rqlite which should help prevent this kind of problem going unnoticed in the future.