-
Notifications
You must be signed in to change notification settings - Fork 3
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
Revert "expand on the getContext()
description"
#125
Conversation
specification.md
Outdated
@@ -166,7 +162,7 @@ using either a remote or local job management library; application jobs | |||
are then submitted to the pilot system, which sends them directly to the | |||
existing pilot job instances for execution, bypassing queuing | |||
systems/LRMs. The requirements for the APIs used to submit the pilot jobs | |||
as well as those used to run the application and remote job management | |||
as well as those used to run the application l and remote job management |
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.
l?
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.
Well, the revert also covers some small bug fixes :-/
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.
Hah, OK. I think we can safely keep this fix though.
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.
ok, done.
specification.md
Outdated
@@ -278,7 +274,7 @@ customary in the language in which the library is implemented | |||
|
|||
#### Interaction with LRMs and Scalability | |||
|
|||
Implementations should use bulk status operations when interacting with | |||
Implementations must use bulk status operations when interacting with |
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.
Are we sure we want "must" instead of "should" here>
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.
I am very much in favor of should
- thus the original edit. I'll do a separate PR for that one if that's ok for you...
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.
A separate PR sounds like a lot of work. I'm fine with this being kept here.
752d29c
to
33a5ffa
Compare
as discussed in #125, this changes `must communicate in bulk` to `should...` - not all backends support bulks, `local` being a prominent example. The commit also fixes a stray `l`.
As discussed in #125, this changes `must communicate in bulk` to `should...`, Not all backends support bulks, `local` being a prominent example. The commit also fixes a stray `l`.
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.
Just some other fixes that were reverted that I think we might want to keep:
As discussed in #125, this changes `must communicate in bulk` to `should...`, Not all backends support bulks, `local` being a prominent example. The commit also fixes a stray `l`.
d0275a7
to
b39f557
Compare
Latest changes look nice. @SteVwonder? |
Yep! LGTM! Clicking the big green button :) |
Reverts #122
See #122