Time Nick Message 07:18 ibnsina[m] hello guys when enable <useldapserver>1<useldapserver> and login its return error 500... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/FpbKkAObIuOncHcDjvZMiajj>) 07:48 cait oh so many caits 07:49 cait good morning #koha 08:16 ashimema mornin' 08:39 magnuse_ \o/ 09:45 ashimema terminology wise.. 09:45 ashimema I'm confused.. is it Bookseller or Vendor these days.. 09:45 ashimema the classes seem to map from Vendor to Bookseller.. which feels the wrong way around to me somehow 09:46 ashimema api calls it Vendor 09:46 ashimema I'm going to stick with that 09:49 Joubu yes, it should be vendor everywhere 09:49 ashimema thanks 09:49 ashimema weird that we still ave Koha::Acquisition::Bookseller class 09:49 ashimema must just be leftovers 09:51 Joubu One of the first Koha::Object, 2014 09:51 Joubu Bug 12896: Move the bookseller-related code into Koha::Acquisition::Bookseller 09:51 huginn` 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12896 normal, P5 - low, ---, jonathan.druart+koha, CLOSED FIXED, Move the bookseller-related code into its own module 09:51 Joubu I guess we didn't enforce the naming yet 09:51 ashimema ha.. that'll be it 🙂 09:52 Joubu the first verion in 2014 wasn't using Koha::Object yet actually :D it didn't exist 09:52 Joubu anyway, yes, should be renamed ;) 09:53 ashimema hmm 09:53 ashimema yeah 09:53 ashimema I can take a look some time 09:53 * ashimema has a weird testbuild failure now.. 09:53 Joubu what's the error? 09:54 ashimema me being an idiot 😜 09:54 ashimema calling ->build on a Koha object class.. instead of build_object 10:04 thibaud_g hi everyone 10:04 cait ashimema: https://wiki.koha-community.org/wiki/Terminology - one of our nicest looking wiki pages :) 10:05 cait and yes, vendor 10:05 ashimema yeah 10:05 ashimema I shouldn't have been lazy 10:06 cait I am just using this to have a reason to post the link again 10:17 ashimema My brain is slow today.. 10:17 ashimema if I want a user with acquisitions -> edi_manage for a test 10:18 ashimema whats the bitmask for that.. 10:18 ashimema looks like acq is bit 11 10:21 Joubu 1 << 11, is that what you are looking for? 10:22 Joubu you may need 4 to login as well 10:22 ashimema ta# 10:22 ashimema yes 10:22 ashimema my brain was slow today 10:25 ashimema ooh 10:26 ashimema the cities api tests are no longer a good reference really 10:26 ashimema we encourage use of q= for queries now.. not adding each field as a query param in it's own right 10:27 cait i'd like to add a keyword for the roadmap projects to bugzilla - any ideas for a good nameß 10:27 cait ? 10:28 Joubu roadmap_24.05 10:28 Joubu ashimema: where are you looking at? paths/cities.yaml? 10:28 Joubu things seem correct threr 10:28 ashimema t/db_dependant/api/v1/cities.t 10:28 cait road_map_24_05 maybe to keeep in line with the syntax of the rel candiates? 10:28 ashimema yes.. it's correct 10:29 ashimema in that it tests what we support on that endpoint 10:29 ashimema but our current best practice is not to list every field as it's own query param in the path schema 10:29 Joubu isn't roadmap a word? 10:29 ashimema instead I think we now encourage the use of q=json_encoded query string 10:29 Joubu ha roadmap_24_05 you meant 10:29 ashimema roadmap is a word here 10:31 Joubu it's how it is in patrons.yaml as well 10:31 ashimema yeah 10:31 ashimema legacy 10:31 ashimema and we probably don't want to get rid of it 10:31 ashimema just saying as cities was our 'best practice'.. but it's not entirely perfect to copy for tests in this case 😜 10:31 Joubu if it's in Cities and Patrons, where should we look at to get a good examples then? :D 10:32 Joubu please reply "this wikipage we are keeping up-to-date for happy devs" 10:32 Joubu ;) 10:33 ashimema lol 10:33 ashimema pass 10:33 cait i looked it up, only found road map 10:34 cait but ther e is both in the wiki... 10:34 cait apparently both is correct, dpeending on which dictionary you use 10:36 cait with a tendency to roadmap in more modern times *shrugs* 10:40 ashimema you wanted roadmap stuff to only go on the roadmap once there's commitment right cait 10:41 ashimema did you want me to use the keyword to add to the dashboard based on some params beyond the keyword? 10:41 ashimema like roadmap + assignee + qa contact + sponsored? 11:12 cait let's discuss that again a little later? I like the idea but have to think about it 11:19 oleonard o/ 11:23 oleonard Joubu still around? 11:23 Joubu yes 11:23 oleonard I've been looking at Bug 27572 (and 35319) 11:23 huginn` 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27572 enhancement, P5 - low, ---, koha-bugs, NEW , Move OpacLocationBranchToDisplay system preference into table settings 11:24 oleonard We could get rid of OPACHoldingsDefaultSortField and OpacLocationBranchToDisplay if we switched to table configuration... 11:24 oleonard But the template conditionally displays columns based on whether they have data 11:24 oleonard I think this is something you encountered with your work on the detail page in the staff interface 11:25 Joubu yes 11:25 oleonard It looks like we would have remove the template logic and hide columns with settings? Or perhaps conditionally modify the settings before passing them to Kohatable? 11:26 oleonard I know it's not exactly the same situation 11:27 Joubu I... am not sure I have written something for this specific case 11:28 oleonard I'm happy to keep tinkering, but I wanted to make sure I wasn't trying to solve a problem you'd already solved 11:28 Joubu to make sure I understand the problem: you are not sure what to do if OPACHoldingsDefaultSortField is set to a given column but the column is hidden because empty, is that correct? 11:29 oleonard Yes 12:18 cait oleonard: when I tested the API version sof the detail page the hidden column is one of the things/problems I came across. When the field is not filled on the first page, it won't show up at all (the column will be hidden) - it was one of the points I think we need to discuss 13:09 * oleonard thinks he has a working solution 13:10 Joubu cait: we discussed it already, it's not possible to fix. 13:11 cait Joubu: it depends on what the fix would be - we could give up on displaying only what is filled... or we can keep your current behaviour... or we can come with a solution we haven#t thought about yet :) but I undersatnd that looking at the whole data set beforehand doesn't work 13:12 Joubu we cannot display empty columns, that will be too many columns displayed. 13:14 cait we could rely on the library to decide what oclumns to display (table config) 13:14 cait but yah... like enumchron always displaying etc (which they would want) it might not work 13:18 Shane-NP[m] back with my kiosk question, so in my office I have a wall mounted chromebook that I have in a Managed Guest Session, it logs itself in and goes to specific URL, in this case my Koha OPAC. I setup a special user for it in Koha with access to circulation. It is a touch screen device and I CAN login, but the glass is cracked, and I want to know if I can push a Username and Password to OPAC via URL 13:19 Shane-NP[m] It is for my use only at my repair station so I can check-in/out devices as I work on them. If not I might just resort to wireless keyboard and mouse...but thats extra wall/desk space I don't really have when I have 2-3 chromebooks in pieces. 13:22 ashimema I don't think you'll be able to just put it in the url 13:22 ashimema we do support http basic auth I think still 13:24 Shane-NP[m] I wish it would allow me to save the username and password, but being a "guest" style account it won't save. I have hoping I could do something like ?userid=username&password=md5hash(orwhatever encyption I need) 13:25 ashimema https://developer.mozilla.org/en-US/docs/Web/HTTP/Authentication#access_using_credentials_in_the_url 13:25 ashimema most browsers even strip it out of the url 13:29 Shane-NP[m] Oh I was looking more the GET vs POST method, which I know isn't "secure" as you see the encryption of the password, but I doubt anyone but me will see it and it is a special access account, its it opened for the user, and if the site logs in and re-directs, then the URL will change. Yes I know it will reside in the "history" but again in my private office, for a internal system (no book data, just my devices) 13:42 Shane-NP[m] looks like re-write code or spend $40 on wireless keyboard and mouse...I like option 2 more :) 13:43 Shane-NP[m] Now I just need a wall mount extending tray.... 14:35 krimsonkharne[m] hey #koha 15:14 davidnind Draft agenda for this week's development meeting added, please update any action items (apologies for not adding sooner): https://wiki.koha-community.org/wiki/Development_IRC_meeting_15_November_2023 15:42 Joubu PedroAmorim[m]: why not backporting bug 35284? 15:42 huginn` 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35284 major, P5 - low, ---, jonathan.druart+koha, RESOLVED FIXED, No more delay between 2 DT requests 15:44 lukeg Hi 16:04 PedroAmorim[m] Joubu: I decided not to backport because at a glance it looked too involved for oldstable, but can revisit it if needed 16:06 reiveune bye 16:44 PedroAmorim[m] Joubu: looks like I'll have to revisit it indeed, selenium/patrons_search.t is failing on 22.11.x and I'm now catching up with the topic 16:53 caroline when a job fails, is it logged somewhere what made it fail? 17:06 tcohen[m] Jenkins has a report on the filing tests 17:06 ashimema Jenkins is bloomin busy today 17:06 tcohen[m] and you usually guess from the color change 19:29 emilyrose Hi everyone, I'm installing koha-testing-docker and I need some help. I keep encountering this error when I run 'ktd up': The environment variable SYNC_REPO does not point to a valid Koha git repository. I observed in the code within the 'run.sh' file of ktd that this error occurs because the script is unable to locate /kohadevbox/koha/about.pl. I don't know how to resolved this 19:31 oleonard-away emilyrose: I hit that issue just yesterday, so I sympathize 19:32 oleonard What is your host platform? PC? Mac? 19:32 emilyrose Pc ubuntu 19:33 oleonard Have you tried to see what SYNC_REPO is set to? echo $SYNC_REPO ? 19:34 emilyrose yes I set it to my Koha git repository (/inlibro/git/koha) 19:35 oleonard But have you confirmed that $SYNC_REPO is evaluating correctly with that value? I've run into problems where KTD didn't find my .bashrc for instance 19:37 emilyrose yes when I do echo $SYNC_REPO, the returned value is /inlibro/git/koha 19:38 oleonard And /inlibro/git/koha is the root directory of your Koha repo? 19:38 emilyrose yes 19:38 oleonard Okay, I guess I haven't seen that particular variation of the problem... 19:42 oleonard I see what run.sh is doing... is about.pl not in that location? 19:44 emilyrose about.pl is in my koha folder but it seems that it can't locate C4::Output, maybe that is the problem 19:45 oleonard If the "ktd up" process was aborted about.pl isn't going to work. 19:46 oleonard sorry emilyrose I'm not an expert so I'm out of ideas 19:47 oleonard You'll find more people around when Europe wakes up again 19:48 emilyrose ok thank you, I will retry tomorow 21:04 pastebot "davidnind" at 127.0.0.1 pasted "emilyrose: my settings for KTD using Ubuntu 22.04" (12 lines) at https://paste.koha-community.org/29504 21:06 caroline thanks davidnind! I passed it on :) 21:13 cait hm if hte ktd up failed, maybe try a ktd down... I had problems with my first time star-up on ktd in the past, sometimes it also resolves after a reboot (or restart of the terminal) 21:19 davidnind good point cait! I do it automatically now... 21:20 cait I just yesterday forgot to restart the terminal after a change to bashrc, it's fresh on my mind ;) 21:22 caroline you can do source ~/.bashrc if you don't want to close your terminal 21:28 davidnind some history about roadmaps (or road maps): https://blogs.bl.uk/magnificentmaps/2021/02/a-roadmap-of-understanding-the-term-roadmap.html 21:31 caroline interesting! 21:32 caroline archive maps are always so fascinating 21:33 caroline (I especially like the fold out one pictured... like oops, I don't have enough room, I'll just add this random piece of paper so I can continue mapping XD) 21:33 caroline 13th century post its... 21:36 davidnind good spotting! no "here be dragons" though... 21:38 cait :) 22:37 tuxayo @later tell mtj for some reason no ES or OS build since a month. And fresh, news: ES 8 and OS 2 support and ES 6 should fail but let's see. 22:37 huginn` tuxayo: The operation succeeded. 22:39 mtj tuxayo: ES* and OS* builds are downstream from master build 22:39 mtj https://jenkins.koha-community.org/view/master/job/Koha_Master/ 22:40 mtj ...they are only built when master build passes 22:41 mtj last master build to pass was... Last stable build (#2678), 1 mo 5 days ago 23:16 tuxayo «they are only built when master build passes» 23:16 tuxayo oh, that's why :( 23:17 tuxayo mtj: thanks, so that's also why they are marked a disabled 23:19 mtj OS2 build is disabled, others are enabled 23:19 mtj https://jenkins.koha-community.org/view/master/ 23:20 mtj ES8 is disabled too 23:21 mtj tuxayo: i think they have historically been broken, so no point enabling them until they are fixed :) 23:24 * mtj starts an ES8 and OS2 build