Well done everybody! Congrats
Jon
On Thu, Apr 20, 2017 at 8:55 PM Matt Foley wrote:
> Really exciting! Congrats to the founding team!
> --Matt
>
>
> On 4/20/17, 4:02 PM, "Houshang Livian" wrote:
>
> Congratulations Team. Great work!
>
>
>
>
>
GitHub user cestella opened a pull request:
https://github.com/apache/incubator-metron/pull/541
METRON-870: Add filtering by packet payload to the pcap query
## Contributor Comments
Currently we have the ability to filter packets in the pcap query tool by
header information
Really exciting! Congrats to the founding team!
--Matt
On 4/20/17, 4:02 PM, "Houshang Livian" wrote:
Congratulations Team. Great work!
On 4/20/17, 2:55 PM, "larry mccay" wrote:
>Wonderful news and well deserved!
Github user mmiklavc commented on the issue:
https://github.com/apache/incubator-metron/pull/538
fwiw, I ran a local test that seems to work fine. There must a be a subtle
difference somewhere in our build, but I haven't found it yet.
```
Maybe it is the relative parent path?
On April 20, 2017 at 20:05:31, mmiklavc (g...@git.apache.org) wrote:
Github user mmiklavc commented on the issue:
https://github.com/apache/incubator-metron/pull/538
Further, the reason that install worked is not because it needs the
artifacts in the
Github user mmiklavc commented on the issue:
https://github.com/apache/incubator-metron/pull/538
As I stated in https://issues.apache.org/jira/browse/METRON-856, this is a
fix that will work given the current configuration, but will quite possibly
break with future changes. Given
Github user mmiklavc commented on the issue:
https://github.com/apache/incubator-metron/pull/538
Further, the reason that install worked is not because it needs the
artifacts in the cache, per se. It's because of something in the way our
multi-module build is structured that isn't
Github user mmiklavc commented on the issue:
https://github.com/apache/incubator-metron/pull/538
The .m2 cache is an extension of the local target directories and you're
correct that upping the version to 0.4.0 caused the initial issue with missing
artifacts. Regardless of maven
Congratulations Team. Great work!
On 4/20/17, 2:55 PM, "larry mccay" wrote:
>Wonderful news and well deserved!
>This community has embraced and committed to the Apache way so quickly.
>
>
>On Thu, Apr 20, 2017 at 5:39 PM, Kyle Richardson
>wrote:
Github user mmiklavc commented on the issue:
https://github.com/apache/incubator-metron/pull/539
+1. Spun up full dev and verified index is still populating via `curl -XGET
"node1:9200/bro*/_count"`. Also spun up the site and grepped for
incubator|incubating in the source files.
Wonderful news and well deserved!
This community has embraced and committed to the Apache way so quickly.
On Thu, Apr 20, 2017 at 5:39 PM, Kyle Richardson
wrote:
> That's awesome! Congratulations everyone. Looking forward to the official
> announcement on Monday.
>
>
Nice! That's great news!
Sent from my Verizon, Samsung Galaxy smartphone
Original message
From: David Lyle
Date: 4/20/17 5:16 PM (GMT-05:00)
To: dev@metron.apache.org
Subject: Re: So we graduated...
Outstanding! Great work everyone. Building a TLP
For anyone paying attention to incubator-general, it will come as no
surprise that we graduated as of last night's board meeting. We have a
press released queued up and planned for monday along with a PR (METRON-687
at https://github.com/apache/incubator-metron/pull/539).
It escaped my notice
GitHub user cestella reopened a pull request:
https://github.com/apache/incubator-metron/pull/539
METRON-867: In the event that we graduate, remove incubating from the
website and documentation
## Contributor Comments
NOTE:
* This is not an indication of graduation status.
Github user cestella commented on the issue:
https://github.com/apache/incubator-metron/pull/539
Yeah, just waiting for the press release before we make this too public.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user JonZeolla commented on the issue:
https://github.com/apache/incubator-metron/pull/539
Am I missing something? I thought we were approved for graduation as of
last night.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
METRON-799 is in master. I know at least METRON-859 now has a conflict on
Kerberos-setup.md, so if anyone has anything similar, please make sure to
update your branch.
On Thu, Apr 20, 2017 at 9:25 AM, Otto Fowler
wrote:
> Maybe in the next release we should have theme
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-metron/pull/518
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/538
In fact, having given it additional thought, the dependency mechanism is a
way of saying "hey Maven, make sure you pull those artifacts into our .m2
cache" which isn't really the
Github user justinleet commented on the issue:
https://github.com/apache/incubator-metron/pull/535
I was able to spin this up in full dev without issues. There might be some
conflicts with METRON-799, but I would expect that to primarily be on the
README.
+1 on what's here
Github user justinleet commented on the issue:
https://github.com/apache/incubator-metron/pull/538
@dlyle65535 I'm all for that. I'll update the ticket and the PR in a
little bit
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
If it didn't resolve the issue, then yeah, we might as well just undo it,
and I can update the PR with that instead.
Justin
On Thu, Apr 20, 2017 at 2:11 PM, David Lyle wrote:
> Being as the dependency additon didn't actually resolve the out-of-order
> build issue, would
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/540
You shouldn't have to build Metron prior to running 'vagrant up', the
Ansible provisioner does that. Following these instructions, you'll actually
build Metron twice for each build.
Maybe it is a container thing? I don’t think my PR for extensions has the
problem,
or has had it in my travis - and it is a vm in travis.
On April 20, 2017 at 09:06:21, Casey Stella (ceste...@gmail.com) wrote:
oh man, yeah, it's pissing me off too. I'm still looking at ways to get
around
Hi Matt,
+1 on the fixes you selected for inclusion. Check with Justin to be sure,
but I believe METRON-799 is ready for review, so pending that, it's ready
to go.
-D...
On Thu, Apr 20, 2017 at 2:13 AM, Matt Foley wrote:
> Hi all,
> I’ve put together RC1 for the 0.4.0
Github user iraghumitra commented on the issue:
https://github.com/apache/incubator-metron/pull/526
I removed usage of WebDriver.manage().window().setSize. It is a best
practice to maximize the window before running the test cases probably we need
to hold back on this practice till
Hi all,
I’ve put together RC1 for the 0.4.0 release of Metron, along with its
book-site. It is available for your review at
https://dist.apache.org/repos/dist/dev/incubator/metron/0.4.0-RC1-incubating/
I’m not putting it to VOTE yet, because I think some additional fixes are
27 matches
Mail list logo