Closed jimmybrancaccio closed 3 years ago
Were you using the image before v1.0.0
? It seems that you're missing some schema changes. Before v1.0.0
schema migrations would have to be made manually but now they are automatic.
To add the missing schemas do the following:
DELETE FROM heartbeats a USING heartbeats b
WHERE a.id < b.id
AND a.time_sent = b.time_sent
AND a.sender = b.sender
AND a.entity = b.entity;
owner
field to your username (it should be null
)
UPDATE projects SET owner = '<replace-with-your-hakatime-username>';
002
to 005
. It's ok if they get skipped with relation <relation_name> already exists
.v1.0.0
.Let me know how this goes as it can be used for others that might have been using pre-v1
images.
@mujx Ah yup! Those steps seemed to do the trick. Apologies on my part for not advising I had been running it pre-1.0.0! I had thought I caught all the updates to get to 1.0.0+ as I had to do some manual work to get some of the new heartbeat (de-duplication) stuff working myself. I appreciate your help in getting me back up and running! 😁
No worries @jimmybrancaccio, I'm glad you're up and running again!
Hello!
I am using
mujx/hakatime:latest
and have been using this image for at least 3-4 weeks now. The container seems to be having some issues. In the logs I see:So I tried running the query manually and I got the same error:
Unfortunately I don't know enough about PGSQL and queries to know what the issue here is 😢 so any help on fixing this would be awesome 😬 !