CDR Tickets

Issue Number 5185
Summary Error when adding to summary translation queue
Created 2023-01-13 15:25:01
Issue Type Task
Submitted By Osei-Poku, William (NIH/NCI) [C]
Assigned To Kline, Bob (NIH/NCI) [C]
Status Closed
Resolved 2023-01-13 17:35:17
Resolution Fixed
Path /home/bkline/backups/jira/ocecdr/issue.336346
Description

I ran into an error message at about 3:10pm today while trying to add a summary, CDR0000062972 to the translation queue. The following error was displayed without any indication that the summary was actually added to the queue (found out after opening another browser and navigating to the queue). Also, there was no email notification in this instance (even though the job was added)

Repro steps:

  1. Retrieve CDR0000062972 as read only

  2. Click on Translation Job icon on the summary toolbar (one with yellow lightening symbol)

  3. Click the button to attach any file

  4. Submit task

Unfortunately it doesn't happen all the time since I have been able to successfully add jobs to the queue without any problems but this is about the second time I have seen this error message in the last couple of days. 

Comment entered 2023-01-13 16:17:23 by Kline, Bob (NIH/NCI) [C]

I am confused as to why this ticket is tagged as a problem with XMetaL. It appears from your description that you're balking about behavior involving communication between your browser and the CDR server, not communication between XMetaL and the CDR server. Am I missing something? Did you leave something out of your description?

Comment entered 2023-01-13 16:46:57 by Osei-Poku, William (NIH/NCI) [C]

I am tagging all the issues I find while testing XMetal 17 on the DEV VM server with that tag. Should I be tagging them differently?

Comment entered 2023-01-13 17:25:25 by Kline, Bob (NIH/NCI) [C]

I think the relevant question to ask yourself in this case would be "would this CDR Admin script behave any differently if the browser were on my own desktop than on this other machine?" I mean, if you think of a schema change you want me to make for some future report while you're testing XMetaL 17 would you create the new ticket for that schema change as "[XMetaL] ...."?

Comment entered 2023-01-13 17:35:17 by Kline, Bob (NIH/NCI) [C]

There's a bug in the Python standard library documentation. I have filed a bug report, but haven't had any feedback yet (it would be astounding if they had responded this quickly), so my tentative fix is in the theory stage at this point, based on reverse engineering and analysis of the Python library code, so it might not be correct. Try again. In order to test the particular path which crashed, you'll need to use a plain text file (extension ".txt") for the attachment. And you don't have to be on the shared testing host for this exercise. You can just bring up the translation queue directly in the browser on your desktop.

https://github.com/NCIOCPL/cdr-lib/commit/036c7b5

Comment entered 2023-01-13 17:41:21 by Kline, Bob (NIH/NCI) [C]

I changed the title. Let's reserve the tag [XMetaL] for problems which actually happen in XMetaL. If XMetaL sends you to the wrong page (or to a non-existent page), that's a problem in our XMetaL macros, and the tag would be appropriate. If XMetaL (and the macros) send you exactly where it's supposed to send you, and a problem happens while you're interacting with that CDR Admin web page, that's completely beyond the control of XMetaL and the macros, and any ticket created for the problem should get some other tag (assuming it's going to have a tag at all).

Comment entered 2023-05-10 09:45:19 by Osei-Poku, William (NIH/NCI) [C]

Verified on QA.

Comment entered 2023-06-01 11:49:33 by Osei-Poku, William (NIH/NCI) [C]

Verified on PROD. Thanks!

Attachments
File Name Posted User
translation queue error.PNG 2023-01-13 15:22:35 Osei-Poku, William (NIH/NCI) [C]

Elapsed: 0:00:00.001170