Time  Nick                 Message
23:44 kushineta            good night from my side
23:44 kushineta            it seems all are sleeping
23:44 kushineta            we have public project and we are interested to engage Koha , but we are newbe on this sector and we need help and support on this matter
23:41 kushineta            Do we have any partnering program with Koha
23:40 kushineta            hello there
21:37 tuxayo               <tcohen[m]> "right now the only way to tell..." <- If the labels could be edited by anyone that could work.
21:35 tuxayo               "see the dependency graph of an issue"
21:35 tuxayo               This one seem to get decent functional acceptance: https://codeberg.org/forgejo/forgejo/issues/446
21:32 tuxayo               And forĝejo
21:32 tuxayo               > file feature requests for Gitlab
21:32 tuxayo               bugzilla is really nice for this
19:57 tcohen[m]            there's no way to have a dashboard with things to re-do
19:57 tcohen[m]            or just silence
19:57 tcohen[m]            right now the only way to tell the author that things are not ok is a comment
19:57 tcohen[m]            so we can 'Fail QA' things
19:56 tcohen[m]            We need to file feature requests for Gitlab
19:09 tuxayo               A lot of the time, it will just fail to commit (or create a MR i'm not sure) due to that desync. Without giving a hint about the issue ^^"
18:44 ashimema             Yeah, it's a pain point of gitlab
18:27 tuxayo               Makes it's less quick to make string edits and less useful for non tech savvy users.
18:26 tuxayo               Too bad the gitlab online editor doesn't actually take the version of the file one clicked "edit" on (on the upstream repo). It goes take the old version from one's fork if it exists.
18:24 tuxayo               hi all ^^
18:24 tuxayo               tcohen++ thanks for the merge :)
18:00 cait                 tcohen++ # he knows why
17:46 cait                 ashimema++ khall++ # help with bug clean-up
16:59 Kolvir               it is the second error that is filling it, the first was just repeated at the ed when I 'tail' the log
16:58 Kolvir               actually, this message may be more prevalent main::catch {...}  /usr/share/koha/bin/workers/background_jobs_worker.pl (120) [2023/09/10 11:42:21] [WARN] Frame not processed - garbage after JSON object, at character offset 6 (before "must include a valid...") at /usr/share/koha/bin/workers/background_jobs_worker.pl line 118
16:56 Kolvir               any clues to fix it?
16:56 Kolvir               I'm getting this error in the worker-output log. It is repeating so often that the log has filled my HD at over 400 GB. Cannot connect to the message broker, the jobs will be processed anyway (Failed to connect: Error connecting to localhost:61613: Connection refused at /usr/share/perl5/Net/Stomp.pm line 27.; giving upat /usr/share/perl5/Net/Stomp.pm line 27. ) at /usr/share/koha/bin/workers/background_jobs_worker.pl line 90.
15:06 reiveune             bye
14:03 cait                 got to run, cya later #koha :)
13:53 tcohen[m]            ashimema++
13:45 caroline_catlady     lol
13:45 ashimema             LOL
13:45 * magnuse            needs dinner
13:45 magnuse              i vote for something subtle, like removing all occurences of the letter "a" in biblio.title, or disabling email for the instance
13:43 ashimema             so skipping was the easiest approach
13:43 ashimema             but I wasn't sure how or where to handle that
13:43 ashimema             the other thing I wasn't 100% happy about.. we just skip 'crap' lines.. we don't report that anywhere.. I wondered if we aught to
13:42 ashimema             I'm still testing it on a live system at the minute.. I was pretty darn confident until they said things weren't working in live.. I'm hoping it's something obvious
13:42 magnuse              ah, makes sense
13:42 ashimema             that's why I went this route
13:42 ashimema             I wanted to make it 100% backward compatible so people didn't need to update their existing configs
13:41 ashimema             but..
13:41 ashimema             so.. I agree
13:41 magnuse              nah, probably just me overthinking it
13:41 magnuse              would it make sense to use two different delimiters? like CPL;itype:eq:BK;ccode:eq:TEEN;3 or something?
13:39 huginn               magnuse: Quote #123: "rangi: #thingsihavelearnt if there is a mad scheme a library somewhere will be doing it ... except madder" (added by wizzyrea at 09:20 PM, March 30, 2011)
13:39 magnuse              @quote get 123
13:39 ashimema             I thought I'd caught all our weird and wonderful sorter configs with your patch.. but we had an upgrade challenge last week and I had to code this up in quick time 😜
13:37 magnuse              ah, cool
13:35 ashimema             an enhancement atop
13:35 huginn               04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34737 enhancement, P5 - low, ---, martin.renvoize, Needs Signoff , Enhance SIP2SortBinMapping to support additional match conditions
13:35 ashimema             bug 34737
13:34 magnuse              ashimema: no, a new one?
13:34 * magnuse            hides
13:34 cait                 hehe quick hide! (joking)
13:34 ashimema             did you see my sip sorter bug?
13:34 ashimema             margnuse
13:34 ashimema             oooh, oooh
13:34 ashimema             hehe
13:33 magnuse              the english words are clearer to me than any norwegian translations i can think of...
13:32 cait                 there is pelnty in that list
13:32 cait                 Contestant and Contestee
13:32 ashimema             I thought my vocabulary was pretty extensive.. always nice to learn a new word
13:32 MichaelaSieberBIB[m] caroline_catlady: hm, not really official
13:32 caroline_catlady     sorry, I just added a bunch recently :(
13:32 ashimema             thanks
13:32 ashimema             nice
13:31 cait                 and I think the rleator terms were not included (or I missed them?) - I might need to do some more reasearch
13:31 cait                 caroline_catlady: not an up to date one I know
13:31 caroline_catlady     A person or organization against whom an appeal is taken.
13:31 caroline_catlady     Appellee [ape]
13:31 caroline_catlady     A person or organization who appeals a lower court's decision.
13:31 caroline_catlady     Appellant [apl]
13:30 ashimema             asks the native english person of the native german regarding an english word
13:30 ashimema             never heard those words
13:30 ashimema             oooh.. what's that mean
13:30 caroline_catlady     Is there no official marc21 translation in german?
13:30 cait                 i so hope i got these all right
13:30 cait                 appellant and appellee
13:29 cait                 Asssignee
13:29 ashimema             πŸ™‚
13:29 caroline_catlady     appellee
13:29 caroline_catlady     good idea cait, the 4th one addressee
13:29 cait                 https://www.loc.gov/marc/relators/relaterm.html
13:28 cait                 I remember struggling there too with translating :)
13:28 ashimema             payee (the person you are paying)
13:28 cait                 caroline_catlady: i think the relator terms list has examples
13:28 ashimema             that's another example I suppose
13:28 ashimema             employer and employee
13:27 caroline_catlady     unless aude_c[m] do you have a better explanation? I see the email wsa sent to you and cc'd to the mailing list (not sure why, but *shrungs*)
13:27 ashimema             okies
13:27 caroline_catlady     Ok, I'll skip my -ee explanation and just say that it is used that way in legal texts and it's clear to english speakers
13:26 ashimema             okeis
13:25 caroline_catlady     there is no reason to change it in Koha in my opinion, since they are not used interchangeably. Guarantor is always guarantor and guarantee is always guarantee
13:25 ashimema             we didn't make up the word.. it's pretty standard
13:25 ashimema             we ddn't
13:25 ashimema             er..
13:25 ashimema             that's for money stuff though.. like when parents will guarantor their children allowing them to get a mortgage
13:24 caroline_catlady     I'm not looking for another word for guarantee, I'm looking for another example of -ee being used in the same way to explain how we came to guarantor/guarantee
13:24 ashimema             in UK law, we pretty much always call it Guarantor and Guarantee
13:23 caroline_catlady     I translated it as dependant in french (fr-CA) "personne Γ  charge"
13:23 ashimema             guarantor and dependants
13:23 ashimema             but it's not entirely the same
13:23 ashimema             'dependants' perhas
13:22 caroline_catlady     the only word I can think of right now is attendee, but it's not really a good example
13:22 ashimema             erm
13:21 caroline_catlady     I can't think of other examples, but it's a common way to form neologism
13:21 ashimema             indeed
13:21 ashimema             happy for them to be change so long as they're as clear as they are now.. haha
13:21 caroline_catlady     to me the -ee suffix is the person being impacted (?)
13:20 ashimema             I can't think of better terms..
13:19 caroline_catlady     They seem to be confused as well. I don't think it's confusing... but I've probably internalized it or something
13:19 ashimema             to me they're not synonyms at all
13:19 ashimema             I've never found it confusing
13:19 ashimema             erm..
13:18 cait                 because it's confusing
13:18 caroline_catlady     I think it's clear because of the -ee suffix, but I'm having trouble putting it into words to explain
13:18 cait                 i know we always get mistakes there in the translation
13:17 caroline_catlady     English speakers, there is a question on the french mailing list about guarantor/guarantee, they are asking if it's clear for english speakers that the guarantee is the guarantee of the guarantor the dictionary says guarantor and guarantee are synonyms (https://www.merriam-webster.com/dictionary/guarantee).
13:16 tcohen[m]            \o/
13:14 ashimema             mreged
13:14 ashimema             yup, i spotted
13:09 tcohen[m]            Jonathan's comment was adressed already
13:09 tcohen[m]            please do
12:59 ashimema             did you look at https://gitlab.com/koha-community/koha-testing-docker/-/merge_requests/469 tcohen?
12:57 ashimema             anywho.. I reckon both are safe to merge now
12:57 ashimema             I missed the whole docker-compose-light comment from Joubu
12:57 ashimema             ooh..
12:55 ashimema             I've approved and am happy to hit that merge button if you agree πŸ™‚
12:55 ashimema             just tried, all working here
12:52 ashimema             πŸ˜„
12:52 tcohen[m]            it is working nicely for me
12:52 tcohen[m]            I just made ENV override what's read from $KTD_HOME/.env
12:51 ashimema             nice one.. will take a look momentarily
12:50 tcohen[m]            ashimema:  I added a follow-up for the 'ktd on arm' pull request
12:07 cait                 hi Bela
11:40 Belal                hi everybody
11:23 tcohen[m]            hola #koha o/
11:12 cait                 we shoudl use them
11:12 cait                 i think they've always been empty
11:12 ashimema             okies
11:11 ashimema             hehe
11:11 ashimema             interesting.. what on earth are those empty fields for then?
11:11 cait                 hm inmpromptu meeting, will try to come back to that
11:11 ashimema             thanks
11:11 cait                 well you instictively did the right thing ;)
11:11 ashimema             yowsers
11:11 ashimema             I didn't spot that at all
11:10 cait                 yep
11:10 cait                 so that shoud work :)
11:10 ashimema             ho, really
11:10 cait                 only.. we don't use them
11:10 ashimema             it's in basket.pl
11:10 cait                 aqorders has 2 columsn with the same name
11:10 cait                 ... sorry, misread
11:10 ashimema             it's part of the patch
11:10 ashimema             I am pulled av category via the fund
11:10 ashimema             say again
11:10 cait                 which is silly because it could be changed... but...
11:09 cait                 you need to pull the AV category via the fund
11:09 cait                 it's like a long standing bug
11:09 ashimema             I must admit I'm struggling with them a bit for patch reviews
11:09 cait                 same for 2
11:09 cait                 sort1_authcat is always null
11:09 cait                 because... we don't use the fields you use :(
11:09 ashimema             these perltidy rules
11:09 cait                 I am sorry it's a fail
11:09 ashimema             will finish the one I'm on then swing onto yours πŸ™‚
11:08 ashimema             just been working through the QA email
11:08 ashimema             certainly
11:07 cait                 that's how I saw the issue - when i rebased mine on top
11:06 cait                 probably needs another rebase too then
11:06 cait                 ashimema: i could do that... can you then QA mine tht is now dependent on it?
10:56 huginn               04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34752 enhancement, P5 - low, ---, martin.renvoize, Needs Signoff , Use AV descriptions in display for sort1/sort2 in basket display
10:56 ashimema             bug 34752
10:56 huginn               04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34618 enhancement, P5 - low, ---, oleonard, Passed QA , Add sort 1 and 2 fields to basket in acquisitions
10:56 ashimema             thanks for the catch on bug 34618.. I totally forgot those fields could be tied to an AV..  I've added a follow-up bug to handle it if you fancied a quick QA of it
10:55 ashimema             cait
08:18 cait                 good morning all
08:18 MatthewBlenkinsop[m] o/
03:54 * fridolin           waves back ;)
03:54 * dcook              waves to fridolin
03:53 fridolin             yellow