Localyzer Dashboard FAQ - Revision history

Olibouban at 20:35, 23 February 2021

2021-02-23T20:35:41Z

← Older revision		Revision as of 20:35, 23 February 2021
Line 9:		Line 9:


	= What are the ~~LRM~~ Source Issues?=		= What are the Localyzer Source Issues?=

	In the Resource Manager Dashboard, the number of ~~LRM~~ Issues is shown.		In the Resource Manager Dashboard, the number of Localyzer Issues is shown.

	[[File: LRMSourceIssues.jpg \|600px]]		[[File: LRMSourceIssues.jpg \|600px]]

Olibouban: Olibouban moved page LRM Dashboard FAQ to Localyzer Dashboard FAQ

2021-02-23T20:35:01Z

Olibouban moved page LRM Dashboard FAQ to Localyzer Dashboard FAQ

← Older revision	Revision as of 20:35, 23 February 2021
(No difference)

Rdaly at 17:22, 26 July 2019

2019-07-26T17:22:59Z

← Older revision		Revision as of 17:22, 26 July 2019
Line 7:		Line 7:
	If the base file text (en US for instance) has been modified, prep kits should be sent for translation. The source files still have the equivalent translated files, with all the keys and all the text, so it remains at 100%. If keys are added to the base file text, the Completion Report will show lower than 100% until the new keys are translated and returned.		If the base file text (en US for instance) has been modified, prep kits should be sent for translation. The source files still have the equivalent translated files, with all the keys and all the text, so it remains at 100%. If keys are added to the base file text, the Completion Report will show lower than 100% until the new keys are translated and returned.

	~~= I keep getting an error on ./sonar start =~~
	~~You can try to start Sonar by launching this command in $DASHBOARD_HOME:~~
	java -Djava.awt.headless=true -XX:MaxPermSize=128m -server -Xmx512m -Xms256m -cp lib/:extensions/jdbc-driver/derby/:extensions/jdbc-driver/mssql/:extensions/jdbc-driver/mysql/:extensions/jdbc-driver/oracle/:extensions/jdbc-driver/postgresql.:. org.sonar.application.StartServer


	= What are the LRM Source Issues ?=		= What are the LRM Source Issues?=

	In the Resource Manager Dashboard, the number of LRM Issues is shown.		In the Resource Manager Dashboard, the number of LRM Issues is shown.

Rdaly at 17:22, 26 July 2019

2019-07-26T17:22:37Z

