- Koha-devel - lists.koha-community.org

Run Koha::Caches->flush_L1_caches() on SIP Server
by dcook＠prosentient.com.au 19 Sep '19

19 Sep '19

Hi all, Who are the SIP experts? I've noticed that Koha::Caches->flush_L1_caches() never gets run on the SIP Server, and this means that the SIP Server can get stuck with old cached values that can never be changed without a restart. I've opened https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23640 to look into this, but I don't know the SIP Server well enough to know off the top of my head which function best represents every request (or if we want to only do it per connection, but I don't know how often connection attempts are done with SIP). I can investigate this, but I figure it makes more sense to leverage other people's expertise first. (Note: If you couple this issue with https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13193, you can theoretically have a SIP server persistently running with invalid system preferences. Either we push #13193, or we update SIP Server to reconnect to Memcached after a fork, so that it doesn't inherit the socket connection from the master SIP process.) Cheers, David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

1 0

Call for News: September 2019 Newsletter
by kohanews 14 Sep '19

14 Sep '19

I'm collecting news for the September newsletter. Send anything noteworthy to: k o h a news AT gmail dot com News criteria: --------------------------- ** For events **: - Please include dates for past events. If I can't find dates I may not add it. - Announcements for future events with dates T.B.A. are fine ...Eg., Kohacon - For past events , **** one month back is the cut-off ****. * News items can be of any length. * Images are fine * Anything and everything Koha. * Submit by the 26th of the month. If you are working on an interesting project or development related to Koha, please let me know and I'll include it in the development section. Thank you! -- Chad Roseburg Editor, Koha Community Newsletter

1 0

BULAC library is looking for developpers !
by Séverine Queune 13 Sep '19

13 Sep '19

Dear Koha community, The BULAC library <http://www.bulac.fr> would like to sponsor new features concerning suggestions , detailed on the following tickets : *Concerning suggestions creation :* - Bug 14963 <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14963> - Ability to suggest purchase on existing catalogue record - Bug 14973 <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14973> - Suggestions - Search and warn user about existing biblio when submitting a suggestion *Concerning suggestions update :* - Bug 18743 <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18743> - Filter suggestion lists correctly for IndependentBranches <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23594> - Bug 23590 <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23590> <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23590> <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23590> - Allow to modify the manager of a suggestion <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18743> - Bug 23594 <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23594> - Batch modification for itemtypes on suggestions page - Bug 23596 <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23596> - Update/Delete suggestion reason when receiving the item *Concerning suggestions workflow :* - Bug 23591 <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23591> - Add a new "Suggestions details" tab on bibliographic record - Bug 23592 <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23592> - Link between suggestion and bibliographic record on staff client - Bug 23593 <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23593> - Link between suggestion and bibliographic record on OPAC - Bug 22784 <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22784> - Archiving Purchase Suggestions Tests will be handled by the BULAC team. Feel free to write to sigb <koha(a)bulac.fr>@bulac.fr <sigb(a)bulac.fr> if you need further information or to send your proposal for these developments. Thank you ! *Séverine QUEUNE* Administrateur fonctionnel du SIGB Équipe signalement et exposition des données Pôle Flux et données *Bibliothèque universitaire des langues et civilisations* 65 rue des Grands Moulins F-75013 PARIS T +33 1 81 69 *18 55* www.bulac.fr

1 0

Fwd: Developer tool anouncement
by Agustin Moyano 04 Sep '19

04 Sep '19

Hi community, I'm proud to anounce this tool I've developed to tidy up "WIP" commits https://gitlab.com/thekesolutions/tools/git-rk Really hope it helps Ps: save the kittens! ;P

1 0

Re: [Koha-devel] IndependentBranches == "softno" on SIP server
by dcook＠prosentient.com.au 02 Sep '19

02 Sep '19

Oh. I've found something interesting! lib/Koha/Patron.pm uses "checkPrevCheckout" instead of "CheckPrevCheckout", which is why I wasn't finding it with my case-sensitive grep. In C4::Circulation::CanBookBeIssued, I think it is very likely that C4::Context->preference("checkPrevCheckout") is called and then the next call is C4::Context->preference("IndependentBranches"), and somehow. the value from "checkPrevCheckout" is being used instead of the true value of "IndepenentBranches". Yikes! I don't know how it's happening, but it's happening. I notice that Plack runs Koha::Caches->flush_L1_caches() routinely. So does bin/migration_tools/rebuild_zebra.pl when it's run in daemon_mode. I reckon a short-term solution would be to add that cache flushing to the SIP server as well. However, I'm still really curious how the wrong value is being returned by C4::Context->preference("IndependentBranches"). David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: dcook(a)prosentient.com.au <dcook(a)prosentient.com.au> Sent: Monday, 2 September 2019 3:49 PM To: 'koha-devel' <koha-devel(a)lists.koha-community.org> Subject: IndependentBranches == "softno" on SIP server Hi all, I've been getting errors on a SIP server that indicate that "IndependentBranches" is non-zero. However, both MySQL and Memcached have said that "IndependentBranches" is zero. So I added some logging to the SIP server, and it's saying that the value of "IndependentBranches" - at the time of the error - is "softno". So I looked through the Koha code and the only reference to "softno" I can find is in regards to "CheckPrevCheckout". I've checked environmental variables and every bit of code I can think of, and I'm absolutely stumped by this one. The most feasible answer to me is a caching problem. However, it happened over the course of weeks, and it always had the same value, so that seems a bit far-fetched too. I suppose the next step is to add yet more logging, but I figured I'd reach out to all of you to see if anyone has had a similar problem. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

