Activity
From 10/24/2019 to 11/22/2019
11/22/2019
- 04:42 PM Bug #4427: Unable to convert keyword input when used to index into an extent
- h1. General
Expression execution error when there is an @input@ statement withing the brackets of an extent which ... - 04:31 PM Bug #4427 (Closed): Unable to convert keyword input when used to index into an extent
- 03:46 PM Bug #4425: Lost frame_id when converting code with missing field names to update
- h1. General
A typo in code resulted in @update@ not having any field names passed to it. This creates a conversion... - 03:38 PM Bug #4425 (Closed): Lost frame_id when converting code with missing field names to update
- 03:11 PM Bug #4423: Incorrect buffer scoping when same buffer name used as a parameter to internal procedure
- It probably should only be set when this is a parameter.
This change is dangerous so it will need some regression ... - 03:07 PM Bug #4423: Incorrect buffer scoping when same buffer name used as a parameter to internal procedure
- Greg Shah wrote:
> I think it needs to do that for regular buffer definitions, but I suspect that buffer parameters ... - 02:45 PM Bug #4423: Incorrect buffer scoping when same buffer name used as a parameter to internal procedure
- I think it needs to do that for regular buffer definitions, but I suspect that buffer parameters should not be propag...
- 02:29 PM Bug #4423: Incorrect buffer scoping when same buffer name used as a parameter to internal procedure
- Greg, the issue is with this code, in @progress.g:procedure@ like 11198:...
- 02:20 PM Bug #4423: Incorrect buffer scoping when same buffer name used as a parameter to internal procedure
- Constantin Asofiei wrote:
> The @bufname@ annotation is incorrect:
> [...]
> instead of the correct one:
> [...]
... - 02:14 PM Bug #4423: Incorrect buffer scoping when same buffer name used as a parameter to internal procedure
- The @bufname@ annotation is incorrect:...
- 01:49 PM Bug #4423: Incorrect buffer scoping when same buffer name used as a parameter to internal procedure
- h1. General
Conversion error occurs when dealing with a shared buffer name that also happens to be defined as a pa... - 01:21 PM Bug #4423 (Closed): Incorrect buffer scoping when same buffer name used as a parameter to interna...
- 03:08 PM Bug #4424: Additional def var needed to receive table handle when keyword FOR included in def par...
- The solution is to add code in annotations that will detect this case. When found, it should:
* delete the @FOR@ ... - 02:58 PM Bug #4424: Additional def var needed to receive table handle when keyword FOR included in def par...
- h1. General
We found usual syntax in code where the keyword @for@ was included as a qualifier to the @def input pa... - 02:08 PM Bug #4424 (Closed): Additional def var needed to receive table handle when keyword FOR included i...
11/21/2019
- 04:59 PM Feature #3867: direct java class access from 4GL code
- In @BlockManager.topLevelBlock()@, it seems like this code should be aware of @BLOCK-LEVEL/ROUTINE-LEVEL ON ERROR UND...
11/20/2019
- 02:56 AM Feature #3753: I18N additions
- We add tests for translation using Chinese language.
For Chinese language we have to use UTF-8 code page for all inv...
11/19/2019
- 05:37 PM Feature #3867: direct java class access from 4GL code
- Greg Shah wrote:
> Any catch block directly inside any top level block will not be parented at a @prog.inner_block@.... - 05:34 PM Feature #3867: direct java class access from 4GL code
- A testcase like this:...
- 05:28 PM Feature #3867: direct java class access from 4GL code
- At this time, the 4GL catch block is incompatible with Java's checked exceptions. This is due to the fact that we ar...
- 02:24 AM Feature #3810: SECURITY-POLICY and other security features
- Igor Skornyakov wrote:
> Constantin. I understand that the top priority for me at this moment is #4363 and #4364. Is... - 02:23 AM Feature #3810: SECURITY-POLICY and other security features
- Thank you, Marian.
Constantin. I understand that the top priority for me at this moment is #4363 and #4364. Is thi... - 01:36 AM Feature #3810: SECURITY-POLICY and other security features
- Igor Skornyakov wrote:
> Regarding the @domainAccessCode@. This is indeed a secret data and is not serialized. I'me ...
11/18/2019
- 05:23 PM Feature #3810: SECURITY-POLICY and other security features
- Igor Skornyakov wrote:
> Constantin. I have to recall the details. I will provide my thoughts tomorrow. Please note,... - 03:54 PM Feature #3810: SECURITY-POLICY and other security features
- Constantin Asofiei wrote:
> Igor, I have two issues:
> * if you try to use @set-client@ a second time, on a already... - 03:42 PM Feature #3810: SECURITY-POLICY and other security features
- Igor, I have two issues:
* if you try to use @set-client@ a second time, on a already auth DB (with the same client-... - 02:52 PM Feature #4417: features to allow direct usage of _progres (and related executables) to be support...
- Customers use @_progres@ (and other related executables) to launch 4GL sessions. oday, in each project a task must b...
- 02:47 PM Feature #4417 (New): features to allow direct usage of _progres (and related executables) to be s...
11/14/2019
- 08:59 AM Feature #3753: I18N additions
- To run tests, follow steps should be done:
Create a database named *tran* in folder testcases/tran_man/db
Load de...
11/13/2019
- 04:18 PM Feature #3867: direct java class access from 4GL code
- Task branch 4069a has been merged to trunk as revision 11339. This is the majority of the necessary support. There ...
11/09/2019
- 09:34 AM Feature #4396: add LONGCHAR support to X-DOCUMENT:LOAD()
- Implement @LONGCHAR@ support to @X-DOCUMENT:LOAD()@.
If I understand correctly, after this addition the @LOAD()@ m... - 09:33 AM Feature #4396 (Closed): add LONGCHAR support to X-DOCUMENT:LOAD()
- 08:15 AM Feature #4395: add support for KEEP-MESSAGES option
- For sure, this can be used in @OUTPUT TO@ and must be implemented for that case.
This option is only documented as... - 08:01 AM Feature #4395 (Closed): add support for KEEP-MESSAGES option
11/08/2019
- 03:57 PM Feature #4392: add -pf support for appserver CONNECT() method
- Example:
@h-appsrv:connect("-pf " + some-filename) no-error.@ - 03:56 PM Feature #4392 (Closed): add -pf support for appserver CONNECT() method
- 03:49 PM Feature #4391 (Closed): enhance existing SESSION:STARTUP-PARAMETERS support to honor -H -db -S -l...
11/07/2019
- 06:40 AM Feature #3753: I18N additions
- Constantin Asofiei wrote in #3753-10
> All runtime needs to be implemented. Below is a list of what it needs to be ... - 02:02 AM Feature #3753: I18N additions
- Eugenie Lyzenko wrote:
> +4GL tests requirement+
>
> The following option's dependency need to be tested in 4GL e...
11/05/2019
- 06:11 PM Feature #4384: Builtin OO Implementation
- h2. OO Built-Ins Requiring Implementation
Breakdown of OO BuiltIns to focus on:
* openedge.core.* = 3 Partial
* ... - 06:10 PM Feature #4384 (Closed): Builtin OO Implementation
11/04/2019
- 03:48 AM Feature #3810: SECURITY-POLICY and other security features
- Greg Shah wrote:
> Igor: Did you ever create this note? I need the list of open items remaining from this task. I ...
11/03/2019
- 02:32 PM Feature #3753: I18N additions
- Greg Shah wrote:
> Eugenie: I don't think that the @NO-MAP@ I/O option was ever implemented in the runtime. It just... - 02:24 PM Feature #3753: I18N additions
- Greg Shah wrote:
> Eugenie: The @NO-CONVERT@ and @CONVERT@ I/O options are listed as full and stub. I think this is... - 01:09 PM Feature #3753: I18N additions
- Eugenie: The @NO-CONVERT@ and @CONVERT@ I/O options are listed as full and stub. I think this is incorrect. I think...
- 01:04 PM Feature #3753: I18N additions
- Eugenie: I don't think that the @NO-MAP@ I/O option was ever implemented in the runtime. It just looks like a stub.
- 08:24 AM Feature #4382: implement configurable directory override for PROGRESS global variable
- Currently the code always returns "Full", but this is probably not a great idea. It means that COMPILE will work, wh...
- 08:20 AM Feature #4382 (Closed): implement configurable directory override for PROGRESS global variable
- 07:08 AM Feature #4381: implement LIBRARY() and MEMBER() built-in functions
- Implement the following:
* @LIBRARY()@ built-in function
* @MEMBER()@ built-in function (has conversion to @FileS... - 07:05 AM Feature #4381 (Closed): implement LIBRARY() and MEMBER() built-in functions
- 06:08 AM Feature #4380: finish work on some security features
- *GES: this is being edited right now. I will be adding other items shortly.*
The following are needed:
* Run t... - 05:49 AM Feature #4380 (New): finish work on some security features
- 06:07 AM Feature #3810: SECURITY-POLICY and other security features
- Greg Shah wrote:
> We actually have much of that code in our spawner today (for Linux/UNIX and Windows). But it wil...
11/02/2019
- 01:07 PM Feature #4378: properly handle clob/lonchar assignment, especially the implicit codepage conversion
- * When a longchar/clob value is assigned to a clob field, it is implicitly converted into the codepage of the target ...
- 01:06 PM Feature #4378 (Closed): properly handle clob/lonchar assignment, especially the implicit codepage...
10/30/2019
- 09:59 AM Feature #3751 (Closed): implement support for OO 4GL and structured error handling
- The remaining work will be done in #4373.
- 09:54 AM Feature #4374: parameter validation for Progress.Lang.Class:invoke and new
- Implement parameter validation for Progress.Lang.Class:invoke and new. Here we may have problems as we had with CALL ...
- 09:54 AM Feature #4374 (New): parameter validation for Progress.Lang.Class:invoke and new
- 09:53 AM Feature #4373: finish core OO 4GL support
- This task is to aggregate the work to finish the OO 4GL implementation. The majority of the work for OO 4GL was alre...
- 09:49 AM Feature #4373 (New): finish core OO 4GL support
10/24/2019
- 03:30 PM Feature #3810: SECURITY-POLICY and other security features
- Branch 3810d was merged into the trunk revision 11338.
- 01:12 PM Feature #3810: SECURITY-POLICY and other security features
- Constantin Asofiei wrote:
> Does the #3810-387 testcase work properly now?
Yes, it does.
> Is #3810-399 fixed, i... - 01:05 PM Feature #3810: SECURITY-POLICY and other security features
- Igor Skornyakov wrote:
> The branch 3810d is ready for the code review.
Does the #3810-387 testcase work properly n...
Also available in: Atom