From mgrigull at redhat.com Mon Sep 3 23:45:22 2012 From: mgrigull at redhat.com (Marco Grigull) Date: Tue, 04 Sep 2012 09:45:22 +1000 Subject: [zanata-users] translate.zanata.org upgrade In-Reply-To: <503DB133.5010106@redhat.com> References: <503DAFB0.3060608@redhat.com> <503DB133.5010106@redhat.com> Message-ID: <50454112.8070807@redhat.com> Scheduled for 10:30 am Australian Eastern standard time On 08/29/2012 04:05 PM, Marco Grigull wrote: > On 08/29/2012 03:59 PM, Marco Grigull wrote: >> Will be commencing shortly. >> >> > > > This will be postponed until a signed package can be gotten into the > correct repo. > > -- Marco Grigull, Systems Administrator, Engineering Operations 85 88229 / +61 7 3514 8229 From mgrigull at redhat.com Tue Sep 4 00:49:33 2012 From: mgrigull at redhat.com (Marco Grigull) Date: Tue, 04 Sep 2012 10:49:33 +1000 Subject: [zanata-users] translate.zanata.org upgrade In-Reply-To: <50454112.8070807@redhat.com> References: <503DAFB0.3060608@redhat.com> <503DB133.5010106@redhat.com> <50454112.8070807@redhat.com> Message-ID: <5045501D.8040904@redhat.com> Outage completed. On 09/04/2012 09:45 AM, Marco Grigull wrote: > Scheduled for 10:30 am Australian Eastern standard time > > On 08/29/2012 04:05 PM, Marco Grigull wrote: >> On 08/29/2012 03:59 PM, Marco Grigull wrote: >>> Will be commencing shortly. >>> >>> >> >> >> This will be postponed until a signed package can be gotten into the >> correct repo. >> >> > > -- Marco Grigull, Systems Administrator, Engineering Operations 85 88229 / +61 7 3514 8229 From inecas at redhat.com Tue Sep 11 10:17:47 2012 From: inecas at redhat.com (=?UTF-8?B?SXZhbiBOZcSNYXM=?=) Date: Tue, 11 Sep 2012 12:17:47 +0200 Subject: [zanata-users] Getting 500 Internal server error when pushing the pot file. Message-ID: <504F0FCB.3020802@redhat.com> Hello, I'm trying to upload my localization files to zanata, but getting 500 or 503 errors, python client version 1.3.11 (fails alwo with 1.3.5) anyone experienced similar behavior lately? I was getting similar errors yesterday, today I was able to successfully push po for one project, but still failing for another (a bit larger one) zanata po push --srcdir . Loading zanata project config from: /root/system-engine/src/locale/zanata.xml Loading zanata user config from: /root/.config/zanata.ini zanata server: https://translate.zanata.org/zanata zanata python client version: 1.3.11, zanata server API version: 1.7.0 Project: cfse Version: 1.1 Username: inecas Source language: en-US Reuse previous translation on server:True PO directory (originals):. Importing source documents only Pushing the content of ./app.pot to server: error: Error 500 - JBoss Web/2.1.12.GA-patch-03 - Error repor t

HTTP S tatus 500 -

type Status report

message

description The server encountered an internal error () that prevented it from fulfilling this request.

JBoss Web/2.1.12.GA-patch-03

Please take a reference in https://github.com/zanata/zanata/wiki/Python-Client-T roubleshooting r Nothing from the TroubleShooting guide helped, I've also tried -no-copytrans option, with no success. -- Ivan From inecas at redhat.com Tue Sep 11 10:38:05 2012 From: inecas at redhat.com (=?UTF-8?B?SXZhbiBOZcSNYXM=?=) Date: Tue, 11 Sep 2012 12:38:05 +0200 Subject: [zanata-users] Getting 500 Internal server error when pushing the pot file. In-Reply-To: <504F0FCB.3020802@redhat.com> References: <504F0FCB.3020802@redhat.com> Message-ID: <504F148D.9000108@redhat.com> On 09/11/2012 12:17 PM, Ivan Ne?as wrote: I've tried running it with --disable-ssl-cert, and it seems it works now. Only one strange thing: when I uploaded the pot file for project cfse-cli version 1.1, most of the translations was reused from previous version. But with cfse project, there is 0% translated, even if there are many common strings. It's true, that the first successful try was run with --no-copytrans option, but then I've rerun it again without this option, overriding the orignal document. Any help on this? -- Ivan > Hello, > > I'm trying to upload my localization files to zanata, but getting 500 > or 503 errors, python client version 1.3.11 (fails alwo with 1.3.5) > anyone experienced similar behavior lately? > > I was getting similar errors yesterday, today I was able to > successfully push po for one project, but still failing for another (a > bit larger one) > > zanata po push --srcdir . > Loading zanata project config from: > /root/system-engine/src/locale/zanata.xml > Loading zanata user config from: /root/.config/zanata.ini > zanata server: https://translate.zanata.org/zanata > zanata python client version: 1.3.11, zanata server API version: 1.7.0 > Project: cfse > Version: 1.1 > Username: inecas > Source language: en-US > Reuse previous translation on server:True > PO directory (originals):. > Importing source documents only > > Pushing the content of ./app.pot to server: > error: Error 500 - JBoss Web/2.1.12.GA-patch-03 - > Error repor > t >

HTTP S > tatus 500 -

type Status > report

message

description The server > encountered an > internal error () that prevented it from fulfilling this > request.

e="1" noshade="noshade">

JBoss > Web/2.1.12.GA-patch-03

> Please take a reference in > https://github.com/zanata/zanata/wiki/Python-Client-T > roubleshooting > r > > Nothing from the TroubleShooting guide helped, I've also tried > -no-copytrans option, with no success. > > -- Ivan -- Ivan From sflaniga at redhat.com Wed Sep 12 00:56:36 2012 From: sflaniga at redhat.com (Sean Flanigan) Date: Wed, 12 Sep 2012 10:56:36 +1000 Subject: [zanata-users] Getting 500 Internal server error when pushing the pot file. In-Reply-To: <504F148D.9000108@redhat.com> References: <504F0FCB.3020802@redhat.com> <504F148D.9000108@redhat.com> Message-ID: <504FDDC4.4060800@redhat.com> Hi Ivan, Unfortunately, copyTrans is somewhat expensive, so it only runs when a document is first created for a specific project version, and only if you don't specify --no-copytrans on that first try. However, in Zanata 1.7 it is also possible for project maintainers to invoke copyTrans manually from the project version page, using the "Copy Translations" action on the right. Note: there is a bug[1] in 1.7.1 which means the options you choose in the Copy Translations dialog will be ignored. That shouldn't affect your project much, because it appears you haven't changed the filenames between 1.0 and 1.1. For you, the bug just means that copyTrans might find some similar strings in other projects/files and re-use as fuzzy, whether you ask it to or not. [1] https://bugzilla.redhat.com/show_bug.cgi?id=856413 Regards Sean. On 2012-09-11 20:38, Ivan Ne?as wrote: > On 09/11/2012 12:17 PM, Ivan Ne?as wrote: > > I've tried running it with --disable-ssl-cert, and it seems it works > now. Only one strange thing: when I uploaded the pot file for project > cfse-cli version 1.1, most of the translations was reused from previous > version. But with cfse project, there is 0% translated, even if there > are many common strings. > > It's true, that the first successful try was run with --no-copytrans > option, but then I've rerun it again without this option, overriding the > orignal document. Any help on this? > > > -- Ivan >> Hello, >> >> I'm trying to upload my localization files to zanata, but getting 500 >> or 503 errors, python client version 1.3.11 (fails alwo with 1.3.5) >> anyone experienced similar behavior lately? >> >> I was getting similar errors yesterday, today I was able to >> successfully push po for one project, but still failing for another (a >> bit larger one) >> >> zanata po push --srcdir . >> Loading zanata project config from: >> /root/system-engine/src/locale/zanata.xml >> Loading zanata user config from: /root/.config/zanata.ini >> zanata server: https://translate.zanata.org/zanata >> zanata python client version: 1.3.11, zanata server API version: 1.7.0 >> Project: cfse >> Version: 1.1 >> Username: inecas >> Source language: en-US >> Reuse previous translation on server:True >> PO directory (originals):. >> Importing source documents only >> >> Pushing the content of ./app.pot to server: >> error: Error 500 - JBoss Web/2.1.12.GA-patch-03 - >> Error repor >> t >>

