Re: [DISCUSS] Next Release - Life After 0.7.1

ions of upgrading that be able to review it, or give some > > > advice on what we should be looking for in the review? > > > > > > On Thu, Dec 5, 2019 at 12:06 PM Shane Ardell > > > > wrote: > > > > > >> Speaking on the UI-related PRs that Justin menti

Re: [DISCUSS] Feature Branch wiki page

I would gladly help with this in whatever way I can. As someone who started contributing not that long ago, this proposed documentation would've saved me a lot of headaches and pain. We should have clear guidelines and expectations for how this should work, just as we do with smaller

[DISCUSS] Metron Alerts UI - possibly deprecate query builder and meta alerts

Hello devs and users, A few of us working on Metron Alerts UI are seeking some user feedback on two existing features. Specifically, we are wondering: * How often do you use the query builder feature of the alerts search bar, especially since the implementation of the manual search query option?

Re: PR Review Request

I reviewed this PR and left a +1. Great work, Tibor! Because of the size of the PR (ie. near the threshold of being big enough to require a feature branch), I'm going to leave it open until tomorrow for others to chime in if they want. Given your detailed description and great work, I'm sure

Re: [DISCUSS] Parser Aggregation in Management UI

ould like to > suggest > > > two > > > > other option to help review PR#1360. > > > > > > > > #1 We could extend that PR with our own author comments in Github. > That > > > > would help following which code part belongs to where and why it was

Re: [DISCUSS] Parser Aggregation in Management UI

gt; What are you using NgRx for in the submitted work that goes beyond the > aggregation feature? > > > > On Thu, May 2, 2019 at 12:22 PM Shane Ardell > wrote: > > > Hello everyone, > > > > In response to discussions in the 0.7.1 release thread, I wanted to > start a &

Re: [DISCUSS] Metron Release - 0.7.1 next steps

Here's a link to the ngrx discussion thread from a few months back: https://lists.apache.org/thread.html/06a59ea42e8d9a9dea5f90aab4011e44434555f8b7f3cf21297c7c87@%3Cdev.metron.apache.org%3E On Thu, May 2, 2019 at 1:17 PM Otto Fowler wrote: > If you can find a link in the archives for that

