LOL what a world

@just_another_person@lemmy.world sorry to answer your actual question: Using https://data.forgejo.org/forgejo/upload-artifact@v4 and https://data.forgejo.org/forgejo/download-artifact@v4

@just_another_person@lemmy.world The runner picks up the task and when they are in the same workflow file the tasks are executed on the same run_id (as far as I understand) which means when using download artifacts code: https://code.forgejo.org/forgejo/download-artifact/src/tag/v4/ the request for artifacts works correctly as the request has the right ID. But sadly when they are separate tasks it requests the wrong ID (as I understand) and the section in the readme about downloading from other workflow runs is incorrect as its just mirrored from github, and the run_id and token field is not implemented which is discussed in this ticket. But I am shocked that everyone is not running into this? Still think im being dumb...

Any company funded by venture capital is coming for your money eventually, whatever they say in the short term.

Disagree this is bad news, stable is more important tbh

I would really love to know how they think this ends. Its like they either cant see 2 moves ahead or they are just delusional

Also very impressed with desec!

The brakes on electric cars are not magic software defined wizardry they are normal hydraulics… so if one was to push hard on the brake pedal even with the motors engaged it would slow down. And it would be extremely easy to prove because the pads would be heavily worn presumably if he was stamping on them and the motors were so powerful to keep it at 30!

“Old man cant drive new car” until there is some more evidence. Sad really! Thanks for sharing for the lol

The important question is what is so wrong with the now countless existing 200/300 mile evs that charge in less than 30 minutes?