HTTP S >> tatus 500 -

type Status >> report

message

description The server >> encountered an >> internal error () that prevented it from fulfilling this >> request.

> e="1" noshade="noshade">

JBoss >> Web/2.1.12.GA-patch-03

>> Please take a reference in >> https://github.com/zanata/zanata/wiki/Python-Client-T >> roubleshooting >> r >> >> Nothing from the TroubleShooting guide helped, I've also tried >> -no-copytrans option, with no success. >> >> -- Ivan > > -- Sean Flanigan Senior Software Engineer Engineering - Internationalisation Red Hat -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 554 bytes Desc: OpenPGP digital signature URL: From alikins at redhat.com Wed Sep 19 19:43:36 2012 From: alikins at redhat.com (Adrian Likins) Date: Wed, 19 Sep 2012 15:43:36 -0400 Subject: [zanata-users] Getting 500 Internal server error when pushing the pot file. In-Reply-To: <504F148D.9000108@redhat.com> References: <504F0FCB.3020802@redhat.com> <504F148D.9000108@redhat.com> Message-ID: <505A2068.8000805@redhat.com> I seem to be running into a similar issue, though I'm consistently getting 503's Things to note: this is on a new "version" (1.1.x of subscription-manager project) while attempting to do the initial push to zanata using: zanata python client version: 1.3.7-2-g4e29 (on rhel6.3(ish)) [adrian at dhcp231-28 po (master *)]$ zanata push --project-type gettext --srcdir . Loading zanata project config from: /home/adrian/subscription-manager/po/zanata.xml Loading zanata user config from: /home/adrian/.config/zanata.ini zanata server: https://translate.zanata.org/zanata zanata python client version: 1.3.7-2-g4e29, zanata server API version: 1.7.0 Project: subscription-manager Version: 1.1.X Username: alikins Source language: en-US Copy previous translations:True PO directory (originals):. Importing source documents only Pushing the content of ./keys.pot to server: Traceback (most recent call last): File "/usr/bin/zanata", line 25, in zanata.run() File "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/zanata.py", line 945, in run program_name=os.path.split(sys.argv[0])[1], File "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/command.py", line 339, in handle_program command(command_options, args) File "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/zanata.py", line 800, in push command.run(command_options, args) File "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/pushcmd.py", line 483, in run zanatacmd.push_command(filelist, tmlfolder, project_id, version_id, copytrans, plural_support) File "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/zanatacmd.py", line 396, in push_command result = self.zanata_resource.documents.commit_template(project_id, iteration_id, body, copytrans) File "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/zanatalib/docservice.py", line 110, in commit_template raise UnavailableServiceError('Error 503', 'Service Temporarily Unavailable') zanataclient.zanatalib.error.UnavailableServiceError: Error 503 - Service Temporarily Unavailable On 09/11/2012 06:38 AM, Ivan Ne?as wrote: > On 09/11/2012 12:17 PM, Ivan Ne?as wrote: > > I've tried running it with --disable-ssl-cert, and it seems it works > now. Only one strange thing: when I uploaded the pot file for project > cfse-cli version 1.1, most of the translations was reused from > previous version. But with cfse project, there is 0% translated, even > if there are many common strings. > > It's true, that the first successful try was run with --no-copytrans > option, but then I've rerun it again without this option, overriding > the orignal document. Any help on this? > > > -- Ivan >> Hello, >> >> I'm trying to upload my localization files to zanata, but getting 500 >> or 503 errors, python client version 1.3.11 (fails alwo with 1.3.5) >> anyone experienced similar behavior lately? >> >> I was getting similar errors yesterday, today I was able to >> successfully push po for one project, but still failing for another >> (a bit larger one) >> >> zanata po push --srcdir . >> Loading zanata project config from: >> /root/system-engine/src/locale/zanata.xml >> Loading zanata user config from: /root/.config/zanata.ini >> zanata server: https://translate.zanata.org/zanata >> zanata python client version: 1.3.11, zanata server API version: 1.7.0 >> Project: cfse >> Version: 1.1 >> Username: inecas >> Source language: en-US >> Reuse previous translation on server:True >> PO directory (originals):. >> Importing source documents only >> >> Pushing the content of ./app.pot to server: >> error: Error 500 - JBoss Web/2.1.12.GA-patch-03 - >> Error repor >> t >>

HTTP S >> tatus 500 -

type Status >> report

message

description The server >> encountered an >> internal error () that prevented it from fulfilling this >> request.

> e="1" noshade="noshade">

JBoss >> Web/2.1.12.GA-patch-03