1 0

IndependentBranches == "softno" on SIP server
by dcook＠prosentient.com.au 02 Sep '19

02 Sep '19

Hi all, I've been getting errors on a SIP server that indicate that "IndependentBranches" is non-zero. However, both MySQL and Memcached have said that "IndependentBranches" is zero. So I added some logging to the SIP server, and it's saying that the value of "IndependentBranches" - at the time of the error - is "softno". So I looked through the Koha code and the only reference to "softno" I can find is in regards to "CheckPrevCheckout". I've checked environmental variables and every bit of code I can think of, and I'm absolutely stumped by this one. The most feasible answer to me is a caching problem. However, it happened over the course of weeks, and it always had the same value, so that seems a bit far-fetched too. I suppose the next step is to add yet more logging, but I figured I'd reach out to all of you to see if anyone has had a similar problem. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

1 0

Koha Community Newsletter: August 2019
by kohanews 29 Aug '19

29 Aug '19

The Koha Community Newsletter for August 2019 is here: https://koha-community.org/koha-community-newsletter-august-2019/ Many thanks to the folks who submitted articles and news to this month's newsletter. Please feel free to email me with any corrections or suggestions. -- Chad Roseburg Editor, Koha Community Newsletter

1 0

Fwd: SC Status before sip2 login
by Karam Qubsi 27 Aug '19

27 Aug '19

Hello Koha Developers, Do you think we should have an option for SIP2 server to allow SC status (99) before the login (93) ? I'm not aware if anyone else before reported about such a problem, I may try to develop this feature for the community if you think it is going to be useful for others, And of course I wish someone can give me some tips about where to start, I tried to look in the SIP2 server code. and it is still not clear for me where is the place we are closing connection if not logged in. if someone can point me to that , this would be really helpful. I'm talking about the raw_transport. Thank you very much. ---------- Forwarded message --------- From: Karam Qubsi <karamqubsi(a)gmail.com> Date: Mon, Aug 26, 2019 at 6:29 PM Subject: SC Status before sip2 login To: Koha <Koha(a)lists.katipo.co.nz> Hello Koha Community, I'm working with a selfcheck machine that is sending the sc status request (99) before the login request (93) . and that is causing koha sip server to close the connection. >From official documentation of SIP * , it look like that this status message can be sent before initialising SIP login, so I'm not sure if there is an option to allow this request or even allow login without username/password as we are going to secure the connection using ssh anyway. Any ideas or tips would be highly appreciated, Thank you very much Karam . * http://multimedia.3m.com/mws/media/355361O/sip2-protocol.pdf (page 6 ) : > SC Status > The SC status message sends SC status to the ACS. It requires an ACS > Status Response message reply from the ACS. This message will be the first > message sent by the SC to the ACS once a connection has been established > (exception: the Login Message may be sent first to login to an ACS server > program). The ACS will respond with a message that establishes some of the > rules to be followed by the SC and establishes some parameters needed for > further communication. -- *Karam Qubsi* -- *Karam Qubsi*

1 0

mailing list migration
by Laurent Ducos 20 Aug '19

20 Aug '19

Hello. The mailman mailing list server for koha-community was migrated last week. Thank you Chris for your help on the area dns koha-community. the novelties are : 1 : A dedicated server on ubuntu bionic. 2 : Mailman upgrade. 3 : A better postfix configuration. 4 : Interaction whith spamassassin. 4 : Better protection with fail2ban filters. 5 : Lets encrypt certificate. 6 : Netdata monitoring. Have a good day. -- Laurent Ducos Administrateur système et réseaux chez BibLibre IT system and network administrator at BibLibre

2 1

Call for News: August 2019 Newsletter
by kohanews 14 Aug '19

14 Aug '19

I'm collecting news for the August newsletter. Send anything noteworthy to: k o h a news AT gmail dot com News criteria: --------------------------- ** For events **: - Please include dates for past events. If I can't find dates I may not add it. - Announcements for future events with dates T.B.A. are fine ...Eg., Kohacon - For past events , **** one month back is the cut-off ****. * News items can be of any length. * Images are fine * Anything and everything Koha. * Submit by the 26th of the month. If you are working on an interesting project or development related to Koha, please let me know and I'll include it in the development section. Thank you! -- Chad Roseburg Editor, Koha Community Newsletter

1 0