April 2023 - Koha-bugs - lists.koha-community.org

[Bug 31336] New: In-progress background jobs give incorrect progress message
by bugzilla-daemon＠bugs.koha-community.org 18 Oct '23

18 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31336 Bug ID: 31336 Summary: In-progress background jobs give incorrect progress message Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 31245 If one loads the background job details page (background_jobs.pl) for a job that has started but not yet completed, Koha shows a message of "No items modified." We should give an accurate message along the lines of "This job is still in progress." A completed job lists all of the modified items/bibs/whatever. I'm ambivalent about whether or not we need to list the already-modified records when loading this page for an incomplete job. To recreate: 1 - write a report, SELECT itemnumber FROM items. With the default dev data, that's 961 items. 2 - use your report to send all of those to batch mod. The page will take a while to load 3 - while your batch mod page is loading, open background_jobs.pl in another tab and have it ready to go 4 - modify something in all 961 records -- add a public note or something -- once you submit this job it should take about 45 seconds to complete 5 - BEFORE THE JOB IS DONE - reload background_jobs.pl, see your job is listed and shows status=started. click to the details view for your job, see it shows a message of "No items modified." Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31245 [Bug 31245] Job detail view for batch mod explode if job not started -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 31580] New: Koha::BackgroundJob->finish should consider the 'failed' case
by bugzilla-daemon＠bugs.koha-community.org 18 Oct '23

18 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31580 Bug ID: 31580 Summary: Koha::BackgroundJob->finish should consider the 'failed' case Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org See bug 27421, which introduces it. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 31363] New: Background jobs table should include columns for name and branch of initiating staff user
by bugzilla-daemon＠bugs.koha-community.org 18 Oct '23

18 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31363 Bug ID: 31363 Summary: Background jobs table should include columns for name and branch of initiating staff user Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: jrobb(a)sekls.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com There is no clear indicator within the background jobs table of who initiated the job. This is problematic in our consortium setting as many different people are triggering jobs in a given day and if we want to check on a specific job, we either need to know the exact time the job was started or the exact number of items that were touched. It would be handy if the table included a column for the initiating staff user's name and a column for their branch to make it easier to distinguish who did what and filter down the table. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 27258] New: Rename BackgroundJobs => Tasks
by bugzilla-daemon＠bugs.koha-community.org 18 Oct '23

18 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27258 Bug ID: 27258 Summary: Rename BackgroundJobs => Tasks Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org We should make the change now it is fresh. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 33334] New: koha-worker.service need update for background job queues
by bugzilla-daemon＠bugs.koha-community.org 18 Oct '23

18 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33334 Bug ID: 33334 Summary: koha-worker.service need update for background job queues Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Bug 27783 added background job queues This need to be added to koha-worker.service which is currently only running default queue -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 32481] New: Rabbit times out when too many jobs are queued and the response takes too long
by bugzilla-daemon＠bugs.koha-community.org 18 Oct '23

18 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481 Bug ID: 32481 Summary: Rabbit times out when too many jobs are queued and the response takes too long Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org We saw this happen several times - a library would queue up 6 batch modifications that would take roughly 6 minutes each. The jobs would process normally, until the 30 minute configured timeout would hit - then the remaining job would fail, and rabbit would disconnect and not reconnect, and jobs would pile up It seems that koha receives all of the jobs immediately, but only acknowledges when complete - so the final job was waiting over 30 minutes for acknowledgement and this caused issues -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 52

[Bug 33028] New: The decimal separator 'comma' and its consequences on the calculation of fines (crons)
by bugzilla-daemon＠bugs.koha-community.org 18 Oct '23

