Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Add missing 'archived' prop for ArtifactPanel component. Fixes #12331 #12397

Merged
merged 12 commits into from
Jan 12, 2024

Conversation

Garett-MacGowan
Copy link
Contributor

@Garett-MacGowan Garett-MacGowan commented Dec 22, 2023

Fixes #12331

Motivation

A missing archived prop in the UI's ArtifactPanel component was causing an improper URL to be used to fetch the artifact (assuming the workflow was archived).

Modifications

Added the missing archived prop to the ArtifactPanel component.

Verification

I added tests to the argo server test suite to account for the URL structure which was previously untested. I called this test GetArtifactByNodeID, in accordance with naming conventions in similar tests.

For the UI, I ran the TestArtifactServerArtifactPassing test (which contains the GetArtifactByNodeID test mentioned above) using:

make start UI=true PROFILE=postgres
make TestArtifactServerArtifactPassing

Once it completed, I manually verified that the artifact in the ArtifactPanel was downloadable.

image

image

(download button)
image

@jmeridth
Copy link
Member

Screenshot example?

@Garett-MacGowan
Copy link
Contributor Author

Screenshot example?

I'll provide it in a moment.

@Garett-MacGowan
Copy link
Contributor Author

Screenshot example?

@jmeridth I added the screenshots.

@agilgur5 agilgur5 self-assigned this Dec 28, 2023
…xes an issue where the UI returns an Internal Server Error. Fixes argoproj#12331

Signed-off-by: Garett MacGowan <garettsoftware@gmail.com>
Signed-off-by: Garett MacGowan <garettsoftware@gmail.com>
Signed-off-by: Garett MacGowan <garettsoftware@gmail.com>
Signed-off-by: Garett MacGowan <garettsoftware@gmail.com>
Signed-off-by: Garett MacGowan <garettsoftware@gmail.com>
@Garett-MacGowan
Copy link
Contributor Author

@agilgur5 this is rebased and ready to go

Copy link
Contributor

@agilgur5 agilgur5 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just have a small comment around test naming, but otherwise LGTM.

Great catch and thanks for the detailed fix!

@@ -1037,6 +1037,30 @@ spec:
})
}

