Github user jasper-k commented on the issue:
https://github.com/apache/metron/pull/628
@ottobackwards regarding the merge conflict, something I need to do?
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/metron/pull/627
---
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 feature is
Hi all,
I was wondering if there is a test framework we can use for Stellar
post-parsing and enrichment use cases. It is very time-consuming to verify
use cases end-to-end. Therefore, I am looking for a way of mocking use
cases step by step to speed up our development.
Regards,
Ali
You should probably use the Stellar REPL (../metron/bin/stellar -z $ZK) which
gives you a kind of Stellar playground.
Simon
> On 4 Jul 2017, at 15:02, Ali Nazemian wrote:
>
> Hi all,
>
> I was wondering if there is a test framework we can use for Stellar
> post-parsing
Hi Simon,
Yeah, it does, but we are looking for a way to mock a specific message and
check some post-parse/enrichments stuff. Is that achievable via Stellar
shell? Right now we are checking that either through end-to-end testing, or
changing flux files to check them section by section.
GitHub user mattf-horton opened a pull request:
https://github.com/apache/metron/pull/629
METRON-1012 Update Metron public web site for 0.4.0 release
## Contributor Comments
Although 52 files were nominally involved, I really only changed two things:
1. replaced the 0.3.1
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/629
+1. I ran up the site and checked it over. Good to see incubating
finishing working its way out of everything.
Minor note, the instructions mention going to incubator-metron/site.
Github user JonZeolla commented on the issue:
https://github.com/apache/metron/pull/629
Are we still planning to keep the old versions of the book on the website,
like under /0.3.1/ instead of /current-book/ ? We previously discussed this