-
Notifications
You must be signed in to change notification settings - Fork 111
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
PM job state management #3702
PM job state management #3702
Changes from 2 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -203,6 +203,14 @@ def jobs | |
end.flatten | ||
end | ||
|
||
def job_from_id(job_id, cluster) | ||
launchers = Launcher.all(directory) | ||
launchers.each do |launcher| | ||
job = launcher.job_from_id(job_id, cluster) | ||
return job unless job.nil? | ||
end | ||
end | ||
Comment on lines
+206
to
+212
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There's something wrong here that I think I started. jobs are associated with the launchers and that's why you have to do all this weirdness here. But I think a better/simpler paradigm really is that the project itself keeps the job log and the entries have a relationship to the launcher (if we even need such a relationship). Which is really just to say that I think we should rethink & refactor this whole paradigm before it gets worse. I think we can move forward with this as it is, but will likely have to change it almost immediately. |
||
|
||
def readme_path | ||
file = Dir.glob("#{directory}/README.{md,txt}").first.to_s | ||
File.readable?(file) ? file : nil | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You should avoid using
params
directly and instead us maybejob_details_params
so the list of parameters we're accessing are known to be valid and permitted.