Bugfest. Inventory. In transit .CSV report fails

Description

Overview: When generating an In transit .CSV report several error messages are thrown, and the report is never generated. Seen in Bugfest lotus.

Steps to reproduce:

  1. Login to Bugfest Lotus, as user f

  2. Go to Inventory

  3. Any item being checked out

  4. Check in 2 -3 items

  5. Go Inventory, in the Actions menu, then select In transit items report (.CSV)

Expected result:
Should get an CSV file listing items In transit

Actual result:
Get at first green success toast

Then about 30 seconds later, then getting an error message

More information:
Can not be reproduced in FOLIO Snapshot.

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Stephanie Buck May 10, 2022 at 1:00 PM

, we are unable to fix this bug without major changes in reports. The performance was improved recently but there will continue to be issues with large datasets until a larger conversation around reports is had. We'd like to close this ticket as won't do. 

Sergiy Bichurin May 4, 2022 at 7:43 AM

In terms of the error, there was an investigation fulfilled. The error appears approximately in 30 seconds after the report generation is triggered at bugfest lotus host. Body of the error is:

 

 

Special performance environment was used with db equal to bugfest kiwi 10.2021, mod-circulation, mod-circulation-storage, mod-inventory-storage versions close to bugfest lotus ones. Approximate quantity of items in transit – 31 000 records.

With the system it is possible to reproduce the error but time to time the report is generated. Here is attached the screens of successful calls via ui and postmen. For the items quantity, the report generation takes about one minute. It confirms that necessary modules work fine.

Body error for UI call is:

Taking into consideration above, the error could appear because of hosts proxy client work which is set to timeout period about 20-30 seconds which is less then needed to proceed big data volume.

Charlotte Whitt April 1, 2022 at 4:31 PM

I put it back in Draft while I don't know what would be the appropriate limitation, or the decision is to do significant development as needed to change how this in-app report is implemented

Stephanie Buck March 30, 2022 at 4:18 PM

Thank you, . Is there a reason this is still in Draft?

Charlotte Whitt March 30, 2022 at 4:07 PM

- in a conversation with and - then they point this ticket to Vega:

Charlotte Whitt:
@marcjohnson - in your research of this, did you come up with a solution for how to solve it? And if this is something Prokopvych or more likely Vega, then should work on?

Marc Johnson
> in your research of this
I have only done a very minimal investigation. That
> did you come up with a solution for how to solve it?
As I said in my comment, any interim solution is likely about changing the data in the BugFest environment.
Otherwise, significant development is likely needed to change how this in-app report is implemented. (There are generally challenges with scaling in-app reports that need to aggregate data)
> And if this is something Prokopvych or more likely Vega, then should work on?
I don’t know. Vega now own this area. And I think @mkuklis comment suggested that they also recently did work to it.

Michal Kuklis: @charlotte that issue should not be taken by prokopovych. Also based on some recent changes in that area it looks like the fix will have to happen on the backend

Won't Do

Assignee

Sergiy Bichurin

Reporter

Priority

Development Team

Vega

Release

Morning Glory (R2 2022)

RCA Group

Not a bug

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created March 28, 2022 at 11:58 AM
Updated June 15, 2022 at 1:49 PM
Resolved May 27, 2022 at 1:33 PM
Loading...