Await8987

joined 3 years ago
[–] Await8987@feddit.uk 4 points 4 months ago (1 children)

Other way round I believe rosetta was to run x86 compiled apps on arm chips. So they are just pulling up the bridge to avoid a situation where developers feel like just making an intel/amd binary that will work on both platforms

[–] Await8987@feddit.uk 3 points 4 months ago
[–] Await8987@feddit.uk 1 points 5 months ago

@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...

 

Hi all, I have recently started using Forgejo runners and it's a great tool. I have run into this surprising limitation with accessing artifacts and I wonder if I am just doing something totally wrong?

If I use the artifacts within the same workflow file as per the tests: e2e test then this works as you would expect. But if you have two separate workflow files, so example one with a build step, and one with a deploy step. then the deploy step has no way to access the artifacts?

I also found an open issue which indicates that the github implementation for accessing the artifacts using a token is not currently possible either.

I am surprised I have not seen more people talking about this, so I wonder if I am just doing something really obviously wrong! The fundamental part is that I am using uses: to specify the first stage from the other workflow file.

Where am I going wrong?

jobs:
  build:
    runs-on: docker
    uses: ./.forgejo/workflows/build.yml

  deploy:
    needs: build
[–] Await8987@feddit.uk 1 points 5 months ago (1 children)

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

[–] Await8987@feddit.uk -1 points 5 months ago

Disagree this is bad news, stable is more important tbh

[–] Await8987@feddit.uk 6 points 5 months ago (7 children)

There is still a pipe dream that next election USA will go back to normal... Spoiler alert: its gone

[–] Await8987@feddit.uk 1 points 5 months ago

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

[–] Await8987@feddit.uk 3 points 5 months ago (1 children)

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!

[–] Await8987@feddit.uk 14 points 11 months ago

Long may it continue!!

view more: next ›