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

Fixes to pelican plugin staging #882

Conversation

joereuss12
Copy link
Contributor

Changes:

  • Found that how condor gives hooks a classad is in a different format than the plugin for some reason. For the hook the classad is split up by newlines but for the plugin it is by ';'. Therefore, made a new function for plugin stage to utilize.
  • Added function within the plugin to force logging to go to stderr (even though that is the default) as well as a file called .PelicanPlugin.log. This extra file is something you can specify in a condor submit file in transfer_output_files to get it back but only works if the job does not go on hold/if the plugin does not fail (not super helpful yet)

@joereuss12 joereuss12 linked an issue Mar 1, 2024 that may be closed by this pull request
@joereuss12
Copy link
Contributor Author

Note: waiting until I write a unit test for review

@joereuss12 joereuss12 force-pushed the shadow-hooks-with-pelican-staging-branch branch from 764da0e to d85e199 Compare March 11, 2024 17:25
@joereuss12 joereuss12 marked this pull request as ready for review March 11, 2024 17:25
@joereuss12
Copy link
Contributor Author

Since I have to wait until #798 is merged for a test to work. Marking as ready for review so we can get the bug fixes and refactoring in

@joereuss12 joereuss12 force-pushed the shadow-hooks-with-pelican-staging-branch branch from d85e199 to 46fb14e Compare March 19, 2024 20:36
Changes:
- Found that how condor gives hooks a classad is in a different format
  than the plugin for some reason. For the hook the classad is split up
  by newlines but for the plugin it is by ';'. Therefore, made a new
  function for plugin stage to utilize.
- Added function within the plugin to force logging to go to stderr
  (even though that is the default) as well as a file called
  `.PelicanPlugin.log`. This extra file is something you can specify in
  a condor submit file in `transfer_output_files` to get it back but only works if the
  job does not go on hold/if the plugin does not fail (not super helpful
  yet)
Separates out a lot of pieces of the main function into smaller
functions. This helps with readability as well as for future unit
testing.
This causes issues with plugin staging as condor will assume this is a
classad being printed out when it in a shadow hook with the -l flag.
This needs to be removed or add some sort of check if this is used with
staging or the plugin
Just annoying for testing and not really needed, at least for now
@joereuss12 joereuss12 force-pushed the shadow-hooks-with-pelican-staging-branch branch from 46fb14e to 1117218 Compare March 29, 2024 15:53
Copy link
Member

@jhiemstrawisc jhiemstrawisc left a comment

Choose a reason for hiding this comment

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

Overall seems good to me. Comments were very helpful to figure out what was going on, thanks!

@joereuss12 joereuss12 merged commit d77c491 into PelicanPlatform:main Apr 4, 2024
19 checks passed
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

Successfully merging this pull request may close these issues.

Revisit condor shadow hooks with plugin staging
2 participants