Bugzilla – Full Text Bug Listing
| Summary: | need support to handle asynchronous events in model and user interface | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Ashish Patel <ashishp> |
| Component: | TPTP | Assignee: | Marius Slavescu <slavescu> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P2 | CC: | amehrega, christophe.telep, guru.nagarajan, popescu, rdanek, sluiman |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | closed471 | ||
| Bug Depends on: | |||
| Bug Blocks: | 148491 | ||
|
Description
Ashish Patel
119991 refers to a work around being checked in. Can you summarize the symptoms as they stand now? Tickets are used in most events to address arriving out of sequence and we need to understand if the tickets are wrong/missing or if they are being procesed wrong. Complete assync support will still not address all negative time problems. Clock skews among othe rthings can cause this to occur. So understanding the exact extend of the problem is important. The tickets looks fine and the sequence diagram shows what Ashish and Robert were expecting, althogh the way we compute the base and cumultative times is not appropiate for async calls (like in their example). We will discuss next week if the workarround for bug 119991 is a good thing and see if the invocation context (used to link distributed invocations) should be used to link asynchronus calls or collect transactions activity. By using bytecode instumentation (especially for ARM events) we can end up with traces that may not be correctly/menigfull represented in the current UI (Statistical or Interaction views), so we need to discuss that side of the problem also. Raising this enhancement as help wanted for 4.3 with P1 priority. Assigning to Ruth, as per converation with Valentina that Marius is away. Having this capability will allow the ARM work in TPTP to function properly when there are asynchronous events taking place. Currrently, the models only interpret events as being synchronous [ or on the flip side: there isn't a way for an event to indicate if it is async in nature in the trace model ]. The ARM work is focusing on developing instrumentation for webservices, and in order to properly model the webservices in user interfaces (such as views) the events themselves need to be marked appropriately when they are observed. Webservices is just one example of asynchronous calls, however, its probably one of the easier cases to test. Not in 4.3 plan due to resource constraint. Ruth, This is currently not in plan, but has there been any progress on the evaluation/investigation of this req. Raising as a blocker. This item will be raised in the PMC this week. Ashish, "blocker" is only for defects, not enhancements. This enhancement wasn't added to the 4.3 plan because no one stepped up to staff this work. If it's that important for your product, perhaps your product could provide the person to do the work? I changed this to blocker as per Guru's instructions. I will let Harm, you and Guru decide how to handle. This item does block work in consuming products and the TPTP ARM component from being delivered. Hi Ashish, I understand that you've reached an impasse in the TPTP ARM etc. but you'll be more likely to get this enhancement into a TPTP release if you follow the TPTP process. The Planning Group & PMC have four stages that go into planning a release of TPTP: requirements gathering, architectural analysis, community review of the draft plan, and then the final plan is published. For exceptions to that process, please ask the Requirements Group lead, Christophe Telep, for instructions on how to proceed. Please change this back from "blocker" to "enhancement" to reflect that this is an enhancement, not a bug that should block TPTP 4.2.1 from GA-ing. The TPTP definition of severity and description of bugzilla fields can be found here: http://www.eclipse.org/tptp/home/documents/process/development/bugzilla.html If you scroll down to the end of that page you'll see, "The bugzilla Reporter (a.k.a. "Originator" or "Submitter"), when opening an enhancement, 1. Sets the severity level of the bugzilla (Severity = "enhancement"). ..." You should raise this issue in the next PMC meeting as you already plan to do. If you are concerned about how the TPTP Planning Group & PMC create a plan, such as not including enhancements that you believe should be included, that too can be raised in a PMC meeting. Incidentally, unless something has changed, you can attend the PMC meeting too to speak for this enhancement and discuss your concerns. Those meetings used to be open to anyone who requested the call-in number. I'll leave a PMC/PG member on the cc list to correct me if the meeting is open now to only PMC & PG members. --Ruth. As per Ruth's instructions. We breifly discussed this enhancement at the PMC/PG Meeting today as the request of Guru. More comprehensive discussion is tabled for next week's PMC/PG F2F meeting in Portland. Please stay tuned. All TPTP meetings are open to anyone interested, just ask for meeting dial-in information via the project mailing lists. Also, note that any enahcement request that is acceptable architecturally/technically and comes with offer to implement is welcome. This request seem to fit that criteria. Reassigning due to Ruth's leave of absence. Moving untargetted enhancements to Future target. (In reply to comment #13) > Moving untargetted enhancements to Future target. > This really is not an enhancement. Event should be handled out of sequence at at one time they were, so this is a bug. The question is if the symptoms still exist, adn I suspect they due, because the default event handler and event overlay code seems to have been removed at some time. As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As such, TPTP is not delivering enhancements. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement is resolved as WONTFIX. For this enhancement to be considered, please re-open with an attached patch including the Description Document (see http://www.eclipse.org/tptp/home/documents/process/development/description_documents.html), code (see http://www.eclipse.org/tptp/home/documents/resources/TPTPDevGuide.htm), and test cases (see http://www.eclipse.org/tptp/home/documents/process/TPTP_Testing_Strategy.html). As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As such, TPTP is not delivering enhancements. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement is resolved as WONTFIX. For this enhancement to be considered, please re-open with an attached patch including the Description Document (see http://www.eclipse.org/tptp/home/documents/process/development/description_documents.html), code (see http://www.eclipse.org/tptp/home/documents/resources/TPTPDevGuide.htm), and test cases (see http://www.eclipse.org/tptp/home/documents/process/TPTP_Testing_Strategy.html). As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open. |