June 2024 - Koha-bugs - lists.koha-community.org

[Bug 30654] New: Even with RabbitMQ enabled, we should poll the database for jobs at worker startup
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '24

01 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30654 Bug ID: 30654 Summary: Even with RabbitMQ enabled, we should poll the database for jobs at worker startup 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 27344 Our worker currently starts up and immediately tries to listen for jobs being passed via STOMP. However, if rabbitMQ wasn't running when the tasks were enqueue, then the worker will never know about them. We should work through the outstanding queue before listening for new jobs. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27344 [Bug 27344] Implement Elastic's update_index_background using Koha::BackgroundJob -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 29

[Bug 37164] New: worker-output.log file grows to incredible sizes and causing the server to crash
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '24

01 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37164 Bug ID: 37164 Summary: worker-output.log file grows to incredible sizes and causing the server to crash Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: Linux Status: NEW Severity: critical Priority: P5 - low Component: bugs.koha-community.org Assignee: koha-bugs(a)lists.koha-community.org Reporter: yuriy.kotsyuk(a)oa.edu.ua QA Contact: testopia(a)bugs.koha-community.org Created attachment 168002 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=168002&action=e… scrinchot worker-output.log.2 (fragment) The worker-output.log file grows to incredible sizes. While checking one of the files (5 GB), a warning entry was found and this entry was duplicated a huge number of times over a short period of time. The first two records are as follows: DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: DBI connect('database=koha_library;host=localhost;port=3306','koha_library',...) failed: Lost connection to MySQL server at 'reading initial communication packet', system error: 104 at /usr/share/koha/lib/Koha/Database.pm line 91. at /usr/share/koha/lib/Koha/Objects.pm line 312 DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: DBI connect('database=koha_library;host=localhost;port=3306','koha_library',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) at /usr/share/koha/lib/Koha/Database.pm line 91. at /usr/share/koha/lib/Koha/Objects.pm line 312 Line number three indicates the date and time 2024/05/20 17:35:52 In general, the record looks like this: [2024/05/20 17:35:52] [WARN] Frame not processed - malformed JSON string, neither tag, array, object, number, string or atom, at character offset 0 (before "You must log in usin...") at /usr/share/koha/bin/workers/background_jobs_worker.pl line 120. main::catch {...} /usr/share/koha/bin/workers/background_jobs_worker.pl (122) This entry occurs 985 times in a row. Recording in the next second: [2024/05/20 17:35:53] [WARN] Frame not processed - malformed JSON string, neither tag, array, object, number, string or atom, at character offset 0 (before "You must log in usin...") at /usr/share/koha/bin/workers/background_jobs_worker.pl line 120. main::catch {...} /usr/share/koha/bin/workers/background_jobs_worker.pl (122) occurs 1483 times in a row. Recording in the next second: [2024/05/20 17:35:54] [WARN] Frame not processed - malformed JSON string, neither tag, array, object, number, string or atom, at character offset 0 (before "You must log in usin...") at /usr/share/koha/bin/workers/background_jobs_worker.pl line 120. main::catch {...} /usr/share/koha/bin/workers/background_jobs_worker.pl (122) occurs 6952 times A total of 16,709,173 messages of the same type were generated from 2024/05/20 17:35:52 to 2024/05/21 10:59:08 After this series of messages, other messages have already appeared: Cannot connect to the message broker, the jobs will be processed anyway (Failed to connect: Error connecting to localhost:61613: Connection refused at /usr/share/perl5/Net/Stomp.pm line 27.; giving up at /usr/share/perl5/Net/Stomp.pm line 27. ) at /usr/share/koha/bin/workers/background_jobs_worker.pl line 92. Cannot connect to the message broker, the jobs will be processed anyway (Failed to connect: Error connecting to localhost:61613: Connection refused at /usr/share/perl5/Net/Stomp.pm line 27.; giving up at /usr/share/perl5/Net/Stomp.pm line 27. ) at /usr/share/koha/bin/workers/background_jobs_worker.pl line 92. Today, worker-output.log was 108 GB in size and took up all free disk space, causing the server to crash. Perhaps someone had the same problems and was able to overcome them -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 35299] New: Allow for items with specific not for loan values to appear in the holds queue
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '24