>> Please take a reference in >> https://github.com/zanata/zanata/wiki/Python-Client-T >> roubleshooting >> r >> >> Nothing from the TroubleShooting guide helped, I've also tried >> -no-copytrans option, with no success. >> >> -- Ivan > > From inecas at redhat.com Thu Sep 20 07:40:46 2012 From: inecas at redhat.com (=?UTF-8?B?SXZhbiBOZcSNYXM=?=) Date: Thu, 20 Sep 2012 09:40:46 +0200 Subject: [zanata-users] Getting 500 Internal server error when pushing the pot file. In-Reply-To: <505A2068.8000805@redhat.com> References: <504F0FCB.3020802@redhat.com> <504F148D.9000108@redhat.com> <505A2068.8000805@redhat.com> Message-ID: <505AC87E.30608@redhat.com> It seems providing --no-copytrans when pushing helped, but at the cost of not getting the translations from previous versions by default and additional steps from the translation team need to be done. -- Ivan On Wed 19 Sep 2012 09:43:36 PM CEST, Adrian Likins wrote: > > I seem to be running into a similar issue, though I'm consistently > getting 503's > > Things to note: this is on a new "version" (1.1.x of > subscription-manager project) > while attempting to do the initial push to zanata > > using: > zanata python client version: 1.3.7-2-g4e29 > (on rhel6.3(ish)) > > [adrian at dhcp231-28 po (master *)]$ zanata push --project-type gettext > --srcdir . > Loading zanata project config from: > /home/adrian/subscription-manager/po/zanata.xml > Loading zanata user config from: /home/adrian/.config/zanata.ini > zanata server: https://translate.zanata.org/zanata > zanata python client version: 1.3.7-2-g4e29, zanata server API > version: 1.7.0 > Project: subscription-manager > Version: 1.1.X > Username: alikins > Source language: en-US > Copy previous translations:True > PO directory (originals):. > Importing source documents only > > Pushing the content of ./keys.pot to server: > Traceback (most recent call last): > File "/usr/bin/zanata", line 25, in > zanata.run() > File > "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/zanata.py", > > line 945, in run > program_name=os.path.split(sys.argv[0])[1], > File > "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/command.py", > > line 339, in handle_program > command(command_options, args) > File > "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/zanata.py", > > line 800, in push > command.run(command_options, args) > File > "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/pushcmd.py", > > line 483, in run > zanatacmd.push_command(filelist, tmlfolder, project_id, > version_id, copytrans, plural_support) > File > "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/zanatacmd.py", > > line 396, in push_command > result = > self.zanata_resource.documents.commit_template(project_id, > iteration_id, body, copytrans) > File > "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/zanatalib/docservice.py", > > line 110, in commit_template > raise UnavailableServiceError('Error 503', 'Service Temporarily > Unavailable') > zanataclient.zanatalib.error.UnavailableServiceError: Error 503 - > Service Temporarily Unavailable > > > On 09/11/2012 06:38 AM, Ivan Ne?as wrote: >> >> On 09/11/2012 12:17 PM, Ivan Ne?as wrote: >> >> I've tried running it with --disable-ssl-cert, and it seems it works >> now. Only one strange thing: when I uploaded the pot file for project >> cfse-cli version 1.1, most of the translations was reused from >> previous version. But with cfse project, there is 0% translated, even >> if there are many common strings. >> >> It's true, that the first successful try was run with --no-copytrans >> option, but then I've rerun it again without this option, overriding >> the orignal document. Any help on this? >> >> >> -- Ivan >>> >>> Hello, >>> >>> I'm trying to upload my localization files to zanata, but getting >>> 500 or 503 errors, python client version 1.3.11 (fails alwo with >>> 1.3.5) anyone experienced similar behavior lately? >>> >>> I was getting similar errors yesterday, today I was able to >>> successfully push po for one project, but still failing for another >>> (a bit larger one) >>> >>> zanata po push --srcdir . >>> Loading zanata project config from: >>> /root/system-engine/src/locale/zanata.xml >>> Loading zanata user config from: /root/.config/zanata.ini >>> zanata server: https://translate.zanata.org/zanata >>> zanata python client version: 1.3.11, zanata server API version: 1.7.0 >>> Project: cfse >>> Version: 1.1 >>> Username: inecas >>> Source language: en-US >>> Reuse previous translation on server:True >>> PO directory (originals):. >>> Importing source documents only >>> >>> Pushing the content of ./app.pot to server: >>> error: Error 500 - JBoss Web/2.1.12.GA-patch-03 - >>> Error repor >>> t >>>

HTTP S >>> tatus 500 -

type >>> Status report

>>>

message

description The server >>> encountered an >>> internal error () that prevented it from fulfilling this >>> request.

>> e="1" noshade="noshade">

JBoss >>> Web/2.1.12.GA-patch-03

>>> Please take a reference in >>> https://github.com/zanata/zanata/wiki/Python-Client-T >>> roubleshooting >>> r >>> >>> Nothing from the TroubleShooting guide helped, I've also tried >>> -no-copytrans option, with no success. >>> >>> -- Ivan >> >> >> > > -- Ivan From alikins at redhat.com Thu Sep 20 17:35:10 2012 From: alikins at redhat.com (Adrian Likins) Date: Thu, 20 Sep 2012 13:35:10 -0400 Subject: [zanata-users] error: Can't find pot file for : on server Message-ID: <505B53CE.4020704@redhat.com> While trying to pull translations for subscription-manager 1.0.x branch: [adrian at dhcp231-28 po (zanata *)]$ zanata pull --project-type gettext Loading zanata project config from: /home/adrian/src/subscription-manager-internal/po/zanata.xml Loading zanata user config from: /home/adrian/.config/zanata.ini zanata server: https://translate.zanata.org/zanata zanata python client version: 1.3.7-2-g4e29, zanata server API version: 1.7.0 Project: subscription-manager Version: 1.0.X Username: alikins Fetching the content of : from Zanata server: error: Can't find pot file for : on server Looking at the project, it does appear to think there is a document called ':', with no .pot or translations. Is there a way to remove that? Or, is there a way for the client to work around it? Adrian From sflaniga at redhat.com Fri Sep 21 02:32:00 2012 From: sflaniga at redhat.com (Sean Flanigan) Date: Fri, 21 Sep 2012 12:32:00 +1000 Subject: [zanata-users] error: Can't find pot file for : on server In-Reply-To: <505B53CE.4020704@redhat.com> References: <505B53CE.4020704@redhat.com> Message-ID: <505BD1A0.40002@redhat.com> It may depend on how the ':' file got there in the first place, but assuming that problem is fixed[1], you should just have to to push the pot file again. If the only file pushed is 'keys', it should automatically delete the ':' file. BTW, I recommend editing zanata.xml to include this: gettext That way you won't need to keep specifying "--project-type gettext" Sean. [1] If not, point me at your source repo/branch and zanata.xml, and I'll see if I can work out what happened. On 2012-09-21 03:35, Adrian Likins wrote: > While trying to pull translations for subscription-manager 1.0.x branch: > > [adrian at dhcp231-28 po (zanata *)]$ zanata pull --project-type gettext > Loading zanata project config from: > /home/adrian/src/subscription-manager-internal/po/zanata.xml > Loading zanata user config from: /home/adrian/.config/zanata.ini > zanata server: https://translate.zanata.org/zanata > zanata python client version: 1.3.7-2-g4e29, zanata server API version: > 1.7.0 > Project: subscription-manager > Version: 1.0.X > Username: alikins > > Fetching the content of : from Zanata server: > error: Can't find pot file for : on server > > > Looking at the project, it does appear to think there is > a document called ':', with no .pot or translations. > > Is there a way to remove that? Or, is there a way for > the client to work around it? > > Adrian > > _______________________________________________ > zanata-users mailing list > zanata-users at redhat.com > https://www.redhat.com/mailman/listinfo/zanata-users -- Sean Flanigan Senior Software Engineer Engineering - Internationalisation Red Hat -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 554 bytes Desc: OpenPGP digital signature URL: From sflaniga at redhat.com Fri Sep 21 05:58:12 2012 From: sflaniga at redhat.com (Sean Flanigan) Date: Fri, 21 Sep 2012 15:58:12 +1000 Subject: [zanata-users] Getting 500 Internal server error when pushing the pot file. In-Reply-To: <505A2068.8000805@redhat.com> References: <504F0FCB.3020802@redhat.com> <504F148D.9000108@redhat.com> <505A2068.8000805@redhat.com> Message-ID: <505C01F4.6010204@redhat.com> Hi Adrian, Ivan, Disabling copyTrans can help, but I would recommend switching from the Python client to the latest version (1.7.1) of the Zanata Maven client, if you can. It splits source documents into multiple batches, to avoid overwhelming the server. You may need to install Apache Maven, and then you can find a basic pom.xml file here (put it in your project directory, along with zanata.xml): https://github.com/zanata/zanata/wiki/Zanata-Maven-Integration Note that you may need to change the srcDir option in the pom file, although you (Adrian) seem to be using current directory ("."), which is the default value. And I would recommend putting gettext (substitute your project type) into your zanata.xml, to save specifying it on the command line. Once you have all of that set up, pushing source documents should be as easy as: $ mvn zanata:push and pulling: $ mvn zanata:pull Sean. On 2012-09-20 05:43, Adrian Likins wrote: > I seem to be running into a similar issue, though I'm consistently > getting 503's > > Things to note: this is on a new "version" (1.1.x of > subscription-manager project) > while attempting to do the initial push to zanata > > using: > zanata python client version: 1.3.7-2-g4e29 > (on rhel6.3(ish)) > > [adrian at dhcp231-28 po (master *)]$ zanata push --project-type gettext > --srcdir . > Loading zanata project config from: > /home/adrian/subscription-manager/po/zanata.xml > Loading zanata user config from: /home/adrian/.config/zanata.ini > zanata server: https://translate.zanata.org/zanata > zanata python client version: 1.3.7-2-g4e29, zanata server API version: > 1.7.0 > Project: subscription-manager > Version: 1.1.X > Username: alikins > Source language: en-US > Copy previous translations:True > PO directory (originals):. > Importing source documents only > > Pushing the content of ./keys.pot to server: > Traceback (most recent call last): > File "/usr/bin/zanata", line 25, in > zanata.run() > File > "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/zanata.py", > line 945, in run > program_name=os.path.split(sys.argv[0])[1], > File > "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/command.py", > line 339, in handle_program > command(command_options, args) > File > "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/zanata.py", > line 800, in push > command.run(command_options, args) > File > "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/pushcmd.py", > line 483, in run > zanatacmd.push_command(filelist, tmlfolder, project_id, version_id, > copytrans, plural_support) > File > "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/zanatacmd.py", > line 396, in push_command > result = self.zanata_resource.documents.commit_template(project_id, > iteration_id, body, copytrans) > File > "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/zanatalib/docservice.py", > line 110, in commit_template > raise UnavailableServiceError('Error 503', 'Service Temporarily > Unavailable') > zanataclient.zanatalib.error.UnavailableServiceError: Error 503 - > Service Temporarily Unavailable > > > On 09/11/2012 06:38 AM, Ivan Ne?as wrote: >> On 09/11/2012 12:17 PM, Ivan Ne?as wrote: >> >> I've tried running it with --disable-ssl-cert, and it seems it works >> now. Only one strange thing: when I uploaded the pot file for project >> cfse-cli version 1.1, most of the translations was reused from >> previous version. But with cfse project, there is 0% translated, even >> if there are many common strings. >> >> It's true, that the first successful try was run with --no-copytrans >> option, but then I've rerun it again without this option, overriding >> the orignal document. Any help on this? >> >> >> -- Ivan >>> Hello, >>> >>> I'm trying to upload my localization files to zanata, but getting 500 >>> or 503 errors, python client version 1.3.11 (fails alwo with 1.3.5) >>> anyone experienced similar behavior lately? >>> >>> I was getting similar errors yesterday, today I was able to >>> successfully push po for one project, but still failing for another >>> (a bit larger one) >>> >>> zanata po push --srcdir . >>> Loading zanata project config from: >>> /root/system-engine/src/locale/zanata.xml >>> Loading zanata user config from: /root/.config/zanata.ini >>> zanata server: https://translate.zanata.org/zanata >>> zanata python client version: 1.3.11, zanata server API version: 1.7.0 >>> Project: cfse >>> Version: 1.1 >>> Username: inecas >>> Source language: en-US >>> Reuse previous translation on server:True >>> PO directory (originals):. >>> Importing source documents only >>> >>> Pushing the content of ./app.pot to server: >>> error: Error 500 - JBoss Web/2.1.12.GA-patch-03 - >>> Error repor >>> t >>>

