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.

Sign up for GitHub

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

Jump to bottom

Clarify description of notifications related to Consume control changes #82

Open
gavin-norman-sociomantic opened this issue Jan 29, 2019 · 0 comments
Open

Clarify description of notifications related to Consume control changes #82

gavin-norman-sociomantic opened this issue Jan 29, 2019 · 0 comments
Labels
type-feature

Comments

@gavin-norman-sociomantic
Copy link

Statements like:

All known nodes have either stopped the request (as requested by the
user, via the controller) or are not currently connected. The request is
now finished

Can be interpreted to mean that the request is finished because either one of the following conditions occurred:

  1. The user used the controller to stop the request
  2. All nodes are not currently connected

It could be made clearer that this is not the meaning: the controller must have been used.
@gavin-norman-sociomantic gavin-norman-sociomantic added this to the v14.3.0 milestone Jan 29, 2019
@matthias-wende-sociomantic matthias-wende-sociomantic modified the milestones: v14.3.0, v14.4.0 Feb 5, 2019
@Geod24 Geod24 removed this from the v14.4.0 milestone Aug 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type-feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Geod24 @gavin-norman-sociomantic @matthias-wende-sociomantic