31 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35299 Bug ID: 35299 Summary: Allow for items with specific not for loan values to appear in the holds queue Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: clemens.tubach(a)kit.edu, gmcharlt(a)gmail.com, michaela.sieber(a)kit.edu We’d like to be able to specify a list of not for loan values that will be considered eligible to fill holds and appear in the holds queue and ideally the pending holds list as well. These would usually be negative not for loan values, that can be placed on hold. It should be possible to still exempt some status, like -1 = on order. Use Case: In libraries with closed stacks there are often items that are not for loan, but can be requested for use in a reading room. Staff will then get the items and fill the holds, but they won't be checked out on self checks etc. An on-site checkout might be forced. (see Library of Congress: https://ask.loc.gov/law/faq/300644) In order for this process to work the library needs the information about the requested items in order to be able to pull the items in the closed stacks. We have tested a change in Holdsqueue.pm that works, but should be made properly configurable: https://git.koha-community.org/Koha-community/Koha/src/branch/master/C4/Hol… Change: $items_query .= " WHERE items.notforloan = 0 To: $items_query .= " WHERE items.notforloan in (-2, -3, 09) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 36717] New: Merge "Patrons (custom slip)" and "Patrons (custom message)" in Notices
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '24

30 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36717 Bug ID: 36717 Summary: Merge "Patrons (custom slip)" and "Patrons (custom message)" in Notices Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org With the introduction of custom email messages in Bug 29393, we discussed (https://chat.koha-community.org/koha-community/pl/ixoy58im47dhpr4gmwtn9sdbjw) the opportunity to merge the "Patrons (custom slip)" notice type introduced in Bug 32986 and the new "Patrons (custom message)" notice type. The "custom slips" would be notices with the print message transport type, and the "custom messages" (email messages) would be notices with the email message transport type. To get there: 1. Go to Tools > Notices and slips 2. Click New notice --> Notice there is a category "Patrons (custom slip)" and (after bug 29393) "Patrons (custom message)" Create and use a custom slip 3. Click "Patrons (custom slip)" 4. Enter a code and a name (e.g. TESTSLIP, Test slip) 5. Click the "Print" tab 6. Enter content in the "Message subject" and "Message body" fields 7. Click "Save" 8. Go to a patron's account 9. Click "Print" --> There should be an option to "Print test slip" (or whatever name you gave it) Create and use a custom message 10. Go back to Tools > Notices and slips > New notice 11. Click "Patrons (custom message)" 12. Enter a code and a name (e.g. TESTMESSAGE, Test message) 13. Click the "Email" tab 14. Enter content in the "Message subject" and "Message body" fields 15. Click "Save" 16. Go to a patron's account 17. Make sure the patron has an email address 18. Click "Add message" 19. In "Add message for" choose Email --> In "Patron notice" there should be "Test message" (or whatever name you gave it) The proposition was to merge the two notice types and only show the ones with the "Print" message transport type filled in the "Print" menu, and only show the ones with the "Email" message transport type filled in the "Add message" menu. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 35189] New: Itemtypes SVG icons should be limited in height/width
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '24

30 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35189 Bug ID: 35189 Summary: Itemtypes SVG icons should be limited in height/width Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: pablo.bianchi(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 158067 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=158067&action=e… Screenshot Steps to reproduce the issue: 1. On Staff interface, on Administration > Item types, modify any item 2. Choose an SVG image as a remote image for an Item type, for eg https://raw.githubusercontent.com/FortAwesome/Font-Awesome/afecf2af5d897b76… Save changes. When listed on itemtypes.pl the icon is not too big, but if you edit again the itemtype (using above SVG, more than 1200px width). This also impact at some degree on Advanced search (staff and OPAC, search.pl, opac-search.pl). -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 37170] New: Elasticsearch is functioning correctly with indices being rebuilt and searchable, but the "About Koha" page incorrectly shows Elasticsearch as "not running."
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '24

30 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37170 Bug ID: 37170 Summary: Elasticsearch is functioning correctly with indices being rebuilt and searchable, but the "About Koha" page incorrectly shows Elasticsearch as "not running." Change sponsored?: --- Product: Koha Version: 24.05 Hardware: Macintosh OS: Other Status: NEW Severity: critical Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: aungmo(a)gmail.com I am experiencing an issue with the Koha "About Koha" page. Although Elasticsearch is functioning correctly (indices are being rebuilt, and records are searchable), the "About Koha" page displays Elasticsearch status as "not running." Steps to Reproduce: Set up Koha with Elasticsearch as the search engine. Successfully rebuild Elasticsearch indices using the command: docker exec -it koha koha-elasticsearch --rebuild --verbose -d mylibrary [436] Checking state of biblios index [436] Dropping and recreating biblios index [436] Checking state of authorities index [436] Dropping and recreating authorities index [436] Indexing biblios [436] Committing final records... [436] Total 1 records indexed [436] Indexing authorities [436] Committing final records... [436] Total 1 records indexed Perform searches in both OPAC and Staff interfaces, confirming that records are searchable. Navigate to the "About Koha" page. Expected Behavior: The "About Koha" page should display the Elasticsearch version, number of nodes, and status as running. Actual Behavior: The "About Koha" page displays: Elasticsearch: Version: | Nodes: | Status: not running System Information Koha version: 24.05.01.000 OS version: Linux 96b981d24116 6.6.31-linuxkit (running on macOS) Perl version: 5.036000 MySQL version: 10.6.18-MariaDB-ubu2004 Apache version: 2.4.59 (Debian) Elasticsearch version: 8.13.0 (single-node cluster) Deployment method: Docker Base image: debian Elasticsearch Configuration in koha-conf.xml: <elasticsearch> <server>elasticsearch:9200</server>  <index_name>koha_mylibrary</index_name>   <cxn_pool>Static</cxn_pool>   </elasticsearch> docker exec -it koha curl -X GET "http://elasticsearch:9200/_cluster/health?pretty" { "cluster_name" : "docker-cluster", "status" : "yellow", "timed_out" : false, "number_of_nodes" : 1, "number_of_data_nodes" : 1, "active_primary_shards" : 10, "active_shards" : 10, "relocating_shards" : 0, "initializing_shards" : 0, "unassigned_shards" : 10, "delayed_unassigned_shards" : 0, "number_of_pending_tasks" : 0, "number_of_in_flight_fetch" : 0, "task_max_waiting_in_queue_millis" : 0, "active_shards_percent_as_number" : 50.0 } -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 35155] New: MARCOverlayRules syspref not in manual
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '24

30 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35155 Bug ID: 35155 Summary: MARCOverlayRules syspref not in manual Change sponsored?: --- Product: Koha Version: unspecified Hardware: All URL: https://gitlab.com/gnucifer/koha-manual/-/commit/593c5 da008dbc4b074cac9dee167cce9a6dfc250#c5e2c75dc923f21c5b 95185b2f350df00fec661f OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: hebah(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 14957 MARCOverlayRules system pref and functionality introduced in 21.11 never made it into Koha manual. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14957 [Bug 14957] Write protecting MARC fields based on source of import -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 25610] New: Inconsistent display of 856$3 in OPAC between brief result and full record
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '24

30 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25610 Bug ID: 25610 Summary: Inconsistent display of 856$3 in OPAC between brief result and full record Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Currently, if a record has an 856$3, this will show in the brief results and not in the full results. It should be consistent between the two views. And what is the opinion that the $3 should show or should not? For decisions like these, it would be nice for the library to decide what is displayed and allow for changes to be made through the staff client vs XSLT stylesheets. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 36194] New: CSRF - svc
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '24

30 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36194 Bug ID: 36194 Summary: CSRF - svc Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical 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 This bug is for tracking follow-ups missed in the initial review. Please see the "svc" section on the framapad here: https://annuel.framapad.org/p/koha_34478_remaining Additional entries can be added there, and should be crossed out when completed Patches should be attached here This bug can be closed when that section of the pad is empty see bug 36084 commits for new method using fetch/api-client.js is retrieved (and adjusted) from the Vue work wiki/coding guideline to follow -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 36956] New: ERM eUsage reports : only the first 20 data providers are listed when creating a new report
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '24

30 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36956 Bug ID: 36956 Summary: ERM eUsage reports : only the first 20 data providers are listed when creating a new report Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: michaela.sieber(a)kit.edu CC: jonathan.druart(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com to reproduce: 1.) Go to ERM module and make sure you have more than 21 data providers stored in your database. 2.) Go to eUsage / reports and create new report (cgi-bin/koha/erm/eusage/reports) 3.) Check that only the first 20 data providers are displayed in the drop down -- You are receiving this mail because: You are watching all bug changes.

1 20