-
Notifications
You must be signed in to change notification settings - Fork 60
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
Target param ignored during retry attempts and barrier notifications. #60
Comments
someone1
added a commit
to someone1/appengine-pipelines
that referenced
this issue
Nov 9, 2015
This was tried differently before in commit 443e311. For barrier notifications, this was tried before by getting all barrier records' pipeline keys and doing a batch get, but that method did not account for situations in which barrier checks were fired but no pipes were ready yet. My method will potentially result in more RPC requests, but only pipes that are ready to be executed will be fetched. For retries: we already have the `pipeline_record` fetched, just pass in the target parameter
Can someone test/merge this? |
This looks like it is fixed here: On Sun, Jan 24, 2016 at 10:23 PM, Emil Sit notifications@github.com wrote:
|
@tkaitchuck no objections from me. |
Merged |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Commit 443e311 addressed this previously, but it was reversed. I'll put in a PR shortly that tries it a different way.
The text was updated successfully, but these errors were encountered: