October 2019 - Koha-bugs - lists.koha-community.org

[Bug 19523] New: Koha:: Cache changes not passed to all plack workers with in-memory caching.
by bugzilla-daemon＠bugs.koha-community.org 27 Jun '25

27 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19523 Bug ID: 19523 Summary: Koha::Cache changes not passed to all plack workers with in-memory caching. 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: olli-antti.kivilahti(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org REPRODUCE: - $KOHA_CONF shouldn't have any <memcached_* -definitions. This triggers in-memory cache usage. - plack workers is atleast 2 - Change some easily visible syspref, such as 'languages'. The syspref change applies only to the worker thread where the change was made. Other worker threads keep using the old syspref. - Observer that 50% of time the old syspref is used. Other times the new syspref is used. - Reduce plack workers to 1. Observe no issues with syspref change taking effect. Using memcached solves this problem. It is still useful to fix it for those who don't want to use memcached. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 23336] New: Add an API endpoint for issuing an item to a patron
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '25

26 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23336 Bug ID: 23336 Summary: Add an API endpoint for issuing an item to a patron Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST api Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com The Checkouts API route RFC (https://wiki.koha-community.org/wiki/Checkouts_endpoint_RFC) proposes a POST on /checkouts, which makes sense. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 107

[Bug 21670] New: t/db_dependent/Plugins.t is failing randomly on Jenkins (U18)
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '25

24 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21670 Bug ID: 21670 Summary: t/db_dependent/Plugins.t is failing randomly on Jenkins (U18) Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org On run #72, Koha_Master_U18 failed: koha_1 | Could not unlink /tmp/xRRc7ht/Koha/Plugin/Com/ByWaterSolutions/KitchenSink.pm.pm: No such file or directory at /kohadevbox/koha/Koha/Plugins/Handler.pm line 105. koha_1 | koha_1 | # Failed test 'Koha::Plugins::Handler::delete works correctly.' koha_1 | # at t/db_dependent/Plugins.t line 127. koha_1 | # Looks like you failed 1 test of 39. koha_1 | [15:24:05] t/db_dependent/Plugins.t ................................................ koha_1 | Dubious, test returned 1 (wstat 256, 0x100) koha_1 | Failed 1/39 subtests We requested another run and it passes (#73), same node (Docker_3) -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 16567] New: RSS feeds show issues in W3C validator and can't be read by some aggregators (Chimpfeedr, feedbucket)
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '25

24 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16567 Bug ID: 16567 Summary: RSS feeds show issues in W3C validator and can't be read by some aggregators (Chimpfeedr, feedbucket) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org We are seeing issues with some RSS aggregators refusing to load koha rss links, there are errors when checked in the W3C validator: https://validator.w3.org/feed/check.cgi -- You are receiving this mail because: You are watching all bug changes.

1 23

[Bug 23102] New: 404 errors on page causes SCI user to be logged out
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23102 Bug ID: 23102 Summary: 404 errors on page causes SCI user to be logged out Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Bug 18387, but for the SCI To recreate: 1 - Have something on the SCO page that won't load 2 - Add the self_checkin_module and self_checkout_module permissions to the AutoSelfCheck user 3 - Access the selfcheckout module https://yoursite.org/cgi-bin/koha/sco/sco-main.pl 4 - Sign in 5 - Click 'Finish' 6 - Yes to print a receipt 7 - You are asked to sign in again 8 - Repeat with the SCI module -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 65

[Bug 23296] New: Auto Renewal Notice does not use Library specific notices
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23296 Bug ID: 23296 Summary: Auto Renewal Notice does not use Library specific notices Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org All notices in Koha are created to be a default ALL libraries notice, however, with branch systems, there is also the ability to create a library specific notice that can be used instead. However, the notice AUTO_RENEWALS is not currently capable of being library specific - instead, the ALL Library Notice for AUTO_RENEWALS is the only one that Koha send. To adjust this, it would be recommended that a library specific notice like all the others in Koha can be created. Following circ control, would be the suggested way to go as with most notices in Koha. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 22780] New: MarkLostItemsAsReturned - map to Lost-sttaus instead of context where the transaction took place
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22780 Bug ID: 22780 Summary: MarkLostItemsAsReturned - map to Lost-sttaus instead of context where the transaction took place Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: klas.blomberg(a)skovde.se QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- Syspref MarkLostItemsAsReturned is mapped to the context where you make the transaction - Holds to pull list, longoverdue cronjob et.c. I can't see any logical reason for this! I think it would be better to map to Lost-statuses: Lost = don't mark as returned Longoverdue = don't mark as returned Lost and paid for = mark as returned et.c. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 17258] New: [OMIBUS] MySQL 5.7
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17258 Bug ID: 17258 Summary: [OMIBUS] MySQL 5.7 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org This is an omnibus report to group the different issues under MySQL 5.7 -- You are receiving this mail because: You are watching all bug changes.

1 136

[Bug 19169] New: Add a test to detect unneeded 'atomicupdate' files
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19169 Bug ID: 19169 Summary: Add a test to detect unneeded 'atomicupdate' files Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: mtj(a)kohaaloha.com QA Contact: testopia(a)bugs.koha-community.org Add a test to detect unneeded 'atomicupdate' files -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 23653] New: Plack stopped working - JSON validation timeout
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23653 Bug ID: 23653 Summary: Plack stopped working - JSON validation timeout Change sponsored?: --- Product: Koha Version: 19.05 Hardware: Other OS: Linux Status: NEW Severity: major Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: rick_conrad(a)sil.org QA Contact: testopia(a)bugs.koha-community.org I had plack working fine before this morning, but now if I have plack enabled, Koha does not respond to web requests, and apache eventually shows me a 502. These are the entries from plack-error.log. I don't know what swagger.io is - seems there is such a website, but I can't `curl` it from the webserver, at least right now. plack-error.log ```` Error while loading /etc/koha/plack.psgi: Can't load application from file "/usr/share/koha/api/v1/app.pl": [JSON::Validator] GET http://swagger.io/v2/schema.json == Inactivity timeout at /usr/share/perl5/JSON/Validator.pm line 274. Compilation failed in require at (eval 389) line 1. Child process 3159 exited with status 255 ```` The only change I made this morning was changing the server's timezone, but I doubt that's related. I did put it back to UTC, but no improvement. Disabling plack works for me, but my site is a lot slower (and it wasn't real quick to begin with). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 118