HTTP S >>> tatus 500 -

type Status >>> report

>>>

message

description The server >>> encountered an >>> internal error () that prevented it from fulfilling this >>> request.

>> e="1" noshade="noshade">

JBoss >>> Web/2.1.12.GA-patch-03

>>> Please take a reference in >>> https://github.com/zanata/zanata/wiki/Python-Client-T >>> roubleshooting >>> r >>> >>> Nothing from the TroubleShooting guide helped, I've also tried >>> -no-copytrans option, with no success. >>> >>> -- Ivan >> >> > > _______________________________________________ > zanata-users mailing list > zanata-users at redhat.com > https://www.redhat.com/mailman/listinfo/zanata-users -- Sean Flanigan Senior Software Engineer Engineering - Internationalisation Red Hat -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 554 bytes Desc: OpenPGP digital signature URL: From bkearney at redhat.com Fri Sep 21 12:14:27 2012 From: bkearney at redhat.com (Bryan Kearney) Date: Fri, 21 Sep 2012 08:14:27 -0400 Subject: [zanata-users] Getting 500 Internal server error when pushing the pot file. In-Reply-To: <505C01F4.6010204@redhat.com> References: <504F0FCB.3020802@redhat.com> <504F148D.9000108@redhat.com> <505A2068.8000805@redhat.com> <505C01F4.6010204@redhat.com> Message-ID: <505C5A23.4070103@redhat.com> Is there a list we should be monitoring to note when changes like this are made? Or, did we miss things? It seems like the client is very fragile, and server upgrades are not backwards compatible. -- bk On 09/21/2012 01:58 AM, Sean Flanigan wrote: > Hi Adrian, Ivan, > > Disabling copyTrans can help, but I would recommend switching from the > Python client to the latest version (1.7.1) of the Zanata Maven client, > if you can. It splits source documents into multiple batches, to avoid > overwhelming the server. > > You may need to install Apache Maven, and then you can find a basic > pom.xml file here (put it in your project directory, along with zanata.xml): > https://github.com/zanata/zanata/wiki/Zanata-Maven-Integration > > Note that you may need to change the srcDir option in the pom file, > although you (Adrian) seem to be using current directory ("."), which is > the default value. > > And I would recommend putting gettext > (substitute your project type) into your zanata.xml, to save specifying > it on the command line. > > Once you have all of that set up, pushing source documents should be as > easy as: > $ mvn zanata:push > > and pulling: > $ mvn zanata:pull > > Sean. > > > > > On 2012-09-20 05:43, Adrian Likins wrote: >> I seem to be running into a similar issue, though I'm consistently >> getting 503's >> >> Things to note: this is on a new "version" (1.1.x of >> subscription-manager project) >> while attempting to do the initial push to zanata >> >> using: >> zanata python client version: 1.3.7-2-g4e29 >> (on rhel6.3(ish)) >> >> [adrian at dhcp231-28 po (master *)]$ zanata push --project-type gettext >> --srcdir . >> Loading zanata project config from: >> /home/adrian/subscription-manager/po/zanata.xml >> Loading zanata user config from: /home/adrian/.config/zanata.ini >> zanata server: https://translate.zanata.org/zanata >> zanata python client version: 1.3.7-2-g4e29, zanata server API version: >> 1.7.0 >> Project: subscription-manager >> Version: 1.1.X >> Username: alikins >> Source language: en-US >> Copy previous translations:True >> PO directory (originals):. >> Importing source documents only >> >> Pushing the content of ./keys.pot to server: >> Traceback (most recent call last): >> File "/usr/bin/zanata", line 25, in >> zanata.run() >> File >> "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/zanata.py", >> line 945, in run >> program_name=os.path.split(sys.argv[0])[1], >> File >> "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/command.py", >> line 339, in handle_program >> command(command_options, args) >> File >> "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/zanata.py", >> line 800, in push >> command.run(command_options, args) >> File >> "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/pushcmd.py", >> line 483, in run >> zanatacmd.push_command(filelist, tmlfolder, project_id, version_id, >> copytrans, plural_support) >> File >> "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/zanatacmd.py", >> line 396, in push_command >> result = self.zanata_resource.documents.commit_template(project_id, >> iteration_id, body, copytrans) >> File >> "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/zanatalib/docservice.py", >> line 110, in commit_template >> raise UnavailableServiceError('Error 503', 'Service Temporarily >> Unavailable') >> zanataclient.zanatalib.error.UnavailableServiceError: Error 503 - >> Service Temporarily Unavailable >> >> >> On 09/11/2012 06:38 AM, Ivan Ne?as wrote: >>> On 09/11/2012 12:17 PM, Ivan Ne?as wrote: >>> >>> I've tried running it with --disable-ssl-cert, and it seems it works >>> now. Only one strange thing: when I uploaded the pot file for project >>> cfse-cli version 1.1, most of the translations was reused from >>> previous version. But with cfse project, there is 0% translated, even >>> if there are many common strings. >>> >>> It's true, that the first successful try was run with --no-copytrans >>> option, but then I've rerun it again without this option, overriding >>> the orignal document. Any help on this? >>> >>> >>> -- Ivan >>>> Hello, >>>> >>>> I'm trying to upload my localization files to zanata, but getting 500 >>>> or 503 errors, python client version 1.3.11 (fails alwo with 1.3.5) >>>> anyone experienced similar behavior lately? >>>> >>>> I was getting similar errors yesterday, today I was able to >>>> successfully push po for one project, but still failing for another >>>> (a bit larger one) >>>> >>>> zanata po push --srcdir . >>>> Loading zanata project config from: >>>> /root/system-engine/src/locale/zanata.xml >>>> Loading zanata user config from: /root/.config/zanata.ini >>>> zanata server: https://translate.zanata.org/zanata >>>> zanata python client version: 1.3.11, zanata server API version: 1.7.0 >>>> Project: cfse >>>> Version: 1.1 >>>> Username: inecas >>>> Source language: en-US >>>> Reuse previous translation on server:True >>>> PO directory (originals):. >>>> Importing source documents only >>>> >>>> Pushing the content of ./app.pot to server: >>>> error: Error 500 - JBoss Web/2.1.12.GA-patch-03 - >>>> Error repor >>>> t >>>>

