[
https://issues.apache.org/jira/browse/METRON-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16685094#comment-16685094
]
ASF GitHub Bot commented on METRON-1740:
Github user nickwallen commented on the issue:
Jon Zeolla created METRON-1868:
--
Summary: metron-committer-common hard codes metron repo
Key: METRON-1868
URL: https://issues.apache.org/jira/browse/METRON-1868
Project: Metron
Issue Type: Task
[
https://issues.apache.org/jira/browse/METRON-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16685201#comment-16685201
]
ASF GitHub Bot commented on METRON-1867:
GitHub user nickwallen opened a pull request:
Github user nickwallen commented on the issue:
https://github.com/apache/metron-bro-plugin-kafka/pull/13
+1
---
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/1171
+1 Thank you very much for the hard work @liuy-tnz!
---
Nick Allen created METRON-1867:
--
Summary: Remove `/api/v1/update/replace` endpoint
Key: METRON-1867
URL: https://issues.apache.org/jira/browse/METRON-1867
Project: Metron
Issue Type: Bug
GitHub user nickwallen opened a pull request:
https://github.com/apache/metron/pull/1259
METRON-1867 Remove `/api/v1/update/replace` endpoint
The `/api/v1/update/replace` endpoint is no longer used. This is dead code
and should be removed.
This is dependent on the
[
https://issues.apache.org/jira/browse/METRON-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jon Zeolla updated METRON-1868:
---
Description:
It appears that metron repo is hard coded, but needs to be more flexible based
on the
[
https://issues.apache.org/jira/browse/METRON-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16685098#comment-16685098
]
ASF GitHub Bot commented on METRON-1740:
Github user asfgit closed the pull request at:
Github user asfgit closed the pull request at:
https://github.com/apache/metron/pull/1171
---
Nick Allen created METRON-1869:
--
Summary: Unable to Escalate Meta Alert
Key: METRON-1869
URL: https://issues.apache.org/jira/browse/METRON-1869
Project: Metron
Issue Type: Bug
[
https://issues.apache.org/jira/browse/METRON-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16685337#comment-16685337
]
ASF GitHub Bot commented on METRON-1868:
GitHub user JonZeolla opened a pull request:
GitHub user JonZeolla opened a pull request:
https://github.com/apache/metron/pull/1260
METRON-1868: metron-committer-common incorrectly checking CHOSEN_REPO
## Contributor Comments
I found a minor bug when trying to use `prepare-commit` against the
metron-bro-plugin-kafka
[
https://issues.apache.org/jira/browse/METRON-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jon Zeolla updated METRON-1868:
---
Description:
It appears that metron repo is hard coded, but needs to be more flexible based
on the
[
https://issues.apache.org/jira/browse/METRON-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jon Zeolla updated METRON-1868:
---
Description:
It appears that REPO_NAME is not being correctly checked.
GitHub user ottobackwards opened a pull request:
https://github.com/apache/metron/pull/1261
METRON-1860 [WIP] new developer option for ansible in docker to deploy to
vagrant
The goal of this PR is to provide a new "full_dev" option for new and old
users that does not require as
[
https://issues.apache.org/jira/browse/METRON-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16685529#comment-16685529
]
ASF GitHub Bot commented on METRON-1860:
GitHub user ottobackwards opened a pull request:
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/1261
Valiant effort @ottobackwards . I am just wondering how much easier this
really makes it?
Have you thought about just publishing a Metron Demo image to Vagrant
Cloud? Does that
[
https://issues.apache.org/jira/browse/METRON-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16685584#comment-16685584
]
ASF GitHub Bot commented on METRON-1860:
Github user nickwallen commented on the issue:
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/1249
I'm on board with the most recent proposal, just one small nit. What's the
significance of using the different, yet still extremely similar words "parser"
and "parsing?" I'd almost be more
[
https://issues.apache.org/jira/browse/METRON-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686069#comment-16686069
]
ASF GitHub Bot commented on METRON-1815:
Github user mmiklavc commented on the issue:
[
https://issues.apache.org/jira/browse/METRON-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Allen updated METRON-1869:
---
Comment: was deleted
(was: [~anandsubbu] We should probably add a check for this in the NATs. Its
[
https://issues.apache.org/jira/browse/METRON-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16685732#comment-16685732
]
Nick Allen commented on METRON-1869:
An example of the stack trace from master.
{code:java}
18/11/13
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/1261
@ottobackwards thanks for the submission. Per recent community comments, it
sounds like we could use some improvements to how our build/deploy dep versions
interact with other tooling that may
[
https://issues.apache.org/jira/browse/METRON-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16685745#comment-16685745
]
ASF GitHub Bot commented on METRON-1860:
Github user mmiklavc commented on the issue:
[
https://issues.apache.org/jira/browse/METRON-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Allen updated METRON-1869:
---
Description:
Steps to Replicate:
# Create a meta-alert.
# Escalate the meta-alert.
# Trigger a
26 matches
Mail list logo
