Re: Migrating ZooKeeper to GitBox

[Andor Molnár]

Cool, that was quick. Thanks for the help Patrick.

Would you please confirm that the new URL is
'https://gitbox.apache.org/repos/asf/zookeeper.git' ?

I mean it uses https:// protocol, not git://?


Andor



On 12/15/18 00:30, Patrick Hunt wrote:
> FYI INFRA has updated the repo location.
>
> You'll want to use git remote set-url to update your remote url.
>
> I'll update the Jenkins jobs now.
>
> Patrick
>
> On Fri, Dec 14, 2018 at 12:17 PM Andor Molnár  wrote:
>
>> Here you are:
>>
>>
>> https://issues.apache.org/jira/browse/INFRA-17446
>>
>>
>> Andor
>>
>>
>>
>>
>> On 12/14/18 07:11, Fangmin Lv wrote:
>>> +1 for proactive move. Is there a Jira to track this?
>>>
>>> Best,
>>> Fangmin
>>>
>>> On Thu, Dec 13, 2018 at 6:41 PM Norbert Kalmar
>> 
>>> wrote:
>>>
 +1 (non-binding) for early voluntarily move.
 I will update the pom files, there is a PR on the POM's anyway, and they
 are WIP.

 Regards,
 Norbert

 On Thu, Dec 13, 2018 at 5:34 AM Michael Han  wrote:

> +1 on voluntarily request to move.
>
> On Wed, Dec 12, 2018 at 11:36 AM Patrick Hunt 
>> wrote:
>> Probably minor, but note there are some website pages that will also
 need
>> to be updated:
>> e.g. https://zookeeper.apache.org/git.html
>>
>> Patrick
>>
>> On Wed, Dec 12, 2018 at 10:58 AM Enrico Olivelli > wrote:
>>
>>> +1  for moving to github now
>>>
>>> Enrico
>>>
>>> Il mer 12 dic 2018, 19:49 Tamas Penzes 
> ha
>>> scritto:
>>>
 Hi Patrick,

 Yes we have to upgrade the main pom.xml, just as the website and
 the
 documentation.
 Do we have to change git urls in old documentations as well?
 (People
>>> might
 read them.)

 Thanks, Tamaas

 On Wed, Dec 12, 2018, 18:31 Patrick Hunt >>>
> Proactive sounds good to me. Can we schedule something outside
 the
> holidays?
>
> Aside from Jenkins is there anything else we need to worry about?
>> e.g.
>>> I
> see a reference in pom.xml
>
> pom.xml
> 63:scm:git:
> https://git-wip-us.apache.org/repos/asf/zookeeper.git
> 
> 64:
> https://git-wip-us.apache.org/repos/asf?p=zookeeper.git
 
> What's the impact wrt github.com and the Apache org? Will this
>> enable
 use
> to become admins at the same time? (greater control over the
>>> issues/prs,
> etc...)
>
> Patrick
>
> On Wed, Dec 12, 2018 at 9:07 AM Andor Molnar 
>> wrote:
>> Hi dev team,
>>
>> Have you seen this?
>>
>>
>> https://blogs.apache.org/infra/entry/relocation-of-apache-git-repositories
>> <
>>
>> https://blogs.apache.org/infra/entry/relocation-of-apache-git-repositories
>> I think we should volunteer for a coordinated migration of
>> ZooKeeper,
>> although the project is not too big, so the impact of a forced
>>> process
>> probably wouldn’t be so much.
>>
>> There’re some benefits though:
>> - We could move to GitBox earlier rather than later, so we
 could
>> take
>> advantage of GitHub write access for example,
>> - Migration needs a write-lock in place during the process, so
 we
>> can
>> avoid some unfortunate surprises,
>> - git-wip-us.apache.org  will
> have
 CNAMEs
>> to gitbox, so it’ll be operational for some time, but the
> read-only
>> git.apache.org  will go away (not sure
>> about
 the
>> timing though), that we use in some of our Jenkins builds. It
> would
>>> be
>> better to migrate Jenkins configs in a coordinated fashion
 rather
