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

Your patches => your matter
by Tomas Cohen Arazi 31 Mar '23

31 Mar '23

Hi all :-D I wanted to ask everyone contributing patches to Koha, that when you get notified your patches have been pushed, at least two things need to happen: - You get happy - You keep an eye on the test suite [1] You get happy because it means a lot of people reviewed your stuff, spent time and energy on making it real, and we all love that feeling. We usually only push things that are fully covered by tests, but also reviewed by various expert community members on their way to the main branch. Hopefully you already had feedback from QA team members you had to respond to. So, congrats :-D But shit happens :-D There are at least two common scenarios: - Your 'little change' that is covered by tests and stuff breaks things in other places - There are poorly coded tests somewhere else (old, that relied on other ways of Koha doing things ,etc) that fail because of your change, or because you're changing a behavior and didn't notice (neither the QA step) things had to be adjusted somewhere else. It might happen... to everyone. In both cases, we [2] are expecting YOU to keep an eye on Jenkins being green, and also that you ACT, and FIX the issues, or communicate your thoughts on them if you cannot solve it. If you don't know who to contact, just go back to your bug and comment there, or just post a comment on IRC and there will be someone to talk to, almost all day hours. Those failures might 'just be minor things in the tests' or serious regressions for our libraries. So don't treat jenkins not being green lightly. PLEASE We are always available to help, so fear none, you are not alone and the best results show up when we work together. BONUS: we'll think of a reward on the next Kohacon for those who look after jenkins and help fixing it just because they care. Stay tuned. Thanks everyone for your contributions, and making Koha so great :-D [1] https://jenkins.koha-community.org [2] The Release Team -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

1 0

Heya
by Tomas Cohen Arazi 31 Mar '23

31 Mar '23

Hi, the hackfest is over, we had great time! I wanted to thank everyone supporting our open source work, and Biblibre for making this opportunity to meet in person real. Thanks! -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

1 0

Session Token fo Login into Koha
by Muhammad Uzair 28 Mar '23

28 Mar '23

Hey! I am using the following code to retrieve the session code from Koha using Koha RestAPI. import requests import base64 domain = 'http://my-domain.com' username = 'user' password = 'password' api_key = 'my-api-key' client_id = 'id' url = f'{domain}/api/v1/auth/token' auth_header_value = base64.b64encode(f'{username}:{password}'.encode()).decode() headers = { 'Authorization': f'Basic {auth_header_value}', 'X-API-Key': api_key } response = requests.post(url, headers=headers) if response.status_code == 200: access_token = response.text print(f"Access token: {access_token}") else: print(f"Error: {response.status_code} {response.reason}") I am supposed to get a session token with response code 200. But I am getting an error 404 i.e. default response. I have done the code in perl but getting the same response. Kindly help me to solve this issue as it is my university project.

2 1

Next Dev Meeting - April 12th 15UTC
by Renvoize, Martin 28 Mar '23

28 Mar '23

Hello, The next dev meeting will be on April 12th at 15UTC https://wiki.koha-community.org/wiki/Development_IRC_meeting_12_April_2023 Lots of topics planned, please have a look at the agenda and make sure you prepared your topics if you have some. Cheers, Martin Renvoize, MPhys (Hons) Head of Development and Community Engagement E: martin.renvoize(a)ptfs-europe.com P: +44 (0) 1483 378728 M: +44 (0) 7725 985636 www.ptfs-europe.com

1 0

Hackfest
by David Cook 24 Mar '23

24 Mar '23

Hi all, Is there any kind of schedule for the Hackfest in Marseilles? I might try to work late some nights so that I can participate a bit more meaningfully online in real time. And then maybe next year Ill actually fly out and participate in person! Je dois practiquer mon français David Cook Senior 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

Using Vue.js in Koha plugins
by David Cook 23 Mar '23

23 Mar '23

Hey Jonathan, Do you think it would be possible to use Vue.js in Koha plugins? I haven't played with webpack but it looks like "koha-tmpl/intranet-tmpl/prog/js/vue/dist/erm.js" contains the entirety of Vue.js in itself, so in theory it would be possible to include whatever Vue.js on a different page that doesn't load erm.js. Have we thought about separating out the core Vue.js library from the Vue.js application code using the SplitChunksPlugin? That way we could include the vue.js library code wherever we might want it, and only load the erm.js application code on the ERM page(s). Perhaps we could split other re-usable components out as well. Of course, the Koha plugin would be implementing its Vue.js application without a build step. But I think that would be OK. I'm thinking of a scenario where the Koha plugin provides data via an API endpoint, and wants to display that data using a Koha Vue DataTable for instance. What do you think? David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

3 5

Mojolicious::Plugin::OAuth2 only uses client_secret_post client authentication method
by David Cook 20 Mar '23

20 Mar '23

Hi all, I can't remember if I've said this before but it looks like Mojolicious::Plugin::OAuth2 only uses the client_secret_post client authentication method. In the OpenID Connect spec, "client_secret_basic" is actually the default method: https://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication I think that Keycloak checks both the Authorization header and the request body, which is probably why it's worked so easily with the Koha OpenID Connect auth. I couldn't find any documentation on this for Keycloak, but I think it's a safe assumption. Reported the issue on Github: https://github.com/marcusramberg/Mojolicious-Plugin-OAuth2/issues/72. Really it should be a very straight forward change to implement in the plugin. David Cook Senior 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

Call for news - Newsletter March 2023
by Koha Newsletter 13 Mar '23

13 Mar '23

Hi I'm collecting news for the March 2023 Koha Community Newsletter. Please send anything noteworthy to: kohanews (at) gmail (dot) com News criteria: * News items can be of any length. * Images are fine. * Anything and everything Koha. * Submit by the 26th of the month. Text format criteria: * Just structured plain text, or * HTML text to include tables or similar For events: * Consider adding your event to the Koha Community calendar at https://koha-community.org/calendar/ Thank you! Michael Kuhn Editor, Koha Community Newsletter

1 0

Easiest sign off in the world (BZ 33189 plugin upload prompt for .kpz files)
by David Cook 10 Mar '23

10 Mar '23

Hi all, I was going to upload a Koha plugin today when I was bemoaning having to sift through all my Downloads entries to find the .kpz file I wanted. Then I remembered that input type="file" actually allows you to specify what files to look for using the "accept" attribute. So I wrote a little patch for the Koha plugin upload, and it's soooo much nicer now. Anyone looking for the world's easiest/fastest sign off, please go and check it out. Thanks! David Cook Senior 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

Using "ucf" to manage log4perl.conf
by David Cook 10 Mar '23

10 Mar '23

Hi all, I've attached an "alternative" patch on "Bug 32791 - Log4perl configuration files need a tool for updating on package upgrade". It uses the utility "ucf" to manage log4perl.conf. It works well for handling upgrades to log4perl.conf configuration, but it needs more testing and some more consideration for koha-create, koha-remove, and apt-get purge. Is anyone else interested in working on this with me? David Cook Senior 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