[DISCUSS] Reverting METRON-2023 (PR #1364)

Hello everyone, I'm sending out this email to notify the community of my intention to revert the commit for METRON-2023 (PR #1364 ). This commit introduced a bug stemming from yauzl, the tool that Cypress uses to unzip itself. This bug causes an error

Re: [DISCUSS] Central Navigation for Alerts and Management UI

Good point, Otto. Just posted there now. On Mon, Mar 11, 2019 at 12:11 PM Otto Fowler wrote: > Maybe you should post to the users@ list > > > On March 11, 2019 at 06:25:48, Shane Ardell (shane.m.ard...@gmail.com) > wrote: > > Thank you both for explaining the original des

Re: [DISCUSS] Central Navigation for Alerts and Management UI

ted > architecture. I don't have a strong opinion one way or the other, but > I'd > be interested to hear whether others in the community find this wall > useful, or if we should come back to a single pain of glass. > > Mike > > On Tue, Mar 5, 2019 at

[DISCUSS] Central Navigation for Alerts and Management UI

Hello everyone, I recently started experimenting with implementing a navigation bar in both the Alerts and Management UI. It would allow us to navigate between the two UIs through links instead of manually entering a url or opening separate tabs from Ambari. I'm just wondering what everyone's

Re: Unzipping Cypress

ainer. > Thanks! > > > On November 28, 2018 at 10:29:25, Shane Ardell (shane.m.ard...@gmail.com) > wrote: > > For me, it's at ~/Library/Caches/Cypress, but the path depends on your OS: > > https://docs.cypress.io/guides/getting-started/installing-cypress.html#Binary-cache > > On W

Re: Unzipping Cypress

For me, it's at ~/Library/Caches/Cypress, but the path depends on your OS: https://docs.cypress.io/guides/getting-started/installing-cypress.html#Binary-cache On Wed, Nov 28, 2018 at 4:19 PM Otto Fowler wrote: > Where is the cache path? > > > On November 28, 2018 at 09:34:18,

Re: Unzipping Cypress

Fowler wrote: > I’m sorry for the confusion, but I see this locally. I’m not looking at > travis. > I have been doing a lot of full dev deployments. > > > > On November 27, 2018 at 11:40:42, Shane Ardell (shane.m.ard...@gmail.com) > wrote: > > Otto, > > Do you

Re: Unzipping Cypress

Otto, Do you have a Travis log you can share that shows Cypress downloaded vs. using a cached version? It looks like my latest merge to master uses a cached version: https://travis-ci.org/apache/metron/jobs/458440883#L7292. Thanks in advance. On Mon, Nov 26, 2018 at 6:14 PM Shane Ardell wrote

Re: [DISCUSS] Add ngrx to handle state management in Angular

> case > > in the UI currently and explain for us how it currently works (or > doesn't, > > ha) versus how it would be modified and improved with using NgRx? > > > > Thanks, > > Mike > > > > On Fri, Nov 23, 2018 at 7:44 AM Shane Ardell > > wr

Re: Unzipping Cypress

It seems we can pretty easily configure the .travis.yml config file to cache our npm modules: https://docs.cypress.io/guides/guides/continuous-integration.html#Caching-the-Cypress-binary It also looks like we are already trying to cache our npm modules in the Travis config, but, obviously, it's

Re: [DISCUSS] Add ngrx to handle state management in Angular

, 2018 at 07:21:43, Shane Ardell (shane.m.ard...@gmail.com) > wrote: > > As both the Management and Alerts UI grow in size, managing application > state continues to become more and more complex. To help us deal with > managing all of this state and ensuring our application derive

[DISCUSS] Add ngrx to handle state management in Angular

As both the Management and Alerts UI grow in size, managing application state continues to become more and more complex. To help us deal with managing all of this state and ensuring our application derives state from a single source of truth, I suggest we start using NgRx, a state management

Re: [ANNOUNCE] Shane Ardell is a committer

an...@hortonworks.com> wrote: > > > Many congratulations, Shane! > > > > Cheers, > > Anand > > > > On 11/19/18, 8:36 PM, "James Sirota" wrote: > > > > > > The Project Management Committee (PMC) for Apache Metron has invited >

Re: [DISCUSS] Switching to a better alternative of Pikaday.js

We are definitely on the same page. On Mon, Oct 15, 2018 at 2:06 PM Tibor Meller wrote: > @Shane It seems like we're agreed on this. :D > > On Mon, Oct 15, 2018 at 1:18 PM Tibor Meller > wrote: > > > Hi Guys, > > > > I think we could consider moving to ng bootstrap. It solves most of our > >

Re: [DISCUSS] Switching to a better alternative of Pikaday.js

> > I'm not satisfied with the alternative individual solutions out there on > npm. I'd rather pick a component library like the angular port of Bootstrap > or the angular material library > . Both of them have a date picker

Re: [DISCUSS] Add e2e step to PR checklist

get one run to fully pass. See the attached output of those runs. > > > > > > > > On Wed, Oct 3, 2018 at 7:36 AM Shane Ardell > > wrote: > > > >> I ran them locally a handful of times just now, and on average they took > >> approximately 15 minut

Invite to Slack Channel

Hello everyone, Is it possible for someone to send me an invite to the Metron Slack channel? Regards, Shane

Re: [DISCUSS] Add e2e step to PR checklist

posure to running the e2e tests in > their current form. It might still be worth it in the short term. > > On Tue, Oct 2, 2018 at 10:20 AM Shane Ardell > wrote: > > > The protractor-flake package should catch and re-run false failures, so > > people shouldn't get failing tests w

Re: [DISCUSS] Add e2e step to PR checklist

t we can add to the documentation? > > On Tue, Oct 2, 2018 at 11:58 AM Shane Ardell > wrote: > > > I also would like to eventually have these tests automated. There are a > > couple hurdles to setting up our e2e tests to run with our build. I think > > the biggest hurdle

Re: [DISCUSS] Add e2e step to PR checklist

us to move forward the > > efforts of running these tests as part of the CI build. > > > > What is the current gap there? > > > > Casey > > > > On Mon, Oct 1, 2018 at 7:41 AM Shane Ardell > > wrote: > > > >> Hello everyone, > >>

[DISCUSS] Add e2e step to PR checklist

Hello everyone, In another discussion thread from July, I briefly mentioned the idea of adding a step to the pull request checklist asking contributors to run the UI end-to-end tests. Since we aren't running e2e tests as part of the CI build, it's easy for contributors to unintentionally break

Re: [DISCUSS] Migrate from Protractor to Cypress

relatively easy to migrate across cypress and protractor I > see no major risks here if we decide to stick with Protractor for some > reason. > > What do you think? > > Thanks for your feedback, > Tibor > > On Wed, Sep 19, 2018 at 1:49 PM Shane Ardell > wrote: > > &g

Re: [DISCUSS] Migrate from Protractor to Cypress

While the Cypress team suggests taking advantage of stubs where you can, especially during development, we would definitely be able to test real endpoints [1]. It can be used exactly like how Protractor is used, but with the many benefits and features it provides [2]. Cypress also offers tools for

[DISCUSS] Migrate from Protractor to Cypress

Hello everyone, Currently, we use Protractor to run our UI "end-to-end" tests. However, there are a handful of major advantages we can gain from switching to Cypress: https://www.cypress.io/features/. - As with most Selenium-based e2e testing frameworks, Protractor suffers from test

Re: package.lock changes during build?

NPM's use of lock files has been quite controversial. I won't go into it too deep here as there are endless posts criticizing and justifying their approach, but `npm install` will install all modules listed as dependencies in package.json and update package-lock.json accordingly instead of

Re: Metron-alerts E2E testing

For now, I think the easiest action for us to take here is to add a step to the pull request checklist asking contributors to run the e2e tests. In the future, we may want to look into moving to Cypress for e2e testing. One of the many advantages of Cypress is that it can be run by Travis