Community
Participate
Working Groups
If a remote log import error occurs and the client machine has Locale A and the remote machine has Locale B, sometimes some of the error messages are displayed in language A and some are displayed in language B. All of the messages should be displayed in the language of the client, A in this case.
This problem is due to the fact some error messages are issued by the RemoteLogParserLoader program that is launched via Agent Controller on the remote system and some are issued by the GLA run-time that is called by RemoteLogParserLoader to parse the log file. The client locale is passed to RemoteLogParserLoader by the client when it is launched and that locale is used by RemoteLogParserLoader to load the messages. However, there is currently no mechanism to pass locale to GLA run-time to use to load messages. It loads the messages in the default locale where it is running.
Deferred to 4.3 as it is not a stop ship issue for 4.2 and not a regression.
Cannot contain in 4.3 - deferring to 4.4
Added sizing.
Targetting to fix in i3 and increasing priority to indicate it is planned for 4.4.
This could not be contained in TPTP 4.4 release. Deferring to a future release.
This is required from AC perspective
This probably requires new API to specify the locale that GLA should log messages in.
Targetting 4.5 i2.
Targetting to 4.5 i4.
Cannot be contained in i5, moving to i6.
Created attachment 91496 [details] Patch Patch spans 3 plugins: org.eclipse.hyades.logging.parsers org.eclipse.hyades.logging.adapters org.eclipse.tptp.platform.logging.events
Hi Dave, Can you please review the patch attached. Thanks. The patch has been tested, but you would have to validate and confirm the approach.
Review completed by Alex, comment to add test case.
Marking the defect as being fixed.
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this originator of this enhancement/defect has an inactive Bugzilla account and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since the originator of this enhancement/defect has an inactive Bugzilla account and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
