From kmoriguc at redhat.com Sun Jun 1 21:02:45 2014 From: kmoriguc at redhat.com (kmoriguc at redhat.com) Date: Mon, 02 Jun 2014 07:02:45 +1000 Subject: [zanata-users] zanata not working? Message-ID: <538B94F5.5000108@redhat.com> Hi At the moment, Zanata seems not working. More specifically, at https://translate.engineering.redhat.com/iteration/view/rhel-installation-guide/7.0# I can not go into my language ja-JP or specific documents to work on strings. Thanks Kenzo Moriguchi From aeng at redhat.com Sun Jun 1 23:04:38 2014 From: aeng at redhat.com (Alex Eng) Date: Sun, 1 Jun 2014 19:04:38 -0400 (EDT) Subject: [zanata-users] Zanata 3.4.1 in translate.engineering.redhat.com In-Reply-To: <1061703857.15211748.1401663549775.JavaMail.zimbra@redhat.com> Message-ID: <2120165747.15212029.1401663878172.JavaMail.zimbra@redhat.com> Zanata users, If you encountered any issue with clicking on project/project iteration page in Zanata 3.4.1, or weird display on your screen, please press CTRL+F5 to force refresh on your browser. This is due to the browser caching on old styling in Zanata. Regards, Alex Eng Senior Software Engineer DID: +61 3514 8262 Mobile: +614 2335 3457 Email: aeng at redhat.com Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 Fax: +61 7 3514 8199 Website: www.redhat.com From aeng at redhat.com Tue Jun 3 00:47:27 2014 From: aeng at redhat.com (Alex Eng) Date: Mon, 2 Jun 2014 20:47:27 -0400 (EDT) Subject: [zanata-users] New project and version screen In-Reply-To: <1212720724.16047710.1401755342484.JavaMail.zimbra@redhat.com> Message-ID: <619867310.16049407.1401756447452.JavaMail.zimbra@redhat.com> There's design changes in project and version screen in Zanata 3.4.1. Below are some basic instructions for navigation until we've got screencast available. New project screen (4.png) Translators are able to navigate to document list on editor from selecting drop down on each of the version. Alternately, user can click on the version they wish to explore. New version screen (1.png) Translator will be able to see list of supported language in the version. Languages that mark with "globe" icon indicates that you are either translator or reviewer of this locale. To navigate to document list in editor i) from project screen, click on the up/down arrow of left side of each version, and click on "Translate in {your locale}". (4.png) To navigate to straight into editor of a particular document i) click on a locale, this will loads up a document list on right side. (1.png) ii) click on the up/down arrow on left side of each document, this will brings down some option (2.png). Click "Translate online" for editor screen. iii)user can also filter documents list by using search function on top of document list. (3.png) Regards, Alex Eng Senior Software Engineer DID: +61 3514 8262 Mobile: +614 2335 3457 Email: aeng at redhat.com Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 Fax: +61 7 3514 8199 Website: www.redhat.com -------------- next part -------------- A non-text attachment was scrubbed... Name: 4.png Type: image/png Size: 85865 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 1.png Type: image/png Size: 189915 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2.png Type: image/png Size: 60448 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 3.png Type: image/png Size: 61271 bytes Desc: not available URL: From bkearney at redhat.com Fri Jun 13 21:02:12 2014 From: bkearney at redhat.com (Bryan Kearney) Date: Fri, 13 Jun 2014 17:02:12 -0400 Subject: [zanata-users] Client problems Message-ID: <539B66D4.3050101@redhat.com> I am trying to upload a new pot file to translate.zanata.org, and again, the client is not working for me. I tried to upload pot files from the webui.. but I get errors there too. Can someone point me at how to fix any of hte clients below? I am on fedora 20, I used the latest in the f20 repo and got zanata-cli push -s . -t . -e /usr/bin/build-classpath: Could not find zanata-rest-client Java extension for this JVM /usr/bin/build-classpath: Could not find zanata-cli Java extension for this JVM /usr/bin/build-classpath: error: Some specified jars were not found so I upgraded to the latest from f21, and I get his error: [bkearney at dhcp137-92 locale]$ zanata-cli push -s . -t . -e /usr/bin/build-classpath: Could not find zanata-rest-client Java extension for this JVM /usr/bin/build-classpath: Could not find zanata-cli Java extension for this JVM /usr/bin/build-classpath: error: Some specified jars were not found Exception in thread "main" java.lang.NoClassDefFoundError: org/kohsuke/args4j/CmdLineException at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2531) at java.lang.Class.getMethod0(Class.java:2774) at java.lang.Class.getMethod(Class.java:1663) at sun.launcher.LauncherHelper.getMainMethod(LauncherHelper.java:494) at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:486) Caused by: java.lang.ClassNotFoundException: org.kohsuke.args4j.CmdLineException at java.net.URLClassLoader$1.run(URLClassLoader.java:366) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at java.lang.ClassLoader.loadClass(ClassLoader.java:425) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) In both cases, I am not sure why an rpm install does not bring in all the requires pacakges. Then, I switched to the latest zanata-client-ivy and I get this exception: /home/bkearney/bin/zanata-cli push -s . -t . -e zanata-cli-3.3.0-ivy-1: resolving dependencies with Ivy... [INFO] Loading project config from zanata.xml [INFO] Loading user config from /home/bkearney/.config/zanata.ini [WARN] exception processing request javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated at sun.security.ssl.SSLSessionImpl.getPeerCertificates(SSLSessionImpl.java:397) at org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:128) at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:397) at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:148) at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:149) at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:121) at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:573) at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:425) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754) at org.jboss.resteasy.client.core.executors.ApacheHttpClient4Executor.execute(ApacheHttpClient4Executor.java:201) at org.jboss.resteasy.core.interception.ClientExecutionContextImpl.proceed(ClientExecutionContextImpl.java:41) at org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor.execute(AcceptEncodingGZIPInterceptor.java:40) at org.jboss.resteasy.core.interception.ClientExecutionContextImpl.proceed(ClientExecutionContextImpl.java:47) at org.zanata.rest.client.TraceDebugInterceptor.execute(TraceDebugInterceptor.java:74) at org.jboss.resteasy.core.interception.ClientExecutionContextImpl.proceed(ClientExecutionContextImpl.java:47) at org.zanata.rest.client.ApiKeyHeaderDecorator.execute(ApiKeyHeaderDecorator.java:41) at org.jboss.resteasy.core.interception.ClientExecutionContextImpl.proceed(ClientExecutionContextImpl.java:47) at org.jboss.resteasy.client.ClientRequest.execute(ClientRequest.java:440) at org.jboss.resteasy.client.ClientRequest.httpMethod(ClientRequest.java:671) at org.jboss.resteasy.client.core.ClientInvoker.invoke(ClientInvoker.java:110) at org.jboss.resteasy.client.core.ClientProxy.invoke(ClientProxy.java:88) at com.sun.proxy.$Proxy38.get(Unknown Source) at org.zanata.rest.client.ZanataProxyFactory.(ZanataProxyFactory.java:82) at org.zanata.client.commands.OptionsUtil.createRequestFactory(OptionsUtil.java:155) at org.zanata.client.commands.PushPullCommand.(PushPullCommand.java:96) at org.zanata.client.commands.push.PushCommand.(PushCommand.java:86) at org.zanata.client.commands.push.PushOptionsImpl.initCommand(PushOptionsImpl.java:69) at org.zanata.client.commands.ArgsUtil.runCommand(ArgsUtil.java:47) at org.zanata.client.ZanataClient.processArgs(ZanataClient.java:168) at org.zanata.client.ZanataClient.main(ZanataClient.java:93) [ERROR] Execution failed: IOException [ERROR] Use -e/--errors for full stack trace (or when reporting bugs) From pahuang at redhat.com Mon Jun 16 02:11:34 2014 From: pahuang at redhat.com (Patrick Huang) Date: Sun, 15 Jun 2014 22:11:34 -0400 (EDT) Subject: [zanata-users] Client problems In-Reply-To: <539B66D4.3050101@redhat.com> References: <539B66D4.3050101@redhat.com> Message-ID: <505575128.21936073.1402884694770.JavaMail.zimbra@redhat.com> Hi Bryan, We have migrated translate.zanata.org to openshift and the SSL certificate have caused issues with old version of zanata client (https://bugzilla.redhat.com/show_bug.cgi?id=1102465). There is also a notice sent out 2 weeks ago on zanata-users https://www.redhat.com/archives/zanata-users/2014-May/msg00008.html For zanata-client error in Fedora, some dependencies of it may have been updated and broke it. I haven't got time to get to the bottom of it but there is already a bug preventing us from pushing an update in f20. So for now the best bet will be to use ivy client. For ivy client, judging by your first line of the output you are still using 3.3.0 version of zanata. So to push and pull against translate.zanata.org, upgrade your client version by either export ZANATA_CLI_VERSION=3.3.2, or edit the ivy script zanata-cli and set the version there. Regards, Patrick Huang Senior Software Engineer Engineering - Internationalisation Red Hat ----- Original Message ----- > From: "Bryan Kearney" > To: zanata-users at redhat.com > Sent: Saturday, June 14, 2014 7:02:12 AM > Subject: [zanata-users] Client problems > > I am trying to upload a new pot file to translate.zanata.org, and again, > the client is not working for me. I tried to upload pot files from the > webui.. but I get errors there too. Can someone point me at how to fix > any of hte clients below? > > I am on fedora 20, I used the latest in the f20 repo and got > > zanata-cli push -s . -t . -e > /usr/bin/build-classpath: Could not find zanata-rest-client Java > extension for this JVM > /usr/bin/build-classpath: Could not find zanata-cli Java extension for > this JVM > /usr/bin/build-classpath: error: Some specified jars were not found > > > so I upgraded to the latest from f21, and I get his error: > > [bkearney at dhcp137-92 locale]$ zanata-cli push -s . -t . -e > /usr/bin/build-classpath: Could not find zanata-rest-client Java > extension for this JVM > /usr/bin/build-classpath: Could not find zanata-cli Java extension for > this JVM > /usr/bin/build-classpath: error: Some specified jars were not found > Exception in thread "main" java.lang.NoClassDefFoundError: > org/kohsuke/args4j/CmdLineException > at java.lang.Class.getDeclaredMethods0(Native Method) > at java.lang.Class.privateGetDeclaredMethods(Class.java:2531) > at java.lang.Class.getMethod0(Class.java:2774) > at java.lang.Class.getMethod(Class.java:1663) > at sun.launcher.LauncherHelper.getMainMethod(LauncherHelper.java:494) > at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:486) > Caused by: java.lang.ClassNotFoundException: > org.kohsuke.args4j.CmdLineException > at java.net.URLClassLoader$1.run(URLClassLoader.java:366) > at java.net.URLClassLoader$1.run(URLClassLoader.java:355) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:354) > at java.lang.ClassLoader.loadClass(ClassLoader.java:425) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) > at java.lang.ClassLoader.loadClass(ClassLoader.java:358) > > > > In both cases, I am not sure why an rpm install does not bring in all > the requires pacakges. > > Then, I switched to the latest zanata-client-ivy and I get this exception: > > /home/bkearney/bin/zanata-cli push -s . -t . -e > zanata-cli-3.3.0-ivy-1: resolving dependencies with Ivy... > [INFO] Loading project config from zanata.xml > > [INFO] Loading user config from /home/bkearney/.config/zanata.ini > [WARN] exception processing request > javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated > at > sun.security.ssl.SSLSessionImpl.getPeerCertificates(SSLSessionImpl.java:397) > at > org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:128) > at > org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:397) > at > org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:148) > at > org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:149) > at > org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:121) > at > org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:573) > at > org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:425) > at > org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820) > at > org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754) > at > org.jboss.resteasy.client.core.executors.ApacheHttpClient4Executor.execute(ApacheHttpClient4Executor.java:201) > at > org.jboss.resteasy.core.interception.ClientExecutionContextImpl.proceed(ClientExecutionContextImpl.java:41) > at > org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor.execute(AcceptEncodingGZIPInterceptor.java:40) > at > org.jboss.resteasy.core.interception.ClientExecutionContextImpl.proceed(ClientExecutionContextImpl.java:47) > at > org.zanata.rest.client.TraceDebugInterceptor.execute(TraceDebugInterceptor.java:74) > at > org.jboss.resteasy.core.interception.ClientExecutionContextImpl.proceed(ClientExecutionContextImpl.java:47) > at > org.zanata.rest.client.ApiKeyHeaderDecorator.execute(ApiKeyHeaderDecorator.java:41) > at > org.jboss.resteasy.core.interception.ClientExecutionContextImpl.proceed(ClientExecutionContextImpl.java:47) > at org.jboss.resteasy.client.ClientRequest.execute(ClientRequest.java:440) > at > org.jboss.resteasy.client.ClientRequest.httpMethod(ClientRequest.java:671) > at > org.jboss.resteasy.client.core.ClientInvoker.invoke(ClientInvoker.java:110) > at org.jboss.resteasy.client.core.ClientProxy.invoke(ClientProxy.java:88) > at com.sun.proxy.$Proxy38.get(Unknown Source) > at > org.zanata.rest.client.ZanataProxyFactory.(ZanataProxyFactory.java:82) > at > org.zanata.client.commands.OptionsUtil.createRequestFactory(OptionsUtil.java:155) > at > org.zanata.client.commands.PushPullCommand.(PushPullCommand.java:96) > at org.zanata.client.commands.push.PushCommand.(PushCommand.java:86) > at > org.zanata.client.commands.push.PushOptionsImpl.initCommand(PushOptionsImpl.java:69) > at org.zanata.client.commands.ArgsUtil.runCommand(ArgsUtil.java:47) > at org.zanata.client.ZanataClient.processArgs(ZanataClient.java:168) > at org.zanata.client.ZanataClient.main(ZanataClient.java:93) > [ERROR] Execution failed: IOException > [ERROR] Use -e/--errors for full stack trace (or when reporting bugs) > > > _______________________________________________ > zanata-users mailing list > zanata-users at redhat.com > https://www.redhat.com/mailman/listinfo/zanata-users > From bkearney at redhat.com Mon Jun 16 11:51:36 2014 From: bkearney at redhat.com (Bryan Kearney) Date: Mon, 16 Jun 2014 07:51:36 -0400 Subject: [zanata-users] Client problems In-Reply-To: <505575128.21936073.1402884694770.JavaMail.zimbra@redhat.com> References: <539B66D4.3050101@redhat.com> <505575128.21936073.1402884694770.JavaMail.zimbra@redhat.com> Message-ID: <539EDA48.9030406@redhat.com> On 06/15/2014 10:11 PM, Patrick Huang wrote: > Hi Bryan, > > We have migrated translate.zanata.org to openshift and the SSL certificate have caused issues with old version of zanata client (https://bugzilla.redhat.com/show_bug.cgi?id=1102465). There is also a notice sent out 2 weeks ago on zanata-users https://www.redhat.com/archives/zanata-users/2014-May/msg00008.html > > For zanata-client error in Fedora, some dependencies of it may have been updated and broke it. I haven't got time to get to the bottom of it but there is already a bug preventing us from pushing an update in f20. So for now the best bet will be to use ivy client. > > For ivy client, judging by your first line of the output you are still using 3.3.0 version of zanata. > > So to push and pull against translate.zanata.org, upgrade your client version by either export ZANATA_CLI_VERSION=3.3.2, or edit the ivy script zanata-cli and set the version there. I pulled the latets from https://github.com/zanata/zanata-client-ivy.. master branch. Is this not the correct location. I would really like to have a location where the client always works from. -- bk From pahuang at redhat.com Mon Jun 16 23:00:39 2014 From: pahuang at redhat.com (Patrick Huang) Date: Mon, 16 Jun 2014 19:00:39 -0400 (EDT) Subject: [zanata-users] Client problems In-Reply-To: <539EDA48.9030406@redhat.com> References: <539B66D4.3050101@redhat.com> <505575128.21936073.1402884694770.JavaMail.zimbra@redhat.com> <539EDA48.9030406@redhat.com> Message-ID: <1474216197.22848190.1402959639573.JavaMail.zimbra@redhat.com> Hi Bryan, That is the correct location. The script there is set to use 3.3.2 by default. But I think you may have previously set an environment variable ZANATA_CLI_VERSION. export ZANATA_CLI_VERSION=3.3.2 should fix that. Patrick Huang Senior Software Engineer Engineering - Internationalisation Red Hat ----- Original Message ----- > From: "Bryan Kearney" > To: "Patrick Huang" > Cc: zanata-users at redhat.com > Sent: Monday, June 16, 2014 9:51:36 PM > Subject: Re: [zanata-users] Client problems > > On 06/15/2014 10:11 PM, Patrick Huang wrote: > > Hi Bryan, > > > > We have migrated translate.zanata.org to openshift and the SSL certificate > > have caused issues with old version of zanata client > > (https://bugzilla.redhat.com/show_bug.cgi?id=1102465). There is also a > > notice sent out 2 weeks ago on zanata-users > > https://www.redhat.com/archives/zanata-users/2014-May/msg00008.html > > > > For zanata-client error in Fedora, some dependencies of it may have been > > updated and broke it. I haven't got time to get to the bottom of it but > > there is already a bug preventing us from pushing an update in f20. So for > > now the best bet will be to use ivy client. > > > > For ivy client, judging by your first line of the output you are still > > using 3.3.0 version of zanata. > > > > So to push and pull against translate.zanata.org, upgrade your client > > version by either export ZANATA_CLI_VERSION=3.3.2, or edit the ivy script > > zanata-cli and set the version there. > > I pulled the latets from https://github.com/zanata/zanata-client-ivy.. > master branch. Is this not the correct location. > > I would really like to have a location where the client always works from. > -- bk > > From aeng at redhat.com Thu Jun 19 05:23:34 2014 From: aeng at redhat.com (Alex Eng) Date: Thu, 19 Jun 2014 01:23:34 -0400 (EDT) Subject: [zanata-users] translate.zanata.org Scheduled Maintenance | 2014-06-19 - 5:50 UTC In-Reply-To: <537D67ED.8030707@redhat.com> References: <537D67ED.8030707@redhat.com> Message-ID: <1266081459.27002997.1403155414741.JavaMail.zimbra@redhat.com> ***// SCHEDULED MAINTENANCE REPORT //*** Priority: High Scheduled Date: 2014-06-19 Scheduled Time: 5:50 UTC Estimated Time Required: 30-60 min Performed By: aeng sflaniga camunoz People/Groups Impacted: users of Zanata Site/Services Affected: translate.zanata.org Impact: Zanata will be unavailable during the outage. Description: Restart of server -- Alex Eng Senior Software Engineer Engineering - Internationalisation Red Hat _______________________________________________ zanata-users mailing list zanata-users at redhat.com https://www.redhat.com/mailman/listinfo/zanata-users -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: signature.asc URL: From aeng at redhat.com Thu Jun 19 06:06:37 2014 From: aeng at redhat.com (Alex Eng) Date: Thu, 19 Jun 2014 02:06:37 -0400 (EDT) Subject: [zanata-users] Fwd: translate.zanata.org Scheduled Maintenance | 2014-06-19 - 5:50 UTC In-Reply-To: <1266081459.27002997.1403155414741.JavaMail.zimbra@redhat.com> References: <537D67ED.8030707@redhat.com> <1266081459.27002997.1403155414741.JavaMail.zimbra@redhat.com> Message-ID: <1727788215.27014949.1403157997601.JavaMail.zimbra@redhat.com> Outage completed. Please report any service faults to aeng at redhat.com or sflaniga at redhat.com camunoz at redhat.com Regards, Alex Eng Senior Software Engineer DID: +61 3514 8262 Mobile: +614 2335 3457 Email: aeng at redhat.com Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 Fax: +61 7 3514 8199 Website: www.redhat.com ----- Forwarded Message ----- From: "Alex Eng" To: outage-list at redhat.com Cc: zanata-users at redhat.com Sent: Thursday, 19 June, 2014 3:23:34 PM Subject: [zanata-users] translate.zanata.org Scheduled Maintenance | 2014-06-19 - 5:50 UTC ***// SCHEDULED MAINTENANCE REPORT //*** Priority: High Scheduled Date: 2014-06-19 Scheduled Time: 5:50 UTC Estimated Time Required: 30-60 min Performed By: aeng sflaniga camunoz People/Groups Impacted: users of Zanata Site/Services Affected: translate.zanata.org Impact: Zanata will be unavailable during the outage. Description: Restart of server -- Alex Eng Senior Software Engineer Engineering - Internationalisation Red Hat _______________________________________________ zanata-users mailing list zanata-users at redhat.com https://www.redhat.com/mailman/listinfo/zanata-users _______________________________________________ Outage-list mailing list Outage-list at redhat.com https://post-office.corp.redhat.com/mailman/listinfo/outage-list