\o/

Thanks.

After unstucking the migration again, he avatar upload routine is now compliant with the
last http client optimization change and works! I've rebased the commit again and pushed
in the swh branch [1].

/me grunts
another one bites the dust:

Unstuck after some mob debugging ;)
There is a fallback which tries and use the git am command and fails as some git config is missing.
We unstuck it by adding some .gitconfig in the dockerfile declaration.

Thanks!

Nice!

lgtm as well.

(i thought that was just aligning existing implementation, i noticed only now the depends on the other diff ¯\_(ツ)_/¯)

They should use the same convention as Git.

ok, one question inline though

thx

"if you say so" ;)

lgtm, one remark inline.

The migration did a lot more work this time. It finally crashed on the git am command though [1] [2] [3].

• List Item

No longer needed as the full functionality got developed and deployed now.

To summarize, the initial intent was to adapt the jar loaded (as extracted directory) to append the pom.xml so we do not lose that reference.

• Private repository after migration are private.

And it seems it finished without any issues this time [1] [2]

(oops, forgot to validate it yesterday ;)

Changing the command args from [1] to [2], the run cli no longer complains! [3]

• Report migration status

Status update:

• Clean up gitlab state
• Checks
  • make sure host ssh key did not change after state reset (ssh-keyscan)
  • state folder permissions ok
  • access token key generated (and properly referenced in config.lisp)
• Trigger migration
• Report migration status

So i dug as to why my laptop was ok but not my desktop.

Better cli to execute...

forgerie@bespin:~$ logpath="/tmp/forgerie/run-$(date +%Y%m%d-%H%M).log"; echo "## Running migration logs in $logpath ##"; time /opt/forgerie/bin/run | tee $logpath
## Running migration logs in /tmp/forgerie/run-20220613-1410.log ##
...