Re: [compress][all]Fwd: Build failed in Jenkins: Commons-Compress PullRequest Builder #56

On 2017-06-19, Gary Gregory wrote: > Is it just me or have there been Jenkins failures left and right for the > last week or so? That's the Jenkins job I've created for github pull requests and it fails whenever there are merge conflicts, for example. Right now it looks as if the workspace was

Re: [compress][all]Fwd: Build failed in Jenkins: Commons-Compress PullRequest Builder #56

Check with Infra weird errors are happening. Regards, Dave Sent from my iPhone > On Jun 19, 2017, at 8:53 PM, Stefan Bodewig wrote: > >> On 2017-06-19, Gary Gregory wrote: >> >> Is it just me or have there been Jenkins failures left and right for the >> last week or so? >

Help with task: Implement Ziggurat algorithm

I would like to help out with the task listed at https://helpwanted.apache.org/task.html?9d71a269

Re: [all] dev@ traffic

On 2017-06-19, Emmanuel Bourg wrote: > Le 19/06/2017 à 12:32, Stefan Bodewig a écrit : >> IMHO neither should go to dev@ and using notifications@ seems more >> logical to me. I'm going to change this for Compress and would likt to >> ask other components to check their settings as well so we can

Re: [all] dev@ traffic

Le 19/06/2017 à 15:41, Stefan Bodewig a écrit : > those two should go to the same list even if its "issues"? Yes, sorry for the ambiguity. Emmanuel Bourg - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For

Re: [all] dev@ traffic

On 19 June 2017 at 14:19, Emmanuel Bourg wrote: > Le 19/06/2017 à 12:32, Stefan Bodewig a écrit : > >> IMHO neither should go to dev@ and using notifications@ seems more >> logical to me. I'm going to change this for Compress and would likt to >> ask other components to check

[GitHub] commons-cli issue #14: Added BugCLI260 JUnit Test

Github user jlm429 commented on the issue: https://github.com/apache/commons-cli/pull/14 fwiw - this is what I had to fix ... probably better off not digging around in the default parser though if not needed :0 private void handleShortAndLongOption(String token) throws

Re: [all] dev@ traffic

Le 19/06/2017 à 12:32, Stefan Bodewig a écrit : > IMHO neither should go to dev@ and using notifications@ seems more > logical to me. I'm going to change this for Compress and would likt to > ask other components to check their settings as well so we can raise the > signal ratio for dev@ again.

