Doubt

This for sure

@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

OP I’m fairly certain your issue is with your music file metadata rather than the software. I suspect if you clean it with musicbrainz picard or open it with a tag editor you will find its using slightly different characters in different metadata fields. You can test this by loading up one of the offending files, clearing all of its metadata and see if that looks better!