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

Revert "expand on the getContext() description" #125

Merged
merged 3 commits into from
Apr 23, 2021

Conversation

andre-merzky
Copy link
Collaborator

Reverts #122

See #122

@andre-merzky andre-merzky requested a review from hategan March 26, 2021 10:06
@andre-merzky
Copy link
Collaborator Author

ping @hategan : I hope this is in the gist we discussed: #122 was a mistake of mine, confusing the roles of context and message.

@hategan
Copy link
Collaborator

hategan commented Apr 17, 2021

ping @hategan : I hope this is in the gist we discussed: #122 was a mistake of mine, confusing the roles of context and message.

I think your "mistake" was invited by our discussions not being very clear on one or the other.

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
Copy link
Collaborator

Choose a reason for hiding this comment

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

l?

Copy link
Collaborator Author

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 :-/

Copy link
Collaborator

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.

Copy link
Collaborator Author

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
Copy link
Collaborator

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>

Copy link
Collaborator Author

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...

Copy link
Collaborator

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.

@andre-merzky andre-merzky force-pushed the revert-122-fix/get_context branch from 752d29c to 33a5ffa Compare April 17, 2021 18:48
andre-merzky added a commit that referenced this pull request Apr 17, 2021
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`.
andre-merzky added a commit that referenced this pull request Apr 18, 2021
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`.
Copy link
Collaborator

@SteVwonder SteVwonder left a 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`.
@andre-merzky andre-merzky force-pushed the revert-122-fix/get_context branch from d0275a7 to b39f557 Compare April 22, 2021 10:05
@andre-merzky andre-merzky requested a review from SteVwonder April 22, 2021 10:07
@hategan
Copy link
Collaborator

hategan commented Apr 22, 2021

Latest changes look nice. @SteVwonder?

@SteVwonder
Copy link
Collaborator

Yep! LGTM! Clicking the big green button :)

@SteVwonder SteVwonder merged commit 67a8419 into main Apr 23, 2021
@SteVwonder SteVwonder deleted the revert-122-fix/get_context branch April 23, 2021 00:06
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.

3 participants