← Previous day | Today | Next day → | Search | Index
All times shown according to UTC.
| Time | Nick | Message |
|---|---|---|
| 03:53 | fridolin joined #koha | |
| 03:53 | fridolin | yellow |
| 03:54 | * dcook | waves to fridolin |
| 03:54 | * fridolin | waves back ;) |
| 05:05 | fridolin1 joined #koha | |
| 05:34 | fridolin1 left #koha | |
| 06:36 | magnuse joined #koha | |
| 06:36 | cait joined #koha | |
| 06:43 | reiveune joined #koha | |
| 07:07 | cait joined #koha | |
| 08:18 | MatthewBlenkinsop[m] | o/ |
| 08:18 | cait | good morning all |
| 09:46 | dpk_ joined #koha | |
| 10:55 | ashimema | cait |
| 10:56 | 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:56 | huginn | 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=34618 enhancement, P5 - low, ---, oleonard, Passed QA , Add sort 1 and 2 fields to basket in acquisitions |
| 10:56 | ashimema | bug 34752 |
| 10:56 | huginn | 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=34752 enhancement, P5 - low, ---, martin.renvoize, Needs Signoff , Use AV descriptions in display for sort1/sort2 in basket display |
| 11:06 | cait | ashimema: i could do that... can you then QA mine tht is now dependent on it? |
| 11:06 | probably needs another rebase too then | |
| 11:07 | that's how I saw the issue - when i rebased mine on top | |
| 11:08 | ashimema | certainly |
| 11:08 | just been working through the QA email | |
| 11:09 | will finish the one I'm on then swing onto yours 🙂 | |
| 11:09 | cait | I am sorry it's a fail |
| 11:09 | ashimema | these perltidy rules |
| 11:09 | cait | because... we don't use the fields you use :( |
| 11:09 | sort1_authcat is always null | |
| 11:09 | same for 2 | |
| 11:09 | ashimema | I must admit I'm struggling with them a bit for patch reviews |
| 11:09 | cait | it's like a long standing bug |
| 11:09 | you need to pull the AV category via the fund | |
| 11:10 | which is silly because it could be changed... but... | |
| 11:10 | ashimema | say again |
| 11:10 | I am pulled av category via the fund | |
| 11:10 | it's part of the patch | |
| 11:10 | cait | ... sorry, misread |
| 11:10 | aqorders has 2 columsn with the same name | |
| 11:10 | ashimema | it's in basket.pl |
| 11:10 | cait | only.. we don't use them |
| 11:10 | ashimema | ho, really |
| 11:10 | cait | so that shoud work :) |
| 11:10 | yep | |
| 11:11 | ashimema | I didn't spot that at all |
| 11:11 | yowsers | |
| 11:11 | cait | well you instictively did the right thing ;) |
| 11:11 | ashimema | thanks |
| 11:11 | cait | hm inmpromptu meeting, will try to come back to that |
| 11:11 | ashimema | interesting.. what on earth are those empty fields for then? |
| 11:11 | hehe | |
| 11:12 | okies | |
| 11:12 | cait | i think they've always been empty |
| 11:12 | we shoudl use them | |
| 11:15 | khall joined #koha | |
| 11:23 | tcohen[m] | hola #koha o/ |
| 11:40 | Belal joined #koha | |
| 11:40 | Belal | hi everybody |
| 12:07 | cait | hi Bela |
| 12:46 | Dyrcona joined #koha | |
| 12:50 | tcohen[m] | ashimema: I added a follow-up for the 'ktd on arm' pull request |
| 12:51 | Dyrcona joined #koha | |
| 12:51 | ashimema | nice one.. will take a look momentarily |
| 12:52 | tcohen[m] | I just made ENV override what's read from $KTD_HOME/.env |
| 12:52 | it is working nicely for me | |
| 12:52 | ashimema | 😄 |
| 12:55 | just tried, all working here | |
| 12:55 | I've approved and am happy to hit that merge button if you agree 🙂 | |
| 12:57 | ooh.. | |
| 12:57 | I missed the whole docker-compose-light comment from Joubu | |
| 12:57 | anywho.. I reckon both are safe to merge now | |
| 12:59 | did you look at https://gitlab.com/koha-commun[…]erge_requests/469 tcohen? | |
| 13:09 | tcohen[m] | please do |
| 13:09 | Jonathan's comment was adressed already | |
| 13:14 | ashimema | yup, i spotted |
| 13:14 | mreged | |
| 13:15 | jalway joined #koha | |
| 13:16 | tcohen[m] | \o/ |
| 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.co[…]ionary/guarantee). |
| 13:18 | cait | i know we always get mistakes there in the translation |
| 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 | because it's confusing |
| 13:19 | ashimema | erm.. |
| 13:19 | I've never found it confusing | |
| 13:19 | to me they're not synonyms at all | |
| 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:20 | ashimema | I can't think of better terms.. |
| 13:21 | caroline_catlady | to me the -ee suffix is the person being impacted (?) |
| 13:21 | ashimema | happy for them to be change so long as they're as clear as they are now.. haha |
| 13:21 | indeed | |
| 13:21 | caroline_catlady | I can't think of other examples, but it's a common way to form neologism |
| 13:22 | ashimema | erm |
| 13:23 | caroline_catlady | the only word I can think of right now is attendee, but it's not really a good example |
| 13:23 | ashimema | 'dependants' perhas |
| 13:23 | but it's not entirely the same | |
| 13:23 | guarantor and dependants | |
| 13:23 | caroline_catlady | I translated it as dependant in french (fr-CA) "personne à charge" |
| 13:24 | ashimema | in UK law, we pretty much always call it Guarantor and Guarantee |
| 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:25 | ashimema | that's for money stuff though.. like when parents will guarantor their children allowing them to get a mortgage |
| 13:25 | er.. | |
| 13:25 | we ddn't | |
| 13:25 | we didn't make up the word.. it's pretty standard | |
| 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:26 | ashimema | okeis |
| 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:27 | ashimema | okies |
| 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:28 | ashimema | employer and employee |
| 13:28 | that's another example I suppose | |
| 13:28 | cait | caroline_catlady: i think the relator terms list has examples |
| 13:28 | ashimema | payee (the person you are paying) |
| 13:28 | cait | I remember struggling there too with translating :) |
| 13:28 | lds joined #koha | |
| 13:29 | cait | https://www.loc.gov/marc/relators/relaterm.html |
| 13:29 | caroline_catlady | good idea cait, the 4th one addressee |
| 13:29 | appellee | |
| 13:29 | ashimema | 🙂 |
| 13:29 | cait | Asssignee |
| 13:30 | appellant and appellee | |
| 13:30 | i so hope i got these all right | |
| 13:30 | caroline_catlady | Is there no official marc21 translation in german? |
| 13:30 | ashimema | oooh.. what's that mean |
| 13:30 | never heard those words | |
| 13:30 | asks the native english person of the native german regarding an english word | |
| 13:31 | caroline_catlady | Appellant [apl] |
| 13:31 | A person or organization who appeals a lower court's decision. | |
| 13:31 | Appellee [ape] | |
| 13:31 | A person or organization against whom an appeal is taken. | |
| 13:31 | cait | caroline_catlady: not an up to date one I know |
| 13:31 | and I think the rleator terms were not included (or I missed them?) - I might need to do some more reasearch | |
| 13:32 | ashimema | nice |
| 13:32 | thanks | |
| 13:32 | caroline_catlady | sorry, I just added a bunch recently :( |
| 13:32 | MichaelaSieberBIB[m] | caroline_catlady: hm, not really official |
| 13:32 | ashimema | I thought my vocabulary was pretty extensive.. always nice to learn a new word |
| 13:32 | cait | Contestant and Contestee |
| 13:32 | there is pelnty in that list | |
| 13:33 | magnuse | the english words are clearer to me than any norwegian translations i can think of... |
| 13:34 | ashimema | hehe |
| 13:34 | oooh, oooh | |
| 13:34 | margnuse | |
| 13:34 | did you see my sip sorter bug? | |
| 13:34 | cait | hehe quick hide! (joking) |
| 13:34 | * magnuse | hides |
| 13:34 | magnuse | ashimema: no, a new one? |
| 13:35 | ashimema | bug 34737 |
| 13:35 | huginn | 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=34737 enhancement, P5 - low, ---, martin.renvoize, Needs Signoff , Enhance SIP2SortBinMapping to support additional match conditions |
| 13:35 | ashimema | an enhancement atop |
| 13:37 | magnuse | ah, cool |
| 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:39 | magnuse | @quote get 123 |
| 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:41 | magnuse | would it make sense to use two different delimiters? like CPL;itype:eq:BK;ccode:eq:TEEN;3 or something? |
| 13:41 | nah, probably just me overthinking it | |
| 13:41 | ashimema | so.. I agree |
| 13:41 | but.. | |
| 13:42 | I wanted to make it 100% backward compatible so people didn't need to update their existing configs | |
| 13:42 | that's why I went this route | |
| 13:42 | magnuse | ah, makes sense |
| 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:43 | 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:43 | but I wasn't sure how or where to handle that | |
| 13:43 | so skipping was the easiest approach | |
| 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:45 | * magnuse | needs dinner |
| 13:45 | ashimema | LOL |
| 13:45 | caroline_catlady | lol |
| 13:53 | tcohen[m] | ashimema++ |
| 14:03 | cait | got to run, cya later #koha :) |
| 14:03 | cait left #koha | |
| 15:00 | bag joined #koha | |
| 15:06 | reiveune | bye |
| 15:06 | reiveune left #koha | |
| 16:55 | Kolvir joined #koha | |
| 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. |
| 16:56 | any clues to fix it? | |
| 16:58 | 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:59 | it is the second error that is filling it, the first was just repeated at the ed when I 'tail' the log | |
| 17:28 | cait joined #koha | |
| 17:46 | cait | ashimema++ khall++ # help with bug clean-up |
| 18:00 | tcohen++ # he knows why | |
| 18:24 | tuxayo | tcohen++ thanks for the merge :) |
| 18:24 | hi all ^^ | |
| 18:26 | 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:27 | Makes it's less quick to make string edits and less useful for non tech savvy users. | |
| 18:44 | ashimema | Yeah, it's a pain point of 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 ^^" |
| 19:56 | tcohen[m] | We need to file feature requests for Gitlab |
| 19:57 | so we can 'Fail QA' things | |
| 19:57 | right now the only way to tell the author that things are not ok is a comment | |
| 19:57 | or just silence | |
| 19:57 | there's no way to have a dashboard with things to re-do | |
| 21:32 | tuxayo | bugzilla is really nice for this |
| 21:32 | > file feature requests for Gitlab | |
| 21:32 | And forĝejo | |
| 21:35 | This one seem to get decent functional acceptance: https://codeberg.org/forgejo/forgejo/issues/446 | |
| 21:35 | "see the dependency graph of an issue" | |
| 21:37 | <tcohen[m]> "right now the only way to tell..." <- If the labels could be edited by anyone that could work. | |
| 23:05 | dcook_ joined #koha | |
| 23:40 | kushineta joined #koha | |
| 23:40 | kushineta | hello there |
| 23:41 | Do we have any partnering program with Koha | |
| 23:44 | 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:44 | it seems all are sleeping | |
| 23:44 | good night from my side | |
| 23:55 | khall joined #koha |
← Previous day | Today | Next day → | Search | Index