HTTP S >>>> tatus 500 -

type Status >>>> report

>>>>

message

description The server >>>> encountered an >>>> internal error () that prevented it from fulfilling this >>>> request.

>>> e="1" noshade="noshade">

JBoss >>>> Web/2.1.12.GA-patch-03

>>>> Please take a reference in >>>> https://github.com/zanata/zanata/wiki/Python-Client-T >>>> roubleshooting >>>> r >>>> >>>> Nothing from the TroubleShooting guide helped, I've also tried >>>> -no-copytrans option, with no success. >>>> >>>> -- Ivan >>> >>> >> >> _______________________________________________ >> zanata-users mailing list >> zanata-users at redhat.com >> https://www.redhat.com/mailman/listinfo/zanata-users > > > > > _______________________________________________ > zanata-users mailing list > zanata-users at redhat.com > https://www.redhat.com/mailman/listinfo/zanata-users > From alikins at redhat.com Fri Sep 21 13:12:55 2012 From: alikins at redhat.com (Adrian Likins) Date: Fri, 21 Sep 2012 09:12:55 -0400 Subject: [zanata-users] error: Can't find pot file for : on server In-Reply-To: <505BD1A0.40002@redhat.com> References: <505B53CE.4020704@redhat.com> <505BD1A0.40002@redhat.com> Message-ID: <505C67D7.9050108@redhat.com> On 09/20/2012 10:32 PM, Sean Flanigan wrote: > It may depend on how the ':' file got there in the first place, No idea on that. > but > assuming that problem is fixed[1], you should just have to to push the > pot file again. If the only file pushed is 'keys', it should > automatically delete the ':' file. Doesn't seem to be fixed, the ':' is still there, for example: https://translate.zanata.org/zanata/iteration/files/subscription-manager/1.0.X/de-DE Trying to push again results in: Loading zanata user config from: /home/adrian/.config/zanata.ini zanata server: https://translate.zanata.org/zanata zanata python client version: 1.3.7-2-g4e29, zanata server API version: 1.7.0 Project: subscription-manager Version: 1.0.X Username: alikins Source language: en-US Copy previous translations:True PO directory (originals):. Importing source documents only This will overwrite/delete any existing documents on the server. Are you sure (y/n)?y Delete the : error: Error 404 - The requested resource is not available No ':' files local, zanata.xml looks ok. Sending you the repo. Adrian > > BTW, I recommend editing zanata.xml to include this: > gettext > That way you won't need to keep specifying "--project-type gettext" > > Sean. > > [1] If not, point me at your source repo/branch and zanata.xml, and I'll > see if I can work out what happened. > > > On 2012-09-21 03:35, Adrian Likins wrote: >> While trying to pull translations for subscription-manager 1.0.x branch: >> >> [adrian at dhcp231-28 po (zanata *)]$ zanata pull --project-type gettext >> Loading zanata project config from: >> /home/adrian/src/subscription-manager-internal/po/zanata.xml >> Loading zanata user config from: /home/adrian/.config/zanata.ini >> zanata server: https://translate.zanata.org/zanata >> zanata python client version: 1.3.7-2-g4e29, zanata server API version: >> 1.7.0 >> Project: subscription-manager >> Version: 1.0.X >> Username: alikins >> >> Fetching the content of : from Zanata server: >> error: Can't find pot file for : on server >> >> >> Looking at the project, it does appear to think there is >> a document called ':', with no .pot or translations. >> >> Is there a way to remove that? Or, is there a way for >> the client to work around it? >> >> Adrian >> >> _______________________________________________ >> zanata-users mailing list >> zanata-users at redhat.com >> https://www.redhat.com/mailman/listinfo/zanata-users > From alikins at redhat.com Fri Sep 21 19:38:03 2012 From: alikins at redhat.com (Adrian Likins) Date: Fri, 21 Sep 2012 15:38:03 -0400 Subject: [zanata-users] error: Can't find pot file for : on server In-Reply-To: <505C67D7.9050108@redhat.com> References: <505B53CE.4020704@redhat.com> <505BD1A0.40002@redhat.com> <505C67D7.9050108@redhat.com> Message-ID: <505CC21B.3020102@redhat.com> On 09/21/2012 09:12 AM, Adrian Likins wrote: > On 09/20/2012 10:32 PM, Sean Flanigan wrote: >> It may depend on how the ':' file got there in the first place, > > No idea on that. > I kind of worked around this by hacking the client to ignore the bogus file, and not trying to delete it. Looking closer, there appears to be some url encoding issues. The client asks for the file lists and get's one of the files listed as ': ' (colon, space). Then it tries to delete that file if it's not there client side, but makes a request like: "https://translate.zanata.org/zanata/seam/resource/restv1/projects/p/subscription-manager/iterations/i/1.0.X/r/: ?ext=gettext&ext=comment" ^ space which 404's, and then the client throws exceptions and stops. (still fuzzy on how that file got there, it doesn't seem to have ever been in the git history, but it could have easily been created by accident and pulled in by 'push' at some point) However, it doesn't seem like what I thought was correct url encoding for ': ', so if someone with privs could delete that... Adrian From sflaniga at redhat.com Mon Sep 24 02:02:06 2012 From: sflaniga at redhat.com (Sean Flanigan) Date: Mon, 24 Sep 2012 12:02:06 +1000 Subject: [zanata-users] Getting 500 Internal server error when pushing the pot file. In-Reply-To: <505C5A23.4070103@redhat.com> References: <504F0FCB.3020802@redhat.com> <504F148D.9000108@redhat.com> <505A2068.8000805@redhat.com> <505C01F4.6010204@redhat.com> <505C5A23.4070103@redhat.com> Message-ID: <505FBF1E.5050606@redhat.com> Not really, we have https://twitter.com/ZanataTM and http://blog-zanatatm.rhcloud.com/, but they're somewhat out of date right now. This problem isn't a client/server incompatibility; unfortunately it's simply a performance bug in the server. We're working on it, but in the meantime using the newer client is a suggested workaround. On 2012-09-21 22:14, Bryan Kearney wrote: > Is there a list we should be monitoring to note when changes like this > are made? Or, did we miss things? It seems like the client is very > fragile, and server upgrades are not backwards compatible. > > -- bk > > On 09/21/2012 01:58 AM, Sean Flanigan wrote: >> Hi Adrian, Ivan, >> >> Disabling copyTrans can help, but I would recommend switching from the >> Python client to the latest version (1.7.1) of the Zanata Maven client, >> if you can. It splits source documents into multiple batches, to avoid >> overwhelming the server. >> >> You may need to install Apache Maven, and then you can find a basic >> pom.xml file here (put it in your project directory, along with zanata.xml): >> https://github.com/zanata/zanata/wiki/Zanata-Maven-Integration >> >> Note that you may need to change the srcDir option in the pom file, >> although you (Adrian) seem to be using current directory ("."), which is >> the default value. >> >> And I would recommend putting gettext >> (substitute your project type) into your zanata.xml, to save specifying >> it on the command line. >> >> Once you have all of that set up, pushing source documents should be as >> easy as: >> $ mvn zanata:push >> >> and pulling: >> $ mvn zanata:pull >> >> Sean. >> >> >> >> >> On 2012-09-20 05:43, Adrian Likins wrote: >>> I seem to be running into a similar issue, though I'm consistently >>> getting 503's >>> >>> Things to note: this is on a new "version" (1.1.x of >>> subscription-manager project) >>> while attempting to do the initial push to zanata >>> >>> using: >>> zanata python client version: 1.3.7-2-g4e29 >>> (on rhel6.3(ish)) >>> >>> [adrian at dhcp231-28 po (master *)]$ zanata push --project-type gettext >>> --srcdir . >>> Loading zanata project config from: >>> /home/adrian/subscription-manager/po/zanata.xml >>> Loading zanata user config from: /home/adrian/.config/zanata.ini >>> zanata server: https://translate.zanata.org/zanata >>> zanata python client version: 1.3.7-2-g4e29, zanata server API version: >>> 1.7.0 >>> Project: subscription-manager >>> Version: 1.1.X >>> Username: alikins >>> Source language: en-US >>> Copy previous translations:True >>> PO directory (originals):. >>> Importing source documents only >>> >>> Pushing the content of ./keys.pot to server: >>> Traceback (most recent call last): >>> File "/usr/bin/zanata", line 25, in >>> zanata.run() >>> File >>> "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/zanata.py", >>> line 945, in run >>> program_name=os.path.split(sys.argv[0])[1], >>> File >>> "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/command.py", >>> line 339, in handle_program >>> command(command_options, args) >>> File >>> "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/zanata.py", >>> line 800, in push >>> command.run(command_options, args) >>> File >>> "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/pushcmd.py", >>> line 483, in run >>> zanatacmd.push_command(filelist, tmlfolder, project_id, version_id, >>> copytrans, plural_support) >>> File >>> "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/zanatacmd.py", >>> line 396, in push_command >>> result = self.zanata_resource.documents.commit_template(project_id, >>> iteration_id, body, copytrans) >>> File >>> "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/zanatalib/docservice.py", >>> line 110, in commit_template >>> raise UnavailableServiceError('Error 503', 'Service Temporarily >>> Unavailable') >>> zanataclient.zanatalib.error.UnavailableServiceError: Error 503 - >>> Service Temporarily Unavailable >>> >>> >>> On 09/11/2012 06:38 AM, Ivan Ne?as wrote: >>>> On 09/11/2012 12:17 PM, Ivan Ne?as wrote: >>>> >>>> I've tried running it with --disable-ssl-cert, and it seems it works >>>> now. Only one strange thing: when I uploaded the pot file for project >>>> cfse-cli version 1.1, most of the translations was reused from >>>> previous version. But with cfse project, there is 0% translated, even >>>> if there are many common strings. >>>> >>>> It's true, that the first successful try was run with --no-copytrans >>>> option, but then I've rerun it again without this option, overriding >>>> the orignal document. Any help on this? >>>> >>>> >>>> -- Ivan >>>>> Hello, >>>>> >>>>> I'm trying to upload my localization files to zanata, but getting 500 >>>>> or 503 errors, python client version 1.3.11 (fails alwo with 1.3.5) >>>>> anyone experienced similar behavior lately? >>>>> >>>>> I was getting similar errors yesterday, today I was able to >>>>> successfully push po for one project, but still failing for another >>>>> (a bit larger one) >>>>> >>>>> zanata po push --srcdir . >>>>> Loading zanata project config from: >>>>> /root/system-engine/src/locale/zanata.xml >>>>> Loading zanata user config from: /root/.config/zanata.ini >>>>> zanata server: https://translate.zanata.org/zanata >>>>> zanata python client version: 1.3.11, zanata server API version: 1.7.0 >>>>> Project: cfse >>>>> Version: 1.1 >>>>> Username: inecas >>>>> Source language: en-US >>>>> Reuse previous translation on server:True >>>>> PO directory (originals):. >>>>> Importing source documents only >>>>> >>>>> Pushing the content of ./app.pot to server: >>>>> error: Error 500 - JBoss Web/2.1.12.GA-patch-03 - >>>>> Error repor >>>>> t >>>>>

