Activity
From 11/10/2022 to 12/09/2022
12/09/2022
- 05:41 AM Bug #5699: broken logfile name on Windows appserver clients (and probably other cases on Windows)
- Greg Shah wrote:
> In your current setup, you are just using a local copy *bound to* the central repo. Any local co... - 05:38 AM Bug #5699 (Test): broken logfile name on Windows appserver clients (and probably other cases on W...
- When you believe that all functional requirements of the task are complete, please set the % Done to 100%.
- 05:37 AM Bug #5699: broken logfile name on Windows appserver clients (and probably other cases on Windows)
- > I messed up the branch creation / co and pushed from the local branch directly to 3821c. I'll be more careful next ...
- 05:32 AM Bug #5699: broken logfile name on Windows appserver clients (and probably other cases on Windows)
- Greg Shah wrote:
> Code Review Task Branch 3821c Revision 14429
>
> The change is good, however you are missing t... - 05:30 AM Bug #5699: broken logfile name on Windows appserver clients (and probably other cases on Windows)
- Code Review Task Branch 3821c Revision 14429
The change is good, however you are missing the history entry. - 05:20 AM Bug #5699 (Review): broken logfile name on Windows appserver clients (and probably other cases on...
- Greg Shah wrote:
> Is @string@ not a pointer to @WCHAR@? If the contents of @string@ are not wide characters, then ...
12/08/2022
- 04:23 PM Bug #5699: broken logfile name on Windows appserver clients (and probably other cases on Windows)
- Is @string@ not a pointer to @WCHAR@? If the contents of @string@ are not wide characters, then that explains the re...
- 11:42 AM Bug #5699 (WIP): broken logfile name on Windows appserver clients (and probably other cases on Wi...
- I was able to reproduce it. The problem is in @replace_str@ function. I've added to the code a few comments to show v...
- 01:55 PM Feature #6939: improve proxy performance by hard-coding method invocation
- In the lambda approach, the target instance is already captured, so changing the array also changes the target.
- 01:43 PM Feature #6939: improve proxy performance by hard-coding method invocation
- Greg Shah wrote:
> If we need the ability to temporarily replace the target methods for an implementation,
I don't ... - 01:29 PM Feature #6939: improve proxy performance by hard-coding method invocation
- If we need the ability to temporarily replace the target methods for an implementation, we should consider a kind of ...
- 01:10 PM Feature #6939: improve proxy performance by hard-coding method invocation
- Constantin Asofiei wrote:
> ... directly from the bytecode of the i.e. DMO Implementation class setter/getter.
wh... - 01:07 PM Feature #6939: improve proxy performance by hard-coding method invocation
- Eric, the main issue of the interceptor flavor of the @InvocationHandler@ is that in some cases the target instance o...
12/07/2022
- 07:07 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...
- From Galya, via email:
> I haven't looked at the Java classes instantiated by the spawner, so let me ask if there ...
12/05/2022
- 09:29 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...
- Greg Shah wrote:
> The approach seems reasonable.
>
> Eugenie: Do you have any thoughts, questions or concerns?
... - 09:11 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...
- The approach seems reasonable.
Eugenie: Do you have any thoughts, questions or concerns? - 06:18 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...
- The Windows spawner is a lot more simple than the UNIX one in the process creation part (more complicated in the secu...
- 04:41 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...
- Greg Shah wrote:
> The test code doesn't help me understand the process tree/pid list/redirected output log name for...
12/02/2022
- 11:17 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...
- The test code doesn't help me understand the process tree/pid list/redirected output log name for the FWD client. Ca...
12/01/2022
- 10:49 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...
- I created a simple test to verify @execvp@ behaviour and uploaded it as zip. The test function in @C@ prints the pid ...
- 09:12 AM Bug #5701 (WIP): logfile names for -O outputToFile use the spawner pid instead of the Java (FWD c...
- Constantin Asofiei wrote:
> The spawner will use @NativeSecureConnection.command@ to determine the launch command fo... - 07:08 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...
- Galya Bogdanova wrote:
> ... running in background where no client driver seems to be instantiated in the Java code,... - 06:51 AM Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client ...
- This is how I read the logic for the spawner (I'll be going with the Unix example):
@ClientBuilder#localStart()@ b...
11/17/2022
- 07:41 AM Feature #6939: improve proxy performance by hard-coding method invocation
- Eric Faulhaber wrote:
> But, recently we discovered that @ReflectASM@ actually can perform worse than reflection on ...
11/16/2022
- 03:28 PM Feature #6939: improve proxy performance by hard-coding method invocation
- When I originally implemented the @com.goldencode.proxy@ package, the pressing goal at the time was to improve memory...
- 02:48 PM Feature #6939 (New): improve proxy performance by hard-coding method invocation
Also available in: Atom