Time Nick Message
23:31 tcohen ^^ is that right, rangi[m] ?
23:31 tcohen ka kite wawe koe
23:31 tcohen have a great weekend y'all
23:30 tcohen team++
23:30 tcohen community++
23:30 tcohen koha++
23:30 tcohen ashimema++
23:30 tcohen khall++
23:30 tcohen kidclamp++
23:30 tcohen cait++
23:30 tcohen Joubu++
23:30 tcohen lukeg++
23:30 tcohen oleonard++
23:30 tcohen please test and provide follow-ups!
23:30 tcohen next (monday) is ERM and OIDC
21:43 huberto Have a good weekend!
20:10 huberto It seems that on some of our servers Apache will strip the Authorization header by default. Adding `CGIPassAuth On` to the API directory worked perfectly.
18:52 huberto Is there anything that would strip the Authorization header when making a request to the API? I dumped the headers and even though I can confirm that I'm sending the Authorization header with Postman or curl, it's not in the headers dumped inside Koha/REST/V1/Auth.pm.
18:30 oleonard I don't know if it's relevant to your situation.
18:30 huginn` 04Bug 28926: normal, P5 - low, ---, mtj, Pushed to oldoldoldstable , Update cpanfile for Mojolicious::Plugin::OpenAPI v2.16
18:30 oleonard Guest440: There is a recent bug related to that: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28926
18:29 oleonard Sorry Guest440, at this time of day not many people are round
18:17 Guest440 Hello! I've been running a Koha instance in AWS for a little bit. We were having some issues that seemed to be tied to Mojolicious::Plugin::OpenAPI today and so I updated/graded our koha version. Since then our instance hasn't been reachable in the load balancer's target group and I'm running out of ideas to debug it. Does anyone have experience with this?
17:14 reiveune bye
16:45 oleonard I wonder if we need a "stop" control
16:44 oleonard Whoops, no. That made it work, thanks
16:42 Joubu oleonard: did you reload plack?
16:40 oleonard Joubu: I'm not sure it's working though... it does one automatic refresh and then reverts to 60 seconds
16:39 oleonard Joubu: I don't think the look of the refresh options isn't perfect but I don't know what to suggest
16:26 huberto Joubu: thanks for the remote debugging :) I will dig down starting with Auth.pm and try to find out why the credentials are not reaching it.
16:22 oleonard I missed the part where you mentioned the bug number before, sorry
16:20 Joubu oleonard: was it the question? Or are you asking on which screen you can find it?
16:20 Joubu oleonard: with the patch from 30963
16:19 Joubu look like you are missing the credential 523 unless ($credentials) {
16:19 oleonard Joubu: How did you arrive at that curbside pickups screenshot?
16:18 Joubu then you will know in which situation you are
16:18 Joubu The other solution is to search for "Authentication failure" in Koha/REST/V1/Auth.pm. Find which occurrence is returned to you (modify the message for instance)
16:16 Joubu huberto: `tail -f /var/log/$KOHA_INSTANCE/*.log`, then `restart_all` (if you have this alias), then try again, and watch the logs
16:15 huberto I am not using docker for this one, it's a standard installation, albeit "inLibro"ised ;)
16:13 huberto Nothing that I can see in the logs, nothing's been added there for the past hour or so, despite my tests.
16:09 Joubu are you using koha-testing-docker?
16:09 Joubu something else in Koha logs?
16:07 huberto Well at least it's good to know I'm not doing anything wrong. This is exactly what I'm using and I keep getting Authentication failure.
16:05 Joubu in tab Authorization, select type:"basic auth", then enter credential for your Koha user (needs the correct permissions, so pick your usual superlibrarian to be sure)
16:04 Joubu http://kohadev-intra.mydnsname.org:8081/api/v1/patrons
16:04 Joubu nope, no filter
16:03 huberto Because I'm getting the same error: "Authentication failure."
16:03 huberto Do I absolutely need to send filters when trying /api/v1/patrons?
16:01 huberto Let me give it a try
16:01 Joubu do you have the same error with GET /patrons?
16:01 huberto Maybe there's something in Kitchensink that I'm missing. The Openapi.json is fairly simple so I don't know what it could be.
16:00 huberto I thought it would work for sure with Postman, because it's trivial to input the username and password and Postman converts it to the "Authorization: Basic [...]" header.
15:59 Joubu cannot remember the exact syntax however
15:59 Joubu With Postman you can ask for the curl version of a given query. But if it does not work with postman then you are missing something else. You need to pass a header with "Authorization: Basic"
15:57 huberto I do, I have the same error in Postman. I have double-checked that RESTBasicAuth is enabled in the system preferences.
15:55 Joubu huberto: do you know Postman?
15:54 huberto I am testing using 'PUT /api/v1/contrib/kitchensink/patrons/patate/bother' but keep getting "Authentication failure" errors, despite having using -u 'username:password'.
15:53 huberto Is there anything special that I need to add when making a curl request to the API?
15:40 huginn` Joubu: The operation succeeded.
15:40 Joubu @later tell oleonard do you think this is reasonable (the refresh section)? https://snipboard.io/sfo6We.jpg - bug 30963
12:32 Joubu NSO now
12:30 huginn` 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32111 critical, P5 - low, ---, jonathan.druart+koha, ASSIGNED , Cannot schedule a pickup at the OPAC
12:30 Joubu tcohen: bug 32111
12:13 Joubu git bisect blames 30718 as well
12:12 Joubu not yet
12:12 tcohen Joubu: is there a report for the breakage?
12:06 ashimema as for broken curbside.. no idea I'm afraid
12:06 ashimema but yeah.. for me it's not a QA fail right now.. just something to be aware of and consider a coding guideline for and fixes down the line.
12:05 ashimema hope that makes sense
12:05 ashimema but there might be the odd case and in those cases I love having it right there in front of me in the same component file rather than having to work my way backwards to the scss source file somewhere else...
12:05 ashimema so in most cases I'm envisaging we won't need to have a really narrowly scoped piece and thus won't have it bunched in with the component itself.
12:05 oleonard That would be my instinct as well
12:04 ashimema my feeling is that we can have css inside with the components.. but stick to only things that are really specific to that one component.. if we find ourselves repeating css then that css should get moved up into our global and thus unscoped
12:01 Joubu did we*
12:01 Joubu do we change something about flatpickr and the "disabled" property? curbside pickup is broken at the OPAC because of that, but cannot find the root of the problem
12:00 Joubu yes, I like to have everything inside the component, but that leads to duplicate css rules...
11:59 ashimema It's also something we can do later.. I expect polishing to continue as part of the overall UI polishing going on
11:58 ashimema I did comment about possibly sharing more CSS rather than doing that scoped stuff.. but at the same time I've not really dug deep enough to know if that's a silly proposal
11:58 ashimema Actually, on that, I reckon I'm nearly ready to add my sign off
11:58 ashimema Nah, I have no issues with eRM so far.. been working through the code.. everything so far that I've questioned I've gone and looked at vue docs and decided you've taken the right approach
11:57 ashimema Haha, I hadn't noticed that yet Joubu
11:52 Joubu asking because you are having a look at erm? I am displaying a sticky dialog at the top when something wrong happens after a form submission
11:40 oleonard Yes, one or two other places I think... Advanced cataloging I think is one
11:40 * ashimema likes less obtrusive bottom right style toasts
11:40 ashimema wow.. they sitck around for a while and are really in your face..
11:39 ashimema hyst the sysprefs
11:39 ashimema w don't use those anywhere else do we?
11:39 ashimema that's a toast UX
11:39 ashimema ah yeah.. that's it.
11:39 oleonard Right HumanMsg
11:38 * ashimema checks
11:38 ashimema I think we used to have something like that in sysprefs.. might still have it...
11:38 ashimema little temporary popovers that detail an action happened then dissaper a few moments later.. or are dismissable if you decide to opt to have them stay around instead of expire and dissaper
11:37 ashimema hehe
11:37 * oleonard is reminded he hasn't had breakfast yet
11:37 oleonard a.... toast?
11:37 ashimema it's the sort of thing a toast would work nicely for
11:36 Joubu oleonard: I thought I did, but cannot find it right now! Maybe I only reported it on IRC
11:36 ashimema I'm probably overthinking
11:36 ashimema does that make sense to you.. it feels like a slightly icky page re-arrange to me.. by adding it in there we shift the page content down..
11:35 ashimema in a few other places we add add our standard 'alert' box at the top above the header on the page.. things like 'Thing X updated successfully'
11:35 ashimema which I can understand
11:35 ashimema He's keen for feedback that an action has taken place on modal submissions
11:34 ashimema I have one for you now oleonard.. it comes from comments from davidnind on my catalog concerns work.
11:33 oleonard Joubu: You didn't file a bug yet for this one did you? https://snipboard.io/2ets1d.jpg
11:28 huginn` 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32108 minor, P5 - low, ---, jonathan.druart+koha, Needs Signoff , Change "x" icon to replace patron when scheduling a pickup
11:28 Joubu bug 32108. Thanks, oleonard!
11:25 oleonard fa-fw is used on the OPAC's bibliographic detail page for the sidebar menu because in that situation it helps the icons and text line up vertically
11:24 Joubu but nevermind, I will remove fa-fw and add the space, to match other occurrences
11:24 Joubu oleonard: not really, there is fa-fw on the current green 'x', and none on the 'trash' icon for guarantor. I've tested the difference and noticed that, with fa-fw you don't need the space betwee <i> and 'Remove'
11:21 oleonard Joubu: Was there a display issue you were hoping to solve?
11:20 Joubu forget that, that's not what their doc says
11:19 tcohen hola #koha o/
11:18 Joubu shouldn't we?
11:18 Joubu <i class="fa fa-trash"></i> Remove</a>
11:18 Joubu instead of
11:17 Joubu <i class="fa fa-fw fa-trash"></i>Remove</a>
11:17 Joubu we should use that in those situations
11:17 Joubu for fixed-width
11:17 oleonard yes
11:17 Joubu ?
11:17 Joubu oleonard: aware of "fa-fw"
11:14 Joubu tcohen: curbside pickup broken, see follow-up on 30718
11:12 Joubu oleonard: ok thanks
11:10 ashimema * so much clearer
11:10 ashimema so much cleare
11:10 * ashimema likes oleonards suggestion.
11:07 oleonard Joubu I'd probably choose to change the link altogether to make it match instances like this: https://snipboard.io/6uLlny.jpg
11:05 * ashimema puts money on davidnind not being around yet
11:03 Joubu oleonard: https://snipboard.io/fNbTzQ.jpg - shouldn't we have the other "x" back to red as well?
10:40 huginn` Joubu: The operation succeeded.
10:40 Joubu @later tell mtj "Can't locate HTTPD/Bench/ApacheBench.pm in @INC"
10:40 huginn` Joubu: The operation succeeded.
10:40 Joubu @later tell mtj aware of the 00-strict failures? https://jenkins.koha-community.org/job/Koha_Master_D12/333/consoleFull
09:59 marcelr do not ignore gitignore
09:58 Joubu thanks, marcelr!
09:57 marcelr warning is gone
09:55 Joubu marcelr: can you try again with the last patch please?
09:54 marcelr thats progress
09:54 Joubu but it does not appear in git status because "plugin" is in .gitignore
09:54 Joubu I have one file that is not committed there
09:53 Joubu Use -f if you really want to add them.
09:53 Joubu koha-tmpl/intranet-tmpl/lib/dayjs/plugin
09:53 Joubu The following paths are ignored by one of your .gitignore files:
09:53 Joubu ok
09:53 Joubu ha
09:50 marcelr familiar experience ;)
09:50 Joubu I am missing something obvious here
09:49 Joubu yes, especially when I am the only one not getting the error!
09:49 marcelr debugging fun
09:49 Joubu that's fun...
09:48 marcelr no my own container
09:48 Joubu https://staff-bz30310.sandboxes.biblibre.eu/cgi-bin/koha/mainpage.pl - not there, right?
09:48 marcelr right on mainpage
09:47 Joubu marcelr: where do you see the warning? mainpage?
09:46 Joubu I have not idea why, but I don't get them, and they don't appear in the sandbox either
09:42 marcelr I am seeing: Uncaught TypeError: t is undefined /intranet-tmpl/lib/dayjs/dayjs.min_22.0600077.js:1 :246
09:40 marcelr let me check if I see a warning
09:39 marcelr they apply Joubu
09:37 huginn` 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30310 enhancement, P5 - low, ---, jonathan.druart+koha, Failed QA , Replace Moment.js with Day.js
09:37 Joubu Can I get help on bug 30310? Could someone apply the patches and confirm they get (or don't get) the warning in the console?
09:27 marcelr o/
08:52 fridolin or reapply changes after each upgrade
08:52 fridolin you may build your own deb package i think
08:52 fridolin Because package upgade may remove your changes
08:51 fridolin Have a look at https://gitlab.com/koha-community/koha-gitify can be usefull
08:51 fridolin https://wiki.koha-community.org/wiki/Commands_provided_by_the_Debian_packages#koha-plack
08:50 SupportLibrary[m] I put the file there and evrything is okey
08:50 fridolin you may need to restart plack middleware
08:50 SupportLibrary[m] Yes and i found it
08:50 fridolin perl files should be in /usr/share/koha/lib
08:47 fridolin SupportLibrary[m]: mmm how did you install Koha ? Debian Package ?
08:01 alex_ Bonjour
07:52 SupportLibrary[m] Hello. I am writing to you with a request for help. After I created a new .pl file and put it in build_folder. How to reflect the changes so that it is visible in Koha?
07:47 SupportLibrary[m] Hi
07:31 reiveune hello
04:42 schnydszch mtj: thanks!
04:42 schnydszch mtk: thanks!
03:59 mtj ..if you get some 'permission denied' error, try the docker prune command(s)
03:58 mtj then kd; kd; ku
03:58 mtj docker-compose-plugin will get you ... docker-compose v2
03:57 mtj ..you are already using the docker apt repo
03:57 mtj schnydszch: that should update you ^
03:57 mtj $ sudo apt-get install docker-ce docker-ce-cli containerd.io docker-compose-plugin
03:27 schnydszch hmmm.. i will just have to run those stated in the docs.docker? and my docker will be updated?
03:24 mtj v2 might be more reliable...
03:23 mtj https://docs.docker.com/compose/install/linux/#install-using-the-repository
03:23 mtj schnydszch: if you have more problems... upgrade docker-compose to v2
03:20 schnydszch anyway, I just cloned it again
03:19 schnydszch hmm koha folder was removed
03:17 mtj docker prune just removes old docker stuff
03:16 mtj koha git repo will still be there
03:16 schnydszch and so the koha I cloned is already deleted?
03:15 mtj i have used it for similar 'permission denied' errors
03:15 mtj yeah
03:15 schnydszch seems like it
03:15 schnydszch oh so this command is to delete all containers?
03:15 mtj ..you can wipe your old docker stuff using 'prune' command
03:14 mtj docker system prune -a -f
03:14 mtj docker image prune -f
03:14 mtj docker volume prune -f
03:14 mtj aah :)
03:14 schnydszch I have already rebooted :)
03:14 mtj ooh wait..
03:14 mtj hmm, can you reboot and try again?
03:13 schnydszch 5:20.10.19~3-0~ubuntu-focal 500
03:13 schnydszch 500 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages
03:13 schnydszch 5:20.10.20~3-0~ubuntu-focal 500
03:13 schnydszch 100 /var/lib/dpkg/status
03:13 schnydszch 500 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages
03:13 schnydszch *** 5:20.10.21~3-0~ubuntu-focal 500
03:13 schnydszch Version table:
03:13 schnydszch Candidate: 5:20.10.21~3-0~ubuntu-focal
03:13 schnydszch Installed: 5:20.10.21~3-0~ubuntu-focal
03:13 schnydszch docker-ce:
03:13 schnydszch WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
03:13 schnydszch root@ubuntu-s-2vcpu-4gb-sgp1-01:~# apt policy docker-ce | head
03:13 schnydszch OpenSSL version: OpenSSL 1.1.1f 31 Mar 2020
03:13 schnydszch CPython version: 3.8.10
03:13 schnydszch docker-py version: 4.1.0
03:13 schnydszch docker-compose version 1.25.0, build unknown
03:13 schnydszch root@ubuntu-s-2vcpu-4gb-sgp1-01:~# docker-compose version
03:13 mtj Installed: 5:20.10.18~3-0~debian-buster
03:12 mtj apt policy docker-ce | head
03:11 mtj Docker Compose version v2.10.2
03:11 mtj docker-compose version
03:11 mtj which docker-compose version?
03:10 schnydszch ubuntu 20.04
03:10 schnydszch 4GB ram, then another 4gb swap
03:10 mtj you are running debian/ubuntu?
03:10 mtj schnydszch: how much RAM does your system have?
03:08 mtj perhaps try to restart docker 1st
03:08 mtj /etc/init.d/docker restart
03:08 mtj hmm, a reboot would fix it :/
03:07 schnydszch now that is the error
03:07 schnydszch Error response from daemon: cannot stop container: f5e70168dfdcb8ddf84adda9800b6d602d93ebba54bd67e1ca9b9d123b5811b2: permission denied
03:07 schnydszch â ¿ Container koha-memcached-1 Error while Stopping 14.1s
03:07 schnydszch â ¿ Container koha_es_1 Error while Stopping 14.1s
03:07 schnydszch â ¿ Container koha_selenium_1 Error while Stopping 14.1s
03:07 schnydszch â ¿ Container koha-db-1 Error while Stopping 14.1s
03:07 schnydszch [+] Running 0/4
03:07 schnydszch tried kd
03:06 schnydszch echo "vm.max_map_count=262144" | sudo tee -a /etc/sysctl.conf
03:06 schnydszch # Make it permanent
03:06 schnydszch sudo sysctl -w vm.max_map_count=262144
03:06 schnydszch well added some swap then issued: # Increase vm.max_map_count
03:06 mtj perhaps we should fix the 'kd' alias to run twice :)
03:05 schnydszch hi mtj! It seems that was the problem. just deleted the first and trying out again
03:01 mtj i always run kd twice, when restarting - just to make sure :0)
02:59 mtj your system probably wants 3 gigs ram, to be happy
02:58 mtj then ku
02:58 mtj well, try control-c first, then kd; kd
02:57 mtj kd; kd
02:57 mtj schnydszch: try stopping , then starting again
01:54 schnydszch I added some swap into the system, re-run command "ku", now, this is what I am getting: Error response from daemon: cannot stop container: f1956468b9cdaefca5d8d6ca69e5a92333d138f66ba99a88a5e96406d3077b36: permission denied
00:53 schnydszch that's the last line where it is stucked. hmmm.. I already adjusted vm.max_map_count
00:52 schnydszch koha-es-1 | [2022-11-04T00:46:18,945][INFO ][o.e.l.LicenseService ] [9wAl3JA] license [8c9a77ac-4ace-4e3a-998e-dddd8fcf3332] mode [basic] - valid
00:52 schnydszch Hi all! I am still stuck with starting my kohadev