func (s *ArgoServerSuite) TestArtifactServerArtifactPassing() {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel like we should specify that this checking Archived Workflows specifically, though I do see that some of the tests name it explicitly and others don't 😕

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will do.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@agilgur5 I changed the name to TestArtifactServerArchivedWorkflow. Is this more along the lines of what you were thinking?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Works for me. Naming is hard, especially for this level of specificity 😅

@agilgur5 agilgur5 requested a review from juliev0 January 8, 2024 22:33
@agilgur5
Copy link
Contributor

agilgur5 commented Jan 8, 2024

Also is there a reason you merge main frequently in this PR? We don't require that PRs be up-to-date with main so it's not necessary. For most PRs, it usually doesn't affect anything either.

@agilgur5
Copy link
Contributor

agilgur5 commented Jan 8, 2024

Btw @Garett-MacGowan would you be interested in joining the Argo project as a Member?
You've had some great fixes along with very high quality PRs etc and we'd love to have you if you're interested. I would be willing to sponsor and I think Julie and others would as well 🙂

@Garett-MacGowan
Copy link
Contributor Author

Garett-MacGowan commented Jan 9, 2024

Btw @Garett-MacGowan would you be interested in joining the Argo project as a Member? You've had some great fixes along with very high quality PRs etc and we'd love to have you if you're interested. I would be willing to sponsor and I think Julie and others would as well 🙂

@agilgur5 I'd be happy to! There's no strict hourly commitment right? I'd be happy to spend a few hours every week.

@Garett-MacGowan
Copy link
Contributor Author

Also is there a reason you merge main frequently in this PR? We don't require that PRs be up-to-date with main so it's not necessary. For most PRs, it usually doesn't affect anything either.

Didn't know PRs didn't need to be up to date. If there are conflicts, it would provide a different prompt than "Update branch" right?

Garett-MacGowan and others added 2 commits January 8, 2024 19:18
…chivedWorkflow for clarity. Addresses PR comment. Fixes argoproj#12331

Signed-off-by: Garett MacGowan <garettsoftware@gmail.com>
@agilgur5
Copy link
Contributor

agilgur5 commented Jan 9, 2024

Didn't know PRs didn't need to be up to date.

It is a requirement you can add on GitHub, but we don't currently require it. There's only been a handful of times where that's caused an issue, which is actually with "invisible" merge conflicts (i.e. two PRs that when merged together break a build, but do not conflict in version control itself). I think we can also solve those with a merge queue as well instead of an extra PR requirement, as was discussed briefly over Slack

If there are conflicts, it would provide a different prompt than "Update branch" right?

Yep, it would say merging is not possible due to conflicts. The prompt instead says "Resolve conflicts" in that case.

@agilgur5
Copy link
Contributor

agilgur5 commented Jan 9, 2024

@agilgur5 I'd be happy to! There's no strict hourly commitment right? I'd be happy to spend a few hours every week.

Awesome! Correct, there are currently no strict commitments associated with Membership or other roles. It comes with some additional privileges (i.e. issue triage) and some small responsibilities that are usually the norm for active contributors in most repos anyway (e.g. responding when tagged). Otherwise, the only main "rule" outlined in the doc is that Members with no activity what-so-ever for an entire year will get pruned (but can still re-request whenever and will be expedited if so).

Could you file a membership request issue in the argoproj repo as is described in the above doc?
Julie upvoted my comment so can list both of us as sponsors and I'm pretty sure the Leads would be glad to sponsor as well once they see the request 🙂

We do also have a separate Sustainability Effort that was recently created that is specific to Argo Workflows (i.e. does not apply to CD or other projects at this time). That effort is a completely optional addition to the formal Argo project roles. If you're interested in that as well, that does have an hourly commitment but is not "strict" per se, as it is an average over time (e.g. I had 0 hours some weeks in Nov/Dec but my average is much higher).

Copy link
Contributor

@agilgur5 agilgur5 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Garett-MacGowan
Copy link
Contributor Author

@agilgur5, @juliev0 can this be merged? It's unfortunate it didn't make it into the latest release.

@agilgur5
Copy link
Contributor

agilgur5 commented Jan 12, 2024

For reference, I'm not an Approver (yet), so I don't have merge permissions, which is why I requested a review from Julie.

Agreed this would have been good to have for the release, but we'll have another soon enough since there are still two P1 bugs out.

@juliev0 juliev0 merged commit b447951 into argoproj:main Jan 12, 2024
27 checks passed
@juliev0
Copy link
Contributor

juliev0 commented Jan 12, 2024

For reference, I'm not an Approver (yet), so I don't have merge permissions, which is why I requested a review from Julie.

Sorry, I missed that you requested my review!

@Garett-MacGowan
Copy link
Contributor Author

Garett-MacGowan commented Jan 12, 2024

Thanks Julie!

sarabala1979 pushed a commit that referenced this pull request Jan 13, 2024
…12331 (#12397)

Signed-off-by: Garett MacGowan <garettsoftware@gmail.com>
Signed-off-by: Saravanan Balasubramanian <sarabala1979@gmail.com>
isubasinghe pushed a commit to isubasinghe/argo-workflows that referenced this pull request Feb 27, 2024
isubasinghe pushed a commit to isubasinghe/argo-workflows that referenced this pull request Feb 27, 2024
isubasinghe pushed a commit to isubasinghe/argo-workflows that referenced this pull request Feb 27, 2024
isubasinghe pushed a commit to isubasinghe/argo-workflows that referenced this pull request Feb 28, 2024
…rgoproj#12331 (argoproj#12397)

Signed-off-by: Garett MacGowan <garettsoftware@gmail.com>
Signed-off-by: Isitha Subasinghe <isubasinghe@student.unimelb.edu.au>
@agilgur5 agilgur5 added this to the v3.5.x patches milestone Apr 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Artifact in workflow diagram not working when workflow is archived and deleted from cluster
4 participants