mirror of
https://github.com/axllent/mailpit.git
synced 2026-04-26 00:35:51 +03:00
[GH-ISSUE #107] [1.6.6] [db] SQL logic error: no such column: Sort (1) #71
Labels
No labels
awaiting feedback
bug
docker
documentation
enhancement
github_actions
invalid
pull-request
question
stale
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/mailpit#71
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @PhilETaylor on GitHub (May 4, 2023).
Original GitHub issue: https://github.com/axllent/mailpit/issues/107
Just noticed this when running the docker container today
@axllent commented on GitHub (May 4, 2023):
Hmmm, is it running with an existing database, or a temporary one? If existing, is it possible that more than one Mailpit instance is running using the same database, and that this error message is coming from an older version of Mailpit? The Sort column had been replaced and I'm fairly sure there should be no references to Sort in the code.
@PhilETaylor commented on GitHub (May 4, 2023):
sorry should have said this is running as a docker container - so totally new 1.6.6 container instantiated by docker-compose
@amaurycid commented on GitHub (May 4, 2023):
Same happening to me using an existing database running locally (no docker).
I'm sure that I'm running one instance.
@PhilETaylor commented on GitHub (May 4, 2023):
I have completely removed the docker container, and started again from scratch using the documented standard way of running the container
and I get output
and then after a short while I get the error
I know nothing about the
goprogramming language, but a quick search of your repo has a suspectSorthere:github.com/axllent/mailpit@f2bce03e9e/storage/utils.go (L95)@axllent commented on GitHub (May 4, 2023):
You're absolutely correct. Fortunately this didn't break anything, it just did not auto-delete any messages (if greater than the current maximum setting) due to the error. I have fixed this now in v1.6.7. Thanks for the report!