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

Files: File transfers that succeed can still be marked failed if we experience a failure after transfer, but before chmod for exe's #180

Open
dvernon-tacc opened this issue Dec 19, 2024 · 0 comments
Assignees

Comments

@dvernon-tacc
Copy link
Contributor

Joshua U was seeing an issue where file transfers were marked failed, but they really succeeded. The issue was that the transfer succeeded, but when we went back to look and see if the source was executable, we had a problem connecting. That check is there to decide if we should chmod the destination file. This can fail regardless of if the file is actually an executable or not. Here are a couple ideas:

  1. Remember if it's executable from the check before we copy the file
  2. Perhaps we could have created the file as executable instead of chmod-ing it.
@dvernon-tacc dvernon-tacc self-assigned this Dec 19, 2024
@dvernon-tacc dvernon-tacc changed the title File transfers that succeed can still be marked failed if we experience a failure after transfer, but before chmod for exe's Files: File transfers that succeed can still be marked failed if we experience a failure after transfer, but before chmod for exe's Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant