From bugzilla at redhat.com Sun Dec 1 19:59:59 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 01 Dec 2013 19:59:59 +0000 Subject: [zanata-bugs] [Bug 1023227] Add language member request email contains string jsf.email.joinrequest.RoleRequested In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1023227 --- Comment #1 from Alex Eng --- Pull request: https://github.com/zanata/zanata-server/pull/306 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=M85lAK7dZb&a=cc_unsubscribe From bugzilla at redhat.com Sun Dec 1 20:00:41 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 01 Dec 2013 20:00:41 +0000 Subject: [zanata-bugs] [Bug 995324] "Agree to the Terms of Use" should be displayed looks relevant to users that sign up with OpenId In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=995324 --- Comment #15 from Alex Eng --- Pull request: https://github.com/zanata/zanata-server/pull/305 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=tE38BPp48c&a=cc_unsubscribe From bugzilla at redhat.com Sun Dec 1 23:37:30 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 01 Dec 2013 23:37:30 +0000 Subject: [zanata-bugs] [Bug 1035959] [RFE] Zanata should recognise file types individually, not from the target project In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1035959 Carlos Munoz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |camunoz at redhat.com --- Comment #2 from Carlos Munoz --- I think eventually that's where we want to go. As for a migration strategy, maybe we still need to support both ways of uploading, and we hide the project type. Users may continue to use the 'legacy' way of uploading files, with their last stored project type (now hidden or non-editable); but if they want to change to a newer client, they would start using the 'new' upload mechanism that Sean describes. This comes with a few technical challenges: We need to find a way to process files (any format) from as they are streamed from the client (like we do with TMX), this will prevent http timeouts, and we still need to break up transactions for larger files. The alternative is to push the file first and then either keep pinging the server for a result (what we currently do when pushing PO or property files), or use comet or some kind of long polling. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=cvxwZRKf8z&a=cc_unsubscribe From bugzilla at redhat.com Mon Dec 2 00:15:31 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 02 Dec 2013 00:15:31 +0000 Subject: [zanata-bugs] [Bug 1036435] New: RFE: Upgrade to Liquibase 3.x Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1036435 Bug ID: 1036435 Summary: RFE: Upgrade to Liquibase 3.x Product: Zanata Version: 3.1 Component: DatabaseChange Assignee: camunoz at redhat.com Reporter: camunoz at redhat.com QA Contact: zanata-qa at redhat.com CC: zanata-bugs at redhat.com Description of problem: Upgrade liquibase library to version 3.x Version-Release number of selected component (if applicable): 3.2 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=LGOV5JWZFr&a=cc_unsubscribe From bugzilla at redhat.com Mon Dec 2 00:20:39 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 02 Dec 2013 00:20:39 +0000 Subject: [zanata-bugs] [Bug 1036435] RFE: Upgrade to Liquibase 3.x In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1036435 Carlos Munoz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |POST -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=W7eiRStD8K&a=cc_unsubscribe From bugzilla at redhat.com Mon Dec 2 00:56:31 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 02 Dec 2013 00:56:31 +0000 Subject: [zanata-bugs] [Bug 1036435] RFE: Upgrade to Liquibase 3.x In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1036435 Sean Flanigan changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sflaniga at redhat.com --- Comment #1 from Sean Flanigan --- https://github.com/zanata/zanata-server/pull/308 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=aaRW6Jw2Ok&a=cc_unsubscribe From bugzilla at redhat.com Mon Dec 2 00:57:30 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 02 Dec 2013 00:57:30 +0000 Subject: [zanata-bugs] [Bug 1036435] RFE: Upgrade to Liquibase 3.x In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1036435 --- Comment #2 from Carlos Munoz --- See Also: https://github.com/zanata/zanata-parent/pull/3 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=zzMTieeDt0&a=cc_unsubscribe From bugzilla at redhat.com Mon Dec 2 02:20:58 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 02 Dec 2013 02:20:58 +0000 Subject: [zanata-bugs] [Bug 1025093] Review and update "Signing Up" page for style and general language In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1025093 David O'Brien changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo? --- Comment #12 from David O'Brien --- Re Comment #11, we (generally, ECS) are aiming for a centralized database of terms that anyone in Red Hat can look up whenever they need to. We haven't settled on a system yet, but I'd prefer to make any sort of Zanata list part of an existing list rather starting a new one. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=gQj1zvroN5&a=cc_unsubscribe From bugzilla at redhat.com Mon Dec 2 06:07:18 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 02 Dec 2013 06:07:18 +0000 Subject: [zanata-bugs] [Bug 980670] [RFE] Add HTML as an input method to be translated In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=980670 David Mason changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED CC| |damason at redhat.com Assignee|irooskov at redhat.com |damason at redhat.com -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=dPjILC8nIz&a=cc_unsubscribe From bugzilla at redhat.com Mon Dec 2 06:30:37 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 02 Dec 2013 06:30:37 +0000 Subject: [zanata-bugs] [Bug 1036435] RFE: Upgrade to Liquibase 3.x In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1036435 Carlos Munoz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|POST |ON_QA --- Comment #3 from Carlos Munoz --- This was tested on both a new, empty database and on top of a Zanata 3.1 baseline database built with Liquibase 2.x. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=xjy4X4J86f&a=cc_unsubscribe From bugzilla at redhat.com Tue Dec 3 00:10:56 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 03 Dec 2013 00:10:56 +0000 Subject: [zanata-bugs] [Bug 1023227] Add language member request email contains string jsf.email.joinrequest.RoleRequested In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1023227 Alex Eng changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |ON_QA -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=z8JvIBMYhu&a=cc_unsubscribe From bugzilla at redhat.com Tue Dec 3 00:11:04 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 03 Dec 2013 00:11:04 +0000 Subject: [zanata-bugs] [Bug 995324] "Agree to the Terms of Use" should be displayed looks relevant to users that sign up with OpenId In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=995324 Alex Eng changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |ON_QA -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=kJAI9p2fAi&a=cc_unsubscribe From bugzilla at redhat.com Tue Dec 3 01:51:30 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 03 Dec 2013 01:51:30 +0000 Subject: [zanata-bugs] [Bug 1035959] [RFE] Zanata should recognise file types individually, not from the target project In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1035959 --- Comment #3 from Carlos Munoz --- Sean and I discussed this in a bit of detail and came up with a stage 1 for this: Extend the File rest service to support other types of files that are not currently processed using okapi (po, properties, xliff). The service would know how to process the files based on the file extension, as it happens right now. The current XML-based rest service to upload translations will still rely on the project type field, and consequently will still only support one file type. Did I miss anything Sean? -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=36I3UxJ7GV&a=cc_unsubscribe From bugzilla at redhat.com Tue Dec 3 02:08:19 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 03 Dec 2013 02:08:19 +0000 Subject: [zanata-bugs] [Bug 1035959] [RFE] Zanata should recognise file types individually, not from the target project In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1035959 --- Comment #4 from Sean Flanigan --- One minor thing: we also plan to have the client upload its idea of the project type, so that the server can store it (for projects where projectType is null). Also, we will have to make a big improvement to the client's support for File type projects. At present, File projects may not have any overlap between source and translation directories: translation directories are always completely separate from source directories, and the translated filename is the same as the source filename, but with a locale directory at the front. In other words, for a source file: src/abc/xyz.odt The translated files will be: translated/de/abc/xyz.odt translated/fr/abc/xyz.odt etc. That's okay for ODT files, but it won't work for .properties files, because the locale is expected to become part of the filename, not the directory name. So we may need a customisable way of specifying the template for the pathname. Also, when there is overlap between source and translated directories, you need a mechanism to avoid treating translated files as if they were source files. For instance, try to upload the files: abc/client_messages.properties abc/client_messages_de.properties As a Java programmer, I know the first one is a source file, and the second is a translation file, but telling them apart programatically is quite difficult. We have something implemented as part of the current Properties support (it uses the list of locales found in zanata.xml), but this would need to be adapted or reinvented to work with File projects. (Instead of looking at zanata.xml, perhaps we could see whether part of the filename "looks like" a locale code.) NB: these rules may need to differ between file types, since most file types don't use underscores to delimit locales. As a simplification, we could start by disallowing overlaps between source and translation, but this limitation will have to be removed before we can use File projects for a typical Java software project. We should check what other projects do to handle these problems. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=uG97I8bDEn&a=cc_unsubscribe From bugzilla at redhat.com Tue Dec 3 14:31:30 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 03 Dec 2013 14:31:30 +0000 Subject: [zanata-bugs] [Bug 1035959] [RFE] Zanata should recognise file types individually, not from the target project In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1035959 Ding-Yi Chen changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dchen at redhat.com --- Comment #5 from Ding-Yi Chen --- I have some experience on something like this when I develop zanata-util. One major issue I have encountered is that: without existing translation, there is no way of knowing that what to pull. For example: 1. Maintainer upload PROJ.pot 2. Translators translated into de and ja. When pulling, which one should the files be output: 1. de.po and ja.po (gettext) 2. de/PROJ.po ja/PROJ.po (podir) -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=qK1WS5xfGP&a=cc_unsubscribe From bugzilla at redhat.com Wed Dec 4 04:40:50 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 04 Dec 2013 04:40:50 +0000 Subject: [zanata-bugs] [Bug 1037920] New: Xml parser error on export obsolete project Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1037920 Bug ID: 1037920 Summary: Xml parser error on export obsolete project Product: Zanata Version: development Component: Component-Logic Severity: high Assignee: zanata-dev-internal at redhat.com Reporter: djansen at redhat.com QA Contact: zanata-qa at redhat.com CC: zanata-bugs at redhat.com Description of problem: If a project owner / admin views an obsolete project and presses "Export project to TMX" the are presented with the error: XML Parsing Error: syntax error Location: http://localhost:9898/zanata/rest/tm/projects/about-fedora Line Number 1, Column 1: Project 'about-fedora' not found. ^ Version-Release number of selected component (if applicable): 3.3 How reproducible: Easy always Steps to Reproduce: 1. Sign in as admin 2. Go to any obsolete project (make one Obsolete if need be) 3. Press "Export project to TMX" Actual results: Parser error Expected results: Perhaps the button should not be available. Additional info: -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=YMgMhqaZm6&a=cc_unsubscribe From bugzilla at redhat.com Wed Dec 4 05:18:05 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 04 Dec 2013 05:18:05 +0000 Subject: [zanata-bugs] [Bug 1035959] [RFE] Zanata should recognise file types individually, not from the target project In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1035959 --- Comment #6 from Sean Flanigan --- Exactly, that's why we need pathname templates. We may still need to keep some idea of the file types (similar to our current project type enumeration) so that we know which template to use for each file. So if the document type is "properties" we will use the standard template for properties files, which might be ${dirname}/${basename}_${locale}.properties, if the document type is "gettext" we use ${dirname}/${locale}.po, and if the document type is "podir" we use ${locale}/${dirname}/${basename}.po. In advanced cases, the user might need to specify the actual templates in zanata.xml, along with a way of associating files/directories with the right templates. And another thing to bear in mind: we need templates when parsing filenames for upload, as well as when generating files. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=gPS7Kv3b3j&a=cc_unsubscribe From bugzilla at redhat.com Wed Dec 4 05:18:06 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 04 Dec 2013 05:18:06 +0000 Subject: [zanata-bugs] [Bug 978072] RFE: integrate client with command-line tools (po4a for roff input/output) In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=978072 David Mason changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ON_QA CC| |damason at redhat.com -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=BihJSqmSx3&a=cc_unsubscribe From bugzilla at redhat.com Wed Dec 4 05:27:08 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 04 Dec 2013 05:27:08 +0000 Subject: [zanata-bugs] [Bug 1037925] New: Search Projects field not character limited Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1037925 Bug ID: 1037925 Summary: Search Projects field not character limited Product: Zanata Version: development Component: Performance Severity: high Assignee: zanata-dev-internal at redhat.com Reporter: djansen at redhat.com QA Contact: zanata-qa at redhat.com CC: zanata-bugs at redhat.com Created attachment 832415 --> https://bugzilla.redhat.com/attachment.cgi?id=832415&action=edit Screenshot Description of problem: The Search Projects field, on the Projects page, does not appear to have a character limit. This means a ridiculous number of character can be entered which has a negative performance impact on the browser and server. Version-Release number of selected component (if applicable): dev How reproducible: Easy always Steps to Reproduce: 1. Go to $server/zanata/projects 2. Enter a massive amount of text into the project search bar (like Gutenberg's Moby Dick!) 3. Press Search 4. Wait for it... Actual results: It displays the entire text, prefixed with "Found 0 Projects matching query" Expected results: I doubt anyone would need more than 256 characters in a search. Additional info: -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=FfaxhCLZqi&a=cc_unsubscribe From bugzilla at redhat.com Wed Dec 4 05:40:09 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 04 Dec 2013 05:40:09 +0000 Subject: [zanata-bugs] [Bug 1037932] New: Unhandled exception: Add language field allows more character than the database does (255) Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1037932 Bug ID: 1037932 Summary: Unhandled exception: Add language field allows more character than the database does (255) Product: Zanata Version: development Component: Component-UI Severity: high Assignee: zanata-dev-internal at redhat.com Reporter: djansen at redhat.com QA Contact: zanata-qa at redhat.com CC: zanata-bugs at redhat.com Description of problem: The column type for localeid is VARCHAR(255) NOT NULL. The field that allows the admin to specify the locale is not limited, and entering more than the 255 characters results in an exception Version-Release number of selected component (if applicable): dev How reproducible: Easy always Steps to Reproduce: 1. Sign in as admin 2. Click Languages, then Add Language 3. In the available Language field, enter a large string 4. Press Save Actual results: org.h2.jdbc.JdbcSQLException: Value too long for column "LOCALEID VARCHAR(255) NOT NULL": "STRINGDECODE('\ufeffThe Project Gutenberg EBook of Moby Dick; or The Whale, by Herman Melville This eBook is for the use of any... (1235149)"; Expected results: A limit on the field Additional info: -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=PF5iVlBQwB&a=cc_unsubscribe From bugzilla at redhat.com Wed Dec 4 05:45:32 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 04 Dec 2013 05:45:32 +0000 Subject: [zanata-bugs] [Bug 1037933] New: Unhandled exception: Add language with a string too large can cause a lock exception on save Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1037933 Bug ID: 1037933 Summary: Unhandled exception: Add language with a string too large can cause a lock exception on save Product: Zanata Version: development Component: Component-UI Severity: high Assignee: zanata-dev-internal at redhat.com Reporter: djansen at redhat.com QA Contact: zanata-qa at redhat.com CC: zanata-bugs at redhat.com Description of problem: Entering a string and clicking somewhere causes the server to attempt a fill in of all the language details. Pressing save while this occurs can cause an exception. Version-Release number of selected component (if applicable): deb How reproducible: Moderate Steps to Reproduce: 1. Sign in as admin 2. Click Languages, then Add Language 3. Enter a massive string into the field 4. Click in the blank area, then about a second later click Save Actual results: org.jboss.seam.core.LockTimeoutException: could not acquire lock on @Synchronized component: languageManagerAction Expected results: No exceptions Additional info: 15:34:39,187 WARNING [javax.enterprise.resource.webcontainer.jsf.lifecycle] (http-/0.0.0.0:9898-1) /WEB-INF/layout/language_detail.xhtml @50,36 rendered="#{not languageManagerAction.language.contains('_')}": org.jboss.seam.core.LockTimeoutException: could not acquire lock on @Synchronized component: languageManagerAction: javax.el.ELException: /WEB-INF/layout/language_detail.xhtml @50,36 rendered="#{not languageManagerAction.language.contains('_')}": org.jboss.seam.core.LockTimeoutException: could not acquire lock on @Synchronized component: languageManagerAction at com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:114) [jsf-impl-2.1.18-jbossorg-1.jar:] at javax.faces.component.ComponentStateHelper.eval(ComponentStateHelper.java:194) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIComponentBase.isRendered(UIComponentBase.java:419) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1172) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1182) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIForm.processDecodes(UIForm.java:225) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1182) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1182) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1182) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1182) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIForm.processDecodes(UIForm.java:225) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1182) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1182) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIViewRoot.processDecodes(UIViewRoot.java:925) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at com.sun.faces.lifecycle.ApplyRequestValuesPhase.execute(ApplyRequestValuesPhase.java:78) [jsf-impl-2.1.18-jbossorg-1.jar:] at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.18-jbossorg-1.jar:] at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.18-jbossorg-1.jar:] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:832) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:620) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:553) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:482) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.tuckey.web.filters.urlrewrite.NormalRewrittenUrl.doRewrite(NormalRewrittenUrl.java:213) [urlrewritefilter-4.0.4.jar:4.0.4] at org.tuckey.web.filters.urlrewrite.RuleChain.handleRewrite(RuleChain.java:171) [urlrewritefilter-4.0.4.jar:4.0.4] at org.tuckey.web.filters.urlrewrite.RuleChain.doRules(RuleChain.java:145) [urlrewritefilter-4.0.4.jar:4.0.4] at org.tuckey.web.filters.urlrewrite.UrlRewriter.processRequest(UrlRewriter.java:92) [urlrewritefilter-4.0.4.jar:4.0.4] at org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:389) [urlrewritefilter-4.0.4.jar:4.0.4] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.zanata.seam.interceptor.MonitoringWrapper.doFilter(MonitoringWrapper.java:68) [classes:] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.zanata.servlet.GWTCacheControlFilter.doFilter(GWTCacheControlFilter.java:61) [classes:] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.zanata.servlet.MDCInsertingServletFilter.doFilter(MDCInsertingServletFilter.java:58) [classes:] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.jboss.security.negotiation.NegotiationAuthenticator$1.invoke(NegotiationAuthenticator.java:326) [jboss-negotiation-common-2.2.2.Final.jar:2.2.2.Final] at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:389) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] Caused by: org.jboss.seam.core.LockTimeoutException: could not acquire lock on @Synchronized component: languageManagerAction at org.jboss.seam.core.SynchronizationInterceptor.aroundInvoke(SynchronizationInterceptor.java:44) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:196) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:114) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.zanata.action.LanguageManagerAction_$$_javassist_seam_75.getLanguage(LanguageManagerAction_$$_javassist_seam_75.java) [classes:] at sun.reflect.GeneratedMethodAccessor769.invoke(Unknown Source) [:1.7.0_25] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25] at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25] at javax.el.BeanELResolver.getValue(BeanELResolver.java:302) [jboss-el-api_2.2_spec-1.0.2.Final.jar:1.0.2.Final] at com.sun.faces.el.DemuxCompositeELResolver._getValue(DemuxCompositeELResolver.java:176) [jsf-impl-2.1.18-jbossorg-1.jar:] at com.sun.faces.el.DemuxCompositeELResolver.getValue(DemuxCompositeELResolver.java:203) [jsf-impl-2.1.18-jbossorg-1.jar:] at org.jboss.el.parser.AstPropertySuffix.getValue(AstPropertySuffix.java:53) [jboss-el-1.0_02.CR6.jar:1.0_02.CR6] at org.jboss.el.parser.AstValue.getValue(AstValue.java:67) [jboss-el-1.0_02.CR6.jar:1.0_02.CR6] at org.jboss.el.parser.AstNot.getValue(AstNot.java:26) [jboss-el-1.0_02.CR6.jar:1.0_02.CR6] at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) [jboss-el-1.0_02.CR6.jar:1.0_02.CR6] at com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:109) [jsf-impl-2.1.18-jbossorg-1.jar:] ... 61 more 15:34:39,193 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/zanata].[Faces Servlet]] (http-/0.0.0.0:9898-1) JBWEB000236: Servlet.service() for servlet Faces Servlet threw exception: org.jboss.seam.core.LockTimeoutException: could not acquire lock on @Synchronized component: languageManagerAction at org.jboss.seam.core.SynchronizationInterceptor.aroundInvoke(SynchronizationInterceptor.java:44) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:196) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:114) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.zanata.action.LanguageManagerAction_$$_javassist_seam_75.getLanguage(LanguageManagerAction_$$_javassist_seam_75.java) [classes:] at sun.reflect.GeneratedMethodAccessor769.invoke(Unknown Source) [:1.7.0_25] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25] at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25] at javax.el.BeanELResolver.getValue(BeanELResolver.java:302) [jboss-el-api_2.2_spec-1.0.2.Final.jar:1.0.2.Final] at com.sun.faces.el.DemuxCompositeELResolver._getValue(DemuxCompositeELResolver.java:176) [jsf-impl-2.1.18-jbossorg-1.jar:] at com.sun.faces.el.DemuxCompositeELResolver.getValue(DemuxCompositeELResolver.java:203) [jsf-impl-2.1.18-jbossorg-1.jar:] at org.jboss.el.parser.AstPropertySuffix.getValue(AstPropertySuffix.java:53) [jboss-el-1.0_02.CR6.jar:1.0_02.CR6] at org.jboss.el.parser.AstValue.getValue(AstValue.java:67) [jboss-el-1.0_02.CR6.jar:1.0_02.CR6] at org.jboss.el.parser.AstNot.getValue(AstNot.java:26) [jboss-el-1.0_02.CR6.jar:1.0_02.CR6] at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) [jboss-el-1.0_02.CR6.jar:1.0_02.CR6] at com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:109) [jsf-impl-2.1.18-jbossorg-1.jar:] at javax.faces.component.ComponentStateHelper.eval(ComponentStateHelper.java:194) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIComponentBase.isRendered(UIComponentBase.java:419) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1172) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1182) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIForm.processDecodes(UIForm.java:225) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1182) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1182) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1182) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1182) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIForm.processDecodes(UIForm.java:225) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1182) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1182) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIViewRoot.processDecodes(UIViewRoot.java:925) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at com.sun.faces.lifecycle.ApplyRequestValuesPhase.execute(ApplyRequestValuesPhase.java:78) [jsf-impl-2.1.18-jbossorg-1.jar:] at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.18-jbossorg-1.jar:] at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.18-jbossorg-1.jar:] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:832) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:620) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:553) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:482) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.tuckey.web.filters.urlrewrite.NormalRewrittenUrl.doRewrite(NormalRewrittenUrl.java:213) [urlrewritefilter-4.0.4.jar:4.0.4] at org.tuckey.web.filters.urlrewrite.RuleChain.handleRewrite(RuleChain.java:171) [urlrewritefilter-4.0.4.jar:4.0.4] at org.tuckey.web.filters.urlrewrite.RuleChain.doRules(RuleChain.java:145) [urlrewritefilter-4.0.4.jar:4.0.4] at org.tuckey.web.filters.urlrewrite.UrlRewriter.processRequest(UrlRewriter.java:92) [urlrewritefilter-4.0.4.jar:4.0.4] at org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:389) [urlrewritefilter-4.0.4.jar:4.0.4] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.zanata.seam.interceptor.MonitoringWrapper.doFilter(MonitoringWrapper.java:68) [classes:] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.zanata.servlet.GWTCacheControlFilter.doFilter(GWTCacheControlFilter.java:61) [classes:] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.zanata.servlet.MDCInsertingServletFilter.doFilter(MDCInsertingServletFilter.java:58) [classes:] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.jboss.security.negotiation.NegotiationAuthenticator$1.invoke(NegotiationAuthenticator.java:326) [jboss-negotiation-common-2.2.2.Final.jar:2.2.2.Final] at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:389) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] 15:34:39,207 ERROR [org.jboss.seam.exception.Exceptions] (http-/0.0.0.0:9898-1) handled and logged exception: javax.servlet.ServletException: could not acquire lock on @Synchronized component: languageManagerAction at javax.faces.webapp.FacesServlet.service(FacesServlet.java:606) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:832) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:620) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:553) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:482) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.tuckey.web.filters.urlrewrite.NormalRewrittenUrl.doRewrite(NormalRewrittenUrl.java:213) [urlrewritefilter-4.0.4.jar:4.0.4] at org.tuckey.web.filters.urlrewrite.RuleChain.handleRewrite(RuleChain.java:171) [urlrewritefilter-4.0.4.jar:4.0.4] at org.tuckey.web.filters.urlrewrite.RuleChain.doRules(RuleChain.java:145) [urlrewritefilter-4.0.4.jar:4.0.4] at org.tuckey.web.filters.urlrewrite.UrlRewriter.processRequest(UrlRewriter.java:92) [urlrewritefilter-4.0.4.jar:4.0.4] at org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:389) [urlrewritefilter-4.0.4.jar:4.0.4] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.zanata.seam.interceptor.MonitoringWrapper.doFilter(MonitoringWrapper.java:68) [classes:] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.zanata.servlet.GWTCacheControlFilter.doFilter(GWTCacheControlFilter.java:61) [classes:] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.zanata.servlet.MDCInsertingServletFilter.doFilter(MDCInsertingServletFilter.java:58) [classes:] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.jboss.security.negotiation.NegotiationAuthenticator$1.invoke(NegotiationAuthenticator.java:326) [jboss-negotiation-common-2.2.2.Final.jar:2.2.2.Final] at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:389) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final.jar:7.2.0.Final] at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] Caused by: org.jboss.seam.core.LockTimeoutException: could not acquire lock on @Synchronized component: languageManagerAction at org.jboss.seam.core.SynchronizationInterceptor.aroundInvoke(SynchronizationInterceptor.java:44) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:196) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:114) [jboss-seam-2.3.1.Final.jar:2.3.1.Final] at org.zanata.action.LanguageManagerAction_$$_javassist_seam_75.getLanguage(LanguageManagerAction_$$_javassist_seam_75.java) [classes:] at sun.reflect.GeneratedMethodAccessor769.invoke(Unknown Source) [:1.7.0_25] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25] at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25] at javax.el.BeanELResolver.getValue(BeanELResolver.java:302) [jboss-el-api_2.2_spec-1.0.2.Final.jar:1.0.2.Final] at com.sun.faces.el.DemuxCompositeELResolver._getValue(DemuxCompositeELResolver.java:176) [jsf-impl-2.1.18-jbossorg-1.jar:] at com.sun.faces.el.DemuxCompositeELResolver.getValue(DemuxCompositeELResolver.java:203) [jsf-impl-2.1.18-jbossorg-1.jar:] at org.jboss.el.parser.AstPropertySuffix.getValue(AstPropertySuffix.java:53) [jboss-el-1.0_02.CR6.jar:1.0_02.CR6] at org.jboss.el.parser.AstValue.getValue(AstValue.java:67) [jboss-el-1.0_02.CR6.jar:1.0_02.CR6] at org.jboss.el.parser.AstNot.getValue(AstNot.java:26) [jboss-el-1.0_02.CR6.jar:1.0_02.CR6] at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) [jboss-el-1.0_02.CR6.jar:1.0_02.CR6] at com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:109) [jsf-impl-2.1.18-jbossorg-1.jar:] at javax.faces.component.ComponentStateHelper.eval(ComponentStateHelper.java:194) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIComponentBase.isRendered(UIComponentBase.java:419) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1172) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1182) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIForm.processDecodes(UIForm.java:225) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1182) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1182) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1182) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1182) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIForm.processDecodes(UIForm.java:225) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1182) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1182) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at javax.faces.component.UIViewRoot.processDecodes(UIViewRoot.java:925) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] at com.sun.faces.lifecycle.ApplyRequestValuesPhase.execute(ApplyRequestValuesPhase.java:78) [jsf-impl-2.1.18-jbossorg-1.jar:] at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.18-jbossorg-1.jar:] at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.18-jbossorg-1.jar:] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final] ... 44 more -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Nuu1oQDhYj&a=cc_unsubscribe From bugzilla at redhat.com Wed Dec 4 05:50:01 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 04 Dec 2013 05:50:01 +0000 Subject: [zanata-bugs] [Bug 1035959] [RFE] Zanata should recognise file types individually, not from the target project In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1035959 --- Comment #7 from Ding-Yi Chen --- Then we need a table of supported locale as well. :) There is also not-so-corner cases: po/polish.po "po" can mean Polish language, or directory of po files. That said, we may take advantage of some mutual exclusive cases, like if you discover UTF8 in .properties, then the project type should be utf8properties, not properties. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=m806NWRFvZ&a=cc_unsubscribe From bugzilla at redhat.com Wed Dec 4 06:07:58 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 04 Dec 2013 06:07:58 +0000 Subject: [zanata-bugs] [Bug 1035959] [RFE] Zanata should recognise file types individually, not from the target project In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1035959 David Mason changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |damason at redhat.com --- Comment #8 from David Mason --- (In reply to Sean Flanigan from comment #6) > Exactly, that's why we need pathname templates. We may still need to keep > some idea of the file types (similar to our current project type > enumeration) so that we know which template to use for each file. > > So if the document type is "properties" we will use the standard template > for properties files, which might be > ${dirname}/${basename}_${locale}.properties, > > if the document type is "gettext" we use ${dirname}/${locale}.po, > > and if the document type is "podir" we use > ${locale}/${dirname}/${basename}.po. > > In advanced cases, the user might need to specify the actual templates in > zanata.xml, along with a way of associating files/directories with the right > templates. > > > And another thing to bear in mind: we need templates when parsing filenames > for upload, as well as when generating files. In addition to a mechanism for specifying how source files are identified and how they map to translation files, a preview of the results of such a mapping would be useful in helping maintainers to ensure and be confident that they have the correct setting. This would entail a display showing some or all source files that are detected with the current settings, and which translation files they would map to in one or more of the active locales (possibly indicating whether the translation files are found on the file system). This would be especially valuable if maintainers are given access to something like the above syntax to specify manually the exact mapping of source files to translation files. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=0Rl7lqGG3b&a=cc_unsubscribe From bugzilla at redhat.com Wed Dec 4 06:10:56 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 04 Dec 2013 06:10:56 +0000 Subject: [zanata-bugs] [Bug 1036435] RFE: Upgrade to Liquibase 3.x In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1036435 Ding-Yi Chen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ON_QA |VERIFIED CC| |dchen at redhat.com Fixed In Version| |3.3.0-SNAPSHOT | |(20131204-0037) --- Comment #4 from Ding-Yi Chen --- VERIFIED with Zanata version 3.3.0-SNAPSHOT (20131204-0037) -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Pb8jbVHdJt&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 5 00:30:27 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 05 Dec 2013 00:30:27 +0000 Subject: [zanata-bugs] [Bug 995324] "Agree to the Terms of Use" should be displayed looks relevant to users that sign up with OpenId In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=995324 Ding-Yi Chen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ON_QA |VERIFIED Fixed In Version| |3.3.0-SNAPSHOT | |(20131205-0040) --- Comment #16 from Ding-Yi Chen --- VERIFIED with Zanata version 3.3.0-SNAPSHOT (20131205-0040). -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=kWIuv3kSPh&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 5 00:59:55 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 05 Dec 2013 00:59:55 +0000 Subject: [zanata-bugs] [Bug 978072] RFE: integrate client with command-line tools (po4a for roff input/output) In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=978072 Ding-Yi Chen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ON_QA |ASSIGNED CC| |dchen at redhat.com --- Comment #6 from Ding-Yi Chen --- Help Documentation should be located in zanata,org and under the section that explain how to use client. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=SgrZakhn4f&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 5 01:23:34 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 05 Dec 2013 01:23:34 +0000 Subject: [zanata-bugs] [Bug 978072] RFE: integrate client with command-line tools (po4a for roff input/output) In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=978072 David Mason changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |ON_QA --- Comment #7 from David Mason --- Added link from zanata.org client configuration instructions to command hook instructions on the Zanata wiki. See paragraph near the end of http://zanata.org/help/cli/cli-configuration/ -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=ovsQoSODDS&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 5 04:13:30 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 05 Dec 2013 04:13:30 +0000 Subject: [zanata-bugs] [Bug 1013419] FAQ missing on translate.zanata.org In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1013419 Damian Jansen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|zanata-dev-internal at redhat. |djansen at redhat.com |com | -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=sehbYyE0UL&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 5 04:19:51 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 05 Dec 2013 04:19:51 +0000 Subject: [zanata-bugs] [Bug 1013419] FAQ missing on translate.zanata.org In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1013419 Damian Jansen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |POST --- Comment #3 from Damian Jansen --- https://github.com/zanata/zanata-server/pull/316 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=qSvZJEMgs4&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 5 05:08:45 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 05 Dec 2013 05:08:45 +0000 Subject: [zanata-bugs] [Bug 978072] RFE: integrate client with command-line tools (po4a for roff input/output) In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=978072 Damian Jansen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ON_QA |ASSIGNED CC| |djansen at redhat.com --- Comment #8 from Damian Jansen --- Reading through the description and comments, I don't believe this feature was delivered in the requested form. What was delivered seems to be a workaround. To elaborate: * "manpage translation requires a tool like po4a on the translator's or maintainer's side" This is still the case, the hook needs to be operated on the user's side. * "...could support roff natively, it would lower the barrier to engagement in translating manpages" Someone with enough understanding of the configuration would have worked this out for themselves. The point seems to be it's for the average user, to upload and download roff files as per any other file. * "Zanata would read the roff files..." It does not - this is done before Zanata gets it. See previous point. Perhaps there's something I missed, a decision to not directly support .roff but to do so in a "upload hook" manner that has been neglected to detail here. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=jnJQV9DpDm&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 5 05:12:03 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 05 Dec 2013 05:12:03 +0000 Subject: [zanata-bugs] [Bug 1038412] New: RFE: Unify Projects Search field for projects, groups and languages Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1038412 Bug ID: 1038412 Summary: RFE: Unify Projects Search field for projects, groups and languages Product: Zanata Version: development Component: Usability Severity: medium Assignee: lbrooker at redhat.com Reporter: djansen at redhat.com QA Contact: zanata-qa at redhat.com CC: zanata-bugs at redhat.com Projects are searched for by the search bar, and groups are searched by filtering the list. Languages cannot be searched at all. The projects search bar could be repurposed to search for the important zanata features - groups, projects, languages - perhaps even documents! I believe we could be doing search better. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=DXtJgMHXXP&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 5 05:25:09 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 05 Dec 2013 05:25:09 +0000 Subject: [zanata-bugs] [Bug 978072] RFE: integrate client with command-line tools (po4a for roff input/output) In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=978072 Damian Jansen changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|irooskov at redhat.com |damason at redhat.com -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=EuULhd5Dh1&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 5 05:29:06 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 05 Dec 2013 05:29:06 +0000 Subject: [zanata-bugs] [Bug 947843] RFE: Dashboard shows favourited/starred/bookmarked projects In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=947843 Damian Jansen changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|unspecified |medium CC| |djansen at redhat.com Component|Usability |Component-UI Version|2.2 |3.1 Summary|RFE: bookmarking projects |RFE: Dashboard shows | |favourited/starred/bookmark | |ed projects --- Comment #2 from Damian Jansen --- * Allow the user to flag [favourited/starred/bookmarked/liked/upvoted] projects, which will be displayed on the user's dashboard. * Allow the user to remove this action, thus removing it from the dashboard -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=SFgjQ6bPrB&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 5 06:01:18 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 05 Dec 2013 06:01:18 +0000 Subject: [zanata-bugs] [Bug 978072] RFE: integrate client with command-line tools (po4a for roff input/output) In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=978072 Ding-Yi Chen changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |r.landmann at redhat.com Flags| |needinfo?(r.landmann at redhat | |.com) --- Comment #9 from Ding-Yi Chen --- Ruedigner, do you think the command hook in zanata.xml is sufficient for your need. Or you still want native push/pull support. (That is, roff can be uploaded and downloaded through Web UI). -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=s6OK0PzVTL&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 5 06:32:25 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 05 Dec 2013 06:32:25 +0000 Subject: [zanata-bugs] [Bug 1038412] RFE: Unify Projects Search field for projects, groups and languages In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1038412 Ding-Yi Chen changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dchen at redhat.com, | |djansen at redhat.com Flags| |needinfo?(djansen at redhat.co | |m) --- Comment #1 from Ding-Yi Chen --- A few questions about scope and expected behaviour. I generally agree that we should have a unify search for project, groups, even documents and users, however: 1. What's the use case for language search? (Who actually need it?) Language are relatively static, i.e., it does not change much. Just a browser search is normally sufficient. For translators and language coordinator, they are more likely to join the languages they interested at the beginning, and then stick with that. Indeed occasionally they might join a few more, but then again, the browser search on language page is sufficient. For maintainers, they are more likely care about the statistics of ALL languages they want in, they don't need to search individual language. 2. What's the landing page should we provide language search? Currently our language related page is the user list of the specified language team. However, IMHO, if I were a translator join the language team, I am more interested in projects yet to be translated in my languages instead of seeing language team member. 3. Should we support incremental or substring search? 4. Should we allow the user to specify the parameters that they only want to search projects, groups and languages? -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=rseyHriwLr&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 5 06:34:11 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 05 Dec 2013 06:34:11 +0000 Subject: [zanata-bugs] [Bug 978072] RFE: integrate client with command-line tools (po4a for roff input/output) In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=978072 --- Comment #10 from Sean Flanigan --- We can't implement native support for every file format under the sun directly in Zanata, for reasons of server security and development capacity, which is why we chose a more general solution which will allow Zanata client to work with any format which has command-line converters. Command hooks provide a solution not just for roff, but for other file formats too. But perhaps we should have split it out into a separate RFE, and left this one alone. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=q2BWGHYXzm&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 5 06:59:14 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 05 Dec 2013 06:59:14 +0000 Subject: [zanata-bugs] [Bug 1038449] New: RFE: integrate client with command-line tools (command hook in zanata.xml) Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1038449 Bug ID: 1038449 Summary: RFE: integrate client with command-line tools (command hook in zanata.xml) Product: Zanata Component: Component-Maven Severity: medium Assignee: damason at redhat.com Reporter: dchen at redhat.com QA Contact: zanata-qa at redhat.com CC: ankit at redhat.com, damason at redhat.com, dchen at redhat.com, djansen at redhat.com, petersen at redhat.com, pschiffe at redhat.com, r.landmann at redhat.com, sflaniga at redhat.com, tagoh at redhat.com, zanata-bugs at redhat.com Some items to test: 1. Output from hook commands is shown by default. 2. Output from hook commands can be hidden if the attribute "quiet" is true. 3. "After" hooks can be run unconditionally if the attribute "always" is true, if a push/pull fails, or if a preceding hook fails. 4. Child process is terminated if the zanata client process is interrupted (eg Ctrl-C). --- Additional comment from Ding-Yi Chen on 2013-12-05 10:59:55 EST --- Help Documentation should be located in zanata,org and under the section that explain how to use client. --- Additional comment from David Mason on 2013-12-05 11:23:34 EST --- Added link from zanata.org client configuration instructions to command hook instructions on the Zanata wiki. See paragraph near the end of http://zanata.org/help/cli/cli-configuration/ -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=WNpkc9XppR&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 5 07:03:48 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 05 Dec 2013 07:03:48 +0000 Subject: [zanata-bugs] [Bug 978072] RFE: support roff as an input/output format In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=978072 Ding-Yi Chen changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.redhat.com | |/show_bug.cgi?id=1038449 Summary|RFE: integrate client with |RFE: support roff as an |command-line tools (po4a |input/output format |for roff input/output) | --- Comment #11 from Ding-Yi Chen --- The functionality of command hook in zanata.xml is now traced by Bug 1038449 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=eAi5mVwqs5&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 5 07:03:48 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 05 Dec 2013 07:03:48 +0000 Subject: [zanata-bugs] [Bug 1038449] RFE: integrate client with command-line tools (command hook in zanata.xml) In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1038449 Ding-Yi Chen changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.redhat.com | |/show_bug.cgi?id=978072 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=eK0I4u6KeC&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 5 08:15:51 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 05 Dec 2013 08:15:51 +0000 Subject: [zanata-bugs] [Bug 1038449] RFE: integrate client with command-line tools (command hook in zanata.xml) In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1038449 Ding-Yi Chen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ON_QA --- Comment #1 from Ding-Yi Chen --- The advantages of this approach over shell script or make are: 1. Suitable for maven prior 2.0.9, which returned correct return codes (i.e. always returning 0, see http://jira.codehaus.org/browse/MNG-3651 for detail). 2. Works regardless your are using zanata maven plugin or zanata-client. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=btzwfeEf9V&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 5 23:30:28 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 05 Dec 2013 23:30:28 +0000 Subject: [zanata-bugs] [Bug 1038844] New: RFE: Add ability in command-hooks to specify that a command should run regardless of prior failed commands Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1038844 Bug ID: 1038844 Summary: RFE: Add ability in command-hooks to specify that a command should run regardless of prior failed commands Product: Zanata Version: development Component: Component-zanata-client Assignee: irooskov at redhat.com Reporter: damason at redhat.com QA Contact: zanata-qa at redhat.com CC: zanata-bugs at redhat.com Description of problem: When commands specified in command hooks are run, if any command fails the process will be aborted and subsequent commands will not run. This may prevent some cleanup commands being run, leaving temporary files in the user's workspace. An optional attribute should be available on and tags to specify that they should run regardless of prior failures so that temporary files can be cleaned up even if prior commands fail. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=D5X1y7GnXw&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 5 23:33:54 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 05 Dec 2013 23:33:54 +0000 Subject: [zanata-bugs] [Bug 1038449] RFE: integrate client with command-line tools (command hook in zanata.xml) In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1038449 David Mason changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.redhat.com | |/show_bug.cgi?id=1038844 --- Comment #2 from David Mason --- (In reply to Ding-Yi Chen from comment #0) > 3. "After" hooks can be run unconditionally if the attribute "always" is > true, if a push/pull fails, or if a preceding hook fails. This is not included in the provided implementation. I have created a separate bug for the addition of this feature. See: https://bugzilla.redhat.com/show_bug.cgi?id=1038844 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=rVLKmYNCKm&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 5 23:33:54 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 05 Dec 2013 23:33:54 +0000 Subject: [zanata-bugs] [Bug 1038844] RFE: Add ability in command-hooks to specify that a command should run regardless of prior failed commands In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1038844 David Mason changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.redhat.com | |/show_bug.cgi?id=1038449 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=001LSDTqfM&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 5 23:43:40 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 05 Dec 2013 23:43:40 +0000 Subject: [zanata-bugs] [Bug 1013961] Inactivate web elements should not appear when version project-type is not specified. In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1013961 David Mason changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |damason at redhat.com Summary|Inactivate web elements |Inactivate web elements |should not appears when |should not appear when |version project type is not |version project-type is not |specified. |specified. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=4UiDgrxHbN&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 5 23:44:10 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 05 Dec 2013 23:44:10 +0000 Subject: [zanata-bugs] [Bug 1030166] Project type should be required for project creation In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1030166 David Mason changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |damason at redhat.com Summary|Project type should be |Project type should be |required when create |required for project |project |creation -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=DYZv39vnng&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 5 23:54:22 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 05 Dec 2013 23:54:22 +0000 Subject: [zanata-bugs] [Bug 1013961] Duplicate buttons and links appear when version's project-type is not specified In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1013961 Sean Flanigan changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Inactivate web elements |Duplicate buttons and links |should not appear when |appear when version's |version project-type is not |project-type is not |specified. |specified --- Comment #2 from Sean Flanigan --- I'm not sure we should hide the "Download All Files (zip)" button just because the project type is unset. The fact that we get two buttons labeled "Offline Translation Config File" is a bug though. If we do decide to hide "Download All Files (zip)", I think we should replace it with a big red warning which will encourage project maintainers to set the project type. If we simply hide it, users might think the feature doesn't exist. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=EYoWjxMb8U&a=cc_unsubscribe From bugzilla at redhat.com Fri Dec 6 00:31:42 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 06 Dec 2013 00:31:42 +0000 Subject: [zanata-bugs] [Bug 1038861] New: RFE: Allow text flows to be linked in workspace chat Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1038861 Bug ID: 1038861 Summary: RFE: Allow text flows to be linked in workspace chat Product: Zanata Version: development Component: Usability Assignee: irooskov at redhat.com Reporter: damason at redhat.com QA Contact: zanata-qa at redhat.com CC: zanata-bugs at redhat.com Description of problem: Chat in the editor is intended to be used to discuss translation of the project in the workspace. Indicating which text flow is being discussed currently requires either:- - clicking the bookmark icon, copying the url and pasting it into chat - selecting the source, translation or both, copying and pasting into chat Any changes to the translation under discussion would require repeating the select-copy-paste operation. Discussing translations would be much easier if a native shortcut could be easily inserted into the chat window for the currently selected row that would allow anyone participating in the chat to view the source and translation for that row by clicking the shortcut. The source and translation would be shown in a non-modal movable popup so that they can be viewed without disrupting the current translation. A button in the popup could open an editor in a new tab that has the linked row selected. The translation in the popup should update when a new translation is saved, or if it shows a historical translation there should be a prominent visible indicator that a newer translation is visible. Showing a historical revision of a translation (i.e. the revision that was current when the shortcut was added to chat) would ensure that the discussion still makes sense if someone looks back at it later. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=AsPRddhueu&a=cc_unsubscribe From bugzilla at redhat.com Fri Dec 6 06:12:57 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 06 Dec 2013 06:12:57 +0000 Subject: [zanata-bugs] [Bug 1038449] RFE: integrate client with command-line tools (command hook in zanata.xml) In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1038449 --- Comment #3 from Ding-Yi Chen --- Scope changed: Attributes in and tag are not covered thus will not be tested with this bug. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=ZknEPvmK6t&a=cc_unsubscribe From bugzilla at redhat.com Fri Dec 6 06:16:35 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 06 Dec 2013 06:16:35 +0000 Subject: [zanata-bugs] [Bug 1038449] RFE: integrate client with command-line tools (command hook in zanata.xml) In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1038449 Ding-Yi Chen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ON_QA |VERIFIED Fixed In Version| |zanata-maven-plugin:3.3.0-S | |NAPSHOT --- Comment #4 from Ding-Yi Chen --- VERIFIED with zanata-maven-plugin:3.3.0-SNAPSHOT Server Zanata version 3.3.0-SNAPSHOT (20131206-0037) -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=T4iykK7HxP&a=cc_unsubscribe From bugzilla at redhat.com Fri Dec 6 06:22:35 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 06 Dec 2013 06:22:35 +0000 Subject: [zanata-bugs] [Bug 1038844] RFE: Add ability in command-hooks to specify that a command should run regardless of prior failed commands In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1038844 Ding-Yi Chen changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dchen at redhat.com Severity|unspecified |low --- Comment #1 from Ding-Yi Chen --- Frankly speaking, project maintainers are more likely to rely on shell or build scripts to accomplish same functionality. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=tu03L4BK5f&a=cc_unsubscribe From bugzilla at redhat.com Sat Dec 7 00:09:31 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sat, 07 Dec 2013 00:09:31 +0000 Subject: [zanata-bugs] [Bug 1039215] New: [RFE] [.properties files] Please make source strings (that consist of an empty space) uneditable in the translation editor Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1039215 Bug ID: 1039215 Summary: [RFE] [.properties files] Please make source strings (that consist of an empty space) uneditable in the translation editor Product: Zanata Component: Usability Assignee: irooskov at redhat.com Reporter: ykatabam at redhat.com QA Contact: zanata-qa at redhat.com CC: zanata-bugs at redhat.com Description of problem: Currently in Zanata, single space in a .properties file that does not require editing is editable in translation editor. This has caused error by translator, like this: BZ#871370 Version-Release number of selected component (if applicable): 3 How reproducible: 100% Steps to Reproduce: 1. push .properties file which contains a string consist of single empty space that should not be edited. 2. Find the string in the translation editor Actual results: It is editable Expected results: Would be better if it is not shown in the editor in the first placed Additional info: -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=qF3LUteQOI&a=cc_unsubscribe From bugzilla at redhat.com Sat Dec 7 00:15:51 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sat, 07 Dec 2013 00:15:51 +0000 Subject: [zanata-bugs] [Bug 1039215] [RFE] [.properties files] Please make source strings (that consist of an empty space) uneditable in the translation editor In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1039215 --- Comment #1 from Yuko Katabami --- With the above mentioned bug BZ#871370, the empty space was used for one of the column headers which should remain empty. A few people made an error with this including entering space, hyphen or other characters to make the "translated" state. (At the time we were working on this, the status did not change unless you enter something and save.) However I do not know other usecases and there is a small possibility that empty spaces may have to be edited in a certain way. If so, this would not be desirable to be implemented. Please look into this prior to introducing this to the product. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=To9cH0VtPL&a=cc_unsubscribe From bugzilla at redhat.com Tue Dec 10 00:35:04 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 10 Dec 2013 00:35:04 +0000 Subject: [zanata-bugs] [Bug 1039776] New: Email template link to zanata log broken Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1039776 Bug ID: 1039776 Summary: Email template link to zanata log broken Product: Zanata Version: development Component: Usability Severity: low Assignee: zanata-dev-internal at redhat.com Reporter: djansen at redhat.com QA Contact: zanata-qa at redhat.com CC: zanata-bugs at redhat.com Description of problem: Emails contain a link to zanata.org in the footer. The icon has a src link to http://zanata.org/images/z-logo-16px.png which appears to no longer exist. Version-Release number of selected component (if applicable): dev Steps to Reproduce: 1. Login as admin 2. Go to Help, Contact Admin 3. Enter message and press Send 4. View received email and check footer -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Q8trHYw1Mf&a=cc_unsubscribe From bugzilla at redhat.com Tue Dec 10 01:48:31 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 10 Dec 2013 01:48:31 +0000 Subject: [zanata-bugs] [Bug 1023227] Add language member request email contains string jsf.email.joinrequest.RoleRequested In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1023227 Ding-Yi Chen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ON_QA |VERIFIED CC| |dchen at redhat.com Fixed In Version| |3.3.0-SNAPSHOT | |(20131206-0037) --- Comment #2 from Ding-Yi Chen --- VERIFIED with Zanata version 3.3.0-SNAPSHOT (20131206-0037) -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=bhYPVvwARc&a=cc_unsubscribe From bugzilla at redhat.com Tue Dec 10 02:37:56 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 10 Dec 2013 02:37:56 +0000 Subject: [zanata-bugs] [Bug 1039776] Email template link to zanata log broken In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1039776 Luke Brooker changed: What |Removed |Added ---------------------------------------------------------------------------- CC|zanata-bugs at redhat.com | CC| |lbrooker at redhat.com -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=yT7u46M8T9&a=cc_unsubscribe From bugzilla at redhat.com Tue Dec 10 02:50:40 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 10 Dec 2013 02:50:40 +0000 Subject: [zanata-bugs] [Bug 1030711] Zanata java client is broken in fedora 18 In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1030711 Ding-Yi Chen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ON_QA |VERIFIED CC| |dchen at redhat.com Fixed In Version| |zanata-client-2.2.0-4.fc18 --- Comment #2 from Ding-Yi Chen --- VERIFIED with zanata-client-2.2.0-4.fc18 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=0o4BzSIR04&a=cc_unsubscribe From bugzilla at redhat.com Tue Dec 10 04:07:23 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 10 Dec 2013 04:07:23 +0000 Subject: [zanata-bugs] [Bug 1039810] New: Cancel contact email causes exception Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1039810 Bug ID: 1039810 Summary: Cancel contact email causes exception Product: Zanata Version: development Component: Component-Logic Severity: high Assignee: zanata-dev-internal at redhat.com Reporter: djansen at redhat.com QA Contact: zanata-qa at redhat.com CC: zanata-bugs at redhat.com Created attachment 834639 --> https://bugzilla.redhat.com/attachment.cgi?id=834639&action=edit Test run log file Description of problem: Pressing Cancel on a contact admin page causes an exception Version-Release number of selected component (if applicable): dev How reproducible: Easy always Steps to Reproduce: 1. Sign in, click Help in menu bar 2. Press Contact Admin 3. Press Cancel Actual results: An unexpected error has occurred. Please report this problem with details of what you were attempting. Expected results: Return to help page Additional info: Last 500 lines of log attached -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=F9nFYXZXJU&a=cc_unsubscribe From bugzilla at redhat.com Tue Dec 10 23:14:47 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 10 Dec 2013 23:14:47 +0000 Subject: [zanata-bugs] [Bug 1040207] New: Fields on contact admin page not limited, user can send large text in emails Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1040207 Bug ID: 1040207 Summary: Fields on contact admin page not limited, user can send large text in emails Product: Zanata Version: development Component: Component-UI Severity: medium Assignee: zanata-dev-internal at redhat.com Reporter: djansen at redhat.com QA Contact: zanata-qa at redhat.com CC: zanata-bugs at redhat.com Description of problem: The Contact Admin page does not limit the text a user can send, so a user can repeatedly send a lengthy novel through the Zanata email system filling the server. Version-Release number of selected component (if applicable): dev How reproducible: Easy always Steps to Reproduce: 1. Sign in as someone 2. Go to Help, click on Contact Admin 3. Enter a massive amount of text into the subject line and message body 4. Press Send Actual results: Admin gets a huge email Expected results: This should not be allowed Additional info: -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Xbimh01kva&a=cc_unsubscribe From bugzilla at redhat.com Tue Dec 10 23:24:37 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 10 Dec 2013 23:24:37 +0000 Subject: [zanata-bugs] [Bug 1040207] Fields on contact admin page not limited, user can send large text in emails In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1040207 --- Comment #2 from Damian Jansen --- Looks like the ckeditor will need a plugin added to do this. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=vC3MSScsLC&a=cc_unsubscribe From bugzilla at redhat.com Wed Dec 11 23:36:19 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 11 Dec 2013 23:36:19 +0000 Subject: [zanata-bugs] [Bug 1037925] Search Projects field not character limited In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1037925 Alex Eng changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aeng at redhat.com Assignee|zanata-dev-internal at redhat. |aeng at redhat.com |com | -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=f7HjrtIMgf&a=cc_unsubscribe From bugzilla at redhat.com Wed Dec 11 23:36:42 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 11 Dec 2013 23:36:42 +0000 Subject: [zanata-bugs] [Bug 1039810] Cancel contact email causes exception In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1039810 Alex Eng changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aeng at redhat.com Assignee|zanata-dev-internal at redhat. |aeng at redhat.com |com | -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=GbU2OFiPYI&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 12 01:06:12 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 12 Dec 2013 01:06:12 +0000 Subject: [zanata-bugs] [Bug 1040717] New: CleanDatabaseRule does not fully clean the database Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1040717 Bug ID: 1040717 Summary: CleanDatabaseRule does not fully clean the database Product: Zanata Version: development Component: Maintainability Severity: medium Assignee: pahuang at redhat.com Reporter: djansen at redhat.com QA Contact: zanata-qa at redhat.com CC: zanata-bugs at redhat.com Description of problem: Areas such as the help page and homepage store the text in the database. These tables are not cleared with the CleanDatabaseRule Version-Release number of selected component (if applicable): dev How reproducible: Easy always Steps to Reproduce: 1. Run a test that changes the Help page content twice, and asserts the text is empty (default) Actual results: It will fail, if it asserts that the text is not already existing Expected results: Pass, assuming the data is cleared Additional info: I found this creating a test for the Help pages, see me if you need details. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=IGuCwlkEIb&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 12 04:00:41 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 12 Dec 2013 04:00:41 +0000 Subject: [zanata-bugs] [Bug 873489] XLIFF strategy should use source and target elements for safety In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=873489 --- Comment #4 from Sean Flanigan --- *** Bug 873930 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=DjdUN2uT0U&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 12 04:00:41 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 12 Dec 2013 04:00:41 +0000 Subject: [zanata-bugs] [Bug 873930] Properties/XLIFF strategies should check source content when pushing In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=873930 Sean Flanigan changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution|--- |DUPLICATE Last Closed| |2013-12-11 23:00:41 --- Comment #1 from Sean Flanigan --- *** This bug has been marked as a duplicate of bug 873489 *** -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=uRfC722aWa&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 12 04:03:24 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 12 Dec 2013 04:03:24 +0000 Subject: [zanata-bugs] [Bug 873489] XLIFF/Properties strategies should calculate and set sourceHash for safety In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=873489 Sean Flanigan changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|XLIFF strategy should use |XLIFF/Properties strategies |source and target elements |should calculate and set |for safety |sourceHash for safety --- Comment #5 from Sean Flanigan --- As of Zanata 3.2.0, TextFlowTarget includes a sourceHash property. If sourceHash is provided, TranslatedDocResourceService on the server will check that the sourceHash matches the HTextFlow before persisting the HTextFlowTarget. The gettext formats (including offlinepo) now provide sourceHash when pushing to the server, but this still needs to be implemented for xliff and properties files. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=MzPZiYREBG&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 12 04:07:24 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 12 Dec 2013 04:07:24 +0000 Subject: [zanata-bugs] [Bug 1039810] Cancel contact email causes exception In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1039810 Alex Eng changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #1 from Alex Eng --- Pull request: https://github.com/zanata/zanata-server/pull/319 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=KdVmYDyj4z&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 12 07:43:29 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 12 Dec 2013 07:43:29 +0000 Subject: [zanata-bugs] [Bug 1040817] New: Old translations should be reinstated when old source Properties/XLIFF files are uploaded Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1040817 Bug ID: 1040817 Summary: Old translations should be reinstated when old source Properties/XLIFF files are uploaded Product: Zanata Version: development Component: Component-Logic Assignee: irooskov at redhat.com Reporter: sflaniga at redhat.com QA Contact: zanata-qa at redhat.com CC: zanata-bugs at redhat.com Description of problem: Reinstating an old string from a Properties file should reinstate any corresponding translations, just as it does for Gettext files. If you upload a POT file, translate it, then change one of the source strings, and push it, it is considered to be a new string. The translation becomes hidden, but it is available as part of the translation memory. If you later resurrect/reinstate the source string (eg by pushing the original POT file again), the corresponding translation is reinstated automatically. This makes pushing source files quite safe, because if you make a mistake, you can always push the old source file and get back your translations. However, this is not true for project which contain XLIFF/Properties files. Because the resId is the same as the trans-unit id (in XLIFF) or the property key, the new source string is recognised as a new version of the same textflow. (This is something we can't do with POT files.) When it happens for XLIFF/Properties files, we keep the translation of the old source string, and we mark it fuzzy, because if the source string is similar, the translation is probably similar too, which should make this a good fuzzy match. The problem is, if the earlier source string is uploaded again (eg by pushing the original Properties file), we leave the translation as it is. (Actually, if the new string has been translated, we mark the new translation as fuzzy.) What we should do is resurrect the translation which previously applied to this source string. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=asqKUiPugs&a=cc_unsubscribe From bugzilla at redhat.com Sun Dec 15 22:48:27 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 15 Dec 2013 22:48:27 +0000 Subject: [zanata-bugs] [Bug 1039810] Cancel contact email causes exception In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1039810 Alex Eng changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |ON_QA -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=E0lEjfERZM&a=cc_unsubscribe From bugzilla at redhat.com Sun Dec 15 23:07:35 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 15 Dec 2013 23:07:35 +0000 Subject: [zanata-bugs] [Bug 1040717] CleanDatabaseRule does not fully clean the database In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1040717 Patrick Huang changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=g1KiBwn9ov&a=cc_unsubscribe From bugzilla at redhat.com Mon Dec 16 00:30:18 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 16 Dec 2013 00:30:18 +0000 Subject: [zanata-bugs] [Bug 1040717] CleanDatabaseRule does not fully clean the database In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1040717 --- Comment #1 from Patrick Huang --- https://github.com/zanata/zanata-server/pull/322 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=qtCP7k1HPo&a=cc_unsubscribe From bugzilla at redhat.com Mon Dec 16 00:32:39 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 16 Dec 2013 00:32:39 +0000 Subject: [zanata-bugs] [Bug 1040717] CleanDatabaseRule does not fully clean the database In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1040717 Damian Jansen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |ON_QA -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=i7qsUcLf1l&a=cc_unsubscribe From bugzilla at redhat.com Mon Dec 16 01:13:58 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 16 Dec 2013 01:13:58 +0000 Subject: [zanata-bugs] [Bug 1043330] New: Existing OpenId user cannot save any setting from the Edit profile view Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1043330 Bug ID: 1043330 Summary: Existing OpenId user cannot save any setting from the Edit profile view Product: Zanata Version: 3.1 Component: Component-zanata-client Severity: urgent Assignee: irooskov at redhat.com Reporter: dchen at redhat.com QA Contact: zanata-qa at redhat.com CC: zanata-bugs at redhat.com Description of problem: The existing OpenId user cannot save any setting from the Edit profile view. Version-Release number of selected component (if applicable): Zanata 3.3.0-SNAPSHOT (20131216-1014) How reproducible: Always Steps to Reproduce: 1. Log In as an existing Open Id user. 2. Click the Person Icon -> Settings 3. Click Action "Edit Profile" 4. Fill all the require form and Click Save. 5. Click Action "Edit Profile" again. Actual results: The fields remain empty. Expected results: The fields should show the values you just typed. Additional info: -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=68W6z9XWlM&a=cc_unsubscribe From bugzilla at redhat.com Tue Dec 17 00:51:38 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 17 Dec 2013 00:51:38 +0000 Subject: [zanata-bugs] [Bug 1043720] New: The project search field failed to found existing project using the project name Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1043720 Bug ID: 1043720 Summary: The project search field failed to found existing project using the project name Product: Zanata Version: 3.1 Component: Component-UI Severity: urgent Assignee: irooskov at redhat.com Reporter: dchen at redhat.com QA Contact: zanata-qa at redhat.com CC: zanata-bugs at redhat.com Description of problem: The project search field failed to found existing project using the project name. Version-Release number of selected component (if applicable): Zanata 3.3.0-SNAPSHOT (20131217-0036) How reproducible: Always Steps to Reproduce: 1. Login to Zanata 2. Click Projects 3. Copy the project name of any existing project, and paste in to project search field. 4. Press enter Actual results: Found 0 Projects matching query 'About' Expected results: At least found the project you copy from. Additional info: -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=IOAJTba9Nx&a=cc_unsubscribe From bugzilla at redhat.com Tue Dec 17 02:22:49 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 17 Dec 2013 02:22:49 +0000 Subject: [zanata-bugs] [Bug 1043720] The project search field failed to found existing project using the project name In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1043720 Alex Eng changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aeng at redhat.com --- Comment #1 from Alex Eng --- Please make sure the test instance has indexing done on Project. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=4SZb0rl2On&a=cc_unsubscribe From bugzilla at redhat.com Wed Dec 18 01:02:56 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 18 Dec 2013 01:02:56 +0000 Subject: [zanata-bugs] [Bug 1043720] The project search field failed to found existing project using the project name In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1043720 --- Comment #2 from Ding-Yi Chen --- After further digging I found out that the search only works only if it contains only the lower case and number. It wont' work when it contains other characters like upper case, '-', spaces and other character like '"'. Steps to Reproduce: 1. Login to Zanata 2. Click Projects 3. Find a project that contains upper case, spaces or dash. 4. Copy and paste the project name to project search field. 5. Press enter Actual results: Found 0 Projects matching query. Expected results: At least found the project you copy from. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=YTaUGM8SSJ&a=cc_unsubscribe From bugzilla at redhat.com Wed Dec 18 02:12:09 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 18 Dec 2013 02:12:09 +0000 Subject: [zanata-bugs] [Bug 1044261] New: RFE: Drupal integration with Zanata Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1044261 Bug ID: 1044261 Summary: RFE: Drupal integration with Zanata Product: Zanata Version: development Component: Usability Assignee: irooskov at redhat.com Reporter: damason at redhat.com QA Contact: zanata-qa at redhat.com CC: zanata-bugs at redhat.com Description of problem: Translating content from Drupal using Zanata is currently a manual process requiring copying of source content from the editor in Drupal, saving it to the local file system, then uploading to Zanata, with a similar reverse process for taking translations from Zanata to the Drupal site. A plugin for Drupal could communicate directly with a Zanata server to automatically push updated source strings whenever content is edited, and check for updated translations periodically or on-demand. This would cut out all the manual content-copying steps for a maintainer of a project in Drupal. Features that may be necessary or useful: - admin page - set Zanata server to use - indicate if the server is not found - set maintainer username & API key - set project & version to use - indicate if the project does not exist on the specified server, offer to create it - indicate if the version does not exist on the specified server, offer to create it - settings page - set interval and timing for automatic check for new translations (including never) - view list of content that is marked for translation - allow content to be added to the list - allow translations to be checked for any item on the list - allow source to be pushed to Zanata for any item on the list - in Drupal content editor - checkbox to indicate whether the content being edited should be sent for translation - if the content being edited should be sent for translation, it will be pushed to Zanata when the content is saved - sensible behaviour should be considered for draft items and publishing of items - publishing an item could trigger a check for translations of the item (to support a workflow in which an item is published when its translations are completed) - notifications could be sent to a specified mailing list when new content is available to translate. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Dg7RYrPyxh&a=cc_unsubscribe From bugzilla at redhat.com Wed Dec 18 02:36:52 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 18 Dec 2013 02:36:52 +0000 Subject: [zanata-bugs] [Bug 1044261] RFE: Drupal integration with Zanata In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1044261 Luke Brooker changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lbrooker at redhat.com --- Comment #1 from Luke Brooker --- It is probably worth looking at this Drupal module (https://drupal.org/project/i18n), as that is what most international sites use and seeing how we could integrate with that. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=3UR4Rrlm89&a=cc_unsubscribe From bugzilla at redhat.com Wed Dec 18 04:09:52 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 18 Dec 2013 04:09:52 +0000 Subject: [zanata-bugs] [Bug 1044301] New: RFE: As a project maintainer, I want to sort the translation by completeness, o that I can easily work out what to put in to final product Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1044301 Bug ID: 1044301 Summary: RFE: As a project maintainer, I want to sort the translation by completeness, o that I can easily work out what to put in to final product Product: Zanata Version: 3.1 Component: Component-UI Severity: medium Assignee: irooskov at redhat.com Reporter: dchen at redhat.com QA Contact: zanata-qa at redhat.com CC: zanata-bugs at redhat.com Description of problem: As a project maintainer, I want to sort the translation by completeness, so that I can easily work out what to put in to final product. Definition of Completeness: percentage of approved/total for project required review; otherwise translated/total. Version-Release number of selected component (if applicable): Zanata 3.3.0-SNAPSHOT (20131218-0039) How reproducible: Always Steps to Reproduce: 1. Click a existing project that is partially translated. 2. Click any version. Actual results: There is no way to sort by completeness by words or messages. Expected results: User should be able to: 1. Ascending sort by word completeness 2. Ascending sort by message completeness 1. Descending sort by word completeness 2. Descending sort by message completeness Additional info: -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=XevNATBRE4&a=cc_unsubscribe From bugzilla at redhat.com Wed Dec 18 05:30:59 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 18 Dec 2013 05:30:59 +0000 Subject: [zanata-bugs] [Bug 1039810] Cancel contact email causes exception In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1039810 Ding-Yi Chen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ON_QA |VERIFIED CC| |dchen at redhat.com Fixed In Version| |3.3.0-SNAPSHOT | |(20131218-0039) --- Comment #2 from Ding-Yi Chen --- VERIFIED with Zanata 3.3.0-SNAPSHOT (20131218-0039) -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=7QcaY3aes2&a=cc_unsubscribe From bugzilla at redhat.com Wed Dec 18 23:40:29 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 18 Dec 2013 23:40:29 +0000 Subject: [zanata-bugs] [Bug 1044768] New: Zanata does not pull the latest changes in translation Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1044768 Bug ID: 1044768 Summary: Zanata does not pull the latest changes in translation Product: Zanata Version: 3.1 Component: Component-Maven Assignee: irooskov at redhat.com Reporter: ykatabam at redhat.com QA Contact: zanata-qa at redhat.com CC: zanata-bugs at redhat.com Description of problem: When I run "mvn org.zanata:zanata-maven-plugin:pull", it does not pull the latest changes in translation, with messages "No changes in translations for xxx" for all files. I am using zanata-maven-plugin:3.0.1 Version-Release number of selected component (if applicable): 3.1.2 How reproducible: 100% Steps to Reproduce: 1. Make a change in translation in zanata 2. Run "$ mvn org.zanata:zanata-maven-plugin:pull" 3. Check the output. Actual results: It prints the following output: Are you sure (y/n)? y [INFO] No changes in translations for locale ja and document Appendix [INFO] No changes in translations for locale ja and document Author_Group [INFO] No changes in translations for locale ja and document Book_Info [INFO] No changes in translations for locale ja and document Converting_VMs_KVM [INFO] No changes in translations for locale ja and document Converting_VMs_RHEV [INFO] No changes in translations for locale ja and document Debugging [INFO] No changes in translations for locale ja and document Feedback [INFO] No changes in translations for locale ja and document Installing [INFO] No changes in translations for locale ja and document Introduction [INFO] No changes in translations for locale ja and document P2V_migration [INFO] No changes in translations for locale ja and document Preface [INFO] No changes in translations for locale ja and document References [INFO] No changes in translations for locale ja and document Revision_History [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 14.960s [INFO] Finished at: Thu Dec 19 09:28:13 EST 2013 [INFO] Final Memory: 8M/141M [INFO] ------------------------------------------------------------------------ Local build does not have the changes applied either. Expected results: Are you sure (y/n)? y [INFO] Writing translation file in locale ja-JP for document Appendix [INFO] Writing translation file in locale ja-JP for document Author_Group [INFO] Writing translation file in locale ja-JP for document Book_Info [INFO] Writing translation file in locale ja-JP for document Converting_VMs_KVM [INFO] Writing translation file in locale ja-JP for document Converting_VMs_RHEV [INFO] Writing translation file in locale ja-JP for document Debugging [INFO] Writing translation file in locale ja-JP for document Feedback [INFO] Writing translation file in locale ja-JP for document Installing [INFO] Writing translation file in locale ja-JP for document Introduction [INFO] Writing translation file in locale ja-JP for document P2V_migration [INFO] Writing translation file in locale ja-JP for document Preface [INFO] Writing translation file in locale ja-JP for document References [INFO] Writing translation file in locale ja-JP for document Revision_History [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 32.221s [INFO] Finished at: Thu Dec 19 09:30:59 EST 2013 [INFO] Final Memory: 8M/110M [INFO] ------------------------------------------------------------------------ Additional info: Running the command with -Dzanata.useCache=false fixes the problem. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=hxySlbyxbQ&a=cc_unsubscribe From bugzilla at redhat.com Wed Dec 18 23:42:32 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 18 Dec 2013 23:42:32 +0000 Subject: [zanata-bugs] [Bug 1044768] Zanata does not pull the latest changes in translation In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1044768 Yuko Katabami changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|unspecified |high Severity|unspecified |high -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=3WNy57Tr5T&a=cc_unsubscribe From bugzilla at redhat.com Wed Dec 18 23:52:03 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 18 Dec 2013 23:52:03 +0000 Subject: [zanata-bugs] [Bug 1044768] Zanata does not pull the latest changes in translation In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1044768 Carlos Munoz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |camunoz at redhat.com --- Comment #2 from Carlos Munoz --- This seems to be related to the cache, as removing the cache directory or using the 'useCache=false' option solves the problem. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=bePasqFPKO&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 19 13:58:23 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 19 Dec 2013 13:58:23 +0000 Subject: [zanata-bugs] [Bug 1044261] RFE: Drupal integration with Zanata In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1044261 Allison Matlack changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bpritche at redhat.com, | |dkolbas at redhat.com, | |enewby at redhat.com, | |tmctighe at redhat.com --- Comment #2 from Allison Matlack --- Adding myself and our Drupal folks to the cc list so we can keep up with you. Also wanted to mention http://www.lingotek.com/. They're a full-service translation vendor, so we didn't follow up much with them, but their technology might be of interest. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=GxjDe8OAT6&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 19 21:26:24 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 19 Dec 2013 21:26:24 +0000 Subject: [zanata-bugs] [Bug 1037925] Search Projects field not character limited In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1037925 Alex Eng changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ON_QA --- Comment #1 from Alex Eng --- Project search field now is limit to 100 character, given it searches through slug (40 char max), name (40 char max), and description(100 char max) -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=LDtfqL4LE0&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 19 21:32:08 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 19 Dec 2013 21:32:08 +0000 Subject: [zanata-bugs] [Bug 1035057] Group "Add Language" field should be limited to something sensible In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1035057 Alex Eng changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |ON_QA --- Comment #4 from Alex Eng --- Pull request: https://github.com/zanata/zanata-server/pull/325 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=fEEGqnFCPA&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 19 21:32:18 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 19 Dec 2013 21:32:18 +0000 Subject: [zanata-bugs] [Bug 1035057] Group "Add Language" field should be limited to something sensible In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1035057 Alex Eng changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|lbrooker at redhat.com |aeng at redhat.com -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=EsOrG5sx2p&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 19 21:34:53 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 19 Dec 2013 21:34:53 +0000 Subject: [zanata-bugs] [Bug 981690] Project maintainer's validation options aren't used in editor In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=981690 Alex Eng changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ON_QA -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=U5ZGyE7zP3&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 19 21:35:02 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 19 Dec 2013 21:35:02 +0000 Subject: [zanata-bugs] [Bug 981690] Project maintainer's validation options aren't used in editor In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=981690 Alex Eng changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|zanata-dev-internal at redhat. |aeng at redhat.com |com | -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=bcu40UA6So&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 19 21:36:53 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 19 Dec 2013 21:36:53 +0000 Subject: [zanata-bugs] [Bug 1037932] Unhandled exception: Add language field allows more character than the database does (255) In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1037932 Alex Eng changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.redhat.com | |/show_bug.cgi?id=1037933 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=yGhDsqAfAa&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 19 21:36:53 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 19 Dec 2013 21:36:53 +0000 Subject: [zanata-bugs] [Bug 1037933] Unhandled exception: Add language with a string too large can cause a lock exception on save In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1037933 Alex Eng changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aeng at redhat.com See Also| |https://bugzilla.redhat.com | |/show_bug.cgi?id=1037932 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=R1v429ltzg&a=cc_unsubscribe From bugzilla at redhat.com Thu Dec 19 21:43:58 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 19 Dec 2013 21:43:58 +0000 Subject: [zanata-bugs] [Bug 919959] Statistic caching In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=919959 Alex Eng changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution|--- |CURRENTRELEASE Last Closed| |2013-12-19 16:43:58 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=UtMyShpKjJ&a=cc_unsubscribe From bugzilla at redhat.com Sun Dec 22 21:16:44 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 22 Dec 2013 21:16:44 +0000 Subject: [zanata-bugs] [Bug 1043720] The project search field failed to found existing project using the project name In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1043720 Alex Eng changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|irooskov at redhat.com |aeng at redhat.com --- Comment #3 from Alex Eng --- Pull request: https://github.com/zanata/zanata-server/pull/329 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=vk4rMJAfxw&a=cc_unsubscribe From bugzilla at redhat.com Sun Dec 22 21:40:55 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 22 Dec 2013 21:40:55 +0000 Subject: [zanata-bugs] [Bug 1043720] The project search field failed to found existing project using the project name In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1043720 --- Comment #4 from Alex Eng --- Given that we are using hibernate search features, there's some limitation apply to it (ignore symbol e.g. quotes and hyphen). This issue can be solve using different type of analyzer, but that will remove the current implement of prefix string search. With recent changes (autocomplete and case insensitive, string prefix search), I think it covers most of the use case in general use. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=3M6XuhosZg&a=cc_unsubscribe From bugzilla at redhat.com Mon Dec 23 00:38:02 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 23 Dec 2013 00:38:02 +0000 Subject: [zanata-bugs] [Bug 1037932] Unhandled exception: Add language field allows more character than the database does (255) In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1037932 Patrick Huang changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pahuang at redhat.com --- Comment #1 from Patrick Huang --- https://github.com/zanata/zanata-server/pull/331 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=FJnadKFkGD&a=cc_unsubscribe From bugzilla at redhat.com Mon Dec 23 00:38:35 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 23 Dec 2013 00:38:35 +0000 Subject: [zanata-bugs] [Bug 1037932] Unhandled exception: Add language field allows more character than the database does (255) In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1037932 --- Comment #2 from Patrick Huang --- https://github.com/zanata/zanata-api/pull/8 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=hKmbJMFtG3&a=cc_unsubscribe From bugzilla at redhat.com Mon Dec 23 00:38:47 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 23 Dec 2013 00:38:47 +0000 Subject: [zanata-bugs] [Bug 1037933] Unhandled exception: Add language with a string too large can cause a lock exception on save In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1037933 Patrick Huang changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pahuang at redhat.com --- Comment #1 from Patrick Huang --- https://github.com/zanata/zanata-server/pull/331 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=pN2r1dy5dF&a=cc_unsubscribe From bugzilla at redhat.com Mon Dec 23 00:39:03 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 23 Dec 2013 00:39:03 +0000 Subject: [zanata-bugs] [Bug 1037933] Unhandled exception: Add language with a string too large can cause a lock exception on save In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1037933 Patrick Huang changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|zanata-dev-internal at redhat. |pahuang at redhat.com |com | -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=BUCR53bSOb&a=cc_unsubscribe From bugzilla at redhat.com Mon Dec 23 00:39:10 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 23 Dec 2013 00:39:10 +0000 Subject: [zanata-bugs] [Bug 1037932] Unhandled exception: Add language field allows more character than the database does (255) In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1037932 Patrick Huang changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|zanata-dev-internal at redhat. |pahuang at redhat.com |com | -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=sckFxM31Z8&a=cc_unsubscribe From bugzilla at redhat.com Mon Dec 23 01:10:10 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 23 Dec 2013 01:10:10 +0000 Subject: [zanata-bugs] [Bug 1037925] Search Projects field not character limited In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1037925 Damian Jansen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ON_QA |VERIFIED Fixed In Version| |3.3.0-SNAPSHOT | |(20131223-0915) --- Comment #2 from Damian Jansen --- Verified at cd51a1620e283882a8eb26cd862314b48af67617 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=EVRdUvLPIC&a=cc_unsubscribe From bugzilla at redhat.com Mon Dec 23 01:14:30 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 23 Dec 2013 01:14:30 +0000 Subject: [zanata-bugs] [Bug 1040717] CleanDatabaseRule does not fully clean the database In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1040717 Damian Jansen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ON_QA |VERIFIED --- Comment #2 from Damian Jansen --- Verified. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=a2LFdkzMT0&a=cc_unsubscribe From bugzilla at redhat.com Mon Dec 23 01:16:52 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 23 Dec 2013 01:16:52 +0000 Subject: [zanata-bugs] [Bug 1035057] Group "Add Language" field should be limited to something sensible In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1035057 Damian Jansen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ON_QA |VERIFIED Fixed In Version| |3.3.0-SNAPSHOT | |(20131223-0915) --- Comment #5 from Damian Jansen --- Verified at cd51a1620e283882a8eb26cd862314b48af67617 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=d3PtLZLeOH&a=cc_unsubscribe From bugzilla at redhat.com Mon Dec 23 03:11:45 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 23 Dec 2013 03:11:45 +0000 Subject: [zanata-bugs] [Bug 906172] Editor becomes slow when working with a long string In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=906172 --- Comment #14 from Alex Eng --- https://bugzilla.redhat.com/show_bug.cgi?id=906172#c12: https://github.com/zanata/zanata-server/pull/332 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=mOoc54DByc&a=cc_unsubscribe From bugzilla at redhat.com Mon Dec 23 03:45:34 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 23 Dec 2013 03:45:34 +0000 Subject: [zanata-bugs] [Bug 981690] Project maintainer's validation options aren't used in editor In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=981690 Damian Jansen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ON_QA |CLOSED CC| |djansen at redhat.com Resolution|--- |DUPLICATE Last Closed| |2013-12-22 22:45:34 --- Comment #2 from Damian Jansen --- This has been invalidated by the Enforced Validations feature, though still yet to make it to live. *** This bug has been marked as a duplicate of bug 1006063 *** -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=UnBkJuSsLT&a=cc_unsubscribe From bugzilla at redhat.com Mon Dec 23 05:14:34 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 23 Dec 2013 05:14:34 +0000 Subject: [zanata-bugs] [Bug 906172] Editor becomes slow when working with a long string In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=906172 Patrick Huang changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |ON_QA CC| |pahuang at redhat.com -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=f7UeHYC10m&a=cc_unsubscribe From bugzilla at redhat.com Mon Dec 23 05:14:55 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 23 Dec 2013 05:14:55 +0000 Subject: [zanata-bugs] [Bug 1037933] Unhandled exception: Add language with a string too large can cause a lock exception on save In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1037933 Patrick Huang changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |ON_QA -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=04CrQYUR34&a=cc_unsubscribe From bugzilla at redhat.com Tue Dec 24 01:01:40 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 24 Dec 2013 01:01:40 +0000 Subject: [zanata-bugs] [Bug 1037933] Unhandled exception: Add language with a string too large can cause a lock exception on save In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1037933 Ding-Yi Chen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ON_QA |ASSIGNED CC| |dchen at redhat.com Depends On| |1037932 --- Comment #2 from Ding-Yi Chen --- Tested with Zanata 3.3.0-SNAPSHOT (20131224-0037) After I pasted description of this bug to the language fields/ It does not have lock exception, however, it shows: Underscores should be replaced with dashes. Replace them Nothing happened after either click "Replace them" or "Save". I suggest this bug shoulb depend on Bug 1037932. Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1037932 [Bug 1037932] Unhandled exception: Add language field allows more character than the database does (255) -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=IRI4CFSeZX&a=cc_unsubscribe From bugzilla at redhat.com Tue Dec 24 01:01:40 2013 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 24 Dec 2013 01:01:40 +0000 Subject: [zanata-bugs] [Bug 1037932] Unhandled exception: Add language field allows more character than the database does (255) In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1037932 Ding-Yi Chen changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1037933 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1037933 [Bug 1037933] Unhandled exception: Add language with a string too large can cause a lock exception on save -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=wuNbdzXwuk&a=cc_unsubscribe