← Older revision		Revision as of 17:22, 26 July 2019
Line 11:		Line 11:
	java -Djava.awt.headless=true -XX:MaxPermSize=128m -server -Xmx512m -Xms256m -cp lib/:extensions/jdbc-driver/derby/:extensions/jdbc-driver/mssql/:extensions/jdbc-driver/mysql/:extensions/jdbc-driver/oracle/:extensions/jdbc-driver/postgresql.:. org.sonar.application.StartServer		java -Djava.awt.headless=true -XX:MaxPermSize=128m -server -Xmx512m -Xms256m -cp lib/:extensions/jdbc-driver/derby/:extensions/jdbc-driver/mssql/:extensions/jdbc-driver/mysql/:extensions/jdbc-driver/oracle/:extensions/jdbc-driver/postgresql.:. org.sonar.application.StartServer

	~~== Sonar starts but then stops ==~~

	~~This FAQ is for older versions of the Lingoport Dashboard. Systems installed after May 2018 no longer use port 9000 and this may no longer be applicable.~~

	~~After starting Sonar, check the status multiple times. Sometimes, it will say that it started, but then quit after a few seconds.~~
	~~<pre>~~
	~~> /var/lib/jenkins/lingoport/dashboard-server-5.6.1/bin/linux-x86-64/sonar.sh start~~
	~~Starting SonarQube...~~
	~~Started SonarQube.~~

	~~> /var/lib/jenkins/lingoport/dashboard-server-5.6.1/bin/linux-x86-64/sonar.sh status~~
	~~SonarQube is running (13880).~~
	~~> /var/lib/jenkins/lingoport/dashboard-server-5.6.1/bin/linux-x86-64/sonar.sh status~~
	~~SonarQube is running (13880).~~
	~~> /var/lib/jenkins/lingoport/dashboard-server-5.6.1/bin/linux-x86-64/sonar.sh status~~
	~~SonarQube is not running.~~
	~~</pre>~~

	~~Check to see if the process is still up, even though Sonar thinks it is down. If there is no output, the process is not running.~~

	~~<pre>~~
	~~> fuser 9000/tcp~~
	~~9090/tcp: 14118~~
	~~> fuser 9001/tcp~~
	~~9010/tcp: 13905~~
	~~</pre>~~

	~~Kill the processes using the following commands:~~
	~~<pre>~~
	~~> fuser -k 9000/tcp~~
	~~9090/tcp: 14118~~
	~~> fuser -k 9001/tcp~~
	~~9010/tcp: 13905~~
	~~</pre>~~

	~~And start the sonar process again and check the status multiple times.~~
	~~<pre>~~
	~~> /var/lib/jenkins/lingoport/dashboard-server-5.6.1/bin/linux-x86-64/sonar.sh start~~
	~~Starting SonarQube...~~
	~~Started SonarQube.~~

	~~> /var/lib/jenkins/lingoport/dashboard-server-5.6.1/bin/linux-x86-64/sonar.sh status~~
	~~SonarQube is running (13880).~~
	~~</pre>~~

	~~= Unable to read and import the source file: What do I do? =~~

	~~I'm getting this error when importing files using the Dashboard_Update.sh:~~
	~~<pre>~~
	~~ERROR: Error during Sonar runner execution~~
	~~ERROR: Unable to execute Sonar~~
	~~ERROR: Caused by: Unable to read and import the source file : 'FILENAME HERE' with the charset : 'UTF-8'.~~
	~~ERROR: Caused by: Unable to persist : SnapshotSource[snapshot_id=120719,data=<?php~~
	[...] ERROR: Caused by: org.hibernate.exception.GenericJDBCException: could not insert: [org.sonar.api.database.model.SnapshotSource] ERROR: Caused by: could not insert: [org.sonar.api.database.model.SnapshotSource] ERROR: Caused by: Incorrect string value: '\xF0\x9F\x8F\x81 ...' for column 'data' at row 1
	~~</pre>~~

	~~This indicates that the import part of the Dashboard is trying to read a file with an encoding (here UTF-8) which is not the encoding of the file to read, or the file is corrupted for that encoding.~~

	~~Some possible solutions:~~
	* Exclude the offending file(s) from being imported using sonar-project.properties <code>sonar.exclusions=com/example/tests/*,com/example/package2/.java. </code>
	* Change the encoding of the Dashboard import using sonar-project.properties <code>sonar.sourceEncoding=Cp1252</code> or whatever is the right encoding for the project.

	= What are the LRM Source Issues ?=		= What are the LRM Source Issues ?=

Rdaly: /* What are the LRM Source Issues ? */

2019-07-26T17:04:58Z

What are the LRM Source Issues ?

← Older revision		Revision as of 17:04, 26 July 2019
Line 84:		Line 84:

	For this case, the majority of the issues are '''<code>LRM Src Tran-Missing File Check</code>''' and '''<code>LRM Src Tran-Missing Key Check</code>''' which simply mean that the files have not been translated yet, so there are no translated files or keys.		For this case, the majority of the issues are '''<code>LRM Src Tran-Missing File Check</code>''' and '''<code>LRM Src Tran-Missing Key Check</code>''' which simply mean that the files have not been translated yet, so there are no translated files or keys.


	See [[LRM Checks]] for more information about these issues. Unless the issues are 'Critical', these are warnings and prepkits can still be created.		See [[LRM Checks]] for more information about these issues. Unless the issues are 'Critical', these are warnings and prepkits can still be created.

Rdaly: /* The Resource Manager Completion Report indicates 100% but some kits are outstanding. What does it mean? */

2019-07-26T17:03:25Z

The Resource Manager Completion Report indicates 100% but some kits are outstanding. What does it mean?

← Older revision		Revision as of 17:03, 26 July 2019
Line 3:		Line 3:
	[[File:DashboardCompleteVTranslation.jpg]]		[[File:DashboardCompleteVTranslation.jpg]]

	The Completion Report is based on the base files (say, en US files) and the translated files (say de and fr) to determine how many keys, how many files, how many base words do not have a translation. If the French files, the keys in the base file, and the translated texts are present, the Completion ~~widget~~ will say 100%.		The Completion Report is based on the base files (say, en US files) and the translated files (say de and fr) to determine how many keys, how many files, how many base words do not have a translation. If the French files, the keys in the base file, and the translated texts are present, the Completion Report will say 100%.

	If the base file text (en US for instance) has been modified, prep kits should be sent for translation. The source files still have the equivalent translated files, with all the keys and all the text, so it remains at 100%.		If the base file text (en US for instance) has been modified, prep kits should be sent for translation. The source files still have the equivalent translated files, with all the keys and all the text, so it remains at 100%. If keys are added to the base file text, the Completion Report will show lower than 100% until the new keys are translated and returned.

	= I keep getting an error on ./sonar start =		= I keep getting an error on ./sonar start =

Rdaly at 17:01, 26 July 2019

2019-07-26T17:01:49Z

← Older revision		Revision as of 17:01, 26 July 2019
Line 1:		Line 1:
	= The Resource Manager Completion ~~widget~~ indicates 100% but some kits are outstanding. What does it mean? =		= The Resource Manager Completion Report indicates 100% but some kits are outstanding. What does it mean? =

	[[File:DashboardCompleteVTranslation.jpg]]		[[File:DashboardCompleteVTranslation.jpg]]

	The Completion ~~widget~~ is based on the base files (say, en US files) and the translated files (say de and fr) to determine how many keys, how many files, how many base words do not have a translation. If the French files, the keys in the base file, and the translated texts are present, the Completion widget will say 100%.		The Completion Report is based on the base files (say, en US files) and the translated files (say de and fr) to determine how many keys, how many files, how many base words do not have a translation. If the French files, the keys in the base file, and the translated texts are present, the Completion widget will say 100%.

	If the base file text (en US for instance) has been modified, prep kits should be sent for translation. The source files still have the equivalent translated files, with all the keys and all the text, so it remains at 100%.		If the base file text (en US for instance) has been modified, prep kits should be sent for translation. The source files still have the equivalent translated files, with all the keys and all the text, so it remains at 100%.

Rdaly: /* Why am I getting this Date Format Check? */

2019-07-26T16:30:47Z

Why am I getting this Date Format Check?

← Older revision		Revision as of 16:30, 26 July 2019
Line 126:		Line 126:
	This check indicates a string in a resource string could be a date format.		This check indicates a string in a resource string could be a date format.
	For instance, the following text could be date formats:		For instance, the following text could be date formats:
	<code>
	*mm/dd/yyyy		*<code>mm/dd/yyyy</code>
	*D		*<code>D</code>
	*F		*<code>F</code>
	*km		*<code>km</code>
	*h:m		*<code>h:m</code>
	*mm		*<code>mm</code>
	*m/s		*<code>m/s</code>
	</code>
	and are tagged as such potential date format.		and are tagged as such potential date format.

	*'F' could be the "day of the week in months", etc.		*<code>F</code> could be the "day of the week in months", etc.

Rdaly: /* Why am I getting this Date Format Check? */

2019-07-26T16:29:18Z

Why am I getting this Date Format Check?

← Older revision		Revision as of 16:29, 26 July 2019
Line 136:		Line 136:
	</code>		</code>
	and are tagged as such potential date format.		and are tagged as such potential date format.



	*'F' could be the "day of the week in months", etc.		*'F' could be the "day of the week in months", etc.

Rdaly: /* What are critical errors and how do I fix them? */

2019-07-26T16:28:00Z

What are critical errors and how do I fix them?

← Older revision		Revision as of 16:28, 26 July 2019
Line 106:		Line 106:
	Since there are critical errors, no prepkits can be created. Selecting the red text will go to the Issues page to see what the critical errors are. Opening up the file, there are actually 4 issues, but only 3 of them are critical.		Since there are critical errors, no prepkits can be created. Selecting the red text will go to the Issues page to see what the critical errors are. Opening up the file, there are actually 4 issues, but only 3 of them are critical.

	[[File: LRMAllIssues.jpg \| ~~600px~~]]		[[File: LRMAllIssues.jpg \| 900px]]

	The three critical issues are:		The three critical issues are: