Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
When canceling a query is the variable i2b2.CRC.ctrlr.deleteCurrentQuery is null than checking on a i2b2.CRC.ctrlr.deleteCurrentQuery.QM which result in a null pointer. Should check to see that i2b2.CRC.ctrlr.deleteCurrentQuery is not null first.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Status | New [ 10000 ] | Open [ 1 ] |
| Assignee | Mike Mendis [ mem61 ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Assignee | Mike Mendis [ mem61 ] | Janice Donahoe [ jmd86 ] |
| Status | In Progress [ 3 ] | Ready to Test [ 10001 ] |
| Fix Version/s | 1.7.09c [ 10800 ] |
| Status | Ready to Test [ 10001 ] | Testing [ 10002 ] |
| Summary | webclient failed to cancel query after informing obfuscated user he is locked out | Webclient failed to cancel query after informing obfuscated user he is locked out |
| Description | RUnning a query as a locked out user, they cant cancel it. |
When an obfuscated exceeds the allowed number of times they can repeat a query they will be "locked out" from running another query. When they receive the message telling them they have been locked out, the system should cancel the query they are trying to run. However, when they click on OK the Web Client continues to run the query.
The resolution is to have the Web Client "cancel" the query when the lockout message is received from the CRC. GIT COMMIT 3ff17f73549eff306ead0fafdfb780f09ef018f0 |
| Resolution | Fixed [ 1 ] | |
| Status | Testing [ 10002 ] | Resolved [ 5 ] |
| Summary | Webclient failed to cancel query after informing obfuscated user he is locked out | Web Client doesn't cancel query when user receives lockout message |
| Resolution | Fixed [ 1 ] | |
| Status | Resolved [ 5 ] | Reopened [ 4 ] |
| Status | Reopened [ 4 ] | In Progress [ 3 ] |
| Assignee | Janice Donahoe [ jmd86 ] | Mike Mendis [ mem61 ] |
| Attachment | obfscUser-lockOut-qryCancelled-2.png [ 10932 ] |
| Attachment | obfscUser-lockOut-qryError.png [ 10933 ] |
| Link | This issue clone of WEBCLIENT-224 [ WEBCLIENT-224 ] |
| Link | This issue clone of WEBCLIENT-224 [ WEBCLIENT-224 ] |
| Description |
When an obfuscated exceeds the allowed number of times they can repeat a query they will be "locked out" from running another query. When they receive the message telling them they have been locked out, the system should cancel the query they are trying to run. However, when they click on OK the Web Client continues to run the query.
The resolution is to have the Web Client "cancel" the query when the lockout message is received from the CRC. GIT COMMIT 3ff17f73549eff306ead0fafdfb780f09ef018f0 |
When canceling a query is the variable i2b2.CRC.ctrlr.deleteCurrentQuery is null than checking on a i2b2.CRC.ctrlr.deleteCurrentQuery.QM which result in a null pointer. Should check to see that i2b2.CRC.ctrlr.deleteCurrentQuery is not null first. |
| Summary | Web Client doesn't cancel query when user receives lockout message | Web Client possible null pointer |
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Resolved [ 5 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |
| Attachment | dtconst_ptst.PNG [ 11031 ] |
| Attachment | dtconst_ptst.PNG [ 11031 ] |