Activity
From 06/03/2024 to 07/02/2024
07/01/2024
- 05:07 PM Feature #6431: implement support to allow CPINTERNAL set to UTF-8 and CP936
- I'm not asure where to bring this up. I ran into some new issues with our latest p2j library. We use functions key F1...
- 09:07 AM Feature #6410: implement additional built-in OO classes/interfaces
- OK, then lets avoid the temp-table implementation.
- 08:04 AM Feature #6410: implement additional built-in OO classes/interfaces
- Greg Shah wrote:
> Constantin: Is this implicit temp-table access heavily used in the application code or is this so... - 07:48 AM Feature #6410: implement additional built-in OO classes/interfaces
- Constantin: Is this implicit temp-table access heavily used in the application code or is this something that can be ...
- 07:44 AM Feature #6410: implement additional built-in OO classes/interfaces
- Constantin Asofiei wrote:
> * shows an implicit temp-table is created
Yes, default constructor is probably using th... - 08:54 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- Alexandru Lungu wrote:
> 6667g is based on trunk rev/15271, so it includes both revisions.
I understand now, I'll... - 08:53 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- Dănuț Filimon wrote:
> ... can you take a look at #8643-12 and let me know if this patch is ok for 7156b?
The patch... - 08:52 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- 6667g is based on trunk rev/15271, so it includes both revisions.
- 08:50 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- Alexandru Lungu wrote:
> Danut, please pend effort until I can get some logs from 6667g to cross-check.
This issu... - 08:46 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- Constantin Asofiei wrote:
> I've tried using @BlockManager@ and @TransactionManager@ from trunk (not just revs 14998... - 08:45 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- Danut, please pend effort until I can get some logs from 6667g to cross-check.
- 08:44 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- I've tried using @BlockManager@ and @TransactionManager@ from trunk (not just revs 14998/15244, so other changes, too...
- 04:22 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- Alexandru Lungu wrote:
> Danut, trunk/14998 was especially created to handle rollbacks, as there were unit tests (on... - 04:19 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- Danut, trunk/14998 was especially created to handle rollbacks, as there were unit tests (on another customer applicat...
- 04:15 AM Bug #8643 (WIP): ErrorManager not handling caught errors and error-status:error attribute properly
- I've been investigating the double validation and was using 7156b with the changes from 8643a for testing. For a set ...
06/29/2024
- 06:20 AM Bug #8910: 'VIEW frame IN WINDOW' converts to invalid Java
- Workaround:...
- 04:19 AM Bug #8910: 'VIEW frame IN WINDOW' converts to invalid Java
- Probably, the correct output shall look like this?...
06/28/2024
- 04:38 PM Bug #8910: 'VIEW frame IN WINDOW' converts to invalid Java
- The @VIEW outerFrame IN WINDOW wnd.@ statement in the following code:...
- 04:33 PM Bug #8910 (New): 'VIEW frame IN WINDOW' converts to invalid Java
- 10:40 AM Feature #4347 (Closed): add runtime support for STOP-AFTER block option
- 10:33 AM Feature #4347: add runtime support for STOP-AFTER block option
- Greg Shah wrote:
> Are all of your testcases meeting the following criteria?
>
> * Checked into xfer [[p2j:Testca... - 04:32 AM Feature #6410: implement additional built-in OO classes/interfaces
- Marian, regarding the @OpenEdge.Core.Collections.List@ question. There are these two cases in #8880:
* shows an imp...
06/26/2024
- 08:43 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- The change mentioned in #8643-15 is not ok, the method called is @RecordBuffer.validate()@ which calls @flush(true)@ ...
- 05:51 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- It's caused by the revalidation of the record in @BlockManager.processForBody()@:...
- 05:38 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- *8643a* changes fail this test where the error is shown into a modal instead of being caught by the catch block:
<pr... - 04:57 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- I've posted my results in #8308-403 where I compared the previously made changes from 8308e with the new changes from...
- 03:52 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- I'll be testing with the attached patch, let me know if it's not correct.
*EDIT*: the patch does not contain the *... - 03:47 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- Constantin, patching ErrorManager for 7156b is a bit hard to understand as there are no @ServerErrorDataAccessor@ and...
- 07:57 AM Feature #6417: cleanup some known items in appserver support
- The documentation for the original implementation in FWD is at [[p2j:Appserver_Support]] and [[p2j:Setup_and_Configur...
- 07:44 AM Feature #4347: add runtime support for STOP-AFTER block option
- Are all of your testcases meeting the following criteria?
* Checked into xfer [[p2j:Testcases]] project.
* Implem... - 04:36 AM Feature #4347 (Test): add runtime support for STOP-AFTER block option
- 04:34 AM Feature #4347: add runtime support for STOP-AFTER block option
- 4347a was merged into trunk revision 15310, and archived.
- 02:33 AM Feature #4347 (Merge Pending): add runtime support for STOP-AFTER block option
- ChUI regression passed. One test failed (time-out) when running all tests automatically, but I re-run it manually and...
- 07:41 AM Feature #8904: implement -catchStop and the integration/conversion of STOP conditions into except...
- See #4347-19 and following for a discussion about how @STOP@ conditions can be converted into @Progress.Lang.Stop@ ex...
- 07:38 AM Feature #8904 (Closed): implement -catchStop and the integration/conversion of STOP conditions in...
06/25/2024
- 10:28 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- I've rebased 7643a from trunk rev 15308.
The changes are in rev 15311. With this, the tests in #8308-397, #8308-3... - 03:12 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- Constantin Asofiei wrote:
> Dănuț Filimon wrote:
> > Committed *8643a/rev.15307* which contains the 15272 and 15273... - 08:46 AM Feature #6417: cleanup some known items in appserver support
- Just a quick note to inform you the tests for consuming WS from 4GL (FWD) client were converted to ABLUnit - availabl...
- 08:15 AM Feature #6417: cleanup some known items in appserver support
- Greg Shah wrote:
> > I think I should implement it and wait for the review to discuss it further, as per usual.
>
... - 08:14 AM Feature #6417: cleanup some known items in appserver support
- > I think I should implement it and wait for the review to discuss it further, as per usual.
Does this really have... - 07:45 AM Feature #6417: cleanup some known items in appserver support
- Marian, thanks for the references.
I've read the Progress documentation, so my question was if we do Progress-like... - 07:39 AM Feature #6417: cleanup some known items in appserver support
- Galya B wrote:
> Greg Shah wrote:
> > Aren't we simulating the nameserver lookup with our services configuration in... - 06:58 AM Feature #6417: cleanup some known items in appserver support
- Greg Shah wrote:
> If I understand correctly, we are just trying to bypass the nameserver nonsense and use the servi... - 06:48 AM Feature #6417: cleanup some known items in appserver support
- Constantin: Please provide some details about how this is supposed to work and why we have it.
Consider that appli... - 06:29 AM Feature #6417: cleanup some known items in appserver support
- Greg Shah wrote:
> Aren't we simulating the nameserver lookup with our services configuration in the directory?
We ... - 06:23 AM Feature #6417: cleanup some known items in appserver support
- Aren't we simulating the nameserver lookup with our services configuration in the directory?
- 03:33 AM Feature #6417: cleanup some known items in appserver support
- Galya B wrote:
> Greg Shah wrote:
> > We have no need for the nameserver. We don't plan to implement a replacement... - 01:58 AM Feature #6417: cleanup some known items in appserver support
- Greg Shah wrote:
> We have no need for the nameserver. We don't plan to implement a replacement for it. Any functi...
06/24/2024
- 09:55 AM Feature #6417: cleanup some known items in appserver support
- We have no need for the nameserver. We don't plan to implement a replacement for it. Any functionality choices shou...
- 09:44 AM Feature #6417: cleanup some known items in appserver support
- What's different in FWD is that appserver connect works without nameserver and without @-DirectConnect@. In Progress ...
- 08:47 AM Feature #6417: cleanup some known items in appserver support
- Greg Shah wrote:
> Galya B wrote:
> > Constantin, I don't understand what is the function of the appserver config @... - 08:43 AM Feature #6417: cleanup some known items in appserver support
- Galya B wrote:
> Constantin, I don't understand what is the function of the appserver config @services@ in the conte... - 08:40 AM Feature #6417: cleanup some known items in appserver support
- > > Where to find the 'TCP/IP services file' in Progress, where the IP <-> service name is configured for appserver c...
- 06:21 AM Feature #6417: cleanup some known items in appserver support
- Another question: How to configure a default appserver for Progress nameserver? There is no such config in the web ma...
- 05:49 AM Feature #6417: cleanup some known items in appserver support
- Constantin, I don't understand what is the function of the appserver config @services@ in the context of the finding ...
- 05:28 AM Feature #6417: cleanup some known items in appserver support
- Galya B wrote:
> Where to find the 'TCP/IP services file' in Progress, where the IP <-> service name is configured f... - 04:03 AM Feature #6417: cleanup some known items in appserver support
- Where to find the 'TCP/IP services file' in Progress, where the IP <-> service name is configured for appserver connect?
- 02:03 AM Feature #6417 (WIP): cleanup some known items in appserver support
- 6417d was merged to trunk as rev. 15307 and archived.
- 01:55 AM Feature #6417 (Merge Pending): cleanup some known items in appserver support
- Galya, please merge 6417d
06/21/2024
- 02:30 PM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- Dănuț Filimon wrote:
> Committed *8643a/rev.15307* which contains the 15272 and 15273 revisions from *8308e*. (see #... - 10:29 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- Committed *8643a/rev.15307* which contains the 15272 and 15273 revisions from *8308e*. (see #8308-397)
- 10:12 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- Created *8643a*.
- 02:28 PM Feature #4347: add runtime support for STOP-AFTER block option
- Alexandru Lungu wrote:
> > ETF or some other appserver application testing to confirm that we haven't affected anyth... - 10:24 AM Feature #4347: add runtime support for STOP-AFTER block option
- Smoke tests for a customer GUI application passed.
- 10:13 AM Feature #4347: add runtime support for STOP-AFTER block option
- Rebased 4347a to latest trunk. It is now at rev. 15315.
- 09:59 AM Feature #4347: add runtime support for STOP-AFTER block option
- I am rebasing this now.
- 09:58 AM Feature #4347: add runtime support for STOP-AFTER block option
- > ChUI regression testing. It uses virtual sessions and more than one FWD server which is definitely affected by thes...
- 09:42 AM Feature #4347: add runtime support for STOP-AFTER block option
- Additional testing:
* ChUI regression testing. It uses virtual sessions and more than one FWD server which is def... - 09:08 AM Feature #4347: add runtime support for STOP-AFTER block option
- Committed on 4347a, revision 15212.
- 09:02 AM Feature #4347 (Internal Test): add runtime support for STOP-AFTER block option
- Eduard, please assess #4347-68 for 4347a.
This should be ready to be merged, right? Greg, other testing you sugges... - 08:56 AM Feature #4347: add runtime support for STOP-AFTER block option
- I tested Ctrl-C tests, with 4347a changes. And haven't got any regressions.
Also tested customer scenario, and it ... - 12:09 PM Feature #6417: cleanup some known items in appserver support
- No, no, I'm reverting, sorry, this is safer. Reverted in r15312.
- 12:08 PM Feature #6417: cleanup some known items in appserver support
- Or at least I need to add one @if (port == 0)@ before the filter.
- 12:04 PM Feature #6417: cleanup some known items in appserver support
- I think we should revert the @serviceName@ check. Less errors thrown, better. I think it's not correct now. What if i...
- 12:02 PM Feature #6417: cleanup some known items in appserver support
- Galya B wrote:
> Constantin Asofiei wrote:
> > So you can have both port and serviceName. More, serviceName for UR... - 11:59 AM Feature #6417: cleanup some known items in appserver support
- Constantin Asofiei wrote:
> So you can have both port and serviceName. More, serviceName for URL connections is con... - 11:46 AM Feature #6417: cleanup some known items in appserver support
- See r15311. I'm committing the test without the if, it works well now.
- 11:40 AM Feature #6417: cleanup some known items in appserver support
- Constantin Asofiei wrote:
> > @appsrv/test/connect_errors/service_name.p@ is successful. Is it not?
> It's a 'false... - 11:38 AM Feature #6417: cleanup some known items in appserver support
- Galya B wrote:
> Constantin Asofiei wrote:
> > > Constantin Asofiei wrote:
> > > > There is also an issue with @(s... - 11:37 AM Feature #6417: cleanup some known items in appserver support
- Constantin Asofiei wrote:
> > Constantin Asofiei wrote:
> > > There is also an issue with @(serviceName == null || ... - 11:20 AM Feature #6417: cleanup some known items in appserver support
- Galya B wrote:
> Our @-S@ is both @serviceName@ and @port@. So the port can be declared @0@ in the connect string, w... - 10:56 AM Feature #6417: cleanup some known items in appserver support
- Note #6417-283 edited.
- 10:54 AM Feature #6417: cleanup some known items in appserver support
- Galya B wrote:
> Constantin Asofiei wrote:
> > Galya, please add back the @if (port != 0)@ test - this is required ... - 10:33 AM Feature #6417: cleanup some known items in appserver support
- Constantin Asofiei wrote:
> Galya, please add back the @if (port != 0)@ test - this is required for connection strin... - 10:29 AM Feature #6417: cleanup some known items in appserver support
- Galya, please add back the @if (port != 0)@ test - this is required for connection strings like @-AppService app_serv...
- 10:01 AM Feature #6417: cleanup some known items in appserver support
- Constantin: Please review.
- 09:32 AM Feature #6417: cleanup some known items in appserver support
- The fix for #7143-1017 is on 6417d.
- 08:56 AM Feature #6417: cleanup some known items in appserver support
- This is a list of all testcases/appsrv/test procedures. Before they were converting / compiling fine, now not.
- 05:36 AM Feature #6417: cleanup some known items in appserver support
- Constantin Asofiei wrote:
> There is also an issue with @(serviceName == null || data.services.contains(serviceName)... - 05:29 AM Feature #6417: cleanup some known items in appserver support
- Constantin Asofiei wrote:
> Galya, please let me know when 6417d is available.
6417d is created from trunk r15306 a... - 04:00 AM Feature #6417: cleanup some known items in appserver support
- This is the async test:
* @appsrv/test/test_raise_quit2.p@...
06/20/2024
- 05:19 PM Feature #4347: add runtime support for STOP-AFTER block option
- Code Review Task Branch 4347a Revision 15211
It looks good.
Minor issue: please remove the @import com.goldenco... - 03:22 PM Feature #4347: add runtime support for STOP-AFTER block option
- Eduard reported in today's meeting that he was working to get Ctrl+C testing running. Greg, FYI, there is a 4347a/152...
- 10:17 AM Feature #6417: cleanup some known items in appserver support
- Branch 6417c was merged to trunk rev 15305 and archived.
- 10:11 AM Feature #6417: cleanup some known items in appserver support
- There is also an issue with the socket connection and 'nohostverify' - I've found when trying to run some reports in ...
- 08:59 AM Feature #6417: cleanup some known items in appserver support
- Constantin Asofiei wrote:
> * the test does not match the comment, I assume it was meant to be 'not equal':
> [...]... - 08:56 AM Feature #6417: cleanup some known items in appserver support
- Go ahead and merge 6417c.
- 08:54 AM Feature #6417: cleanup some known items in appserver support
- I've checked @test_raise_stop.p@, @test_raise_quit.p@, @test_return_value.p@ and these work with 6417c and a change i...
- 08:41 AM Feature #6417: cleanup some known items in appserver support
- Greg Shah wrote:
> > 'Time' doesn't close old tasks by itself. My assessment is that this functionality should not b... - 08:40 AM Feature #6417: cleanup some known items in appserver support
- > 'Time' doesn't close old tasks by itself. My assessment is that this functionality should not be reverted.
That... - 08:38 AM Feature #6417: cleanup some known items in appserver support
- Greg Shah wrote:
> > > No one is saying everything is your fault. And who really cares about blame when we simply n... - 08:36 AM Feature #6417: cleanup some known items in appserver support
- > > No one is saying everything is your fault. And who really cares about blame when we simply need to help a custom...
- 08:33 AM Feature #6417: cleanup some known items in appserver support
- Constantin found the issue early today. If he spoke with me, we might have had already found the proper solution. If ...
- 08:31 AM Feature #6417: cleanup some known items in appserver support
- Greg Shah wrote:
> No one is saying everything is your fault. And who really cares about blame when we simply need ... - 08:29 AM Feature #6417: cleanup some known items in appserver support
- Greg Shah wrote:
> runtime issue in converison issue with @FileSystemOps.initFileInfo@ fixed in 15299
This is not i... - 08:28 AM Feature #6417: cleanup some known items in appserver support
- No one is saying everything is your fault. And who really cares about blame when we simply need to help a customer w...
- 08:27 AM Feature #6417: cleanup some known items in appserver support
- # runtime issue in @FileSystemOps.initFileInfo@ fixed in 15299
# conversion issue in @control_flow.rules@ fixed in 1... - 08:25 AM Feature #6417: cleanup some known items in appserver support
- I wondered how I get so many black points in the register. Now I see. All issues in FWD are on my account.
- 08:22 AM Feature #6417: cleanup some known items in appserver support
- Greg Shah wrote:
> This is the 3rd regression from 6417a and if the solution Constantin proposes is not obviously sa... - 08:20 AM Feature #6417: cleanup some known items in appserver support
- > > Are you saying it is better to back out 6417a completely?
> I'm obviously saying that a hotfix takes some time a... - 08:20 AM Feature #6417: cleanup some known items in appserver support
- Greg Shah wrote:
> Across all of our customers, SOAP is much less used than appserver. For this customer, it is clo... - 08:19 AM Feature #6417: cleanup some known items in appserver support
- Across all of our customers, SOAP is much less used than appserver. For this customer, it is close to a production i...
- 08:17 AM Feature #6417: cleanup some known items in appserver support
- Greg Shah wrote:
> Are you saying it is better to back out 6417a completely?
I'm obviously saying that a hotfix tak... - 08:15 AM Feature #6417: cleanup some known items in appserver support
- I mean when SOAP wasn't working for days after java 17 related changes merge it wasn't urgent.
- 08:15 AM Feature #6417: cleanup some known items in appserver support
- Are you saying it is better to back out 6417a completely?
- 08:15 AM Feature #6417: cleanup some known items in appserver support
- I'm generally surprised by the urgency of an issue not on production. Even issues on production usually take a day or...
- 08:13 AM Feature #6417: cleanup some known items in appserver support
- Greg Shah wrote:
> Galya: Please split this discussion into 2 parts. The first, urgent part is to ensure that 6417c... - 08:10 AM Feature #6417: cleanup some known items in appserver support
- Also don't expect me to remember just like that what a change done months ago involves. That's what automation is about.
- 08:07 AM Feature #6417: cleanup some known items in appserver support
- Greg Shah wrote:
> This regression is holding back a customer's testing. While it exists in trunk, they are blocked... - 07:49 AM Feature #6417: cleanup some known items in appserver support
- This regression is holding back a customer's testing. While it exists in trunk, they are blocked. It is urgent to g...
- 06:19 AM Feature #6417: cleanup some known items in appserver support
- Constantin Asofiei wrote:
> Galya B wrote:
> > Constantin Asofiei wrote:
> > > Galya B wrote:
> > > > Can you exp... - 06:17 AM Feature #6417: cleanup some known items in appserver support
- Galya B wrote:
> Constantin Asofiei wrote:
> > Galya B wrote:
> > > Can you explain why you back it out? What are ... - 06:10 AM Feature #6417: cleanup some known items in appserver support
- Constantin Asofiei wrote:
> Galya B wrote:
> > Can you explain why you back it out? What are the steps for reproduc... - 06:07 AM Feature #6417: cleanup some known items in appserver support
- Galya B wrote:
> Can you explain why you back it out? What are the steps for reproducing an issue?
The root cause i... - 05:40 AM Feature #6417: cleanup some known items in appserver support
- Can you explain why you back it out? What are the steps for reproducing an issue?
- 05:39 AM Feature #6417: cleanup some known items in appserver support
- Constantin Asofiei wrote:
> 6417c rev 15304 backed out part of trunk rev 15287 in AppServerManager - the client need... - 05:37 AM Feature #6417: cleanup some known items in appserver support
- Constantin Asofiei wrote:
> 6417c rev 15304 backed out part of trunk rev 15287 in AppServerManager - the client need... - 05:34 AM Feature #6417: cleanup some known items in appserver support
- Created task branch 6417c from trunk rev 15303.
6417c rev 15304 backed out part of trunk rev 15287 in AppServerMan... - 03:12 AM Feature #6417: cleanup some known items in appserver support
- Also the revert in #6417-235 breaks a core functionality of SOAP, so we should address it somehow.
- 03:10 AM Feature #6417: cleanup some known items in appserver support
- Constantin, give me more information on #7143-1012.
06/19/2024
- 12:56 PM Feature #4347: add runtime support for STOP-AFTER block option
- After making these changes, please work with Tomasz to run all the CTRL-C tests using this branch.
- 12:55 PM Feature #4347: add runtime support for STOP-AFTER block option
- Code Review Task Branch 4347a Revision 15210
This is good. It is very close.
1. I'm worried about the use of @... - 11:00 AM Feature #4347: add runtime support for STOP-AFTER block option
- Committed on 4347a, revision 15210.
Changed implementation to insert Ctrl-C into TypeAhead queue.
Added as spec... - 07:55 AM Feature #6417: cleanup some known items in appserver support
- Just a quick note to let you know the tests for calling appsrv from 4GL client (RPC style) were converted to AblUnit ...
- 04:46 AM Feature #6417: cleanup some known items in appserver support
- Created task branch 6417b from trunk rev 15298 to fix an existing bug exposed by the changes in 6417a.
The fix is ...
06/18/2024
- 03:35 PM Feature #4347: add runtime support for STOP-AFTER block option
- > > > Perhaps we need to down-call to cause this to occur. But I don't think it is as simple as making a downcall, s...
- 01:46 PM Feature #4347: add runtime support for STOP-AFTER block option
- Code Review Task Branch 4347a Revision 15209
1. The changes to rewrite the @Control@ synchronization are extensive... - 01:29 PM Feature #4347: add runtime support for STOP-AFTER block option
- > >I think we might have to insert @CTRL-C@ into the type ahead queue. Interestingly, that should even work when the...
- 11:01 AM Feature #4347: add runtime support for STOP-AFTER block option
- Committed on 4347a, revision 15209.
I implemented a mechanism to interrupt a Conversation thread and synchronize the... - 06:40 AM Feature #6417 (WIP): cleanup some known items in appserver support
- 05:31 AM Feature #6417: cleanup some known items in appserver support
- 6417a was merged to trunk as rev. 15287 and archived.
- 03:04 AM Feature #6417: cleanup some known items in appserver support
- Constantin Asofiei wrote:
> Galya B wrote:
> > Let me know about 7994a and merge.
> Lets get 6417a to trunk first ... - 03:01 AM Feature #6417: cleanup some known items in appserver support
- Galya B wrote:
> Let me know about 7994a and merge.
Lets get 6417a to trunk first and after that we'll check #7994 ... - 02:59 AM Feature #6417 (Merge Pending): cleanup some known items in appserver support
- This can be merged after 8848a
- 01:36 AM Feature #6417: cleanup some known items in appserver support
- Galya B wrote:
> > Galya, this must be from the Jetty upgrade - we need a @baseRequest.setHandled(true);@ being call... - 12:38 AM Feature #6417: cleanup some known items in appserver support
- Greg Shah wrote:
> Did 6417a pass its testing? If so, I'd like to get it merged.
It passed, but my concern is th...
06/17/2024
- 03:05 PM Feature #6417: cleanup some known items in appserver support
- Did 6417a pass its testing? If so, I'd like to get it merged.
- 02:39 PM Feature #6417: cleanup some known items in appserver support
- > Greg/Tomasz: is it worth it to integrate the #7994 work from 6667i into 6417a, so we can merge it to trunk?
Yes,... - 02:30 PM Feature #6417: cleanup some known items in appserver support
- Galya, this must be from the Jetty upgrade - we need a @baseRequest.setHandled(true);@ being called always in @SoapHa...
- 03:29 AM Feature #6417: cleanup some known items in appserver support
- There is something wrong with SOAP on +trunk+. Jetty returns 404, although the @SoapHandler@ handles the requests suc...
06/14/2024
- 10:25 AM Feature #4347: add runtime support for STOP-AFTER block option
- Greg Shah wrote:
>I think we might have to insert @CTRL-C@ into the type ahead queue. Interestingly, that should ev...
06/13/2024
- 07:42 AM Feature #4347: add runtime support for STOP-AFTER block option
- Eduard Soltan wrote:
> Imagine an situation.
> If I am in timer thread and control is on the client side, I send a ... - 04:02 AM Feature #4347: add runtime support for STOP-AFTER block option
- Imagine an situation.
If I am in timer thread and control is on the client side, I send a interrupt message to the c... - 01:30 AM Feature #6417: cleanup some known items in appserver support
- Constantin Asofiei wrote:
> Galya B wrote:
> > Since the tests are up to date, how do I solve #6417-149?
> This is...
06/12/2024
- 11:11 AM Feature #4347: add runtime support for STOP-AFTER block option
- OK, go ahead with that idea.
- 04:51 AM Feature #4347: add runtime support for STOP-AFTER block option
- Greg Shah wrote:
> Perhaps we need to down-call to cause this to occur. But I don't think it is as simple as making... - 10:16 AM Feature #6417: cleanup some known items in appserver support
- Galya B wrote:
> Since the tests are up to date, how do I solve #6417-149?
This is tricky; on a first glance, decim... - 09:11 AM Feature #6417: cleanup some known items in appserver support
- Constantin Asofiei wrote:
> Galya, I don't think you need to setup OpenEdge to run the REST/SOAP tests.
>
> @webt... - 03:11 AM Bug #8799: ON ERROR UNDO, THROW problems leading to infinite loops
- Greg Shah wrote:
> Do you think that 40% is accurate for %Done?
We need to run the tests from xfer - we'll now more... - 02:45 AM Bug #8799: ON ERROR UNDO, THROW problems leading to infinite loops
- Constantin Asofiei wrote:
> * Once a structured exception is re-thrown, mark it as explicit, so it can be re-thrown ...
06/11/2024
- 05:44 PM Bug #8799 (Test): ON ERROR UNDO, THROW problems leading to infinite loops
- Do you think that 40% is accurate for %Done?
- 05:37 PM Bug #8799: ON ERROR UNDO, THROW problems leading to infinite loops
- Branch 8799a was merged to trunk rev 15279 and archived.
- 05:16 PM Bug #8799 (Merge Pending): ON ERROR UNDO, THROW problems leading to infinite loops
- You can merge to trunk now.
- 04:59 PM Bug #8799: ON ERROR UNDO, THROW problems leading to infinite loops
- 8799a passed #7156 customer testing and other unit tests.
- 09:19 AM Bug #8799: ON ERROR UNDO, THROW problems leading to infinite loops
- Code Review Task Branch 8799a Revision 15277
I'm good with the changes. - 08:15 AM Bug #8799 (Internal Test): ON ERROR UNDO, THROW problems leading to infinite loops
- 04:12 PM Feature #4347: add runtime support for STOP-AFTER block option
- Eduard Soltan wrote:
> Greg Shah wrote:
> >7. Help me understand why the implementation of Control.setControl() is ... - 07:27 AM Feature #4347: add runtime support for STOP-AFTER block option
- Greg Shah wrote:
> 8. In @StopAfterTimer.addTimeOut()@, directly raising @NumberedException@ seems to be incorrect. ... - 07:22 AM Feature #4347: add runtime support for STOP-AFTER block option
- Greg Shah wrote:
>7. Help me understand why the implementation of Control.setControl() is correct. In particular, do... - 08:04 PM Feature #4347: add runtime support for STOP-AFTER block option
- Code Review 4347a Revisions 15205 through 15208
1. The @BlockManager.LOG@ should not be initialized using @ErrorMa... - 05:39 AM Feature #6417: cleanup some known items in appserver support
- Galya B wrote:
> Can you check r15302.
The changes look good. I was trying to get a standalone test with FWD clien... - 04:18 AM Feature #6417: cleanup some known items in appserver support
- Can you check r15302.
- 04:09 AM Feature #6417: cleanup some known items in appserver support
- Galya B wrote:
> Constantin Asofiei wrote:
> > Also, the @server@ handle can also be assigned to @SESSION@ - in thi... - 04:00 AM Feature #6417: cleanup some known items in appserver support
- Constantin Asofiei wrote:
> Also, the @server@ handle can also be assigned to @SESSION@ - in this case, @if (serverH... - 03:18 AM Feature #6417: cleanup some known items in appserver support
- Constantin Asofiei wrote:
> by @throw on the Conversion thread@ you meant @throw on the Conversation thread@?
Yes. ... - 02:41 AM Feature #6417: cleanup some known items in appserver support
- Galya B wrote:
> Client type is not done. It will have to be reviewed and tested further. It's way more complicated ... - 01:36 AM Feature #6417: cleanup some known items in appserver support
- Constantin Asofiei wrote:
> Review for 6417a/15301 built on trunk rev 15276:
> * @src/com/goldencode/p2j/oo/lang/Oe...
06/10/2024
- 11:57 AM Feature #6417: cleanup some known items in appserver support
- Review for 6417a/15301 built on trunk rev 15276:
* @src/com/goldencode/p2j/oo/lang/OeversionInfo.java@
** in the ja... - 07:45 AM Feature #6417: cleanup some known items in appserver support
- Constantin Asofiei wrote:
> The runtime needs to be regression tested with ChUI and other unit testing for customer ... - 07:44 AM Feature #6417: cleanup some known items in appserver support
- New r15301 of 6417a based on trunk r15276 ready for review.
- 07:29 AM Feature #6417: cleanup some known items in appserver support
- Galya B wrote:
> Other cases need to be fixed by calling a new server exported method, which I forgot and left in TO... - 07:26 AM Feature #6417: cleanup some known items in appserver support
- Constantin Asofiei wrote:
> ** @recordOrThrowError@ can be called from FWD client, too - why @if (serverSide) { thro... - 07:01 AM Feature #6417: cleanup some known items in appserver support
- Constantin Asofiei wrote:
> * @src/com/goldencode/p2j/util/SessionUtils.java@
> ** for @getClientType@, the value o... - 06:46 AM Feature #6417: cleanup some known items in appserver support
- Galya B wrote:
> It fixes a startup procedure being configured without startup params.
OK, just for clarification: ... - 06:43 AM Feature #6417: cleanup some known items in appserver support
- Constantin Asofiei wrote:
> Galya B wrote:
> > The last example doesn't work. If you want me to revert the change, ... - 06:40 AM Feature #6417: cleanup some known items in appserver support
- Galya B wrote:
> The last example doesn't work. If you want me to revert the change, it will continue to fail agents... - 06:33 AM Feature #6417: cleanup some known items in appserver support
- Constantin Asofiei wrote:
> I'm talking about this code in @Agent.listen@:
> [...]
>
> This is executed when the... - 06:28 AM Feature #6417: cleanup some known items in appserver support
- I'm talking about this code in @Agent.listen@:...
- 06:22 AM Feature #6417: cleanup some known items in appserver support
- Constantin Asofiei wrote:
> I don't understand - startup procedure defines an input parameter, always. FWD must pas... - 06:16 AM Feature #6417: cleanup some known items in appserver support
- I don't understand - startup procedure defines an input parameter, always. FWD must pass this argument, otherwise th...
- 06:14 AM Feature #6417: cleanup some known items in appserver support
- Constantin Asofiei wrote:
> * @src/com/goldencode/p2j/util/Agent.java@
> ** Agent's startup-procedure signature alw... - 05:19 AM Feature #6417: cleanup some known items in appserver support
- Comment this line, at the time this was written I think there was a problem with the log:
> // generateRestTests(RES... - 02:51 AM Feature #6417: cleanup some known items in appserver support
- @SoapUILog2Harness@ doesn't compile.
- 02:44 AM Feature #6417: cleanup some known items in appserver support
- Constantin Asofiei wrote:
> Galya, I don't think you need to setup OpenEdge to run the REST/SOAP tests.
>
> @webt... - 02:37 AM Feature #6417: cleanup some known items in appserver support
- Marian Edu wrote:
> Galya B wrote:
> > I need confirmation if I got it right: I need to figure out by myself how to...
06/09/2024
- 10:46 AM Feature #6417: cleanup some known items in appserver support
- Review for 6417a/15226 built on trunk rev 15202:
* branch needs rebase
* files with missing history entry:... - 02:39 AM Bug #8799: ON ERROR UNDO, THROW problems leading to infinite loops
- Created task branch 8799a from trunk rev 15266. Rev 15277 has:
* Once a structured exception is re-thrown, mark it ...
06/07/2024
- 09:27 AM Feature #6417: cleanup some known items in appserver support
- Galya, I don't think you need to setup OpenEdge to run the REST/SOAP tests.
@webtests_from_logs@ is meant to autom... - 09:19 AM Feature #6417: cleanup some known items in appserver support
- Galya B wrote:
> I need confirmation if I got it right: I need to figure out by myself how to setup Progress classic... - 08:46 AM Feature #6417: cleanup some known items in appserver support
- I need confirmation if I got it right: I need to figure out by myself how to setup Progress classic appserver with RE...
- 08:21 AM Feature #6417: cleanup some known items in appserver support
- Greg Shah wrote:
> > The comment also says run all SoapUI tests. Am I supposed to set SOAP and REST api in Progress ... - 08:14 AM Feature #6417: cleanup some known items in appserver support
- > The comment also says run all SoapUI tests. Am I supposed to set SOAP and REST api in Progress corresponding to wha...
- 07:58 AM Feature #6417: cleanup some known items in appserver support
- Greg Shah wrote:
> Is this not what was documented in #6417-8 and following discussion?
The "documentation" is ex... - 07:40 AM Feature #6417: cleanup some known items in appserver support
- Is this not what was documented in #6417-8 and following discussion?
- 07:33 AM Feature #6417: cleanup some known items in appserver support
- Greg Shah wrote:
> Setup equivalent testing environments in both OE and FWD.
Hasn't this already been done / docume... - 07:29 AM Feature #6417: cleanup some known items in appserver support
- Can you start with this:
# Setup equivalent testing environments in both OE and FWD.
# Run the tests in both envi... - 07:25 AM Feature #6417: cleanup some known items in appserver support
- I can't proceed with fixing all tests or related issues in FWD appservers without clear documentation what has been d...
- 07:24 AM Feature #6417: cleanup some known items in appserver support
- We should separate our artifacts from OE and FWD. Either by more specific name or by separate directories.
- 07:19 AM Feature #6417: cleanup some known items in appserver support
- Constantin Asofiei wrote:
> Galya B wrote:
> > So @webtests_from_logs/results/20211112_201954_soap_classic/test_set... - 07:17 AM Feature #6417: cleanup some known items in appserver support
- Galya B wrote:
> Constantin Asofiei wrote:
> > Galya, the @errorCode@ text from the @Error in SOAP parameter: error... - 06:27 AM Feature #6417: cleanup some known items in appserver support
- Constantin Asofiei wrote:
> Galya, the @errorCode@ text from the @Error in SOAP parameter: errorCode@ message is the... - 06:22 AM Feature #6417: cleanup some known items in appserver support
- Galya, the @errorCode@ text from the @Error in SOAP parameter: errorCode@ message is the first argument from @new App...
- 06:12 AM Feature #6417: cleanup some known items in appserver support
- I'm puzzled by @webtests_from_logs/results/20211112_201954_soap_classic/test_set_2_exceptions/test_5_throw_error_1.ht...
- 08:01 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- In #8308, it was discovered that errors related to the database are handled differently when a CATCH block is present...
06/05/2024
- 03:10 PM Bug #8799: ON ERROR UNDO, THROW problems leading to infinite loops
- For this test:...
- 09:09 AM Feature #6417: cleanup some known items in appserver support
- Marian may just be referencing your comment from #6417-160 where you said "I'm not testing OE.".
- 08:51 AM Feature #6417: cleanup some known items in appserver support
- Marian Edu wrote:
> I still don't understand how do you plan to fix those tests without testing against a real Progr... - 08:48 AM Feature #6417: cleanup some known items in appserver support
- Greg Shah wrote:
> Marian: Can you please list them here so that Galya knows not to touch those without discussing... - 08:45 AM Feature #6417: cleanup some known items in appserver support
- Galya B wrote:
> Marian, the work on the tests seems disjointed. I'm trying to help the team coordinate their versio... - 08:42 AM Feature #6417: cleanup some known items in appserver support
- > > Galya: The failures you mention in #6417-162 are from the harness, probably something written by Constantin. The...
- 08:14 AM Feature #6417: cleanup some known items in appserver support
- Greg Shah wrote:
> Galya: The failures you mention in #6417-162 are from the harness, probably something written by ... - 08:06 AM Feature #6417: cleanup some known items in appserver support
- Galya: The failures you mention in #6417-162 are from the harness, probably something written by Constantin. These w...
- 08:05 AM Feature #6417: cleanup some known items in appserver support
- Marian, I believe acorn.ro is familiar not only with the @*.log@ files, but also with the SoapUI tests:...
- 07:57 AM Feature #6417: cleanup some known items in appserver support
- Marian, let me help you understand what I'm working on here:
Greg Shah wrote:
> These are items that can be found... - 07:53 AM Feature #6417: cleanup some known items in appserver support
- Marian, the work on the tests seems disjointed. I'm trying to help the team coordinate their versions to achieve a st...
- 07:30 AM Feature #6417: cleanup some known items in appserver support
- Galya B wrote:
> Well said. The asserts in the SoapUI tests indeed match those from the Progress runs, i.e. are fa... - 07:02 AM Feature #6417: cleanup some known items in appserver support
- Marian Edu wrote:
> Galya B wrote:
> > The SoapUI tests in @testcases/appsrv/soap/test/web/fwd-soapui-project.xml@ ... - 06:44 AM Feature #6417: cleanup some known items in appserver support
- Greg Shah wrote:
> > Greg please let me know if we should move those to ABLUnit as well.
>
> Yes
>
> > Not sur... - 06:42 AM Feature #6417: cleanup some known items in appserver support
- Galya B wrote:
> The SoapUI tests in @testcases/appsrv/soap/test/web/fwd-soapui-project.xml@ are based on the OE res... - 06:28 AM Feature #6417: cleanup some known items in appserver support
- > Greg please let me know if we should move those to ABLUnit as well.
Yes
> Not sure if FWD supports this (RPC,... - 06:26 AM Feature #6417: cleanup some known items in appserver support
- > > > I find it very weird that so many tests were failing in OE, but not fixed,
> >
> > Please be more specific ... - 05:57 AM Feature #6417: cleanup some known items in appserver support
- The SoapUI tests in @testcases/appsrv/soap/test/web/fwd-soapui-project.xml@ are based on the OE results in @testcases...
- 05:18 AM Feature #6417: cleanup some known items in appserver support
- Galya B wrote:
> I'm not testing OE.
Maybe we've got confused by your previous statement then... "I find it very... - 12:43 AM Feature #6417: cleanup some known items in appserver support
- Greg Shah wrote:
> > I find it very weird that so many tests were failing in OE, but not fixed,
>
> Please be mo...
06/04/2024
- 04:54 PM Feature #6417: cleanup some known items in appserver support
- > I find it very weird that so many tests were failing in OE, but not fixed,
Please be more specific about this. ... - 09:39 AM Feature #4347: add runtime support for STOP-AFTER block option
- We don't want a timer thread to exist if there is no @STOP-AFTER@ active.
- 08:51 AM Feature #4347: add runtime support for STOP-AFTER block option
- Committed on 4347a, revision 15208.
- 08:14 AM Feature #4347: add runtime support for STOP-AFTER block option
- Constantin Asofiei wrote:
> * StopAfterTimer
> ** in the constructor, the @if (timer == null)@ is not needed - you ...
06/03/2024
- 08:12 AM Feature #6417: cleanup some known items in appserver support
- I find it very weird that so many tests were failing in OE, but not fixed, instead directly ported to testcases and s...
- 03:13 AM Feature #4347: add runtime support for STOP-AFTER block option
- Review for 4347a rev 15206:
* StandardServer
** only change is a 'bad import', revert this file to rev 15203.
* Bl...
Also available in: Atom