CharSequence vs. String (was Re: [GitHub] commons-text pull request #46: TEXT-85:Added CaseUtils class with camel case...)

On Jun 12, 2017 10:47 AM, "arunvinudss" wrote: Github user arunvinudss commented on a diff in the pull request: I am a bit biased towards using String instead of CharSequence . Yes CharSequence allows us to pass String Buffers and builders and other types as input

Re: [all] dev@ traffic

On 2017-06-19, Simon Spero wrote: > (this was prompted by me interrupting a quasi-appropriate JIRA > meta-discussion about JIRA workflow & permissions (on an issue I had opened > because I encountered it whilst working another issue, and had fixed but > not PRed, which Stefan then also fixed) to

Code formatting for COMMONS (was Re: [GitHub] commons-text issue #52: Test: Improved testcase coverage for StrBuilder)

Is there a set of commons code formatting conventions? More particularly, is there a machine readable file of same? I use intellij, so native, checkstyle, or Eclipse is fine. I've been having problems where I am doing the pre-commit diff check, and find that I have made unintentional changes to

[GitHub] commons-cli issue #14: Added BugCLI260 JUnit Test

Github user jlm429 commented on the issue: https://github.com/apache/commons-cli/pull/14 fwiw - this is what I had to fix ... probably better off not digging around in the default parser though if not needed :0 private void handleShortAndLongOption(String token) throws

Re: [all] dev@ traffic

(this was prompted by me interrupting a quasi-appropriate JIRA meta-discussion about JIRA workflow & permissions (on an issue I had opened because I encountered it whilst working another issue, and had fixed but not PRed, which Stefan then also fixed) to further apologize to Stefan for not

Re: [all] dev@ traffic

On Jun 19, 2017 9:56 AM, "Stefan Bodewig" wrote: On 2017-06-19, Simon Spero wrote: with all parenteses properly nested, wow ;-) No need to apologize, really. (apply #'append '((not) (a problem)))

Help with task: Implement Ziggurat algorithm

I would like to help out with the task listed at https://helpwanted.apache.org/task.html?9d71a269

Re: [ANNOUNCE] Apache Commons FileUpload 1.3.3 released.

Hi, can you trigger an update of the pattern on https://nvd.nist.gov/vuln/detail/CVE-2016-131 somehow? Currently OWASP dependency check still considers 1.3.3 as insecure. Cheers Dennis - To unsubscribe, e-mail:

[GitHub] commons-compress issue #38: Testing hudson/jenkins (added contributor line t...

Github user coveralls commented on the issue: https://github.com/apache/commons-compress/pull/38 [](https://:/builds/12037439) Coverage decreased (-0.005%) to 84.723% when pulling

[GitHub] commons-compress issue #38: Testing hudson/jenkins (added contributor line t...

Github user coveralls commented on the issue: https://github.com/apache/commons-compress/pull/38 [](https://:/builds/12037517) Coverage remained the same at 84.728% when pulling

[GitHub] commons-compress issue #38: Testing hudson/jenkins (added contributor line t...

Github user coveralls commented on the issue: https://github.com/apache/commons-compress/pull/38 [](https://:/builds/12037759) Coverage remained the same at 84.728% when pulling

[GitHub] commons-compress issue #38: Testing hudson/jenkins (added contributor line t...

Github user coveralls commented on the issue: https://github.com/apache/commons-compress/pull/38 [](https://:/builds/12037816) Coverage increased (+0.02%) to 84.747% when pulling

[GitHub] commons-compress issue #38: Testing hudson/jenkins (added contributor line t...

Github user coveralls commented on the issue: https://github.com/apache/commons-compress/pull/38 [](https://:/builds/12038097) Coverage increased (+0.02%) to 84.747% when pulling

[GitHub] commons-compress issue #38: Testing hudson/jenkins (added contributor line t...

Github user coveralls commented on the issue: https://github.com/apache/commons-compress/pull/38 [](https://:/builds/12038184) Coverage increased (+0.02%) to 84.744% when pulling

[GitHub] commons-compress issue #38: Testing hudson/jenkins (added contributor line t...

Github user coveralls commented on the issue: https://github.com/apache/commons-compress/pull/38 [](https://:/builds/12037681) Coverage remained the same at 84.728% when pulling

[GitHub] commons-compress issue #38: Testing hudson/jenkins (added contributor line t...

Github user coveralls commented on the issue: https://github.com/apache/commons-compress/pull/38 [](https://:/builds/12037681) Coverage remained the same at 84.728% when pulling

[GitHub] commons-compress issue #38: Testing hudson/jenkins (added contributor line t...

Github user coveralls commented on the issue: https://github.com/apache/commons-compress/pull/38 [](https://:/builds/12037873) Coverage increased (+0.02%) to 84.747% when pulling

[GitHub] commons-compress issue #38: Testing hudson/jenkins (added contributor line t...

Github user coveralls commented on the issue: https://github.com/apache/commons-compress/pull/38 [](https://:/builds/12038134) Coverage decreased (-0.005%) to 84.723% when pulling

[GitHub] commons-compress issue #38: Testing hudson/jenkins (added contributor line t...

Github user coveralls commented on the issue: https://github.com/apache/commons-compress/pull/38 [](https://:/builds/12036300) Coverage increased (+0.02%) to 84.744% when pulling

[GitHub] commons-compress issue #38: Testing hudson/jenkins (added contributor line t...

Github user coveralls commented on the issue: https://github.com/apache/commons-compress/pull/38 [](https://:/builds/12036561) Coverage remained the same at 84.728% when pulling

[GitHub] commons-compress issue #38: Testing hudson/jenkins (added contributor line t...

Github user coveralls commented on the issue: https://github.com/apache/commons-compress/pull/38 [](https://:/builds/12036920) Coverage decreased (-0.008%) to 84.72% when pulling

[GitHub] commons-compress issue #38: Testing hudson/jenkins (added contributor line t...

Github user coveralls commented on the issue: https://github.com/apache/commons-compress/pull/38 [](https://:/builds/12036920) Coverage decreased (-0.005%) to 84.723% when pulling

[GitHub] commons-compress issue #38: Testing hudson/jenkins (added contributor line t...

Github user coveralls commented on the issue: https://github.com/apache/commons-compress/pull/38 [](https://:/builds/12036920) Coverage decreased (-0.008%) to 84.72% when pulling

[GitHub] commons-compress pull request #38: Testing hudson/jenkins (added contributor...

GitHub user sesuncedu opened a pull request: https://github.com/apache/commons-compress/pull/38 Testing hudson/jenkins (added contributor line to pom.xml so that there would be a change) They've been failing PRs on the checkout of master. Lets try this. You can merge this pull

[GitHub] commons-compress issue #38: Testing hudson/jenkins (added contributor line t...

Github user coveralls commented on the issue: https://github.com/apache/commons-compress/pull/38 [](https://:/builds/12036386) Coverage increased (+0.2%) to 84.885% when pulling

[compress][all]Fwd: Build failed in Jenkins: Commons-Compress PullRequest Builder #56

Is it just me or have there been Jenkins failures left and right for the last week or so? Gary -- Forwarded message -- From: Apache Jenkins Server Date: Mon, Jun 19, 2017 at 1:47 PM Subject: Build failed in Jenkins: Commons-Compress PullRequest Builder

Build failed in Jenkins: Commons-Compress PullRequest Builder #30

See -- GitHub pull request #37 to apache/commons-compress [EnvInject] - Loading node environment variables. Building remotely on H14 (ubuntu xenial) in workspace

Re: Wondering VFS will support Read/Write on Google Cloud Storage?

I think the gcsfuse mounted directory cannot even be identified by Java, I'll report this issue to `gcsfuse` community. 2017-06-19 15:39 GMT+08:00 楊閔富 : > Hi > > I've tried and the log is as follows: > > ``` > $ ls -al /tmp/gcs > total 0 > drwxrwxrwx 1 root root 0 Jun 19 07:37

[GitHub] commons-compress issue #37: COMPRESS-410 - cherry picked to fix merging issu...

Github user coveralls commented on the issue: https://github.com/apache/commons-compress/pull/37 [](https://:/builds/12027861) Coverage increased (+0.04%) to 84.77% when pulling

Re: Wondering VFS will support Read/Write on Google Cloud Storage?

Hi I've tried and the log is as follows: ``` $ ls -al /tmp/gcs total 0 drwxrwxrwx 1 root root 0 Jun 19 07:37 hive-warehouse drwxrwxrwx 1 root root 0 Jun 19 07:37 softwares drwxrwxrwx 1 root root 0 Jun 19 07:37 zeppelin-notebooks $ sudo java -cp

[all] dev@ traffic

Hi all apart from dev@ and user@ we've got three lists that have been created for specific notifications that people may be interested in or not: issues, commits and notifications. My MUA is configured to merge those three with dev so I didn't really notice we are getting more messages (and for

[GitHub] commons-text issue #52: Test: Improved testcase coverage for StrBuilder

Github user chtompki commented on the issue: https://github.com/apache/commons-text/pull/52 Agreed with Pascal here, just for semantics on commit history. --- 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] commons-text pull request #46: TEXT-85:Added CaseUtils class with camel case...

Github user asfgit closed the pull request at: https://github.com/apache/commons-text/pull/46 --- 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

[ALL] commits@ notifications@

I assume commits@ is intended for SVN and Git commit messages. [Except for /websites/ commits which go to notifications@] It looks like notifications@ is also being used for commons-numbers PRs Why is that the only component doing so? Should other PRs also go to notifications? Or should numbers

Re: [ALL] commits@ notifications@

Sorry, did not notice Stefan's earlier email. Ignore this thread... On 19 June 2017 at 13:51, sebb wrote: > I assume commits@ is intended for SVN and Git commit messages. > [Except for /websites/ commits which go to notifications@] > > It looks like notifications@ is also