Skip to content

Conversation

@merrimanr
Copy link

Contributor Comments

Found and fixed a couple bugs:

  • When testing with pycapa, we found that were cases where fields are missing. The UI code was not handling this and throwing errors.
  • Job submissions should display error messages from REST

Hope this helps. Feel free to change these as you see fit but these seem like issues we need to fix.

Pull Request Checklist

Thank you for submitting a contribution to Apache Metron.
Please refer to our Development Guidelines for the complete guide to follow for contributions.
Please refer also to our Build Verification Guidelines for complete smoke testing guides.

In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following:

For all changes:

  • Is there a JIRA ticket associated with this PR? If not one needs to be created at Metron Jira.
  • Does your PR title start with METRON-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)?

For code changes:

  • Have you included steps to reproduce the behavior or problem that is being changed or addressed?

  • Have you included steps or a guide to how the change may be verified and tested manually?

  • Have you ensured that the full suite of tests and checks have been executed in the root metron folder via:

    mvn -q clean integration-test install && dev-utilities/build-utils/verify_licenses.sh 
    
  • Have you written or updated unit tests and or integration 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?

  • Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?

For documentation related changes:

  • Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via site-book/target/site/index.html:

    cd site-book
    mvn site
    

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.
It is also recommended that travis-ci is set up for your personal repository such that your branches are built there before submitting a pull request.

this.statusSubscription.unsubscribe();
this.queryRunning = false;
this.errorMsg = `Response status: ${error.responseCode}. Something went wrong with your status request!`;
this.errorMsg = `Response status: ${error.message}. Something went wrong with your status request!`;
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change returns undefined for me testing on full-dev.

screen shot 2018-07-25 at 10 41 42 am

screen shot 2018-07-25 at 10 24 30 am

@sardell
Copy link
Owner

sardell commented Jul 25, 2018

+1

@sardell sardell merged commit 779cbed into sardell:METRON-1683 Jul 25, 2018
sardell pushed a commit that referenced this pull request Nov 26, 2018
sardell pushed a commit that referenced this pull request Nov 30, 2018
sardell pushed a commit that referenced this pull request Dec 21, 2018
sardell pushed a commit that referenced this pull request Jan 24, 2019
METRON-1906: Migrate tests from Tree View spec
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