Github user michalklempa commented on the issue:
https://github.com/apache/nifi/pull/675
@trixpan regarding any "defaultCharset" issues, I guess, that author was
thinking about what Java process sees as the default charset of the system it
runs on. I have seen it couple of times, that
Github user PuspenduBanerjee commented on the issue:
https://github.com/apache/nifi/pull/675
closing as commented to have already been resolved by:
- LSB compliant exit codes -> 99d3c39
- SSH restart hangs -> 88d1251
---
If your project is set up for it, you can reply to
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/675
@PuspenduBanerjee
The following commits seem to solve some this issues:
* LSB compliant exit codes -> 99d3c397481a98a5b3d2d4e44b84516fc0e3675e
* SSH restart hangs -> 88d125137e3bf3
Github user michalklempa commented on the issue:
https://github.com/apache/nifi/pull/675
This approach is too complicated. Why clutter with grepping output when we
can fix the RunNifi.java
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user PuspenduBanerjee commented on the issue:
https://github.com/apache/nifi/pull/675
taking care of a personal emergency at my native place in India and will
not be available till 17th Oct. Sorry for any inconvenience.
Thanks & Regards,
Puspendu Banerjee
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/675
@apiri have a look on
https://github.com/apache/nifi/pull/1092
and
https://github.com/apache/nifi/pull/1093
Which are essentially addressing a number of the issues di
Github user apiri commented on the issue:
https://github.com/apache/nifi/pull/675
It was my understanding there were to be some modifications based on the
last review and then we would commit that to capture the effort already done
with follow on work to get completely there.
---
If
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/675
@PuspenduBanerjee From what I understand from the trail, we can close PR?
Best regards
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user PuspenduBanerjee commented on the issue:
https://github.com/apache/nifi/pull/675
Agreed. That sounds like a plan!
---
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
enab
Github user apiri commented on the issue:
https://github.com/apache/nifi/pull/675
Hey @PuspenduBanerjee, in the interest of wrapping this up, maybe we can
just take your changes as presented with the adjustments mentioned above and
then create a new JIRA to explore addressing the need
Github user PuspenduBanerjee commented on the issue:
https://github.com/apache/nifi/pull/675
Thanks @apiri . Please let me know in case there is any gap.
Thanks & Regards,
Puspendu Banerjee
On Jul 24, 2016 6:07 PM, "Aldrin Piri" wrote:
Hey @PuspenduBanerj
Github user apiri commented on the issue:
https://github.com/apache/nifi/pull/675
Hey @PuspenduBanerjee, sorry for the delay. Will scope this out in the
next day or so.
---
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 PuspenduBanerjee commented on the issue:
https://github.com/apache/nifi/pull/675
@apiri @joewitt
`Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.007 sec
<<< FAILURE! - in
org.apache.nifi.controller.service.StandardControllerServiceProviderTest
o
13 matches
Mail list logo
