Skip to content

Make ping count/delay configurable#23

Merged
matburt merged 6 commits intoproject-receptor:masterfrom
jimi-c:ping_count
Sep 17, 2019
Merged

Make ping count/delay configurable#23
matburt merged 6 commits intoproject-receptor:masterfrom
jimi-c:ping_count

Conversation

@jimi-c
Copy link
Copy Markdown
Contributor

@jimi-c jimi-c commented Sep 9, 2019

Make ping count/delay configurable

  • Adds float type to allowed value types
  • Modifies entrypoints.run_as_ping to use new config options
  • Modifies controller.send_directiveto use a new param namedexpected_responses`, which allows us to stop waiting for more responses after the set # is received (defaults to 1 response)

* Adds `float` type to allowed value types
* Modifies `entrypoints.run_as_ping` to use new config options
* Modifies controller.send_directive` to use a new param named
  `expected_responses`, which allows us to stop waiting for more
  responses after the set # is received (defaults to 1 response)
@matburt
Copy link
Copy Markdown
Member

matburt commented Sep 9, 2019

I wonder if we should allow a way to make this basically indefinite. Sometimes, and especially in the case of Runner integration this could be some unknown number.

@jimi-c
Copy link
Copy Markdown
Contributor Author

jimi-c commented Sep 9, 2019

If we did, I'd break the connect logic out of send_directive and allow the caller to control when the connection is created/destroyed rather than doing it as a one-shot now.

We also need better response handling to make sure we're not getting fragments, but that's a different future PR.

Comment thread receptor/controller.py Outdated
@matburt matburt merged commit d0a2186 into project-receptor:master Sep 17, 2019
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.

2 participants