-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Fix NPE in ComputationState constructor introduced by PR/7846 #7869
Conversation
…ot cause was assuming an empty transformUserNameToStateFamily map was passed, when instead null was passed.
R: @reuvenlax |
I don't know.
…On Sun, Feb 17, 2019, 7:04 PM Ryan Williams ***@***.*** wrote:
Thanks for the quick fix here @drieber <https://github.com/drieber>!
One question I had was why the Java_Examples_Dataflow precommit didn't
run on #7846 <#7846> (and so far
doesn't seem to have run here)?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#7869 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AT9x-qjJo9bL0c4XqE3a4mKyB8BEfghjks5vOhg0gaJpZM4a_9dw>
.
|
Run Dataflow ValidatesRunner |
Run Java PostCommit |
Run Java_Examples_Dataflow PreCommit |
@drieber thanks for the quick fix! For future reference, when changing a specific runner, it's best to run the ValidatesRunner tests for that runner before merging (see the run I triggered above for the Dataflow runner). Unfortunately the documentation on these trigger phrases is still a bit spotty. |
@reuvenlax per my comment above, do you know why "Java_Examples_Dataflow PreCommit" ran on our PRs (#7823, #7865) that didn't seem to have to do with Dataflow, but not #7846 (where the bug was introduced) nor here (where the bug was fixed)? |
Here is the trigger pattern (from
job_PreCommit_Java_Examples_Dataflow.groovy
<https://github.com/apache/beam/pull/6802/files#diff-29c78beae45d057dc4643ea33166a399>
)
I think the path runners/google-cloud-dataflow in the trigger is incorrect.
The actual code path is runners/dataflow.
PrecommitJobBuilder builder = new PrecommitJobBuilder(
scope: this,
nameBase: 'Java_Examples_Dataflow',
gradleTask: ':javaExamplesDataflowPreCommit',
gradleSwitches: ['-PdisableSpotlessCheck=true'], // spotless
checked in separate pre-commit
triggerPathPatterns: [
'^model/.*$',
'^sdks/java/.*$',
'^runners/google-cloud-dataflow/.*$',
'^examples/java/.*$',
'^release/.*$',
]
)
…On Mon, Feb 18, 2019 at 1:16 PM Ryan Williams ***@***.***> wrote:
@reuvenlax <https://github.com/reuvenlax> per my comment above
<#7869 (comment)>, do you
know why "Java_Examples_Dataflow PreCommit" ran on our PRs (#7823
<#7823>, #7865
<#7865>) that didn't seem to have to
do with Dataflow, but not #7846 <#7846>
(where the bug was introduced) nor here (where the bug was fixed)?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#7869 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AUGE1XbjxbuXaeQHvqetViDggv7EpPCiks5vOxgegaJpZM4a_9dw>
.
|
The root cause was assuming an empty transformUserNameToStateFamily map was passed, when instead null was passed.
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
R: @username
).[BEAM-XXX] Fixes bug in ApproximateQuantiles
, where you replaceBEAM-XXX
with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.Post-Commit Tests Status (on master branch)
See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.