18 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33028 Bug ID: 33028 Summary: The decimal separator 'comma' and its consequences on the calculation of fines (crons) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: thibaud.guillot(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Hello @ll, I hesitate between 'fines and fee' section or 'cron' so don't move it if you think that's better in cron section.. When currency format is set on FR commas are decimals separators but when cron like fines.pl try to calculate fines it's fails due to this format. I know there is a lot of discussion around this behavior and decimal separator by 'countries'.. like bug 12310 and bug 21507 but I would like to propose this patch to solve at least the behavior on the fine calculations related to cronjob 'fines.pl' which will use some circulation rules and therefore their formatting is important if you want to make calculations with -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 129

[Bug 26558] New: Guarantor information is lost when an error occurs during new account creation
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '23

17 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26558 Bug ID: 26558 Summary: Guarantor information is lost when an error occurs during new account creation Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: george(a)nekls.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To reproduce: 1. Create a new account but cause an error that will keep the account from saving (enter the wrong age for a category or give the patron a username that's already being used) 2. Search for and select a guarantor 3. Try to save the account and wait for the "The following fields are wrong. Please fix them." message 4. Note that the guarantor information is gone and you need to search for and select the guarantor again -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 33074] New: ReservesControlBranch not taken into account in opac-reserve.pl
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '23

17 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33074 Bug ID: 33074 Summary: ReservesControlBranch not taken into account in opac-reserve.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Hold requests Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In opac-reserve.pl there is this line: my $rule = GetBranchItemRule( $patron->branchcode, $type ); $patron->branchcode should be replaced by the result of GetReservesControlBranch Test plan: 1. Set system preferences: - Disable OPACAllowUserToChooseBranch - Set ReservesControlBranch to "item's home library" - Enable UseBranchTransferLimits - Set BranchTransferLimitsType to "item type" - Enable canreservefromotherbranches - Disable IndependantBranches 2. Create two libraries: ITEM_LIB and PATRON_LIB 3. Set circulation rules: - Remove all circulation rules (DELETE FROM circulation_rules) - Set a default rule that allow some holds and with "OPAC item level holds" = "force". Allow "on shelf" holds for easier testing. - In the rules for ITEM_LIB, under "Default checkout, hold and return policy", - set "Hold policy" to "From any library" - set "Hold pickup library match" to "item's home library" - In the rules for PATRON_LIB, under "Default checkout, hold and return policy", - set "Hold policy" to "From any library", - set "Hold pickup library match" to "any library" 4. In "Library transfer limits" disable all transfers from ITEM_LIB to PATRON_LIB for an item type (let's say "BOOK") 5. Create a biblio with an item: - item type must be the same as in previous step ("BOOK") - home branch and holding branch must be ITEM_LIB 6. Create a patron at PATRON_LIB, give it a password so it can log in. 7. Go to OPAC, and login with this patron 8. Try to place a hold for the new item. You should be allowed to place a hold, but when doing it, no holds will be created. -- You are receiving this mail because: You are watching all bug changes.

1 24

[Bug 33395] New: Patron search results shows only overdues if patron has overdues
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '23

17 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33395 Bug ID: 33395 Summary: Patron search results shows only overdues if patron has overdues Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When you search for patrons, in the results table, there is a Checkouts column. If the patron has no checkouts, it shows 0 / 0 (0 overdues / 0 total checkouts). If the patron has checkouts but no overdues, it shows, for example, 0 / 1 (0 overdues / 1 total checkout). If the patron has only overdues, it shows, for example, only 1 in red (1 overdue ?? total checkouts?). If the patron has checkouts and overdues, it shows, for example, only 1 in red also (1 overdue ?? total checkouts?) It's like if there are overdues, the number of checkouts disappear. To replicate: 1. Make sure SpecifyDueDate is enabled 2. Have 4 patrons (I used 4 patrons with B last names to see them all in one go) 3. Checkout items as follows - Checkout 1 item normally to Patron A - Checkout 1 item to Patron B, specifying a due date in the past - Checkout 1 item normally and 1 item with a past due date to Patron C - Nothing to Patron D 4. Go to Patrons and search for the patrons, making sure there are more than one results --> In the results table, the Checkouts column is like this Patron A: 0 / 1 Patron B: 1 (red) Patron C: 1 (red) Patron D: 0 / 0 For Patron B, it should be (I think?) 1 / 1 For Patron C, it should be (I think?) 1 / 2 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19