>>> than
> when
>> the house is burning.
>>
>> There’re a bunch of unkowns in each project, hence Infra guys
>>> recommend
>> the coordinated way, but we need an agreement in the community,
> so
 please
>> share your thoughts.
>>
>> Regards,
>> Andor
>>
>>
>>
>>> --
>>>
>>>
>>> -- Enrico Olivelli
>>>

[jira] [Commented] (ZOOKEEPER-3216) Make init/sync limit tunable via JMX

[Jie Huang (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16722018#comment-16722018
 ] 

Jie Huang commented on ZOOKEEPER-3216:
--

This will allow us to fix syncing issues when they happen without restart

> Make init/sync limit tunable via JMX
> 
>
> Key: ZOOKEEPER-3216
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3216
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: jmx
>Reporter: Jie Huang
>Priority: Minor
>
> Add beans for initLimit and syncLimit so they can be adjusted through JMX



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ZOOKEEPER-3216) Make init/sync limit tunable via JMX

[Fangmin Lv (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721958#comment-16721958
 ] 

Fangmin Lv commented on ZOOKEEPER-3216:
---

[~jiehuang] Please also add some comments why we want to make this a JMX bean, 
I think there is comment there in the original diff.

> Make init/sync limit tunable via JMX
> 
>
> Key: ZOOKEEPER-3216
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3216
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: jmx
>Reporter: Jie Huang
>Priority: Minor
>
> Add beans for initLimit and syncLimit so they can be adjusted through JMX



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (ZOOKEEPER-3216) Make init/sync limit tunable via JMX

[Fangmin Lv (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Fangmin Lv reassigned ZOOKEEPER-3216:
-

Assignee: (was: Fangmin Lv)

> Make init/sync limit tunable via JMX
> 
>
> Key: ZOOKEEPER-3216
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3216
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: jmx
>Reporter: Jie Huang
>Priority: Minor
>
> Add beans for initLimit and syncLimit so they can be adjusted through JMX



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (ZOOKEEPER-3216) Make init/sync limit tunable via JMX

[Fangmin Lv (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Fangmin Lv reassigned ZOOKEEPER-3216:
-

Assignee: Fangmin Lv

> Make init/sync limit tunable via JMX
> 
>
> Key: ZOOKEEPER-3216
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3216
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: jmx
>Reporter: Jie Huang
>Assignee: Fangmin Lv
>Priority: Minor
>
> Add beans for initLimit and syncLimit so they can be adjusted through JMX



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

owasp job just started flagging slf4j

[Patrick Hunt]

https://builds.apache.org/view/S-Z/view/ZooKeeper/job/ZooKeeper-trunk-owasp/204/artifact/build/test/owasp/dependency-check-vulnerability.html

https://nvd.nist.gov/vuln/detail/CVE-2018-8088

We don't use EventData but should consider upgrading.

https://issues.apache.org/jira/browse/ZOOKEEPER-3217

Patrick

[jira] [Commented] (ZOOKEEPER-3217) owasp job flagging slf4j on trunk

[Patrick Hunt (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721907#comment-16721907
 ] 

Patrick Hunt commented on ZOOKEEPER-3217:
-

afaict there is no stable release of slf4j which includes this fix. There is a 
beta available though from the looks of it.

> owasp job flagging slf4j on trunk
> -
>
> Key: ZOOKEEPER-3217
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3217
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Patrick Hunt
>Priority: Major
> Fix For: 3.6.0, 3.5.5, 3.4.14
>
>
> https://builds.apache.org/view/S-Z/view/ZooKeeper/job/ZooKeeper-trunk-owasp/204/artifact/build/test/owasp/dependency-check-vulnerability.html
> https://nvd.nist.gov/vuln/detail/CVE-2018-8088
> We don't use EventData but should consider upgrading.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ZOOKEEPER-3217) owasp job flagging slf4j on trunk

[Patrick Hunt (JIRA)]

Patrick Hunt created ZOOKEEPER-3217:
---

 Summary: owasp job flagging slf4j on trunk
 Key: ZOOKEEPER-3217
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3217
 Project: ZooKeeper
  Issue Type: Bug
Reporter: Patrick Hunt
 Fix For: 3.6.0, 3.5.5, 3.4.14


https://builds.apache.org/view/S-Z/view/ZooKeeper/job/ZooKeeper-trunk-owasp/204/artifact/build/test/owasp/dependency-check-vulnerability.html

https://nvd.nist.gov/vuln/detail/CVE-2018-8088

We don't use EventData but should consider upgrading.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Build failed in Jenkins: ZooKeeper-trunk-owasp #204

[Apache Jenkins Server]

See 

--
[...truncated 13.10 KB...]
[ivy:retrieve]  found org.eclipse.jetty#jetty-security;9.4.10.v20180503 in 
maven2
[ivy:retrieve]  found com.fasterxml.jackson.core#jackson-databind;2.9.5 in 
maven2
[ivy:retrieve]  found com.fasterxml.jackson.core#jackson-annotations;2.9.0 in 
maven2
[ivy:retrieve]  found com.fasterxml.jackson.core#jackson-core;2.9.5 in maven2
[ivy:retrieve]  found org.slf4j#slf4j-api;1.7.25 in maven2
[ivy:retrieve]  found org.slf4j#slf4j-log4j12;1.7.25 in maven2
[ivy:retrieve]  found commons-cli#commons-cli;1.2 in maven2
[ivy:retrieve]  found log4j#log4j;1.2.17 in maven2
[ivy:retrieve]  found org.apache.yetus#audience-annotations;0.5.0 in maven2
[ivy:retrieve]  found io.netty#netty-all;4.1.29.Final in maven2
[ivy:retrieve]  found com.googlecode.json-simple#json-simple;1.1.1 in maven2
[ivy:retrieve] :: resolution report :: resolve 52ms :: artifacts dl 8ms
-
|  |modules||   artifacts   |
|   conf   | number| search|dwnlded|evicted|| number|dwnlded|
-
|  default |   18  |   0   |   0   |   0   ||   18  |   0   |
-
[ivy:retrieve] :: retrieving :: org.apache.zookeeper#zookeeper
[ivy:retrieve]  confs: [default]
[ivy:retrieve]  18 artifacts copied, 0 already retrieved (7954kB/19ms)

ivy-retrieve-clover:

clover.check:

clover.setup:

clover:

ivy-retrieve-javacc:
[mkdir] Created dir: 

[ivy:retrieve] :: resolving dependencies :: 
org.apache.zookeeper#zookeeper;3.6.0-SNAPSHOT
[ivy:retrieve]  confs: [javacc]
[ivy:retrieve]  found net.java.dev.javacc#javacc;5.0 in maven2
[ivy:retrieve] :: resolution report :: resolve 13ms :: artifacts dl 1ms
-
|  |modules||   artifacts   |
|   conf   | number| search|dwnlded|evicted|| number|dwnlded|
-
|  javacc  |   1   |   0   |   0   |   0   ||   1   |   0   |
-
[ivy:retrieve] :: retrieving :: org.apache.zookeeper#zookeeper
[ivy:retrieve]  confs: [javacc]
[ivy:retrieve]  1 artifacts copied, 0 already retrieved (291kB/2ms)

generate_jute_parser:
[mkdir] Created dir: 

[ivy:artifactproperty] DEPRECATED: 'ivy.conf.file' is deprecated, use 
'ivy.settings.file' instead
[ivy:artifactproperty] :: loading settings :: file = 

 [move] Moving 1 file to 

   [javacc] Java Compiler Compiler Version 5.0 (Parser Generator)
   [javacc] (type "javacc" with no arguments for help)
   [javacc] Reading from file 

 . . .
   [javacc] File "TokenMgrError.java" does not exist.  Will create one.
   [javacc] File "ParseException.java" does not exist.  Will create one.
   [javacc] File "Token.java" does not exist.  Will create one.
   [javacc] File "SimpleCharStream.java" does not exist.  Will create one.
   [javacc] Parser generated successfully.

jute:
[javac] Compiling 39 source files to 

[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 8
[javac] 1 warning

compile_jute_uptodate:

compile_jute:
[mkdir] Created dir: 

[mkdir] Created dir: 

 [java] ../../../src/main/resources/zookeeper.jute Parsed Successfully
 [java] ../../../zookeeper-jute/src/main/resources/zookeeper.jute Parsed 
Successfully
[touch] Creating 


ver-gen:
[javac] Compiling 1 source file to 

[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 8
[javac] 1 warning

git-revision:
[mkdir] Created dir: 


version-info:

process-template:

Re: Migrating ZooKeeper to GitBox

[Patrick Hunt]

FYI INFRA has updated the repo location.

You'll want to use git remote set-url to update your remote url.

I'll update the Jenkins jobs now.

Patrick

On Fri, Dec 14, 2018 at 12:17 PM Andor Molnár  wrote:

> Here you are:
>
>
> https://issues.apache.org/jira/browse/INFRA-17446
>
>
> Andor
>
>
>
>
> On 12/14/18 07:11, Fangmin Lv wrote:
> > +1 for proactive move. Is there a Jira to track this?
> >
> > Best,
> > Fangmin
> >
> > On Thu, Dec 13, 2018 at 6:41 PM Norbert Kalmar
> 
> > wrote:
> >
> >> +1 (non-binding) for early voluntarily move.
> >> I will update the pom files, there is a PR on the POM's anyway, and they
> >> are WIP.
> >>
> >> Regards,
> >> Norbert
> >>
> >> On Thu, Dec 13, 2018 at 5:34 AM Michael Han  wrote:
> >>
> >>> +1 on voluntarily request to move.
> >>>
> >>> On Wed, Dec 12, 2018 at 11:36 AM Patrick Hunt 
> wrote:
> >>>
>  Probably minor, but note there are some website pages that will also
> >> need
>  to be updated:
>  e.g. https://zookeeper.apache.org/git.html
> 
>  Patrick
> 
>  On Wed, Dec 12, 2018 at 10:58 AM Enrico Olivelli  >
>  wrote:
> 
> > +1  for moving to github now
> >
> > Enrico
> >
> > Il mer 12 dic 2018, 19:49 Tamas Penzes 
> >>> ha
> > scritto:
> >
> >> Hi Patrick,
> >>
> >> Yes we have to upgrade the main pom.xml, just as the website and
> >> the
> >> documentation.
> >> Do we have to change git urls in old documentations as well?
> >> (People
> > might
> >> read them.)
> >>
> >> Thanks, Tamaas
> >>
> >> On Wed, Dec 12, 2018, 18:31 Patrick Hunt  >>
> >>> Proactive sounds good to me. Can we schedule something outside
> >> the
> >>> holidays?
> >>>
> >>> Aside from Jenkins is there anything else we need to worry about?
>  e.g.
> > I
> >>> see a reference in pom.xml
> >>>
> >>> pom.xml
> >>> 63:scm:git:
> >>> https://git-wip-us.apache.org/repos/asf/zookeeper.git
> >>> 
> >>> 64:
> >>> https://git-wip-us.apache.org/repos/asf?p=zookeeper.git
> >> 
> >>> What's the impact wrt github.com and the Apache org? Will this
>  enable
> >> use
> >>> to become admins at the same time? (greater control over the
> > issues/prs,
> >>> etc...)
> >>>
> >>> Patrick
> >>>
> >>> On Wed, Dec 12, 2018 at 9:07 AM Andor Molnar 
>  wrote:
>  Hi dev team,
> 
>  Have you seen this?
> 
> 
> >>
> https://blogs.apache.org/infra/entry/relocation-of-apache-git-repositories
>  <
> 
> >>
> https://blogs.apache.org/infra/entry/relocation-of-apache-git-repositories
>  I think we should volunteer for a coordinated migration of
>  ZooKeeper,
>  although the project is not too big, so the impact of a forced
> > process
>  probably wouldn’t be so much.
> 
>  There’re some benefits though:
>  - We could move to GitBox earlier rather than later, so we
> >> could
>  take
>  advantage of GitHub write access for example,
>  - Migration needs a write-lock in place during the process, so
> >> we
>  can
>  avoid some unfortunate surprises,
>  - git-wip-us.apache.org  will
> >>> have
> >> CNAMEs
>  to gitbox, so it’ll be operational for some time, but the
> >>> read-only
>  git.apache.org  will go away (not sure
>  about
> >> the
>  timing though), that we use in some of our Jenkins builds. It
> >>> would
> > be
>  better to migrate Jenkins configs in a coordinated fashion
> >> rather
> > than
> >>> when
>  the house is burning.
> 
>  There’re a bunch of unkowns in each project, hence Infra guys
> > recommend
>  the coordinated way, but we need an agreement in the community,
> >>> so
> >> please
>  share your thoughts.
> 
>  Regards,
>  Andor
> 
> 
> 
> > --
> >
> >
> > -- Enrico Olivelli
> >
>

Build failed in Jenkins: ZooKeeper-trunk-owasp #202

[Apache Jenkins Server]

See 

--
Started by user phunt
[EnvInject] - Loading node environment variables.
Building remotely on H28 (ubuntu xenial) in workspace 

[WS-CLEANUP] Deleting project workspace...
[WS-CLEANUP] Done
Cloning the remote Git repository
Cloning repository https://git-wip-us.apache.org/repos/asf/zookeeper.git
 > git init  # 
 > timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/zookeeper.git
 > git --version # timeout=10
 > git fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/zookeeper.git 
 > +refs/heads/*:refs/remotes/origin/*
ERROR: Error cloning remote repo 'origin'
hudson.plugins.git.GitException: Command "git fetch --tags --progress 
https://git-wip-us.apache.org/repos/asf/zookeeper.git 
+refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout: 
stderr: fatal: repository 
'https://git-wip-us.apache.org/repos/asf/zookeeper.git/' not found

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2002)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1721)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:72)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:405)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:614)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)
at hudson.remoting.UserRequest.perform(UserRequest.java:212)
at hudson.remoting.UserRequest.perform(UserRequest.java:54)
at hudson.remoting.Request$2.run(Request.java:369)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to 
H28
at 
hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741)
at 
hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)
at hudson.remoting.Channel.call(Channel.java:955)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146)
at sun.reflect.GeneratedMethodAccessor1641.invoke(Unknown 
Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132)
at com.sun.proxy.$Proxy118.execute(Unknown Source)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1146)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1186)
at hudson.scm.SCM.checkout(SCM.java:504)
at 
hudson.model.AbstractProject.checkout(AbstractProject.java:1208)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)
at 
jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)
at hudson.model.Run.execute(Run.java:1794)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at 
hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:429)
ERROR: Error cloning remote repo 'origin'
Retrying after 10 seconds
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/zookeeper.git # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/zookeeper.git
 > git --version # timeout=10
 > git fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/zookeeper.git 
 > +refs/heads/*:refs/remotes/origin/*
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from 
https://git-wip-us.apache.org/repos/asf/zookeeper.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:888)
at 

[GitHub] zookeeper issue #680: ZOOKEEPER-3174: Quorum TLS - support reloading trust/k...

[ivmaykov]

Github user ivmaykov commented on the issue:

https://github.com/apache/zookeeper/pull/680
  
@anmolnar is there anything blocking this from being merged at this point?


---

Re: Migrating ZooKeeper to GitBox

[Andor Molnár]

Here you are:


https://issues.apache.org/jira/browse/INFRA-17446


Andor




On 12/14/18 07:11, Fangmin Lv wrote:
> +1 for proactive move. Is there a Jira to track this?
>
> Best,
> Fangmin
>
> On Thu, Dec 13, 2018 at 6:41 PM Norbert Kalmar 
> wrote:
>
>> +1 (non-binding) for early voluntarily move.
>> I will update the pom files, there is a PR on the POM's anyway, and they
>> are WIP.
>>
>> Regards,
>> Norbert
>>
>> On Thu, Dec 13, 2018 at 5:34 AM Michael Han  wrote:
>>
>>> +1 on voluntarily request to move.
>>>
>>> On Wed, Dec 12, 2018 at 11:36 AM Patrick Hunt  wrote:
>>>
 Probably minor, but note there are some website pages that will also
>> need
 to be updated:
 e.g. https://zookeeper.apache.org/git.html

 Patrick

 On Wed, Dec 12, 2018 at 10:58 AM Enrico Olivelli 
 wrote:

> +1  for moving to github now
>
> Enrico
>
> Il mer 12 dic 2018, 19:49 Tamas Penzes 
>>> ha
> scritto:
>
>> Hi Patrick,
>>
>> Yes we have to upgrade the main pom.xml, just as the website and
>> the
>> documentation.
>> Do we have to change git urls in old documentations as well?
>> (People
> might
>> read them.)
>>
>> Thanks, Tamaas
>>
>> On Wed, Dec 12, 2018, 18:31 Patrick Hunt >
>>> Proactive sounds good to me. Can we schedule something outside
>> the
>>> holidays?
>>>
>>> Aside from Jenkins is there anything else we need to worry about?
 e.g.
> I
>>> see a reference in pom.xml
>>>
>>> pom.xml
>>> 63:scm:git:
>>> https://git-wip-us.apache.org/repos/asf/zookeeper.git
>>> 
>>> 64:
>>> https://git-wip-us.apache.org/repos/asf?p=zookeeper.git
>> 
>>> What's the impact wrt github.com and the Apache org? Will this
 enable
>> use
>>> to become admins at the same time? (greater control over the
> issues/prs,
>>> etc...)
>>>
>>> Patrick
>>>
>>> On Wed, Dec 12, 2018 at 9:07 AM Andor Molnar 
 wrote:
 Hi dev team,

 Have you seen this?


>> https://blogs.apache.org/infra/entry/relocation-of-apache-git-repositories
 <

>> https://blogs.apache.org/infra/entry/relocation-of-apache-git-repositories
 I think we should volunteer for a coordinated migration of
 ZooKeeper,
 although the project is not too big, so the impact of a forced
> process
 probably wouldn’t be so much.

 There’re some benefits though:
 - We could move to GitBox earlier rather than later, so we
>> could
 take
 advantage of GitHub write access for example,
 - Migration needs a write-lock in place during the process, so
>> we
 can
 avoid some unfortunate surprises,
 - git-wip-us.apache.org  will
>>> have
>> CNAMEs
 to gitbox, so it’ll be operational for some time, but the
>>> read-only
 git.apache.org  will go away (not sure
 about
>> the
 timing though), that we use in some of our Jenkins builds. It
>>> would
> be
 better to migrate Jenkins configs in a coordinated fashion
>> rather
> than
>>> when
 the house is burning.

 There’re a bunch of unkowns in each project, hence Infra guys
> recommend
 the coordinated way, but we need an agreement in the community,
>>> so
>> please
 share your thoughts.

 Regards,
 Andor



> --
>
>
> -- Enrico Olivelli
>

[GitHub] zookeeper issue #714: Zookeeper 1818 (on branch-3.5)

[anmolnar]

Github user anmolnar commented on the issue:

https://github.com/apache/zookeeper/pull/714
  
retest this please


---

[GitHub] zookeeper issue #714: Zookeeper 1818 (on branch-3.5)

[anmolnar]

Github user anmolnar commented on the issue:

https://github.com/apache/zookeeper/pull/714
  
@lvfangmin Please approve.


---

Build failed in Jenkins: ZooKeeper-trunk-owasp #201

[Apache Jenkins Server]

See 

--
[...truncated 13.46 KB...]
[ivy:retrieve]  found commons-cli#commons-cli;1.2 in maven2
[ivy:retrieve]  found log4j#log4j;1.2.17 in maven2
[ivy:retrieve]  found org.apache.yetus#audience-annotations;0.5.0 in maven2
[ivy:retrieve]  found io.netty#netty-all;4.1.29.Final in maven2
[ivy:retrieve]  found com.googlecode.json-simple#json-simple;1.1.1 in maven2
[ivy:retrieve] :: resolution report :: resolve 59ms :: artifacts dl 8ms
-
|  |modules||   artifacts   |
|   conf   | number| search|dwnlded|evicted|| number|dwnlded|
-
|  default |   18  |   0   |   0   |   0   ||   18  |   0   |
-
[ivy:retrieve] :: retrieving :: org.apache.zookeeper#zookeeper
[ivy:retrieve]  confs: [default]
[ivy:retrieve]  18 artifacts copied, 0 already retrieved (7954kB/20ms)

ivy-retrieve-clover:

clover.check:

clover.setup:

clover:

ivy-retrieve-javacc:
[mkdir] Created dir: 

[ivy:retrieve] :: resolving dependencies :: 
org.apache.zookeeper#zookeeper;3.6.0-SNAPSHOT
[ivy:retrieve]  confs: [javacc]
[ivy:retrieve]  found net.java.dev.javacc#javacc;5.0 in maven2
[ivy:retrieve] :: resolution report :: resolve 34ms :: artifacts dl 0ms
-
|  |modules||   artifacts   |
|   conf   | number| search|dwnlded|evicted|| number|dwnlded|
-
|  javacc  |   1   |   0   |   0   |   0   ||   1   |   0   |
-
[ivy:retrieve] :: retrieving :: org.apache.zookeeper#zookeeper
[ivy:retrieve]  confs: [javacc]
[ivy:retrieve]  1 artifacts copied, 0 already retrieved (291kB/4ms)

generate_jute_parser:
[mkdir] Created dir: 

[ivy:artifactproperty] DEPRECATED: 'ivy.conf.file' is deprecated, use 
'ivy.settings.file' instead
[ivy:artifactproperty] :: loading settings :: file = 

 [move] Moving 1 file to 

   [javacc] Java Compiler Compiler Version 5.0 (Parser Generator)
   [javacc] (type "javacc" with no arguments for help)
   [javacc] Reading from file 

 . . .
   [javacc] File "TokenMgrError.java" does not exist.  Will create one.
   [javacc] File "ParseException.java" does not exist.  Will create one.
   [javacc] File "Token.java" does not exist.  Will create one.
   [javacc] File "SimpleCharStream.java" does not exist.  Will create one.
   [javacc] Parser generated successfully.

jute:
[javac] Compiling 39 source files to 

[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 8
[javac] 1 warning

compile_jute_uptodate:

compile_jute:
[mkdir] Created dir: 

[mkdir] Created dir: 

 [java] ../../../src/main/resources/zookeeper.jute Parsed Successfully
 [java] ../../../zookeeper-jute/src/main/resources/zookeeper.jute Parsed 
Successfully
[touch] Creating 


ver-gen:
[javac] Compiling 1 source file to 

[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 8
[javac] 1 warning

git-revision:
[mkdir] Created dir: 


version-info:

process-template:

build-generated:
[javac] Compiling 63 source files to 

[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 8
[javac] 1 warning

compile:
[javac] Compiling 299 source files to 

[javac] warning: [options] bootstrap class path not set in conjunction with 
-source