HTTP S >>>>> tatus 500 -

type Status >>>>> report

>>>>>

message

description The server >>>>> encountered an >>>>> internal error () that prevented it from fulfilling this >>>>> request.

>>>> e="1" noshade="noshade">

JBoss >>>>> Web/2.1.12.GA-patch-03

>>>>> Please take a reference in >>>>> https://github.com/zanata/zanata/wiki/Python-Client-T >>>>> roubleshooting >>>>> r >>>>> >>>>> Nothing from the TroubleShooting guide helped, I've also tried >>>>> -no-copytrans option, with no success. >>>>> >>>>> -- Ivan >>>> >>>> >>> >>> _______________________________________________ >>> zanata-users mailing list >>> zanata-users at redhat.com >>> https://www.redhat.com/mailman/listinfo/zanata-users >> >> >> >> >> _______________________________________________ >> zanata-users mailing list >> zanata-users at redhat.com >> https://www.redhat.com/mailman/listinfo/zanata-users >> > > _______________________________________________ > zanata-users mailing list > zanata-users at redhat.com > https://www.redhat.com/mailman/listinfo/zanata-users -- Sean Flanigan Senior Software Engineer Engineering - Internationalisation Red Hat -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 554 bytes Desc: OpenPGP digital signature URL: From bkearney at redhat.com Mon Sep 24 10:22:00 2012 From: bkearney at redhat.com (Bryan Kearney) Date: Mon, 24 Sep 2012 06:22:00 -0400 Subject: [zanata-users] Getting 500 Internal server error when pushing the pot file. In-Reply-To: <505FBF1E.5050606@redhat.com> References: <504F0FCB.3020802@redhat.com> <504F148D.9000108@redhat.com> <505A2068.8000805@redhat.com> <505C01F4.6010204@redhat.com> <505C5A23.4070103@redhat.com> <505FBF1E.5050606@redhat.com> Message-ID: <50603448.90602@redhat.com> OK.. thanks. -- bk On 09/23/2012 10:02 PM, Sean Flanigan wrote: > > Not really, we have https://twitter.com/ZanataTM and > http://blog-zanatatm.rhcloud.com/, but they're somewhat out of date > right now. > > This problem isn't a client/server incompatibility; unfortunately it's > simply a performance bug in the server. We're working on it, but in the > meantime using the newer client is a suggested workaround. > > > On 2012-09-21 22:14, Bryan Kearney wrote: >> Is there a list we should be monitoring to note when changes like this >> are made? Or, did we miss things? It seems like the client is very >> fragile, and server upgrades are not backwards compatible. >> >> -- bk >> >> On 09/21/2012 01:58 AM, Sean Flanigan wrote: >>> Hi Adrian, Ivan, >>> >>> Disabling copyTrans can help, but I would recommend switching from the >>> Python client to the latest version (1.7.1) of the Zanata Maven client, >>> if you can. It splits source documents into multiple batches, to avoid >>> overwhelming the server. >>> >>> You may need to install Apache Maven, and then you can find a basic >>> pom.xml file here (put it in your project directory, along with zanata.xml): >>> https://github.com/zanata/zanata/wiki/Zanata-Maven-Integration >>> >>> Note that you may need to change the srcDir option in the pom file, >>> although you (Adrian) seem to be using current directory ("."), which is >>> the default value. >>> >>> And I would recommend putting gettext >>> (substitute your project type) into your zanata.xml, to save specifying >>> it on the command line. >>> >>> Once you have all of that set up, pushing source documents should be as >>> easy as: >>> $ mvn zanata:push >>> >>> and pulling: >>> $ mvn zanata:pull >>> >>> Sean. >>> >>> >>> >>> >>> On 2012-09-20 05:43, Adrian Likins wrote: >>>> I seem to be running into a similar issue, though I'm consistently >>>> getting 503's >>>> >>>> Things to note: this is on a new "version" (1.1.x of >>>> subscription-manager project) >>>> while attempting to do the initial push to zanata >>>> >>>> using: >>>> zanata python client version: 1.3.7-2-g4e29 >>>> (on rhel6.3(ish)) >>>> >>>> [adrian at dhcp231-28 po (master *)]$ zanata push --project-type gettext >>>> --srcdir . >>>> Loading zanata project config from: >>>> /home/adrian/subscription-manager/po/zanata.xml >>>> Loading zanata user config from: /home/adrian/.config/zanata.ini >>>> zanata server: https://translate.zanata.org/zanata >>>> zanata python client version: 1.3.7-2-g4e29, zanata server API version: >>>> 1.7.0 >>>> Project: subscription-manager >>>> Version: 1.1.X >>>> Username: alikins >>>> Source language: en-US >>>> Copy previous translations:True >>>> PO directory (originals):. >>>> Importing source documents only >>>> >>>> Pushing the content of ./keys.pot to server: >>>> Traceback (most recent call last): >>>> File "/usr/bin/zanata", line 25, in >>>> zanata.run() >>>> File >>>> "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/zanata.py", >>>> line 945, in run >>>> program_name=os.path.split(sys.argv[0])[1], >>>> File >>>> "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/command.py", >>>> line 339, in handle_program >>>> command(command_options, args) >>>> File >>>> "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/zanata.py", >>>> line 800, in push >>>> command.run(command_options, args) >>>> File >>>> "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/pushcmd.py", >>>> line 483, in run >>>> zanatacmd.push_command(filelist, tmlfolder, project_id, version_id, >>>> copytrans, plural_support) >>>> File >>>> "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/zanatacmd.py", >>>> line 396, in push_command >>>> result = self.zanata_resource.documents.commit_template(project_id, >>>> iteration_id, body, copytrans) >>>> File >>>> "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/zanatalib/docservice.py", >>>> line 110, in commit_template >>>> raise UnavailableServiceError('Error 503', 'Service Temporarily >>>> Unavailable') >>>> zanataclient.zanatalib.error.UnavailableServiceError: Error 503 - >>>> Service Temporarily Unavailable >>>> >>>> >>>> On 09/11/2012 06:38 AM, Ivan Ne?as wrote: >>>>> On 09/11/2012 12:17 PM, Ivan Ne?as wrote: >>>>> >>>>> I've tried running it with --disable-ssl-cert, and it seems it works >>>>> now. Only one strange thing: when I uploaded the pot file for project >>>>> cfse-cli version 1.1, most of the translations was reused from >>>>> previous version. But with cfse project, there is 0% translated, even >>>>> if there are many common strings. >>>>> >>>>> It's true, that the first successful try was run with --no-copytrans >>>>> option, but then I've rerun it again without this option, overriding >>>>> the orignal document. Any help on this? >>>>> >>>>> >>>>> -- Ivan >>>>>> Hello, >>>>>> >>>>>> I'm trying to upload my localization files to zanata, but getting 500 >>>>>> or 503 errors, python client version 1.3.11 (fails alwo with 1.3.5) >>>>>> anyone experienced similar behavior lately? >>>>>> >>>>>> I was getting similar errors yesterday, today I was able to >>>>>> successfully push po for one project, but still failing for another >>>>>> (a bit larger one) >>>>>> >>>>>> zanata po push --srcdir . >>>>>> Loading zanata project config from: >>>>>> /root/system-engine/src/locale/zanata.xml >>>>>> Loading zanata user config from: /root/.config/zanata.ini >>>>>> zanata server: https://translate.zanata.org/zanata >>>>>> zanata python client version: 1.3.11, zanata server API version: 1.7.0 >>>>>> Project: cfse >>>>>> Version: 1.1 >>>>>> Username: inecas >>>>>> Source language: en-US >>>>>> Reuse previous translation on server:True >>>>>> PO directory (originals):. >>>>>> Importing source documents only >>>>>> >>>>>> Pushing the content of ./app.pot to server: >>>>>> error: Error 500 - JBoss Web/2.1.12.GA-patch-03 - >>>>>> Error repor >>>>>> t >>>>>>

