[RANCHER-74] Changes to specific file on mod-circulation not showing on scratch environment. Created: 17/Nov/21  Updated: 18/Nov/21  Resolved: 18/Nov/21

Status: Closed
Project: rancher
Components: None
Affects versions: None
Fix versions: None

Type: Bug Priority: TBD
Reporter: Kyle Felker Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
blocks CIRC-1112 Recalls not being honored when there ... Closed
Sprint:
Development Team: FOLIO DevOps

 Description   

Overview:

It looks like no changes made to the ChangeDueDateResource.java file in mod-circulation are reflected when the module is built locally and upgraded using Rancher. The problem appears to be ONLY with this specific file-changes made to other parts of the code do seem to be present. This is for the Prokopovych scratch environment: https://core-functional.ci.folio.org/

Steps to Reproduce:

1. Clone mod-circulation and open the file noted above.
2. insert a logging statement anywhere in the processChangeDueDate() function.
3. Save your changes, and then build and deploy to scratch as outlined in this document: https://folio-org.atlassian.net/wiki/display/FOLIJET/Back-end+module+development+using+the+scratch+environment+and+Rancher
4. Go to scratch (https://core-functional.ci.folio.org/) and check out an item to a patron. The exact item and patron should not matter. Make a note of the patron barcode or UUID.
5. Go to Users and look up the patron. Click on their open loans and find the item you checked out to them. Click on it.
6. Initiate a change due date for the item. For this issue, what you change the due date to should not matter.
7. Once the due date change is complete, pull the logs for mod-circulation from scratch using rancher. Description of how to do this is in the documentation linked above.
8. Search the logfile for your logging statement.

Expected Results:

Your log output should be present.

Actual Results:

It is not present.

Additional Information:

No changes I make to this part of the code seem to affect its behavior at all. I have uploaded a version of the module with code in the noted function that should cause it to fail when executed. It continued to execute just as it had before I loaded the changes.

URL:
Charlotte WhittKyle FelkerMarc Johnson



 Comments   
Comment by Marc Johnson [ 17/Nov/21 ]

Jakub Skoczen Who is the right person to help Kyle Felker out with this issue?

Comment by Jakub Skoczen [ 18/Nov/21 ]

Aleh Litasau Hleb Surnovich Aliaksei Luhavy can one of you guys please take a look at this problem?

Comment by Marc Johnson [ 18/Nov/21 ]

Jakub Skoczen Thank you for responding quickly to my request.

I think Kyle Felker might have done more testing yesterday and figured out what was going on.

Hleb Surnovich Aliaksei Luhavy I suggest waiting to work on this until Kyle Felker is around and can comment further.

Comment by Kyle Felker [ 18/Nov/21 ]

Jakub SkoczenHleb SurnovichAliaksei Luhavy

We've worked out the source of this problem-the Ui does not actually use the code in this file for change due date operations, which is why lit looks like the code is dead-it just never gets triggered at all. So this is not, in fact, an issue with the scratch environment. I'll close this.

Generated at Thu Feb 08 23:27:26 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.