Activity
From 11/16/2023 to 12/15/2023
12/15/2023
- 07:04 AM Feature #6417: cleanup some known items in appserver support
- @WebSpeed@ used to be OE app in the browser (in some script) running on the WebSpeed agent. So the client knew it is ...
- 04:39 AM Feature #6417: cleanup some known items in appserver support
- > * VersionInfo:clientType supports only 4GLCLIENT and APPSERVER at this time
Access to @clientType@ via:
* @SESS... - 02:51 AM Feature #6649: improve the performance or SourceNameMapper runtime
- [[p2j:Database Configuration#Cache-Sizes]] was updated with the necessary information for configuring the cache size ...
12/14/2023
- 12:24 PM Feature #8124: rework conversion and runtime support for BLOCK-LEVEL and ROUTINE-LEVEL statements
- Instead of emitting @onBlockLevel(Condition.ERROR, Action.THROW);@ or @onRoutineLevel(Condition.ERROR, Action.THROW);...
- 12:22 PM Feature #8124 (New): rework conversion and runtime support for BLOCK-LEVEL and ROUTINE-LEVEL stat...
- 12:18 PM Bug #8084 (Test): refactor the 'execute' method for legacy classes
- 11:56 AM Bug #8084: refactor the 'execute' method for legacy classes
- Branch 8084a was merged to trunk rev 14876 and archived.
- 11:38 AM Bug #8084: refactor the 'execute' method for legacy classes
- If you've done enough, you can merge.
- 11:34 AM Bug #8084: refactor the 'execute' method for legacy classes
- Greg Shah wrote:
> Yes, if you are complete with testing.
I haven't converted all apps, but I think the conversion ... - 09:47 AM Bug #8084 (Internal Test): refactor the 'execute' method for legacy classes
- Yes, if you are complete with testing.
- 09:32 AM Bug #8084: refactor the 'execute' method for legacy classes
- Greg Shah wrote:
> As an additional improvement, I wonder if we should change how @BLOCK-LEVEL@ and @ROUTINE-LEVEL@ ... - 07:10 PM Bug #8084: refactor the 'execute' method for legacy classes
- Code Review Task Branch 8084a Revisions 14870 through 14873
The changes are good.
As an additional improvement,... - 11:19 AM Feature #6649 (Test): improve the performance or SourceNameMapper runtime
- Branch 6649b was merged to trunk rev 14874 and archived.
- 11:08 AM Feature #6649: improve the performance or SourceNameMapper runtime
- Yes, please merge now.
- 11:01 AM Feature #6649: improve the performance or SourceNameMapper runtime
- As this was the last testing required for #6649, I am preparing to merge 6649b.
- 10:58 AM Feature #6649: improve the performance or SourceNameMapper runtime
- Constantin Asofiei wrote:
> Alexandru Lungu wrote:
> > Constantin, if 6649b passes ETF, we can merge it to trunk. P... - 10:32 AM Feature #6649: improve the performance or SourceNameMapper runtime
- Alexandru Lungu wrote:
> Constantin, if 6649b passes ETF, we can merge it to trunk. Please let me know when to proce... - 09:43 AM Feature #6649: improve the performance or SourceNameMapper runtime
- Constantin, if 6649b passes ETF, we can merge it to trunk. Please let me know when to proceed.
- 08:49 AM Feature #6649: improve the performance or SourceNameMapper runtime
- Together with Alexandru we've managed to find a cause and solution for the trunk regression. I'm working on running ...
- 05:37 AM Feature #6649: improve the performance or SourceNameMapper runtime
- Great news! I've ran the regression tests and all tests passed successfully.
- 10:30 AM Bug #8119 (Review): JavaDoc build task produces more warnings in Windows in comparison to Linux
- 10:30 AM Bug #8119 (WIP): JavaDoc build task produces more warnings in Windows in comparison to Linux
- 8119a r14874,14875: Option added to javadoc task to show all warnings.
- 09:15 AM Bug #8119: JavaDoc build task produces more warnings in Windows in comparison to Linux
- @ant@ automatically picks up any @-D@ options on the command line and turns them into properties that can be referenc...
- 09:08 AM Bug #8119: JavaDoc build task produces more warnings in Windows in comparison to Linux
- Once upon a time I got a project with configured linter that wasn't used. I enabled a test plan in the CI/CD for each...
- 08:57 AM Bug #8119: JavaDoc build task produces more warnings in Windows in comparison to Linux
- > So do we want to open the Pandora box?
No, but I do want to have a @-D@ option that we can use to enable it. Ma... - 02:12 AM Bug #8119: JavaDoc build task produces more warnings in Windows in comparison to Linux
- Here it is: The same output with @-Xdoclint:all@. So do we want to open the Pandora box?
- 09:29 AM Bug #8116: SEARCH vs FILE-INFO
- I like the idea.
- 07:13 AM Bug #8116: SEARCH vs FILE-INFO
- Vladimir Tsichevski wrote:
> The only difference I can recall is that the client configuration cannot be set from co... - 06:46 AM Bug #8116: SEARCH vs FILE-INFO
- Eugenie Lyzenko wrote:
> From application point of view the @PROPATH/SEARACHPATH@ should be @,@ separated. But in a ...
12/13/2023
- 10:49 AM Bug #8119: JavaDoc build task produces more warnings in Windows in comparison to Linux
- I don't know of a way to make OpenJDK show them. I'd be glad to see them (as long as it was optional) because to fin...
- 10:30 AM Bug #8119: JavaDoc build task produces more warnings in Windows in comparison to Linux
- Yes, it's Oracle. This explains it.
But the Oracle ones are valid issues. Can we somehow make Open JDK show them, ... - 10:15 AM Bug #8119: JavaDoc build task produces more warnings in Windows in comparison to Linux
- Could you be building on Windows using the Oracle JDK? The Oracle JDK generates a ver long list of javadoc errors as...
- 09:19 AM Bug #8119: JavaDoc build task produces more warnings in Windows in comparison to Linux
- @./gradlew ant-javadoc@ build task produces more warnings in Windows in comparison to Linux.
- 09:16 AM Bug #8119 (Closed): JavaDoc build task produces more warnings in Windows in comparison to Linux
- 10:08 AM Feature #6649: improve the performance or SourceNameMapper runtime
- Alexandru Lungu wrote:
> It is normal to have 18-21 tests failed on that regression tests.
>
> As of my understan... - 09:52 AM Feature #6649: improve the performance or SourceNameMapper runtime
- I ran the #7669-1 test and one of the users failed during the run 75 due to a @StaleRecordException@. I am running 71...
- 09:06 AM Feature #6649: improve the performance or SourceNameMapper runtime
- It is normal to have 18-21 tests failed on that regression tests.
As of my understanding: if ETF passes, only ChUI... - 09:01 AM Feature #6649: improve the performance or SourceNameMapper runtime
- I finished testing a customer application with 7156b and 6649b and got between 18 (first run) and 21 (seconds run) te...
- 08:02 AM Feature #6649: improve the performance or SourceNameMapper runtime
- Rebased 6649b to latest trunk. It is now at rev. 14886.
Constantin, you can start the ETF tests. These tests are n... - 07:46 AM Feature #6649: improve the performance or SourceNameMapper runtime
- Danut, I am planning to do rebase of 6649b to the latest trunk now.
- 06:48 AM Feature #6649: improve the performance or SourceNameMapper runtime
- Alexandru Lungu wrote:
> Danut, lets focus merging this by EOD. What testing is left?
Currently fixed the import.db... - 06:46 AM Feature #6649: improve the performance or SourceNameMapper runtime
- Alexandru Lungu wrote:
> Danut, lets focus merging this by EOD. What testing is left?
Are all changes in 6649? I ca... - 06:45 AM Feature #6649: improve the performance or SourceNameMapper runtime
- Danut, lets focus merging this by EOD. What testing is left?
- 09:38 AM Feature #7045: re-implement "normal" (non-abend) stack unwinding to avoid throwing an exception
- Committed on 7045b, revision 14837.
This change requires reconversion. 4gl constructs like @for tt@, should be con... - 08:27 AM Feature #7045: re-implement "normal" (non-abend) stack unwinding to avoid throwing an exception
- I discussed with Eduard and it seems that the problem is that we have @forBlock(P2JQuery, int, String, Block)@, but w...
- 09:03 AM Bug #8116: SEARCH vs FILE-INFO
- Greg Shah wrote:
> Vladimir can also help here regarding the specifics of our ABLUnit support. It is slightly diffe... - 08:58 AM Bug #8116: SEARCH vs FILE-INFO
- From application point of view the @PROPATH/SEARACHPATH@ should be @,@ separated. But in a real application the separ...
- 08:53 AM Bug #8116: SEARCH vs FILE-INFO
- Vladimir can also help here regarding the specifics of our ABLUnit support. It is slightly different because of the ...
- 08:51 AM Bug #8116: SEARCH vs FILE-INFO
- I'll make a couple of quick points and then Eugenie will take it from there.
1. Your use case should be supported ... - 08:53 AM Feature #4392: add -pf support for appserver CONNECT() method
- 4392a r14868 Ready for review. Fixing the remote @FileStream@ by adding a flag to determine if the file is supposed t...
- 06:11 AM Feature #4392: add -pf support for appserver CONNECT() method
- A note: Even with @StreamFactory@ it's not always the client filesystem, but depends on the directory config @server-...
- 01:39 AM Feature #4392: add -pf support for appserver CONNECT() method
- I'll add a flag to handle both cases. By default it will be the old logic, since we can't pinpoint where it's used. A...
- 08:26 PM Feature #4392: add -pf support for appserver CONNECT() method
- Constantin Asofiei wrote:
> Ovidiu, please see previous note - do you recall why that was added?
I remember the mom... - 06:40 AM Bug #8084 (Review): refactor the 'execute' method for legacy classes
- The changes for this and #8069 are in 8084a rev 14873. Please review.
12/12/2023
- 02:31 PM Feature #6649: improve the performance or SourceNameMapper runtime
- Alexandru Lungu wrote:
> Danut, is it possible to test 6649b without reconverting? This should theoretically run wit... - 11:18 AM Feature #6649: improve the performance or SourceNameMapper runtime
- Danut, is it possible to test 6649b without reconverting? This should theoretically run with no problem and build up ...
- 07:04 AM Feature #6649: improve the performance or SourceNameMapper runtime
- The results of the POC test are in :)
|_. |_. Baseline (4 cold tests avg) |_. 7156b + 66... - 05:07 AM Feature #6649: improve the performance or SourceNameMapper runtime
- I smoke tested a large customer application with 6649b and everything worked well. Currently running POC tests.
- 04:44 AM Feature #6649: improve the performance or SourceNameMapper runtime
- Dănuț Filimon wrote:
> I addressed the review from Hynek in *6649b.rev.14879*
Code review. The changes are good.
- 03:33 AM Feature #6649 (Internal Test): improve the performance or SourceNameMapper runtime
- 03:32 AM Feature #6649: improve the performance or SourceNameMapper runtime
- I addressed the review from Hynek in *6649b.rev.14879* where I added a @removeIdentifier@ method and changed the logg...
- 02:55 AM Feature #6649: improve the performance or SourceNameMapper runtime
- Alexandru Lungu wrote:
> Constantin, can you run the ETF tests with 6649b once ready? Thank you.
Will do.
- 02:54 AM Feature #6649: improve the performance or SourceNameMapper runtime
- Danut, please mark this as Urgent; we need to test it asap.
Thus, address the review from Hynek and lets move on w... - 11:07 AM Feature #7045: re-implement "normal" (non-abend) stack unwinding to avoid throwing an exception
- Eduard, there is an API issue we have on BlockManager. I think the rewriting of the BlockManager API to include the q...
- 03:55 AM Feature #7045: re-implement "normal" (non-abend) stack unwinding to avoid throwing an exception
- Committed on 7045b, revision 14836.
- removed @handleQueryOffEnd@ method from QueryWrapper and all of its usage.
- ... - 02:58 AM Feature #7045: re-implement "normal" (non-abend) stack unwinding to avoid throwing an exception
- Eduard, please address the latest suggestions and commit to 7045b.
Lets redo the whole testing process with this l... - 09:09 AM Feature #4392: add -pf support for appserver CONNECT() method
- > By the way @-pf@ for DB connect uses @new File()@. Is it acceptable there?
No. That is not OK there either. - 02:37 AM Feature #4392: add -pf support for appserver CONNECT() method
- Constantin Asofiei wrote:
> Galya B wrote:
> > By the way @-pf@ for DB connect uses @new File()@. Is it acceptable ... - 02:17 AM Feature #4392: add -pf support for appserver CONNECT() method
- Galya B wrote:
> By the way @-pf@ for DB connect uses @new File()@. Is it acceptable there?
You mean the code in @C... - 01:48 AM Feature #4392: add -pf support for appserver CONNECT() method
- Ovidiu, please see previous note - do you recall why that was added?
- 01:44 AM Feature #4392: add -pf support for appserver CONNECT() method
- I've found the issue with the remote stream:
@FileStream@:... - 12:47 AM Feature #4392: add -pf support for appserver CONNECT() method
- Greg Shah wrote:
> Code Review Task Branch 4392a Revisions 14865 and 14866
>
> I did a quick review. The primary... - 12:45 AM Feature #4392: add -pf support for appserver CONNECT() method
- Greg Shah wrote:
> Code Review Task Branch 4392a Revisions 14865 and 14866
>
> I did a quick review. The primary... - 08:16 AM Bug #8116: SEARCH vs FILE-INFO
- Although there is this slight difference in FWD implementation my issue seems to come from invalid @PROPATH@ settings...
- 04:19 AM Bug #8116: SEARCH vs FILE-INFO
- When using @SEARCH@ using relative path in 4GL the file is looked-up in all @PROPATH@ entries and if found the full-p...
- 04:19 AM Bug #8116 (New): SEARCH vs FILE-INFO
12/11/2023
- 03:56 PM Feature #4392: add -pf support for appserver CONNECT() method
- Some other notes, beside what Greg mentioned:
# does @-pf@ overwrite only the preceding options (the one which appea... - 03:10 PM Feature #4392: add -pf support for appserver CONNECT() method
- Constantin: Please review.
- 03:10 PM Feature #4392: add -pf support for appserver CONNECT() method
- Code Review Task Branch 4392a Revisions 14865 and 14866
I did a quick review. The primary issue I see is that the... - 10:12 AM Feature #4392: add -pf support for appserver CONNECT() method
- ...and r14866 for the file header.
- 10:07 AM Feature #4392 (Review): add -pf support for appserver CONNECT() method
- 4392a r14865 ready for review.
Fixes the connect param "-pf" for servers. The code wasn't completed and was throwi... - 01:19 PM Feature #6649: improve the performance or SourceNameMapper runtime
- Code review 6649b revision 14878.
@MonitorRunnable.identifiers@ are never cleared. Shouldn't an entry be removed, ... - 03:15 AM Feature #6417: cleanup some known items in appserver support
- > * versioninfo fields are read-only, but writing them is a runtime error and not compile error in FWD.
This one see...
12/08/2023
- 08:38 AM Feature #6649: improve the performance or SourceNameMapper runtime
- Rebased 6649b to latest trunk. 6649b is now at rev. 14878.
- 05:54 AM Feature #6649: improve the performance or SourceNameMapper runtime
- *Committed 6649b/rev.14849* where I made the following changes:
- Created @MonitorRunnable@ which allows identifying... - 06:40 AM Feature #6417: cleanup some known items in appserver support
- > * argument translation to remote definition type I think is done the same as the CALL statement does it...
What do...
12/07/2023
- 08:53 AM Feature #7045: re-implement "normal" (non-abend) stack unwinding to avoid throwing an exception
- Alexandru Lungu wrote:
> Regarding your last comment: it depends upon the delegate right? If the delegate is not len... - 08:40 AM Feature #7045: re-implement "normal" (non-abend) stack unwinding to avoid throwing an exception
- Eduard, I started converting a really large application with 7045b (on top of 7156b). You have 3 days left to do the ...
- 08:34 AM Feature #7045: re-implement "normal" (non-abend) stack unwinding to avoid throwing an exception
- I think is not needed, as @QueryWrapper@ is used in conversion of @open query@ statement. And in this case QQE is not...
- 08:04 AM Feature #7045: re-implement "normal" (non-abend) stack unwinding to avoid throwing an exception
- Alexandru, I haven't looked at the full code, but is the @QueryWrapper.handleQueryOffEnd@ still needed?
- 07:08 AM Feature #6417 (WIP): cleanup some known items in appserver support
12/06/2023
- 06:18 AM Feature #7045: re-implement "normal" (non-abend) stack unwinding to avoid throwing an exception
- Eduard, please focus on reaching a "state-of-the-art" solution for 7045b (also referring to #7045-84). Also, triple c...
- 02:00 AM Feature #7045: re-implement "normal" (non-abend) stack unwinding to avoid throwing an exception
- Alexandru Lungu wrote:
> I've run 7045b with the performance tests and got 8.168s. Comparing to the baseline of 7.95...
12/05/2023
- 11:01 AM Feature #7045: re-implement "normal" (non-abend) stack unwinding to avoid throwing an exception
- I am looking now in the changes of 7045b:
* Eduard, mind that you have some hard-tabs in your last commit (@Adaptive... - 08:58 AM Feature #6649: improve the performance or SourceNameMapper runtime
- Hynek Cihlar wrote:
> The logic gets more and more complex so it would be nice to be able to know how does it perfor... - 05:33 AM Feature #6649: improve the performance or SourceNameMapper runtime
- Hynek Cihlar wrote:
> With the LinkedBlockingQueue on the limit, adding more tasks to the executor will cause Reject... - 05:14 AM Feature #6649: improve the performance or SourceNameMapper runtime
- Dănuț Filimon wrote:
> Hynek Cihlar wrote:
> Initially the cache entry was a @Map@, but a potential leak was notice... - 03:15 AM Feature #6649: improve the performance or SourceNameMapper runtime
- Hynek Cihlar wrote:
> In @createSourceCacheEntry@ the object submitted to the @mappingExecutor@ is a @Thread@, but i... - 05:51 AM Bug #8008: read-json on a 1252 longchar should convert to utf-8 automatically before hydrating te...
- In this Note, I summarize the parts from #7944 which were out of scope there.
The @convert_json_1252_fcp_memptr.p@ f...
12/04/2023
- 10:38 AM Feature #7045 (Internal Test): re-implement "normal" (non-abend) stack unwinding to avoid throwin...
- I've run 7045b with the performance tests and got 8.168s. Comparing to the baseline of 7.958s, this is +2.5% slower. ...
- 05:54 AM Feature #7045: re-implement "normal" (non-abend) stack unwinding to avoid throwing an exception
- Committed on 7045b, revision 14835.
I tested @uast/query_off_end/qoe_exception@ , did not see any regressions. In ... - 03:47 AM Feature #7045: re-implement "normal" (non-abend) stack unwinding to avoid throwing an exception
- Eduard, please address the review and commit a final solution to 7045b (including javadoc / history entries / etc.) a...
- 03:07 AM Feature #7045: re-implement "normal" (non-abend) stack unwinding to avoid throwing an exception
- Eric Faulhaber wrote:
> I have noted the discussion above that @QOEE@ is not yet fully eliminated. I see this, for i... - 03:25 AM Bug #7460: implement Progress.Lang.Class:getMethods
- 6410b rev 14828 was rebased from trunk rev 14856 - new rev 14860
- 03:19 AM Bug #7460: implement Progress.Lang.Class:getMethods
- Constantin Asofiei wrote:
> Yes, I'll need to rebase. Are all changes in 6410b?
I have some local changes but no... - 03:00 AM Bug #7460: implement Progress.Lang.Class:getMethods
- Yes, I'll need to rebase. Are all changes in 6410b?
- 02:50 AM Bug #7460: implement Progress.Lang.Class:getMethods
- Constantin Asofiei wrote:
> Created task branch 7460a from trunk rev 14850.
>
> 7460a rev 14851 has a regression ... - 03:24 AM Feature #6410: implement additional built-in OO classes/interfaces
- 6410b rev 14828 was rebased from trunk rev 14856 - new rev 14860
12/02/2023
- 03:36 PM Feature #6649: improve the performance or SourceNameMapper runtime
- Code review 6649b revisions 14840..14847.
In @createSourceCacheEntry@ the object submitted to the @mappingExecutor...
12/01/2023
- 06:00 AM Bug #8084 (WIP): refactor the 'execute' method for legacy classes
- Created task branch 8084a from trunk rev 14853
11/30/2023
- 01:53 PM Bug #7460: implement Progress.Lang.Class:getMethods
- Branch 7460a was merged into trunk as rev. 14851 and archived.
- 01:38 PM Bug #7460 (Merge Pending): implement Progress.Lang.Class:getMethods
- Code Review Task Branch 7460a Revisions 14850 and 14851
No objections. - 12:52 PM Bug #7460: implement Progress.Lang.Class:getMethods
- Created task branch 7460a from trunk rev 14850.
7460a rev 14851 has a regression fix: Do not use 'TypeFactory.obje...
11/29/2023
- 08:59 AM Feature #7045: re-implement "normal" (non-abend) stack unwinding to avoid throwing an exception
- I am addressing some regression on running POC. But I think, I am close to find the problem causing this regression. ...
- 08:35 AM Feature #7045: re-implement "normal" (non-abend) stack unwinding to avoid throwing an exception
- Eduard, please make an update on your status of running the POC with your changes and addressing Eric's #7045-77.
11/28/2023
- 09:20 AM Feature #6649: improve the performance or SourceNameMapper runtime
- I ran a large POC with *7156b/rev.14846* and the changes from *6649b/rev.14835 - 14847* and obtained good results (th...
- 05:50 AM Feature #6649 (Review): improve the performance or SourceNameMapper runtime
- *Committed 6649b/rev.14847* which solves the problem mentioned in #6649-144. By not keeping the thread idle, the corr...
- 03:49 AM Bug #8084: refactor the 'execute' method for legacy classes
- Oh right, this makes sense - getting rid of the @BlockManager@ API. This way we avoid doing @ProcedureManager@ work.
- 03:31 AM Bug #8084: refactor the 'execute' method for legacy classes
- What I meant is to emit all the code (like buffer scopes) directly in the Java method, and do not enclose it in @Bloc...
- 03:29 AM Bug #8084: refactor the 'execute' method for legacy classes
- Contantin, just a question here: I thought we open scopes in @externalProcedure@ due to the fact that we are aware *o...
11/27/2023
- 02:28 PM Bug #8084: refactor the 'execute' method for legacy classes
- Currently, each legacy class has a synthetic 'execute' instance method which includes initialization like instance-le...
- 02:23 PM Bug #8084 (Test): refactor the 'execute' method for legacy classes
11/24/2023
- 06:11 AM Feature #6649 (WIP): improve the performance or SourceNameMapper runtime
- 06:05 AM Feature #6649: improve the performance or SourceNameMapper runtime
- After investigating, I found out that the @mappingExecutor@ creates an @AssociatedThread@ with the current context, m...
- 02:11 AM Feature #6649: improve the performance or SourceNameMapper runtime
- There is an issue with how the cache entries are built. The @AssociatedThread@ doesn't use the correct context when b...
- 04:11 AM Feature #7045: re-implement "normal" (non-abend) stack unwinding to avoid throwing an exception
- Code review 7045b/14825-14834:
There are file header entries problems (i.e., duplicate entries in some files, miss...
11/22/2023
- 03:02 PM Feature #6819: refactor FWD proxy implementation to use ReflectASM instead of Java Method reflection
- > > What specific use cases would be using the modified code?
> RecordBuffer, TemporarBuffer, DataSet, ControlFlowOp... - 08:56 AM Feature #6819: refactor FWD proxy implementation to use ReflectASM instead of Java Method reflection
- Greg Shah wrote:
> Please post the test harness code or whatever it is that you are using to create the failing case... - 08:22 AM Feature #6819: refactor FWD proxy implementation to use ReflectASM instead of Java Method reflection
- Please post the test harness code or whatever it is that you are using to create the failing case ("where I created 1...
- 04:11 AM Feature #6649: improve the performance or SourceNameMapper runtime
- I tested with a rebased 6649b from 7156b (7156b at rev. 14846, branched from trunk rev. 14822 + all 8 commits from 66...
11/21/2023
- 02:43 PM Feature #6819: refactor FWD proxy implementation to use ReflectASM instead of Java Method reflection
- Currently there are three experimental branches:
* 6819c - uses singleton, byte-code generated, BiFunction inner cla... - 01:56 PM Feature #6819: refactor FWD proxy implementation to use ReflectASM instead of Java Method reflection
- Please post details of the results from your testing described in #6819-61 (6 months ago).
I understand you've bee... - 02:40 PM Feature #7045: re-implement "normal" (non-abend) stack unwinding to avoid throwing an exception
- Eric: Please don't forget to do a code review ASAP.
- 07:52 AM Feature #7045: re-implement "normal" (non-abend) stack unwinding to avoid throwing an exception
- Eduard, I didn't had the chance to convert yet the POC. Can you attempt it? I have already queued some other performa...
- 11:24 AM Feature #6649: improve the performance or SourceNameMapper runtime
- Alex, when you test the large app, do you use 7156b with the changes from 6649b on top? Will the latest 7156b work OK?
- 09:35 AM Feature #6649: improve the performance or SourceNameMapper runtime
- *6649b* was rebased to *trunk/rev.14834* and the current revision is *14845*.
*Committed 6649b/rev.14846*:
* Used... - 07:29 AM Bug #7656: investigate performance of context-local helpers (e.g. TransactionManager.TransactionH...
- Alexandru, in @devsrv01:/tmp/AccessModifier.7z@ there is the project I use to automatically 'fix' the access modifie...
11/20/2023
- 06:03 AM Feature #6649: improve the performance or SourceNameMapper runtime
- On a large POC, the total improvement of the changes in 6649b was of -0.3%.
- 04:00 AM Feature #6649: improve the performance or SourceNameMapper runtime
- Hynek Cihlar wrote:
> Do you mean 70 individual propath entries or 70 paths in a single propath?
One single long ... - 02:34 AM Feature #6649: improve the performance or SourceNameMapper runtime
- Alexandru Lungu wrote:
> I've done some tests, and there were no obvious problems. I am moving this to the profiler ...
11/18/2023
- 07:33 PM Feature #6431: implement support to allow CPINTERNAL set to UTF-8 and CP936
- Marian Edu wrote:
> Hi Theodoros, just pushed the i18n tests on testcases (rev#1514), we're still working one some c...
11/17/2023
- 08:47 AM Feature #6431: implement support to allow CPINTERNAL set to UTF-8 and CP936
- Theodoros Theodorou wrote:
> Hello Marian. Greg asked me to coordinate with you that we do not do the same effort tw... - 07:41 AM Feature #6431: implement support to allow CPINTERNAL set to UTF-8 and CP936
- Hello Marian. Greg asked me to coordinate with you that we do not do the same effort twice. Please have a look at @te...
- 07:11 AM Feature #6431: implement support to allow CPINTERNAL set to UTF-8 and CP936
- Yes, it needs to be fixed. Such conversions should yield identical results. It seems likely that the cause is relat...
- 08:23 AM Feature #6649: improve the performance or SourceNameMapper runtime
- Alexandru Lungu wrote:
> Mind that the search-path cache is not synchronized. Please add @synchronize@ to that acces... - 08:13 AM Feature #6649: improve the performance or SourceNameMapper runtime
- *Review of 6649b/rev.14808*
Mind that the search-path cache is not synchronized. Please add @synchronize@ to that ... - 08:03 AM Feature #6649: improve the performance or SourceNameMapper runtime
- Alexandru Lungu wrote:
> Some extra ideas:
>
> * Also, what about @convertedNames@? Can't it possible leak as we ... - 07:33 AM Feature #6649: improve the performance or SourceNameMapper runtime
- Alexandru Lungu wrote:
> Danut please fix #6649-131 - I am planning to start performance testing with 6649a as soon ... - 07:08 AM Feature #6649: improve the performance or SourceNameMapper runtime
- Some extra ideas:
* Also, what about @convertedNames@? Can't it possible leak as we are constantly adding to it th... - 06:26 AM Feature #6649: improve the performance or SourceNameMapper runtime
- I've done some tests, and there were no obvious problems. I am moving this to the profiler asap.
However, I want t... - 04:04 AM Feature #6649: improve the performance or SourceNameMapper runtime
- I converted a large application and generated a @name_map.xml@ with ~39k (~7k of OO classes) class-mappings and only ...
11/16/2023
- 06:03 PM Feature #6431: implement support to allow CPINTERNAL set to UTF-8 and CP936
- Hello, I wrote a small test (chr_and_asc.p) which tests the conversion of a character from one code page to another (...
- 12:40 AM Feature #6649: improve the performance or SourceNameMapper runtime
- *Committed 6649b/rev.14807*. Fixed a NPE when there are no path-mapping nodes in name_map.xml.
Also available in: Atom