Activity
From 11/18/2024 to 12/17/2024
12/17/2024
- 08:19 AM Bug #9482: Reduce logging for warnings coming outside FWD.
- CentralLogger logs warning with throwables and their respective stack trace, if the throwable was passed as a paramet...
- 08:15 AM Bug #9482 (New): Reduce logging for warnings coming outside FWD.
- 04:40 AM Bug #9037: Two timers problem: only one fires
- Review:
Not sure if locking in @ContextLocal@ would introduce even more problems, but I've found that out while wor...
12/16/2024
- 09:37 AM Bug #9354: Invalid handle (3135) error is thrown insted of the 10068 error.
- There are some prints for debugging reasons....
12/13/2024
- 02:13 PM Bug #9354: Invalid handle (3135) error is thrown insted of the 10068 error.
- > I think what is needed is to put an annotation when @chainedRef@ should be true and after a @REFERENCE@ gets added ...
- 09:48 AM Bug #9354: Invalid handle (3135) error is thrown insted of the 10068 error.
- For the progress code given by Alex: @obj:gen():gen():test():test().@...
12/12/2024
- 10:49 AM Bug #9037: Two timers problem: only one fires
- > @SecurityContext@ instance (Greg, IIRC this is a singleton for each FWD context, right?)
In most cases, yes it i... - 08:13 AM Bug #9037: Two timers problem: only one fires
- Vladimir Tsichevski wrote:
> Constantin Asofiei wrote:
>
> > Regarding the changes in 9037a...
>
> Branch 9037... - 08:13 AM Bug #9037: Two timers problem: only one fires
- Constantin Asofiei wrote:
> Regarding the changes in 9037a...
Branch 9037a never existed :-(. The change is in ... - 07:54 AM Bug #9037: Two timers problem: only one fires
- Greg/Vladimir: I agree that the synchronization in ContextLocal is faulty. But I propose to improve and fix the sync...
- 10:01 AM Bug #9354: Invalid handle (3135) error is thrown insted of the 10068 error.
- > I like the second version more. Maybe use @ref()@, @chainedRef()@ (which will call @chainedRef(false)@ underneath) ...
- 09:36 AM Bug #9354: Invalid handle (3135) error is thrown insted of the 10068 error.
- I think your approach is right. Please consider:...
- 08:54 AM Bug #9354: Invalid handle (3135) error is thrown insted of the 10068 error.
- ...
- 04:29 AM Bug #9396: Improve Incompatible data types in expression or assignment. (223) error handling
- I thought about this and found that we have a map storing function definitions in @SignatureHelper@ (@map_func@), thi...
12/11/2024
- 03:57 AM Bug #9411: Implement SESSION:STREAM
- I am OK with the changes in 9411a.
- 09:01 PM Feature #9448: compatibility test security features
- Check the tests in Testcases to ensure they are complete and comprehensive. Add tests if needed. Convert and run the ...
- 08:58 PM Feature #9448 (Closed): compatibility test security features
- 08:53 PM Feature #9447: XML support feature improvements and testing
- * @SAX-READER@ (also should be added to @X-DOCUMENT@ if easily done, but only the @SAX-READER@ version is used in the...
- 08:52 PM Feature #9447 (Closed): XML support feature improvements and testing
- 08:20 PM Support #9446: compatibility test PUT-DOUBLE
- Check the @PUT-DOUBLE@ tests in [[p2j:Testcases]] to ensure they are complete and comprehensive. Add tests if needed...
- 08:20 PM Support #9446 (Closed): compatibility test PUT-DOUBLE
- 08:18 PM Support #9445: compatibility test FIX-CODEPAGE
- Check the @FIX-CODEPAGE@ tests in [[p2j:Testcases]] to ensure they are complete and comprehensive. Add tests if need...
- 08:13 PM Support #9445 (Closed): compatibility test FIX-CODEPAGE
12/10/2024
- 12:35 PM Feature #9442: implement limited support for RCODE-INFORMATION
- Greg Shah wrote:
> Both start with an assignment of @RCODE-INFORMATION:FILENAME@ to some program name or class name.... - 12:32 PM Feature #9442: implement limited support for RCODE-INFORMATION
- There are 2 patterns used that should be supported.
Both start with an assignment of @RCODE-INFORMATION:FILENAME@ ... - 12:29 PM Feature #9442 (Closed): implement limited support for RCODE-INFORMATION
- 09:59 AM Bug #9411: Implement SESSION:STREAM
- Greg Shah wrote:
> Eugenie: Please review and comment on #9411-14.
>
> > is not needed then we can either change ... - 09:35 AM Bug #9411: Implement SESSION:STREAM
- It is already committed!
- 09:28 AM Bug #9411: Implement SESSION:STREAM
- Please apply the changes to the branch.
- 09:26 AM Bug #9411: Implement SESSION:STREAM
- Committed 9411a revision 15609. ...
- 09:04 AM Bug #9411: Implement SESSION:STREAM
- Perfect. OE treats these as synonyms too. Go ahead with that idea.
- 08:52 AM Bug #9411: Implement SESSION:STREAM
- !6.png!
I think it's worth mentioning that even if I set @-stream "someEncoder"@ the error message contains @-cps... - 08:27 AM Bug #9411: Implement SESSION:STREAM
- Alexandru Lungu wrote:
> Running a 4GL application with @-cpstream@ option at CLI is also changing @STREAM@?
Yes.
... - 08:12 AM Bug #9411: Implement SESSION:STREAM
- > As such I think we can go ahead and make SESSION:STREAM be SESSION:CPSTREAM in conversion.
Running a 4GL applica... - 08:10 AM Bug #9411: Implement SESSION:STREAM
- I tested with every encoder and I found the following:
* the encoder is the key of @convmap2JavaDefault@
* @SESSION... - 06:47 AM Bug #9411: Implement SESSION:STREAM
- Eugenie: Please review and comment on #9411-14.
> is not needed then we can either change the rules to call @getCP... - 06:12 AM Bug #9411: Implement SESSION:STREAM
- Alexandru Lungu wrote:
> Functional: I might not properly understand the use of @convmap2JavaDefault@. What is the g... - 05:03 AM Bug #9411: Implement SESSION:STREAM
- Review of 9411a:
* please keep the naming consistent with the rest of CommonSession API (aka use @get@ prefix)
* ... - 04:26 AM Bug #9411: Implement SESSION:STREAM
- Since we moved the @stream()@ method we should also do the following changes:...
- 04:06 AM Bug #9411: Implement SESSION:STREAM
- Committed 9411a revision 15610.
- 04:05 AM Bug #9411 (Review): Implement SESSION:STREAM
- Greg Shah wrote:
> Code Review Task Branch 9411a Revision 15609
>
> 1. Instead of @SessionUtils@, the getter shou... - 09:57 AM Bug #9350 (Internal Test): gap marking for LOG-MANAGER attributes and methods is probably wrong
- Code Review Task Branch 9198a Revision 15486
The changes are good.
I've checked in rev 15487 with minor comment... - 09:27 AM Bug #9350 (Review): gap marking for LOG-MANAGER attributes and methods is probably wrong
- 09:27 AM Bug #9350: gap marking for LOG-MANAGER attributes and methods is probably wrong
- Up in 9198a r15486.
Diff:... - 08:52 AM Bug #9350 (WIP): gap marking for LOG-MANAGER attributes and methods is probably wrong
- The current state should be:
1. LOG-MANAGER attributes:
* LOGFILE-NAME (KW_LOGF_NAM) - conversion full/runtime fu... - 07:44 AM Bug #9354: Invalid handle (3135) error is thrown insted of the 10068 error.
- I can reproduce the issue. The problem is in @object.ref@:...
- 04:28 AM Bug #9354 (WIP): Invalid handle (3135) error is thrown insted of the 10068 error.
- 07:38 AM Feature #4392 (Closed): add -pf support for appserver CONNECT() method
- 08:34 PM Feature #9437: enhancements for Progress.Lang.Class
- ...
- 08:33 PM Feature #9437 (Closed): enhancements for Progress.Lang.Class
- 08:26 PM Feature #9436: add built-in OO classes
- ...
- 08:24 PM Feature #9436 (WIP): add built-in OO classes
12/09/2024
- 06:50 PM Feature #9435: class-level virtual procedure/function definitions
- Some procedures and functions can be defined in classes.
* @PROCEDURE EXTERNAL@
* @PROCEDURE/FUNCTION ... IN hand... - 06:49 PM Feature #9435 (Closed): class-level virtual procedure/function definitions
- 06:44 PM Bug #4602: fixes for OO 4GL and structured error handling
- Some things to ensure are fully working:
* @CATCH@ with inner @UNDO, THROW@
* @FINALLY@ with @DELETE OBJECT@ (wit... - 04:56 PM Bug #9411: Implement SESSION:STREAM
- Code Review Task Branch 9411a Revision 15609
1. Instead of @SessionUtils@, the getter should be in @I18nOps@.
2... - 10:05 AM Bug #9411: Implement SESSION:STREAM
- Committed 9411a revision 15609.
- 09:39 AM Bug #9411: Implement SESSION:STREAM
- That seems reasonable. Please put the changes in a branch.
- 09:24 AM Bug #9411: Implement SESSION:STREAM
- ...
- 09:20 AM Bug #9411: Implement SESSION:STREAM
- I tested the OE application and introduced other encoding formats in startup. @SESSION:STREAM@ can also output other ...
- 09:07 AM Bug #9411: Implement SESSION:STREAM
In @method_attributes.rules@:...- 03:03 AM Bug #9411 (WIP): Implement SESSION:STREAM
- 11:55 AM Bug #6640: parsing bug for initial ",0000" for decimal variables or fields
- What happens in OE when you set the decimal separator or group separator to different values?
You can set this on ... - 10:44 AM Bug #6640: parsing bug for initial ",0000" for decimal variables or fields
- Seems, the decimal separators are ignored completely when parsing a string to a number.
In OE this works as if the i...
12/05/2024
- 09:47 AM Bug #8309: Do the error handling for r-index and extend implementation to INDEX and LONGCHAR
- Greg Shah wrote:
> Yuck. I'm not OK with error messages being dependent upon files independently installed or edite... - 08:27 AM Bug #8309: Do the error handling for r-index and extend implementation to INDEX and LONGCHAR
- Marian Edu wrote:
> Greg Shah wrote:
> > Yes, exactly this. Luckily, this is a pretty rare case because they try t... - 09:02 AM Bug #9417: Errors might not be logged by the LegacyLogManager.
- Apart from the example in note 1, I have not been able to find cases where errors are not logged, but there might be....
- 08:56 AM Bug #9417: Errors might not be logged by the LegacyLogManager.
- How might you test this bug?
- 08:38 AM Bug #9417: Errors might not be logged by the LegacyLogManager.
- +Galya, +Constantin
- 08:36 AM Bug #9417: Errors might not be logged by the LegacyLogManager.
- ...
- 08:33 AM Bug #9417 (New): Errors might not be logged by the LegacyLogManager.
- 05:34 AM Bug #9396: Improve Incompatible data types in expression or assignment. (223) error handling
- Alexandru Lungu wrote:
> Danut, I am trying to drag the discussion to the point where proving that the error occurs ... - 05:26 AM Bug #9396: Improve Incompatible data types in expression or assignment. (223) error handling
- Danut, I am trying to drag the discussion to the point where proving that the error occurs only when @var4glType@ and...
- 03:55 AM Bug #9396: Improve Incompatible data types in expression or assignment. (223) error handling
- Alexandru Lungu wrote:
> Please investigate why @tt.f1 = LENGTH('abc')@ is hitting the switch-case, making @var4glTy... - 03:20 AM Bug #9396 (WIP): Improve Incompatible data types in expression or assignment. (223) error handling
- Resuming work for #9396-25.
12/04/2024
- 08:01 AM Bug #9396: Improve Incompatible data types in expression or assignment. (223) error handling
- > My conclusion is that we need to add the full type checking during standard conversion with error reporting if we w...
- 06:43 AM Bug #9396: Improve Incompatible data types in expression or assignment. (223) error handling
- Alexandru Lungu wrote:
> Ovidiu, the work-flow of static and dynamic queries in FWD differs a bit, especially throug... - 04:55 AM Bug #9396: Improve Incompatible data types in expression or assignment. (223) error handling
- *Review of 8396a*
* While the approach should fix the evident problem, I think it is too relaxed. Mind that @1 + 1... - 04:17 AM Bug #9396: Improve Incompatible data types in expression or assignment. (223) error handling
- Ovidiu, the work-flow of static and dynamic queries in FWD differs a bit, especially through @DynamicQueryHelper@. @f...
- 04:34 AM Bug #8309: Do the error handling for r-index and extend implementation to INDEX and LONGCHAR
- Greg Shah wrote:
> Yes, exactly this. Luckily, this is a pretty rare case because they try to keep OE backwards com...
12/03/2024
- 05:41 PM Bug #9396: Improve Incompatible data types in expression or assignment. (223) error handling
- Alexandru Lungu wrote:
> *Ovidiu*, can you provide an insight for this matter?
First, a bit of wisdom :) from my ... - 08:49 AM Bug #9396 (Review): Improve Incompatible data types in expression or assignment. (223) error hand...
- Committed the changes to *9396a/15588*. Partially reverted changes from 15583 and 15584 revisions.
Please review.
... - 07:58 AM Bug #9396: Improve Incompatible data types in expression or assignment. (223) error handling
- Alexandru Lungu wrote:
> > 528 - 4359 times (ProgressParserTokenTypes.KW_AND)
>
> I wonder if this is something l... - 07:03 AM Bug #9396: Improve Incompatible data types in expression or assignment. (223) error handling
- > 528 - 4359 times (ProgressParserTokenTypes.KW_AND)
I wonder if this is something line @tt.f1 = 1 and true@ kind ... - 06:59 AM Bug #9396: Improve Incompatible data types in expression or assignment. (223) error handling
- Alexandru Lungu wrote:
> Can you check what the construct is in that case? I expect to see UPPER(RTRIM()) kind of co... - 06:55 AM Bug #9396: Improve Incompatible data types in expression or assignment. (223) error handling
- Can you check what the construct is in that case? I expect to see UPPER(RTRIM()) kind of combination in 99% of that c...
- 06:12 AM Bug #9396: Improve Incompatible data types in expression or assignment. (223) error handling
- I've run the analysis on how often we get @FUNCTION(literal)@ constructs (the scenario involves the extended performa...
- 04:47 AM Bug #9396: Improve Incompatible data types in expression or assignment. (223) error handling
- I also committed the logical(int) constructor change to *9396a/15586*.
Adjusted Done%. - 04:45 AM Bug #9396: Improve Incompatible data types in expression or assignment. (223) error handling
- Alexandru Lungu wrote:
> Danut, lets go for to the more evident fix of not allowing the literals to be extracted in ... - 04:42 AM Bug #9396 (WIP): Improve Incompatible data types in expression or assignment. (223) error handling
- Danut, lets go for to the more evident fix of not allowing the literals to be extracted in such complex scenarios. Th...
- 04:33 AM Bug #9396: Improve Incompatible data types in expression or assignment. (223) error handling
- Alexandru, you are right. The problem also happens with other functions, the example:...
- 04:15 AM Bug #9396: Improve Incompatible data types in expression or assignment. (223) error handling
- > Is the literal extraction happening only in f1 = 1 kind is situations? Or f1 + 1 = f2 is also a valid case in which...
- 03:51 AM Bug #9396: Improve Incompatible data types in expression or assignment. (223) error handling
- Somehow I modified this, sorry.
- 03:47 AM Bug #9396: Improve Incompatible data types in expression or assignment. (223) error handling
- > where the injected variable is actually a CHARACTER but the conversion should fail because of the datetime function...
- 05:39 AM Bug #9411: Implement SESSION:STREAM
- This task is created to cover the implementation details of SESSION:STREAM.
- 05:39 AM Bug #9411 (Closed): Implement SESSION:STREAM
12/02/2024
- 10:29 AM Bug #9396: Improve Incompatible data types in expression or assignment. (223) error handling
- *Review of 9396a*
* The logical constructor can be condensed: @assign(value != 0)@. I agree that the constructor s... - 08:19 AM Support #9398 (Review): Incomplete SESSION:DATE-FORMAT implementation in FWD and setting session ...
- 08:19 AM Support #9398 (WIP): Incomplete SESSION:DATE-FORMAT implementation in FWD and setting session dat...
- The issue fixed in 9398a rev. 15587.
Now the @date-format@ client option can be used to set the @SESSION:DATA-FORM...
11/29/2024
- 10:20 AM Support #9398: Incomplete SESSION:DATE-FORMAT implementation in FWD and setting session date form...
- I've created the 9398a branch for fixing this.
- 09:35 AM Bug #9396 (Review): Improve Incompatible data types in expression or assignment. (223) error hand...
- Committed *9396a/15585*. Added logical(int) constructor to fix #9396-7.
All written tests passed (tests cover dyna... - 09:13 AM Bug #9396: Improve Incompatible data types in expression or assignment. (223) error handling
- Found the following test:...
- 07:01 AM Bug #9396: Improve Incompatible data types in expression or assignment. (223) error handling
- Dănuț Filimon wrote:
> This turns out to be more complicated for certain cast functions, for example you can have @D... - 03:43 AM Bug #9396: Improve Incompatible data types in expression or assignment. (223) error handling
- This turns out to be more complicated for certain cast functions, for example you can have @DATETIME(DATE(3,3,2001), ...
- 06:08 AM Bug #8309 (Internal Test): Do the error handling for r-index and extend implementation to INDEX a...
- I am OK with the 8309a changes.
11/28/2024
- 08:39 AM Support #9398: Incomplete SESSION:DATE-FORMAT implementation in FWD and setting session date form...
- In FWD, the command line options that can be specified in OE are handled using our @com.goldencode.p2j.main.StartupPa...
- 08:12 AM Support #9398: Incomplete SESSION:DATE-FORMAT implementation in FWD and setting session date form...
- Progress allows to set the @SESSION:DATE-FORMAT@ from command-line using the @Date Format@ (@-d@) option.
Does FWD... - 08:09 AM Support #9398 (Test): Incomplete SESSION:DATE-FORMAT implementation in FWD and setting session da...
- 07:08 AM Bug #9396: Improve Incompatible data types in expression or assignment. (223) error handling
- *Committed 9396a/15583*. This commit fixes all of my testcases related to #9396-2 table (except the 3rd bullet point)...
- 06:42 AM Bug #9396: Improve Incompatible data types in expression or assignment. (223) error handling
- The third bullet point is a regression added in trunk/15456, @recordOrShowError@ throws a @DeferredLegacyErrorExcepti...
- 06:10 AM Bug #9396 (WIP): Improve Incompatible data types in expression or assignment. (223) error handling
- From #9377-8:
I've created unit tests for testing the behavior of *temp-tables* fields and literals:
|_. Field ty... - 06:04 AM Bug #9396 (WIP): Improve Incompatible data types in expression or assignment. (223) error handling
- 04:38 AM Bug #8643 (Test): ErrorManager not handling caught errors and error-status:error attribute properly
- 04:38 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- Branch 8643a was merged into trunk 15582 and archived.
11/27/2024
- 01:18 PM Bug #8309: Do the error handling for r-index and extend implementation to INDEX and LONGCHAR
- Greg Shah wrote:
> > Does this mean we shall make FWD runtime honor the version returned by @EnvironmentOps@?
>
>... - 12:37 PM Bug #8309: Do the error handling for r-index and extend implementation to INDEX and LONGCHAR
- > Does this mean we shall make FWD runtime honor the version returned by @EnvironmentOps@?
Yes, exactly this. Luc... - 12:35 PM Bug #8309: Do the error handling for r-index and extend implementation to INDEX and LONGCHAR
- Greg Shah wrote:
> I know it isn't nice to write, but in the 4GL code we can use @PROVERSION@ and have conditional m... - 12:32 PM Bug #8309: Do the error handling for r-index and extend implementation to INDEX and LONGCHAR
- Greg Shah wrote:
> I know it isn't nice to write, but in the 4GL code we can use @PROVERSION@ and have conditional m... - 10:59 AM Bug #8309: Do the error handling for r-index and extend implementation to INDEX and LONGCHAR
- I know it isn't nice to write, but in the 4GL code we can use @PROVERSION@ and have conditional matching code. On th...
- 08:55 AM Bug #8309: Do the error handling for r-index and extend implementation to INDEX and LONGCHAR
- Greg Shah wrote:
> Marian's team currently writes everything for 12.2 since that is what they have. That doesn't me... - 08:46 AM Bug #8309: Do the error handling for r-index and extend implementation to INDEX and LONGCHAR
- Marian's team currently writes everything for 12.2 since that is what they have. That doesn't meant that that is the...
- 08:29 AM Bug #8309: Do the error handling for r-index and extend implementation to INDEX and LONGCHAR
- Greg Shah wrote:
> We MUST support both. Please add runtime version checking using the @EnvironmentOps@ "Progress" ... - 08:22 AM Bug #8309: Do the error handling for r-index and extend implementation to INDEX and LONGCHAR
- We MUST support both. Please add runtime version checking using the @EnvironmentOps@ "Progress" version helpers.
- 07:42 AM Bug #8309: Do the error handling for r-index and extend implementation to INDEX and LONGCHAR
- Some implication found:
The @INDEX/R-INDEX@ tests now existing in the testcases assume the error message is:
<p... - 05:53 AM Bug #8309: Do the error handling for r-index and extend implementation to INDEX and LONGCHAR
- Alexandru Lungu wrote:
> When updating I get:
> [...]
>
> The revisions you are mentioning look newer; maybe you... - 02:58 AM Bug #8309: Do the error handling for r-index and extend implementation to INDEX and LONGCHAR
- When updating I get:...
- 11:31 AM Bug #8643 (Merge Pending): ErrorManager not handling caught errors and error-status:error attribu...
- You can merge after 9342a.
- 09:46 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- Greg, can I merge 8643a?
- 07:50 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- Run CHUI regression tests, and they are passing.
11/26/2024
- 02:28 PM Bug #8309: Do the error handling for r-index and extend implementation to INDEX and LONGCHAR
- Greg Shah wrote:
> > > * there are many places where @final@ was added to the method parameters. This remembered me ... - 02:23 PM Bug #8309: Do the error handling for r-index and extend implementation to INDEX and LONGCHAR
- > > * there are many places where @final@ was added to the method parameters. This remembered me of the "Overuse-of-f...
- 11:23 AM Bug #8309 (Review): Do the error handling for r-index and extend implementation to INDEX and LONG...
- Alexandru Lungu wrote:
> Review of 8309a/rev. 15573:
>
> * I am OK with the functionality of the changes and the ... - 08:53 AM Bug #8309 (WIP): Do the error handling for r-index and extend implementation to INDEX and LONGCHAR
- 08:00 AM Bug #8309: Do the error handling for r-index and extend implementation to INDEX and LONGCHAR
- Review of 8309a/rev. 15573:
* I am OK with the functionality of the changes and the overall refactoring!
* minor ... - 09:15 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- I have run again *one by one* the fwd tests that failed only with @8643a@ and they passed.
- 07:51 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- Andrei Plugaru wrote:
> *The testing I have done yesterday was probably flawed.*
>
> The problem was that I didn'... - 06:23 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- Constatin wrote:
> Did you restore the database before running the tests?
yes, a couple of times.
Andrei Plu... - 06:09 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- *The testing I have done yesterday was probably flawed.*
The problem was that I didn't reimport the DB before runn... - 05:56 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- ETF testing passed
- 04:11 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- Eduard Soltan wrote:
> But the baseline result for fwd tests that I obtained it is a bit worse that the result Andre...
11/25/2024
- 02:13 PM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- Andrei Plugaru wrote:
> I have run the fwdtests and, unfortunately, *it seems there are 5 regressions*. I would want... - 01:53 PM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- Andrei Plugaru wrote:
> I have run the fwdtests and, unfortunately, *it seems there are 5 regressions*. I would want... - 10:28 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- I have run the fwdtests and, unfortunately, *it seems there are 5 regressions*. I would want, however, to make anothe...
- 08:48 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- Andrei Plugaru wrote:
> Constantin Asofiei wrote:
> > Andrei: did you run both fwdtests and unittests?
>
> No, I... - 08:30 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- Constantin Asofiei wrote:
> Andrei: did you run both fwdtests and unittests?
No, I have only run the exact test t... - 08:29 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- I run unitest for a large application.
Also run unittest of a large GUI app, and harness of a big rest app. - 08:28 AM Bug #8643 (Internal Test): ErrorManager not handling caught errors and error-status:error attribu...
- Review is OK. I can run ETF - what other testing is needed?
Andrei: did you run both fwdtests and unittests? - 03:27 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- *Eduard*, I retested #9353 with @8643a rev. 15530@ and the exception is still handled right. ✅
- 03:24 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- Constantin Asofiei wrote:
> Eduard, so there are no changes required for the branch?
No, there should be a change... - 03:21 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- Eduard, so there are no changes required for the branch?
- 02:59 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- I run the example from #9298-38 using command line, and got the same result as if running from OE.
Got the excepti... - 10:04 AM Bug #6389: LENGTH function with COLUMN option
- My understanding from that time is the 'column' length is to align the text for i.e. printing. So this can not depen...
- 10:02 AM Bug #6389: LENGTH function with COLUMN option
- Maybe there is one more thing we can try, I was thinking that the @column@ length is determined by the width of the c...
11/22/2024
- 10:22 AM Bug #8309: Do the error handling for r-index and extend implementation to INDEX and LONGCHAR
- Please coordinate with Marian to check these into the [[p2j:Testcases]] project.
- 06:17 AM Bug #8309: Do the error handling for r-index and extend implementation to INDEX and LONGCHAR
- Attached are unit tests for testing case-sensitivity.
- 04:10 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- Actully I think that the problematic line in this code from #8643-38....
11/21/2024
- 03:10 PM Bug #8309 (Review): Do the error handling for r-index and extend implementation to INDEX and LONG...
- Issue fixed in rev. 15573. Review, please.
- 01:31 PM Bug #8309: Do the error handling for r-index and extend implementation to INDEX and LONGCHAR
- Vladimir Tsichevski wrote:
> Another issue discovered: the @R-INDEX@ implementation does not support @CHARACTER@ cas... - 07:28 AM Bug #8309: Do the error handling for r-index and extend implementation to INDEX and LONGCHAR
- Another issue discovered: the @R-INDEX@ implementation does not support @CHARACTER@ case sensitivity, the comparison ...
- 10:13 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- Constantin Asofiei wrote:
> But a question: does this test still work in FWD with 8643a?
Well, not really. I cha... - 03:41 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- The changes make sense, we've seen weird behavior for db-related errors in other places.
But a question: does this...
11/20/2024
- 05:37 PM Bug #8309: Do the error handling for r-index and extend implementation to INDEX and LONGCHAR
- Branch 8309a rev. 15571 now handles invalid index argument for @R-INDEX@ correctly.
ABLUnit tests attached for the @... - 12:14 PM Bug #8309 (WIP): Do the error handling for r-index and extend implementation to INDEX and LONGCHAR
- I've created the 8309a branch for this.
- 09:55 AM Bug #6389: LENGTH function with COLUMN option
- I am sorry, I forgot to add the 'destination' parameter for @chr@ function. I updated the procedures above. It turn o...
- 09:19 AM Bug #6389: LENGTH function with COLUMN option
- Constantin Asofiei wrote:
> But: are we sure characters in a certain string are not 'merged' into i.e. 3 columns eve... - 09:10 AM Bug #6389: LENGTH function with COLUMN option
- I extended the extractor to:...
- 09:07 AM Bug #6389: LENGTH function with COLUMN option
- We can keep this data in a file (or an array) directly, no need to complicate things with intervals.
But: are we s... - 09:02 AM Bug #6389: LENGTH function with COLUMN option
- Correct me if I am wrong, but the main problem with an approach like this is the fact that we can't rely on intervals...
- 08:49 AM Bug #6389: LENGTH function with COLUMN option
- To extract the column lengths for all 64Ki Unicode characters we can use the following procedure (do not forget to st...
- 07:59 AM Bug #6389: LENGTH function with COLUMN option
- Artur Școlnic wrote:
> Ovidiu, won't manually scanning the Unicode planes for any type of characters limit the funct... - 07:08 AM Bug #6389: LENGTH function with COLUMN option
- Yes, the results are from OE. In FWD the @length@ function does not work with any of the parameters if multi byte cha...
- 07:03 AM Bug #6389: LENGTH function with COLUMN option
- Are these results from OE?
- 06:12 AM Bug #6389: LENGTH function with COLUMN option
- I was operating under the assumption that @chr(, "utf-8")@ encodes a character using utf-8 and 4gl will calculate the...
11/19/2024
- 12:51 PM Bug #6389: LENGTH function with COLUMN option
- Eugenie Lyzenko wrote:
> However the main question here I think is to detect what is the output of the @LENGTH@ in 4... - 12:44 PM Bug #6389: LENGTH function with COLUMN option
- +Review of 6389a/15563+
The solution seems close, but there are some issues we need to discuss:
* your sample in ... - 12:07 PM Bug #6389: LENGTH function with COLUMN option
- The approach used in @15563@ should work for 16-bit Java characters. If 4GL @LENGTH@ function always return number of...
- 08:04 AM Bug #6389: LENGTH function with COLUMN option
- Ovidiu and Eugenie: Please review.
- 07:19 AM Bug #6389 (Review): LENGTH function with COLUMN option
- The length of wide chars seems to be @2@ regardless of the mode the program is ran in (gui, chui, batch), of the outp...
- 09:15 AM Bug #9037 (Review): Two timers problem: only one fires
- Branch 8393b on rev. 15573 fixes the problem. I (re)tested it with the @8393.p@ and the big customer application.
I ... - 09:01 AM Bug #9354: Invalid handle (3135) error is thrown insted of the 10068 error.
- This issue is derived from #9271-11.
- 09:00 AM Bug #9354: Invalid handle (3135) error is thrown insted of the 10068 error.
- start.p...
- 08:54 AM Bug #9354 (WIP): Invalid handle (3135) error is thrown insted of the 10068 error.
11/18/2024
- 09:38 AM Bug #6389: LENGTH function with COLUMN option
- I am using tests like the one in #6389-21.
- 09:36 AM Bug #6389: LENGTH function with COLUMN option
- Did you test in both ChUI, GUI and batch process?
- 09:19 AM Bug #6389: LENGTH function with COLUMN option
- Should I commit the fix for the "Column" parameter, or fix the other ones too?
- 08:50 AM Bug #6389: LENGTH function with COLUMN option
- I have a fix for the @COLUMN@ parameter, but it looks like the same method could be used for all the parameters.
- 08:49 AM Bug #6389: LENGTH function with COLUMN option
- ...
- 07:41 AM Bug #6389: LENGTH function with COLUMN option
- I was not aware we already have it :), thank you.
- 07:32 AM Bug #6389: LENGTH function with COLUMN option
- The same class exists in FWD as @p2j/build/lib/jline-2.14.6.jar:jline.console.WCWidth@. I'm confused why you need th...
- 07:29 AM Bug #6389: LENGTH function with COLUMN option
- Constantin Asofiei wrote:
> Artur, you mean this project? https://github.com/jline/jline3
No, it it a class in the ... - 07:23 AM Bug #6389: LENGTH function with COLUMN option
- Artur, you mean this project? https://github.com/jline/jline3
Greg: please comment about BSD. - 07:21 AM Bug #6389: LENGTH function with COLUMN option
- I wrote an implementation for the @columnLength@ method, but it relies on the @jdk.internal.org.jline.utils.WCWidth@ ...
- 05:57 AM Bug #6389 (WIP): LENGTH function with COLUMN option
- 08:11 AM Bug #9350: gap marking for LOG-MANAGER attributes and methods is probably wrong
- We have analytics tooling that allows us to evaluate the level of support for each 4GL language feature. This is rep...
- 08:10 AM Bug #9350: gap marking for LOG-MANAGER attributes and methods is probably wrong
- Greg Shah wrote:
> See [[p2j:Gap Analysis]].
Where is the gap marking for @LOG-MANAGER@? - 08:06 AM Bug #9350: gap marking for LOG-MANAGER attributes and methods is probably wrong
- How is this task different from #3853?
- 08:06 AM Bug #9350: gap marking for LOG-MANAGER attributes and methods is probably wrong
- See [[p2j:Gap Analysis]].
- 08:05 AM Bug #9350: gap marking for LOG-MANAGER attributes and methods is probably wrong
- These are some items in reports for an application being evaluated.
* attributes
** @LOGGING-LEVEL@ (conversion f... - 08:02 AM Bug #9350: gap marking for LOG-MANAGER attributes and methods is probably wrong
- What is the concern? I tested what I implemented, when I implemented it.
- 07:55 AM Bug #9350 (Internal Test): gap marking for LOG-MANAGER attributes and methods is probably wrong
Also available in: Atom