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

[Bug 13193] Discussion: strategy for diagnosing memcache issues.
by bugzilla-daemon＠bugs.koha-community.org 17 Sep '19

17 Sep '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13193 David Cook <dcook(a)prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |critical --- Comment #15 from David Cook <dcook(a)prosentient.com.au> --- I'm actually going to bump this up to critical, since I think this is probably impacting libraries more than we all realize. I have a library that is having lots of issues because of this problem, and a resolution ASAP would be great. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13193] Discussion: strategy for diagnosing memcache issues.
by bugzilla-daemon＠bugs.koha-community.org 17 Sep '19

17 Sep '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13193 --- Comment #14 from David Cook <dcook(a)prosentient.com.au> --- cpanm Cache::Memcached::Fast::Safe git bz apply 13191 And now the output is beautifully accurate: Cache for version is 18.1101000 at C4/Context.pm line 420. Cache for version is 18.1101000 at C4/Context.pm line 420. Cache for timeout is 1d at C4/Context.pm line 420. Cache for version is 18.1101000 at C4/Context.pm line 420. Cache for version is 18.1101000 at C4/Context.pm line 420. Cache for timeout is 1d at C4/Context.pm line 420. Cache for version is 18.1101000 at C4/Context.pm line 420. Cache for version is 18.1101000 at C4/Context.pm line 420. Cache for timeout is 1d at C4/Context.pm line 420. Cache for version is 18.1101000 at C4/Context.pm line 420. Cache for version is 18.1101000 at C4/Context.pm line 420. Cache for timeout is 1d at C4/Context.pm line 420. Cache for version is 18.1101000 at C4/Context.pm line 420. Cache for version is 18.1101000 at C4/Context.pm line 420. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13193] Discussion: strategy for diagnosing memcache issues.
by bugzilla-daemon＠bugs.koha-community.org 17 Sep '19

17 Sep '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13193 --- Comment #13 from David Cook <dcook(a)prosentient.com.au> --- Using the code provided, I was able to reproduce the problem, although I found it easier to see using 100 iterations rather than 50 iterations. Cache for timeout is 1d at C4/Context.pm line 420. Cache for timeout is 18.1101000 at C4/Context.pm line 420. Cache for version is 1d at C4/Context.pm line 420. Cache for version is 1d at C4/Context.pm line 420. Argument "1d" isn't numeric in numeric lt (<) at C4/Auth.pm line 1407. Cache for version is 18.1101000 at C4/Context.pm line 420. Cache for version is 18.1101000 at C4/Context.pm line 420. ... Cache for timeout is 1d at C4/Context.pm line 420. Cache for version is 18.1101000 at C4/Context.pm line 420. Cache for version is 18.1101000 at C4/Context.pm line 420. Use of uninitialized value $cached_var in concatenation (.) or string at C4/Context.pm line 420. Cache for timeout is at C4/Context.pm line 420. Use of uninitialized value $cached_var in concatenation (.) or string at C4/Context.pm line 420. Cache for version is at C4/Context.pm line 420. Cache for version is 18.1101000 at C4/Context.pm line 420. Cache for timeout is 1d at C4/Context.pm line 420. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13193] Discussion: strategy for diagnosing memcache issues.
by bugzilla-daemon＠bugs.koha-community.org 17 Sep '19

17 Sep '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13193 Mason James <mtj(a)kohaaloha.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mtj(a)kohaaloha.com -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13193] Discussion: strategy for diagnosing memcache issues.
by bugzilla-daemon＠bugs.koha-community.org 17 Sep '19

17 Sep '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13193 --- Comment #12 from David Cook <dcook(a)prosentient.com.au> --- (In reply to Joonas Kylmälä from comment #4) > I don't think there is corruption happening in memcached but a race > condition caused by us using Cache::Memcached::Fast even though it is not > thread/fork safe. I fixed this issue by replacing it with > Cache::Memcached::Fast::Safe, hopefully I will manage to send a patch soon. Joonas, you are my favourite person in the world right now. I've been bumping into this problem, and it's been driving me insane. I haven't verified it yet, but I will as soon as I can! -- Reading through the documentation, it looks like we could still use Cache::Memcached::Fast, if we were diligent with the use of "disconnect_all", but that would be a lot of effort to refactor Koha to do that, so I think it would be better to switch to Cache::Memcached::Fast::Safe as you've suggested. The downside is that I don't think Cache::Memcached::Fast::Safe is packaged for Debian (https://packages.debian.org/search?suite=default&section=all&arch=any&searc…) so Mirko would have to package it and put it in Koha's APT repository -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8995] Show OpenURL links in OPAC search results
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '19

16 Sep '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8995 Tomás Cohen Arazi <tomascohen(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |23627 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23627 [Bug 23627] Koha::Biblio->get_coins too noisy if no 245$b -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13193] Discussion: strategy for diagnosing memcache issues.
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '19

16 Sep '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13193 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |katrin.fischer(a)bsz-bw.de, | |martin.renvoize@ptfs-europe | |.com -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 23621] New: Apply holds circulation rules at branch level, not system level.
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '19

16 Sep '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23621 Bug ID: 23621 Summary: Apply holds circulation rules at branch level, not system level. Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: niamh.walker-headon(a)it-tallaght.ie QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Currently patrons are not able to place requests on items from the OPAC when the title they wish to request has another item attached which is not holdable. The item that is “not holdable” is an available item, so, as far as the system is concerned there is an available item on the shelves and it does not allow the request to proceed. The circulation rules are not applied at the branch level but at the system level. Therefore, if an item from branch A is holdable and from branch B is not, the branch a patron can’t place a hold on the branch a item, eventhough the branch b item is not holdable. . The circulation rules for holds should able to be applied at the branch level, rather that at the entire system level. At the moment if items for more than one branch are attached to a bibliographic record and the system preference set to deny a hold if the item is available, the system will not allow a patron to place a hold at branch A if there is an available item at branch B even if holds are not allowed on the second branch in the circulation rules. In addition if I have the title on loan from branch B and return it the system tries to fill the hold for branch A with the item from branch B. We need to be able to enable ability of patrons to place a hold on a title that has a mixture branches, locations and collections, some of which are not holdable e.g. short loan and reference items, special collections and multiple formats. Holds are being incorrectly filled, and patrons can’t place holds on items at their home branch if it is available at another. Without this change, the patron is turned away from getting the book required leaving an unsatisfied customer. The customer may leave it at that (which negatively affects our feedback in relation to high demand items and customer service), or approach library staff who will have to either override the system in order to place the hold or temporarily check out the short loan item until the request is made. This in turn takes up more staff time and creates issues and confusion re holds. Dissatisfied customers, poor collection development based on patron demands and inefficient use of staff time are also caused by this. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 13193] Discussion: strategy for diagnosing memcache issues.
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '19

16 Sep '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13193 Joonas Kylmälä <joonas.kylmala(a)helsinki.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - low |P3 Severity|enhancement |normal --- Comment #11 from Joonas Kylmälä <joonas.kylmala(a)helsinki.fi> --- Bumping the criticality of this patch from low to at least normal now since returning wrong system preference could potentially cause unwanted access to some things or block access from some user (we had a case where a SIP user was not able to connect because the system was supposedly in "maintenance mode" because the timeout syspref value was returned instead of Koha database version number) -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13193] Discussion: strategy for diagnosing memcache issues.
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '19

16 Sep '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13193 --- Comment #10 from Joonas Kylmälä <joonas.kylmala(a)helsinki.fi> --- I fixed a typo "verson" in the commit message. -- You are receiving this mail because: You are watching all bug changes.

1 0