Wakatime.com migration

[SrIzan10]

initial work for migrating wakatime.com heartbeats to hackatime v2.

still not done:

• show status on the settings
• confirm duplicate checks work after migrating hackatime v1
• mirror to wakatime.com (i'll probably leave this for another pr) max has already implemented this

[SrIzan10]

@maxwofford how do i test hackatime v1 migrations? i need a database url apparently...

[hexaaagon]

any progress?

[SrIzan10]

migrating is done, but i want to polish more things down the line

[JasonLovesDoggo]

Is this abandoned @SrIzan10?

[SrIzan10]

no, just waiting for max to respond. wanted to check if hackatime v1 heartbeats weren't duplicated when migrating.

i'll probably find a way to do it myself, so i guess i can move on to mirroring the heartbeats

[JasonLovesDoggo]

no, just waiting for max to respond. wanted to check if hackatime v1 heartbeats weren't duplicated when migrating.

i'll probably find a way to do it myself, so i guess i can move on to mirroring the heartbeats

see muety/wakapi#87

[hexaaagon]

no, just waiting for max to respond. wanted to check if hackatime v1 heartbeats weren't duplicated when migrating.
i'll probably find a way to do it myself, so i guess i can move on to mirroring the heartbeats

see muety/wakapi#87

technically yes, but this project is using ruby on rails, not golang. and he had some problem to integrate this, because it will overlap the hackatime v1 data so ended up doubling the data on the hackatime. not sure how he'll fix this problem tho.

i wish i can code ruby languange. i'll help this man fr

[JasonLovesDoggo]

no, just waiting for max to respond. wanted to check if hackatime v1 heartbeats weren't duplicated when migrating.
i'll probably find a way to do it myself, so i guess i can move on to mirroring the heartbeats

see muety/wakapi#87

technically yes, but this project is using ruby on rails, not golang. and he had some problem to integrate this, because it will overlap the hackatime v1 data so ended up doubling the data on the hackatime. not sure how he'll fix this problem tho.

i wish i can code ruby languange. i'll help this man fr

I'm referring to their techniques to prevent duplication. That is not language bound

[SrIzan10]

i didn't notice that, thank you! i'll work on it this weekend.

[hexaaagon]

no, just waiting for max to respond. wanted to check if hackatime v1 heartbeats weren't duplicated when migrating.
i'll probably find a way to do it myself, so i guess i can move on to mirroring the heartbeats

see muety/wakapi#87

technically yes, but this project is using ruby on rails, not golang. and he had some problem to integrate this, because it will overlap the hackatime v1 data so ended up doubling the data on the hackatime. not sure how he'll fix this problem tho.
i wish i can code ruby languange. i'll help this man fr

I'm referring to their techniques to prevent duplication. That is not language bound

they don't have 2 wakatime datas at the same time tho, i don't know which one did you call "duplication"

[SrIzan10]

alright, i think it's good enough, though i think that if you first migrate wakatime and then hackatime it might still duplicate

[SrIzan10]

maybe it'd not because of the unique constraint in fields_hash?
i'm honestly pretty lost on this one rn, because maybe hackatime stores data in a different format that makes the hash check totally different.

[JasonLovesDoggo]

maybe it'd not because of the unique constraint in fields_hash?
i'm honestly pretty lost on this one rn, because maybe hackatime stores data in a different format that makes the hash check totally different.

Cc @taciturnaxolotl @maxwofford

[taciturnaxolotl]

fairly certain we do store it differently there. I'm not entirely sure as that was something I didn't touch that much when creating hackatime. I think I adjusted it to account for some new fields but that was it

[SrIzan10]

@taciturnaxolotl have you touched this?

[taciturnaxolotl]

Nope; only bit im familiar with is the summary endpoint since I made it

[SrIzan10]

i think we're one step closer, then!

i don't know when wakatime syncing will be pushed to production though, so maybe this pr will get pushed back until that gets done since it's getting the api key from there.

[JasonLovesDoggo]

This doesn't close #85

#85 is about hackatime -> wakatime
this is wakatime -> hackatime

[SrIzan10]

i had #85 in mind for this pr, but max already has done this upstream, though still not in production.
i'll remove that on the first comment so it won't get closed when this gets merged.

[JasonLovesDoggo]

i had #85 in mind for this pr, but max already has done this upstream, though still not in production.
i'll remove that on the first comment so it won't get closed when this gets merged.

So if it's already in main, what does this PR do?