[FORGEJO] a network of "" is not the same as "host" #35

Merged
earl-warren merged 1 commit from earl-warren/act:wip-network into main 2024-03-24 11:58:35 +00:00
Owner

The comment that introduced this change suggests it was motivated by a
border case by which the image would be empty. It is however unclear
why it should have any impact on how the network name is determined.

The hunk is reverted.

https://github.com/nektos/act/pull/1949/files#r1315163582

The comment that introduced this change suggests it was motivated by a border case by which the image would be empty. It is however unclear why it should have any impact on how the network name is determined. The hunk is reverted. https://github.com/nektos/act/pull/1949/files#r1315163582
earl-warren added 1 commit 2024-03-24 11:11:15 +00:00
All checks were successful
checks / check and test (pull_request) Successful in 6m58s
/ cascade (pull_request) Has been skipped
09d179c15b
[FORGEJO] a network of "" is not the same as "host"
The comment that introduced this change suggests it was motivated by a
border case by which the image would be empty. It is however unclear
why it should have any impact on how the network name is determined.

The hunk is reverted.

https://github.com/nektos/act/pull/1949/files#r1315163582
Contributor

cascading-pr updated at forgejo/runner#166

cascading-pr updated at https://code.forgejo.org/forgejo/runner/pulls/166
Contributor

cascading-pr updated at forgejo/runner#166

cascading-pr updated at https://code.forgejo.org/forgejo/runner/pulls/166
twenty-panda approved these changes 2024-03-24 11:35:54 +00:00
viceice approved these changes 2024-03-24 11:45:17 +00:00
Member

should we upstream it? I think it's an issue there too.

should we upstream it? I think it's an issue there too.
Author
Owner

Passed end to end.

Passed [end to end](https://code.forgejo.org/forgejo/end-to-end/actions/runs/946/jobs/2#jobstep-3-543).
Author
Owner

should we upstream it? I think it's an issue there too.

I would wait: the entire service patch in ACT is going to be reverted in the next few days in the Gitea fork because there was concerns it has other regressions. I can't find the discussion right now, it is somewhere in the issues. I'm happy to let the dust settle and see what happens.

> should we upstream it? I think it's an issue there too. I would wait: the entire service patch in ACT is going to be reverted in the next few days in the Gitea fork because there was concerns it has other regressions. I can't find the discussion right now, it is somewhere in the issues. I'm happy to let the dust settle and see what happens.
earl-warren merged commit af0a149a4d into main 2024-03-24 11:58:35 +00:00
earl-warren deleted branch wip-network 2024-03-24 11:58:35 +00:00
Member

should we upstream it? I think it's an issue there too.

I would wait: the entire service patch in ACT is going to be reverted in the next few days in the Gitea fork because there was concerns it has other regressions. I can't find the discussion right now, it is somewhere in the issues. I'm happy to let the dust settle and see what happens.

plausible 👍

> > should we upstream it? I think it's an issue there too. > > I would wait: the entire service patch in ACT is going to be reverted in the next few days in the Gitea fork because there was concerns it has other regressions. I can't find the discussion right now, it is somewhere in the issues. I'm happy to let the dust settle and see what happens. plausible 👍
Author
Owner

https://gitea.com/gitea/act/issues/99 is the corresponding discussion.

https://gitea.com/gitea/act/issues/99 is the corresponding discussion.
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: forgejo/act#35
No description provided.