Activity - Runtime Infrastructure - Golden Code Redmine

Activity

From 07/20/2023 to 08/18/2023

08/18/2023

04:26 AM Bug #7649: logging level for ScanDriver's "Failure in file" must be sever to log the stacktrace: Can we merge this to trunk? Constantin Asofiei

08/11/2023

10:50 AM Feature #7675: add missing runtime support for 4GL command line parameters: Some of the 4GL command line parameters which we can specify (in either the directory or as a bootstrap config value)... Greg Shah
10:02 AM Feature #7675 (New): add missing runtime support for 4GL command line parameters: Greg Shah

08/01/2023

09:28 AM Bug #7649: logging level for ScanDriver's "Failure in file" must be sever to log the stacktrace: Code Review Task Branch 7649a Revision 14680
No objection. Greg Shah
09:27 AM Bug #7649: logging level for ScanDriver's "Failure in file" must be sever to log the stacktrace: > It will take effect if no mode is already selected for the JVM. The point of the mode will be to simply reroute the... Greg Shah
03:09 AM Bug #7649: logging level for ScanDriver's "Failure in file" must be sever to log the stacktrace: ops Galya B
03:08 AM Bug #7649: logging level for ScanDriver's "Failure in file" must be sever to log the stacktrace: This is fine.
If you find some interactive tools having inconsistent output in standalone, then we should do as I ... Galya B
03:02 AM Bug #7649 (Review): logging level for ScanDriver's "Failure in file" must be sever to log the sta...: Created task branch 7649a from trunk rev 14679.
The fix is in 7649a rev 14680. Constantin Asofiei
03:00 AM Bug #7649: logging level for ScanDriver's "Failure in file" must be sever to log the stacktrace: Galya B wrote:
> On trunk @Failure in file@ is:
>
> [...]
>
> But maybe you've already reworked it on another ... Constantin Asofiei
02:59 AM Bug #7649: logging level for ScanDriver's "Failure in file" must be sever to log the stacktrace: On trunk @Failure in file@ is:... Galya B
02:57 AM Bug #7649: logging level for ScanDriver's "Failure in file" must be sever to log the stacktrace: In this case (ScanDriver is used by conversion) FWD uses @CentralLoggerFallback@, which has a default logging level o... Constantin Asofiei
02:56 AM Bug #7649: logging level for ScanDriver's "Failure in file" must be sever to log the stacktrace: An important side note: @Failure in file@ at the moment is not logged in any way way, it's simple System.out.println.... Galya B
02:54 AM Bug #7649: logging level for ScanDriver's "Failure in file" must be sever to log the stacktrace: With standalone tools I was cautious to convert all @System.out@ prints to logs, because when these run in standalone... Galya B
02:44 AM Bug #7649: logging level for ScanDriver's "Failure in file" must be sever to log the stacktrace: There are two places in @ScanDriver@ where a @Failure in file@ parsing problem may be encountered - both these need t... Constantin Asofiei
02:38 AM Bug #7649 (Closed): logging level for ScanDriver's "Failure in file" must be sever to log the sta...: Constantin Asofiei

07/25/2023

10:52 AM Bug #7635 (Test): RemoteObject defaults to 'tracing' mode: I forgot.
Task branch 7635a was merged to trunk as rev 14671 and archived.
Galya B
10:39 AM Bug #7635: RemoteObject defaults to 'tracing' mode: You can merge to trunk. Greg Shah
10:39 AM Bug #7635: RemoteObject defaults to 'tracing' mode: Code Review 7635a Revision 14669
The change is fine. The cost is 3 extra method calls (isLoggable() and inside th... Greg Shah

07/24/2023

08:21 AM Bug #7635 (Review): RemoteObject defaults to 'tracing' mode: 7635a r14669 simply removing the flag should be good enough. There is already optimization and invalidation in the @C... Galya B
08:06 AM Bug #7635 (WIP): RemoteObject defaults to 'tracing' mode: Galya B
08:03 AM Bug #7635: RemoteObject defaults to 'tracing' mode: In @RemoteObject@, the @LOG@ instance gets created and @RemoteObject$RemoteAccess.tracing@ flag gets set before the l... Constantin Asofiei
08:01 AM Bug #7635 (Closed): RemoteObject defaults to 'tracing' mode: Constantin Asofiei

07/20/2023

07:14 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat: According to the logs customer's app uses the first implementation it finds, i.e. FWD's, that's why we see Spring try... Galya B
07:08 AM Bug #7589: org.slf4j.impl.StaticLoggerBinder when deploying p2j.jar in tomcat: The customer's log has this:... Constantin Asofiei

Also available in: Atom