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

Correctly return the transfer attempt information #1063

Merged
merged 3 commits into from
Apr 8, 2024

Conversation

bbockelm
Copy link
Collaborator

@bbockelm bbockelm commented Apr 6, 2024

v7.6.x has a regression where the downloadObject function returns an error whenever an error occurs; rather, it's only supposed to return an error if no transfers are attempted. That change causes the multiple attempts to not be returned to the transfer plugin -- instead, only the last one is.

This change:

  • Returns all the failed attempts
  • Fixes the "15s since start" in error messages by recording when the error occurred.
  • Stubs out any paths in the plugin error message (since HTCSS also reports the path).
  • Switches the client to golang time objects where appropriate, converting to integers (and floats) only at the plugin level.

v7.6.x has a regression where the `downloadObject` function returns
an error whenever an error occurs; rather, it's only supposed to return
an error if no transfers are attempted.  That change causes the multiple
attempts to not be returned to the transfer plugin -- instead, only the
last one is.

This change:
- Returns all the failed attempts
- Fixes the "15s since start" in error messages by recording when
  the error occurred.
- Stubs out any paths in the plugin error message (since HTCSS also
  reports the path).
- Switches the client to golang time objects where appropriate, converting
  to integers (and floats) only at the plugin level.
@bbockelm bbockelm requested a review from joereuss12 April 6, 2024 16:58
@bbockelm bbockelm added this to the v7.7.0 milestone Apr 6, 2024
@bbockelm bbockelm added bug Something isn't working client Issue affecting the OSDF client critical High priority for next release labels Apr 6, 2024
bbockelm added 2 commits April 6, 2024 12:25
Previously, errors were converted to a long string which loses the
type information of the error.  Parts of the local cache were depending
on extracting the error stack, causing test failures.
Copy link
Contributor

@joereuss12 joereuss12 left a comment

Choose a reason for hiding this comment

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

LGTM!

@joereuss12 joereuss12 merged commit 722b371 into PelicanPlatform:main Apr 8, 2024
19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working client Issue affecting the OSDF client critical High priority for next release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants