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

Elasticsearch vs OpenSearch
by dcook＠prosentient.com.au 03 May '21

03 May '21

Because I'm good at stirring up trouble. https://www.techrepublic.com/google-amp/article/opensearch-aws-rolls-out-its -open-source-elasticsearch-fork/ As you may know, AWS have forked the last FOSS Elasticsearch (7.10 I think). They've announced that they're calling it OpenSearch. It's still only in alpha stage and they won't have a production-ready release for months yet, but it is interesting to keep notes on. Elastic are responsible for the vast majority of commits in Elasticsearch, so I'm somewhat skeptical about a fork, but I think there is a lot of anger at Elastic and a lot of support for OpenSearch, so who knows. I don't think there's anything to do at this stage, but just wanted to share the information for people David Cook Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

2 2

HTTP/HTTPS cheme in Base Path in API documentation
by dcook＠prosentient.com.au 03 May '21

03 May '21

Hi all, I just noticed on a HTTPS site that the Base URL at /api/v1/.html was listed as HTTP rather than HTTPS. Looking at Mojolicious::Plugin::OpenAPI, it seems that it's hard-coded to HTTP *if* a scheme isn't specified in the spec: https://github.com/jhthorsen/mojolicious-plugin-openapi/blob/master/lib/Mojo licious/Plugin/OpenAPI/SpecRenderer.pm#L406 Looking at https://swagger.io/docs/specification/2-0/api-host-and-base-path/, we could be setting "schemes" there. I'm not 100% sure what we should do here. Maybe nothing. But it just seem unfortunate to be showing a HTTP link on a HTTPS page especially for an API... David Cook Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

1 0

Koha Community Newsletter: April 2021
by Koha Newsletter 01 May '21

01 May '21

The Koha Community Newsletter for April 2021 is here: * https://koha-community.org/koha-community-newsletter-april-2021/ Many thanks to everyone who submitted articles and news to last month's newsletter! Please feel free to email me with any corrections or suggestions. -- Michael Kuhn Editor, Koha Community Newsletter

1 0

Optimizing Starman startup
by dcook＠prosentient.com.au 30 Apr '21

30 Apr '21

Hi all, Do you despair when you see the following periodically in "top" when a starman worker is recreated ? PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 9529 my-koha 20 0 460108 197212 17172 R 100.0 0.4 0:03.41 /usr/share/koha/api/v1/app.pl Or the following in top when you install koha-common package or restart the koha-common service? 11101 1-koha 20 0 447232 193320 16076 R 10.6 0.4 0:09.09 /usr/share/koha/api/v1/app.pl 11168 1-koha 20 0 447240 193264 16056 R 10.6 0.4 0:08.72 /usr/share/koha/api/v1/app.pl 11306 2-koha 20 0 447220 193148 16000 R 10.6 0.4 0:08.07 /usr/share/koha/api/v1/app.pl 11543 2-koha 20 0 447232 193036 15828 R 10.6 0.4 0:07.07 /usr/share/koha/api/v1/app.pl 11784 3-koha 20 0 441536 189664 16172 R 10.6 0.4 0:06.04 /usr/share/koha/api/v1/app.pl 11830 3-koha 20 0 439548 187212 15748 R 10.6 0.4 0:05.82 /usr/share/koha/api/v1/app.pl 11831 4-koha 20 0 438620 186344 15748 R 10.6 0.4 0:05.81 /usr/share/koha/api/v1/app.pl 11853 4-koha 20 0 437680 185672 16000 R 10.6 0.4 0:05.79 /usr/share/koha/api/v1/app.pl Well, I still have a lot of investigation left to do, but I notice 1 place that a lot of time taken is here (per worker): my $validator = JSON::Validator::OpenAPI::Mojolicious->new; $validator->load_and_validate_schema( $self->home->rel_file("api/v1/swagger/swagger.json"), { allow_invalid_ref => 1, } ); push @{$self->routes->namespaces}, 'Koha::Plugin'; my $spec = $validator->schema->data; $self->plugin( 'Koha::REST::Plugin::PluginRoutes' => { spec => $spec, validator => $validator } ); $self->plugin( OpenAPI => { spec => $spec, route => $self->routes->under('/api/v1')->to('Auth#under'), allow_invalid_ref => 1, # required by our spec because $ref directly under # Paths-, Parameters-, Definitions- & Info-object # is not allowed by the OpenAPI specification. } ); Anyone have ideas for improving this? Do we have to validate the schema every time? Can we move the schema validation into a different module and preload it into Starman using the -M flag so that it's done 1 time per Starman master instance rather than 1 time per Starman worker instance? I find "/usr/share/koha/api/v1/app.pl" to be the bane of deployments, as it puts a massive load on a server, when you have multiple Koha instances on the server. David Cook Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

5 24

git trick for compiled CSS
by Fridolin SOMERS 29 Apr '21

29 Apr '21

Hi, I'd like to share a trick. When generating compiled CSS files, no way to check the git diff since all is on one line. I've managed to find a trick : git show --word-diff shows chucks deleted/added so with some regexp : git show --word-diff $SHA1 | egrep '(\[\-)|(\{\+)' | sed -r 's/^.*(\[\-.*\-\]\{\+.*\+\}).*$/\1/g' For example : aebd3f6a53 Bug 27566: Compiled CSS [-textarea{font-family:NotoSans}.navbar-]{+textarea{font-family:NotoSans,sans-serif}.navbar+} [-textarea{font-family:NotoSans}.navbar-]{+textarea{font-family:NotoSans,sans-serif}.navbar+} [-textarea{font-family:NotoSans}.navbar-]{+textarea{font-family:NotoSans,sans-serif}.navbar+} [-textarea{font-family:NotoSans}.navbar-]{+textarea{font-family:NotoSans,sans-serif}.navbar+} This is very usefull to check that compilation worked and did not broke the 90% of the file XD Best regards :D -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> Software and system maintainer 🦄 BibLibre, France

3 2

Template::Toolkit and Translations
by dcook＠prosentient.com.au 28 Apr '21

28 Apr '21

Hi all, While I mostly work in English, I occasionally do support libraries in other languages like French, Arabic, and Chinese. And more recently Ive been looking at the Languages dropdown in the OPAC advanced search. In the templates, I notice that we often translate HTML, but what if we translated strings for a Template::Toolkit data structure instead? Consider the following: [% BLOCK en %]Anglais[% END %] [% BLOCK fr %]Français[% END %] [% langs.en = INCLUDE en %] [% langs.fr = INCLUDE fr %] I suppose its not very beautiful, but the translation process should be simple and in the end we have a re-usable hash map rather than static HTML. As I commented on Bug 12017 (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12017) we could have a database table of language codes with native language names, and then iterate through that and use the hash map of translations to provide the translations. Since were not producing HTML, we could flexibly reuse this language data in various different contexts. Whether its the Languages dropdown in the OPAC advanced search, the language selector, or whatever. We could probably use this concept in other places as well where we need translations but we dont want to be bound to HTML. What do people think? Im not wedded to the idea, but its something that crossed my mind this morning, when I looked at the large switch statements at https://bugs.koha-community.org/bugzilla3/page.cgi?id=splinter.html <https://bugs.koha-community.org/bugzilla3/page.cgi?id=splinter.html&bug=120 17&attachment=40285> &bug=12017&attachment=40285. (To that end, I would also suggest a theme-independent Template::Toolkit include directory, but thats another story) David Cook Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

2 4

Koha 19.11.17 released
by Victor Grousset/tuxayo 26 Apr '21

26 Apr '21

Hello! The Koha Community is happy to announce the release of Koha 19.11.17 The full release notes can be found at: https://koha-community.org/koha-19-11-17-released/ Debian packages should be available shortly. Thanks to everyone involved :) Cheers, -- Victor Grousset/tuxayo

1 0

Release of Koha 20.05.11
by Andrew Fuerste-Henry 26 Apr '21

26 Apr '21

Hi all! We're proud to announce the release of Koha 20.05.11. This is a maintenance release. Full release notes can be found here: https://koha-community.org/koha-20-05-11-released/ Debian packages should be available in a few days. Thank you! -- Andrew Fuerste-Henry Educator (he/him/his) ByWater Solutions bywatersolutions.com Phone:(888)900-8944 <(888)%20900-8944> What is Koha? <http://bywatersolutions.com/what-is-koha/>

1 0

Issue with bugzilla
by Jonathan Druart 26 Apr '21

26 Apr '21

Hi all, We are experiencing issues on bugzilla. It seems that it is not possible to comment and search. However you can search if you are logged out, and apply patches using git-bz. The issue will certainly not be fixed until tomorrow. Cheers, Jonathan

1 1

Release of Koha 20.11.05
by Fridolin SOMERS 26 Apr '21

26 Apr '21

Hello everyone 🤗 The Koha community is proud to announce the release of Koha 20.11.05. It is a maintenance release. The full release notes are available here: https://koha-community.org/koha-20-11-05-released/ Debian packages should be available in a few days. Best regards 🤓 -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> Software and system maintainer 🦄 BibLibre, France

1 0