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

NIFI-528 add support to specify timeout in ExecuteProcess #1755

Closed
wants to merge 2 commits into from

Conversation

medjessy
Copy link

@medjessy medjessy commented May 4, 2017

Thank you for submitting a contribution to Apache NiFi.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

For all changes:

  • Is there a JIRA ticket associated with this PR? Is it referenced
    in the commit message?

  • Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

  • Has your PR been rebased against the latest commit within the target branch (typically master)?

  • Is your initial contribution a single, squashed commit?

For code changes:

  • Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
  • Have you written or updated unit tests to verify your changes?
  • If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
  • If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
  • If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
  • If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

  • Have you ensured that format looks appropriate for the output in which it is rendered?

Note:

Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

@jvwing
Copy link
Contributor

jvwing commented Jun 18, 2017

@medjessy - Thanks for submitting this PR. The changes look larger than I would expect when comparing diffs. There appear to be a number of whitespace changes that make it difficult to review the commits. The GitHub UI presents the diffs as a 100% change (line endings?), but I also see what look like extraneous whitespace changes in IntelliJ. Do the diffs look right to you?

@MikeThomsen
Copy link
Contributor

I wonder if this was done on Windows with the Git options not being set to "checkout w/ Windows line encoding, check in with Unix."

@joewitt
Copy link
Contributor

joewitt commented Mar 25, 2021

Closing due to inactivity.

@joewitt joewitt closed this Mar 25, 2021
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.

5 participants