HTTP S >>>>>> tatus 500 -

type Status >>>>>> report

>>>>>>

message

description The server >>>>>> encountered an >>>>>> internal error () that prevented it from fulfilling this >>>>>> request.

>>>>> e="1" noshade="noshade">

JBoss >>>>>> Web/2.1.12.GA-patch-03

>>>>>> Please take a reference in >>>>>> https://github.com/zanata/zanata/wiki/Python-Client-T >>>>>> roubleshooting >>>>>> r >>>>>> >>>>>> Nothing from the TroubleShooting guide helped, I've also tried >>>>>> -no-copytrans option, with no success. >>>>>> >>>>>> -- Ivan >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> zanata-users mailing list >>>> zanata-users at redhat.com >>>> https://www.redhat.com/mailman/listinfo/zanata-users >>> >>> >>> >>> >>> _______________________________________________ >>> zanata-users mailing list >>> zanata-users at redhat.com >>> https://www.redhat.com/mailman/listinfo/zanata-users >>> >> >> _______________________________________________ >> zanata-users mailing list >> zanata-users at redhat.com >> https://www.redhat.com/mailman/listinfo/zanata-users > > From sflaniga at redhat.com Wed Sep 26 03:43:02 2012 From: sflaniga at redhat.com (Sean Flanigan) Date: Wed, 26 Sep 2012 13:43:02 +1000 Subject: [zanata-users] Getting 500 Internal server error when pushing the pot file. In-Reply-To: <505C01F4.6010204@redhat.com> References: <504F0FCB.3020802@redhat.com> <504F148D.9000108@redhat.com> <505A2068.8000805@redhat.com> <505C01F4.6010204@redhat.com> Message-ID: <506279C6.1020308@redhat.com> Correction, the new client only splits *target* documents into batches. If source documents are the problem, right now your best bet is to use --no-copytrans as suggested by Ivan. This does mean that existing translations won't be filled in, but note: after pushing with CopyTrans disabled, the project maintainer can run CopyTrans via the web UI on the project version page. This currently works best if the filenames stay the same from one project version to the next. (Due to a bug [1] in Zanata 1.7.1, if the filenames have changed, the copied translations will be marked fuzzy regardless of the CopyTrans options you choose. This will be fixed in 1.7.3.) [1] https://bugzilla.redhat.com/show_bug.cgi?id=856413 On 2012-09-21 15:58, Sean Flanigan wrote: > Hi Adrian, Ivan, > > Disabling copyTrans can help, but I would recommend switching from the > Python client to the latest version (1.7.1) of the Zanata Maven client, > if you can. It splits source documents into multiple batches, to avoid > overwhelming the server. > > You may need to install Apache Maven, and then you can find a basic > pom.xml file here (put it in your project directory, along with zanata.xml): > https://github.com/zanata/zanata/wiki/Zanata-Maven-Integration > > Note that you may need to change the srcDir option in the pom file, > although you (Adrian) seem to be using current directory ("."), which is > the default value. > > And I would recommend putting gettext > (substitute your project type) into your zanata.xml, to save specifying > it on the command line. > > Once you have all of that set up, pushing source documents should be as > easy as: > $ mvn zanata:push > > and pulling: > $ mvn zanata:pull > > Sean. > > > > > On 2012-09-20 05:43, Adrian Likins wrote: >> I seem to be running into a similar issue, though I'm consistently >> getting 503's >> >> Things to note: this is on a new "version" (1.1.x of >> subscription-manager project) >> while attempting to do the initial push to zanata >> >> using: >> zanata python client version: 1.3.7-2-g4e29 >> (on rhel6.3(ish)) >> >> [adrian at dhcp231-28 po (master *)]$ zanata push --project-type gettext >> --srcdir . >> Loading zanata project config from: >> /home/adrian/subscription-manager/po/zanata.xml >> Loading zanata user config from: /home/adrian/.config/zanata.ini >> zanata server: https://translate.zanata.org/zanata >> zanata python client version: 1.3.7-2-g4e29, zanata server API version: >> 1.7.0 >> Project: subscription-manager >> Version: 1.1.X >> Username: alikins >> Source language: en-US >> Copy previous translations:True >> PO directory (originals):. >> Importing source documents only >> >> Pushing the content of ./keys.pot to server: >> Traceback (most recent call last): >> File "/usr/bin/zanata", line 25, in >> zanata.run() >> File >> "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/zanata.py", >> line 945, in run >> program_name=os.path.split(sys.argv[0])[1], >> File >> "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/command.py", >> line 339, in handle_program >> command(command_options, args) >> File >> "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/zanata.py", >> line 800, in push >> command.run(command_options, args) >> File >> "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/pushcmd.py", >> line 483, in run >> zanatacmd.push_command(filelist, tmlfolder, project_id, version_id, >> copytrans, plural_support) >> File >> "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/zanatacmd.py", >> line 396, in push_command >> result = self.zanata_resource.documents.commit_template(project_id, >> iteration_id, body, copytrans) >> File >> "/usr/lib/python2.6/site-packages/zanata_python_client-1.3.7_2_g4e29-py2.6.egg/zanataclient/zanatalib/docservice.py", >> line 110, in commit_template >> raise UnavailableServiceError('Error 503', 'Service Temporarily >> Unavailable') >> zanataclient.zanatalib.error.UnavailableServiceError: Error 503 - >> Service Temporarily Unavailable >> >> >> On 09/11/2012 06:38 AM, Ivan Ne?as wrote: >>> On 09/11/2012 12:17 PM, Ivan Ne?as wrote: >>> >>> I've tried running it with --disable-ssl-cert, and it seems it works >>> now. Only one strange thing: when I uploaded the pot file for project >>> cfse-cli version 1.1, most of the translations was reused from >>> previous version. But with cfse project, there is 0% translated, even >>> if there are many common strings. >>> >>> It's true, that the first successful try was run with --no-copytrans >>> option, but then I've rerun it again without this option, overriding >>> the orignal document. Any help on this? >>> >>> >>> -- Ivan >>>> Hello, >>>> >>>> I'm trying to upload my localization files to zanata, but getting 500 >>>> or 503 errors, python client version 1.3.11 (fails alwo with 1.3.5) >>>> anyone experienced similar behavior lately? >>>> >>>> I was getting similar errors yesterday, today I was able to >>>> successfully push po for one project, but still failing for another >>>> (a bit larger one) >>>> >>>> zanata po push --srcdir . >>>> Loading zanata project config from: >>>> /root/system-engine/src/locale/zanata.xml >>>> Loading zanata user config from: /root/.config/zanata.ini >>>> zanata server: https://translate.zanata.org/zanata >>>> zanata python client version: 1.3.11, zanata server API version: 1.7.0 >>>> Project: cfse >>>> Version: 1.1 >>>> Username: inecas >>>> Source language: en-US >>>> Reuse previous translation on server:True >>>> PO directory (originals):. >>>> Importing source documents only >>>> >>>> Pushing the content of ./app.pot to server: >>>> error: Error 500 - JBoss Web/2.1.12.GA-patch-03 - >>>> Error repor >>>> t >>>>

HTTP S >>>> tatus 500 -

type Status >>>> report

>>>>

message

description The server >>>> encountered an >>>> internal error () that prevented it from fulfilling this >>>> request.

>>> e="1" noshade="noshade">