Posts by fin_ger@mastodon.social
(DIR) Post #9nU5tnqXYrWPqddDea by fin_ger@mastodon.social
2019-10-01T10:18:20Z
1 likes, 0 repeats
@fredowald and me finished adding error handling to the cursive-async-view #rust crate. We added a small animation to display an error message. The program shown is the `timeout` example from the git repository:https://github.com/deinstapel/cursive-async-view/blob/master/examples/timeout.rs#rustlang
(DIR) Post #9qbIDAsX0Ik4cn92au by fin_ger@mastodon.social
2020-01-02T19:17:25Z
1 likes, 0 repeats
@sean @FiXato Do another vote, I will boost and vote :D
(DIR) Post #9rHocYmkIzGihmEcwi by fin_ger@mastodon.social
2020-01-23T07:51:04Z
0 likes, 0 repeats
@rugk yesterday, I tried the gitea github migrator on codeberg... It horribly failed. Issues, PRs, etc. got imported, but where not assigned to the correct repository. Instead, all issues where randomly added to other projects ðŸ˜ðŸ˜ðŸ˜https://gitea.com/gitea/migratorAll 53 of my projects got screwed up...#gitea
(DIR) Post #9rIHR6hzFcgH6ztrhg by fin_ger@mastodon.social
2020-01-23T11:14:28Z
0 likes, 0 repeats
@paolo @rugk I used this command with gitea-github-migrator 0.0.11+128 from the github releases downloads:gitea-github-migrator_linux_amd64 migrate-all --gh-user fin-ger --gh-token ... --url https://codeberg.org --token ...
(DIR) Post #9rIHR7Y67sMficHTvc by fin_ger@mastodon.social
2020-01-23T11:30:07Z
0 likes, 0 repeats
@paolo @rugk Hmm, I tried to use the Migration form on codeberg but could not figure out how it should work. All my imports via the migration form skipped issues, prs, etc.The form said I should just enter my github username to see further options, but no further options appeared...
(DIR) Post #9rIHR8YUNuGuq7TJB2 by fin_ger@mastodon.social
2020-01-23T13:11:08Z
0 likes, 0 repeats
@paolo @rugk Oh no, I misunderstood the migration form 🙈 I thought the `Migrate` label indicates the form field for the github username...Sadly, the gitea FAQ points to the gitea-github-migrator tool which lead me in the wrong direction:https://docs.gitea.io/en-us/faq/#how-to-migrate-from-gogs-github-etc-to-gitea
(DIR) Post #9rIHR93KXEwSNltwFU by fin_ger@mastodon.social
2020-01-23T13:11:45Z
0 likes, 0 repeats
@paolo @rugk Also, Github informed me that using a password-based authentication for migration is deprecated:> You recently used a password to access an endpoint through the GitHub API using go-github. We will deprecate basic authentication using password to this endpoint soon:> We recommend using a personal access token (PAT) with the appropriate scope to access this endpoint instead. Visit https://github.com/settings/tokens for more information.
(DIR) Post #9rIHR9jW0OgaUbdd0C by fin_ger@mastodon.social
2020-01-23T13:13:03Z
0 likes, 0 repeats
@paolo @rugk Changing the password label to something like `API Token` and providing the above link to generate such a token would help users. I tested the migration with a PAT and it worked flawlessly.
(DIR) Post #9rIJAsc05sDgfQUR4C by fin_ger@mastodon.social
2020-01-23T13:33:20Z
0 likes, 0 repeats
@rugk @paolo I submitted some issueshttps://github.com/go-gitea/gitea/issues/7635https://github.com/go-gitea/gitea/issues/9951
(DIR) Post #A1sUFhIA2c8IBRdGsK by fin_ger@mastodon.social
2020-01-21T16:11:56Z
0 likes, 0 repeats
And here is the blog-post on getting pixel-perfect scrolling working under Linux with a Logitech M720 mousehttps://blog.like-a-fin.lol/Pixel-Perfect-Scrolling-With-a-Mouse-Wheel-Under-Linux#linux #gnome #logitech #libinput