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

upgrade upload-artifact to v4 #3130

Merged
merged 1 commit into from
Aug 6, 2024
Merged

upgrade upload-artifact to v4 #3130

merged 1 commit into from
Aug 6, 2024

Conversation

Migelo
Copy link
Contributor

@Migelo Migelo commented Aug 2, 2024

Description

This pull request upgrades the upload-artifact action to v4 following the closing of actions/upload-artifact#485 by release 4.3.5 which allows the v4 action to handle a large amount of files in the artifact zip file.

Change log entry

  • Is a change log needed? If yes, is it added to CHANGES.rst? If you want to avoid merge conflicts,
    list the proposed change log here for review and add to CHANGES.rst before merge. If no, maintainer
    should add a no-changelog-entry-needed label.

Checklist for package maintainer(s)

This checklist is meant to remind the package maintainer(s) who will review this pull request of some common things to look for. This list is not exhaustive.

  • Are two approvals required? Branch protection rule does not check for the second approval. If a second approval is not necessary, please apply the trivial label.
  • Do the proposed changes actually accomplish desired goals? Also manually run the affected example notebooks, if necessary.
  • Do the proposed changes follow the STScI Style Guides?
  • Are tests added/updated as required? If so, do they follow the STScI Style Guides?
  • Are docs added/updated as required? If so, do they follow the STScI Style Guides?
  • Did the CI pass? If not, are the failures related?
  • Is a milestone set? Set this to bugfix milestone if this is a bug fix and needs to be released ASAP; otherwise, set this to the next major release milestone. Bugfix milestone also needs an accompanying backport label.
  • After merge, any internal documentations need updating (e.g., JIRA, Innerspace)?

@pllim pllim added the Build standalone Additional pylons label Aug 2, 2024
@pllim pllim added this to the 4.0 milestone Aug 2, 2024
@pllim
Copy link
Contributor

pllim commented Aug 2, 2024

The decision to use v3 was intentional, see #2855

But perhaps not needed anymore? 🤷‍♀️

@pllim
Copy link
Contributor

pllim commented Aug 2, 2024

Hard to tell whether this fix works or not given a seemingly unrelated error: Error: Timed out waiting for: tcp:8866

I will defer to @rosteen

Thank you!

Copy link

codecov bot commented Aug 2, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.85%. Comparing base (b3bbd9f) to head (01f8880).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3130   +/-   ##
=======================================
  Coverage   88.85%   88.85%           
=======================================
  Files         112      112           
  Lines       17409    17409           
=======================================
  Hits        15468    15468           
  Misses       1941     1941           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@Migelo
Copy link
Contributor Author

Migelo commented Aug 5, 2024

The decision to use v3 was intentional, see #2855

You are right! The underlying issue of "too many open files" described in the pull request you quote was addressed in the issue actions/upload-artifact#485 which just recently got fixed in the following pull request actions/toolkit#1771 2 weeks ago.

Copy link
Contributor

@pllim pllim left a comment

Choose a reason for hiding this comment

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

Only one way to find out. Thanks!

Copy link
Collaborator

@rosteen rosteen left a comment

Choose a reason for hiding this comment

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

Since the fix was released, seems like we can go back to v4. Thanks!

@pllim pllim added the no-changelog-entry-needed changelog bot directive label Aug 6, 2024
@pllim pllim merged commit f8cd410 into spacetelescope:main Aug 6, 2024
21 of 24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Build standalone Additional pylons no-changelog-entry-needed changelog bot directive testing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants