Time  Nick           Message
00:00 aleisha        thanks for starting davidnind !
00:00 davidnind      only 136 steps to go!!:-D
00:00 aleisha        heh is quite a hefty test plan
00:05 oleonard       aleisha FYI it looks like a change to smart-rules.tt within the last 24 hours is causing a conflict, but nothing I couldn't resolve
00:05 oleonard       aleisha: Might be good to rebase again anyway :(
00:10 oleonard       davidnind I thought "136 steps to go" was a joke!!
00:10 dcook          Whoa there are humans around
00:11 dcook          oleonard: Nice tinkering
00:11 hayley         not a joke! it's a very thorought est plan :
00:11 hayley         wow
00:12 hayley         thorough test plan :)
00:12 aleisha        dang oleonard, ill take a look tomorrow
00:14 davidnind      oleonard: some are pretty straight forward though, am testing in smaller chunks to break it up.
00:15 * oleonard     dives in too
00:35 oleonard       aleisha++
00:49 tuxayo         aleisha, are branches on an external repo more suited for bugs with many patches that often conflict?
00:49 tuxayo         I fear missing something important when scrolling through the 500 comments.
00:50 tuxayo         Or maybe just reading the firsts, the lasts, the wiki page and the commit messages i enough?
00:50 tuxayo         It could make rebase easier. Just force push when it's done ^^
00:52 aleisha        sorry tuxayo what do you mean by an external repo?
00:57 tuxayo         bug 20271
00:57 huginn         Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20271 enhancement, P1 - high, ---, jonathan.druart, Signed Off , Merge deleted biblio, biblioitems, biblio_metadata, and items tables
00:57 tuxayo         https://gitlab.com/joubu/Koha/commits/bug_20271
00:58 tuxayo         Jonathan hosts the patch here
00:59 tuxayo         That case is more extreme. The patches are so large that bugzilla refuses them. So I don't know if the incentives are enough there in your case.
01:00 tuxayo         https://gitlab.com/joubu/Koha/activity
01:00 tuxayo         Nine pushes in the last 2.5 months
01:02 * oleonard     makes it to step 18 too
01:10 aleisha        hmm im not sure
01:10 aleisha        i think once it is through it wont be a problem because only a small chunk of it will cause conflicts, in the circulation module
01:19 tuxayo         Indeed, if in the next weeks, the relevant parts of Koha don't conflict much it wouldn't have been worth it.
01:22 aleisha        yes i agree. other patches will need to be rebased on top of it but i think that's an easier ask than moving everything to an external repo
01:26 tuxayo         The external repo thing is only during the phase before going in master. Once in master, nothing to worry about
06:37 reiveune       hello
06:37 wahanui        privet, reiveune
06:46 alex_a         Bonjour
07:48 nlegrand       Ahoj.
07:57 cait2          hi nlegrand
08:32 nlegrand       Salut cait2
09:01 magnuse        see you in august, #koha!
10:25 oleonard       Hi all
11:43 oleonard       Halfway through the recalls test plan *whew*
11:44 davidnind      you are way ahead of me!
11:44 oleonard       davidnind that's strange considering you appear to have been awake for... 98 hours? ;)
11:47 davidnind      hehe - had to do some work work :)
12:18 tcohen         morning
12:21 oleonard       Hi tcohen
12:45 ashimema       ooh.. the weird Jenkins failure that now haunts us.. I got that when I first tested jajm's critic fixes.. but couldn't replicate it when I came back to it
12:46 ashimema       I couldn't work out what was doing a copy of the qa-tests-tools into kohaclone
12:46 ashimema       and yeah.. failed to replicate it :(
13:18 eythian        hi
13:18 wahanui        bonjour, eythian
13:40 eythian        Someone needs to get andreashm a reliable internet connection :)
13:47 tcohen         LOL
14:07 tcohen         do we have coding guidelines for index names?
14:39 juanyo         Hello, can anyone help us with the koha email and notification system?
14:50 tuxayo         hi juanyo state your question. Hopefully someone will have cues.
14:51 tuxayo         If not, you can retry after some hours. And after that there are the mailing lists.
14:52 juanyo         thank you!.hello, the email system of our koha installation is not working, we want to enable it again but we are afraid that it will send massive mail. is there any way to disable that pending email queue?
14:57 sophie_m       juanyo: pending email are in table message_queue, you can truncate this table or just delete records you don't want to send
15:01 juanyo         thank you very much!
15:23 lisettelatah   hi cait
16:26 oleonard       So tell me, what is y'all's favorite thing about the XPM image format? I think mine is that it doesn't really exist.
16:30 tuxayo         oleonard: this ? https://en.wikipedia.org/wiki/X_PixMap
16:30 oleonard       Our local cover image upload page says that it accepts XPM images
16:31 oleonard       I have not managed to create an XPM image which it accepts
16:31 oleonard       Also, what Koha user on Earth in the year twenty twenty is uploading book covers in XPM format?
16:32 oleonard       At the very least we shouldn't say we accept the format because its WEIRD
16:37 tuxayo         > Also, what Koha user on Earth in the year twenty twenty is uploading book covers in XPM format?
16:37 tuxayo         Indeed!
16:37 tuxayo         > At the very least we shouldn't say we accept the format because its WEIRD
16:37 tuxayo         That's mean!
16:37 * oleonard     is known for being very mean
16:41 * oleonard     files a bug to restore XPM format support in cover image uploads and marks it CRITICAL
16:52 oleonard       https://zivotdesign.com/p/view.php?p=15935359246340
16:53 oleonard       (boss if you're reading this I promise I paused my work timer to make that)
16:59 reiveune       bye
17:01 tuxayo         > bug to restore XPM format support in cover image uploads and marks it CRITICAL
17:01 tuxayo         what a change of mind
17:05 tuxayo         That would be a good April fools bug ^^
17:05 tuxayo         Including the promotional animation, Koha RFCs are outdated, memes are more efficient.
17:12 * oleonard     runs off to work the circulation desk for the first time in three months
17:16 tuxayo         Patrons! They still exist! :o
18:36 * cait         waves
18:37 cait           oh now i missed oleonard-away
18:38 cait           and i am still wondering about the mysterious xpm
18:38 * CrispyBran   slaps CrispyBran with a rainbow trout
19:01 * CrispyBran   waves
19:07 cait           ouch?
19:08 CrispyBran     cait, did you hurt yourself?
19:09 cait           the rainbow trout slapping you did to yourself sounded painful
19:09 CrispyBran     It was better than a brick.
19:10 cait           i will not ask about that
19:26 koha-jenkins   Project Koha_19.05_D8 build #251: FAILURE in 2 min 2 sec: https://jenkins.koha-community.org/job/Koha_19.05_D8/251/
19:28 koha-jenkins   Project Koha_19.05_D9 build #245: FAILURE in 3 min 4 sec: https://jenkins.koha-community.org/job/Koha_19.05_D9/245/
19:31 * oleonard     waves to cait
19:37 koha-jenkins   Project Koha_19.05_U18 build #247: FAILURE in 9 min 51 sec: https://jenkins.koha-community.org/job/Koha_19.05_U18/247/
19:37 koha-jenkins   Project Koha_19.05_U18 build #248: STILL FAILING in 29 sec: https://jenkins.koha-community.org/job/Koha_19.05_U18/248/
19:37 tuxayo         hmmm
19:37 tuxayo         tcohen: around? ^^"
19:39 tuxayo         And somehow, it magically tried to built twice the Ubuntu 18.04 build when only one push was done. (in case that info helps)
19:39 tuxayo         https://jenkins.koha-community.org/view/19.05/job/Koha_19.05_U18/
19:39 tuxayo         *build
20:52 aleisha        hi
20:52 wahanui        salut, aleisha
21:15 * CrispyBran   waves a fish at lisettelatah
21:16 * lisettelatah waves at CrispyBran and his fish
21:34 lukeG          Hi Koha!
21:34 wahanui        somebody said Hi Koha! was there a table in which i can see if a borrower has borrowed any books (or if library lended out any books) ?
21:35 lukeG          Has anyone ever encountered this error when starting a new Koha Testing Docker:
21:35 lukeG          ERROR: The Compose file './docker-compose.yml' is invalid because:
21:35 lukeG          services.koha.networks.kohanet contains non-unique items, please remove duplicates from ['', '']
21:35 tuxayo         lukeG: is your `.env` file there?
21:35 tuxayo         At the root of the KTD
21:37 lukeG          ah ha tuxayo!
21:37 lukeG          Now there is!!! Thanks
21:38 tuxayo         Very obvious from the error message!
21:39 tuxayo         I and then lisettelatah had the same issue and it took some time to find the cause ^^
21:40 tuxayo         BTW lisettelatah were you able to use koha-testing-docker ?
21:41 lukeG          kd
21:41 lukeG          oops :)
21:42 lisettelatah   tuxayo not yet. We ended up opening this week and it seriously delayed my ability to get back to testing it last week.
21:42 tuxayo         everything shuts down
21:42 tuxayo         lukeG: what have you done!!! :o
21:43 tuxayo         ku
21:44 tuxayo         pfiou. Hopefully no one noticed :P
21:46 tuxayo         lisettelatah: hopefully, no more issues. Because the environment should be quite standard now that the container can start.
21:47 lisettelatah   tuxayo I did a git pull and updated a file but I'm still getting the same "no such file or directory" issue.
21:57 aleisha        hey everyone, does anyone know what might be causing (or how to fix) this error in the devbox? Error while loading /etc/koha/sites/kohadev/plack.psgi: Can't load application from file "/home/vagrant/kohaclone/api/v1/app.pl": [JSON::Validator] GET http://swagger.io/v2/schema.json == Connect timeout at /usr/share/perl5/JSON/Validator.pm line 343.
22:07 tuxayo         aleisha: related to Bug 23653
22:07 huginn         Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23653 major, P5 - low, ---, tomascohen, In Discussion , Plack stopped working - JSON validation timeout
22:16 tuxayo         aleisha: is the error persistent? Or just transient?
22:17 aleisha        persistent tuxayo
22:17 aleisha        thanks for the bug link! just reading now
22:18 lukeG          Anyone know how to fix this one:
22:18 lukeG          koha_1       |
22:18 lukeG          koha_1       | chown: cannot access '/var/cache/koha/kohadev': No such file or directory
22:18 lukeG          koha_koha_1 exited with code 1
22:18 lukeG          Lots of devbox problems today!
22:18 tuxayo         lukeG: `cd /kohadevbox/koha`
22:21 tuxayo         aleisha: indeed, http://swagger.io/v2/schema.json doesn't load for me either. This is bad.
22:21 tuxayo         Not only our tests will fail, but many peoples, plack won't start. In production also! 😱😱
22:22 tuxayo         lukeG: the cause of your last issue was bug 25752
22:22 huginn         Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25752 major, P5 - low, ---, jonathan.druart, Signed Off , Current directory not kept when using koha-shell
22:25 tuxayo         lukeG: you should expect to hit the same issue as aleisha
22:26 aleisha        super weird tuxayo
22:26 tuxayo         I have it also I koha-testing-docker. Some schema validation is not reachable so we can't start plack without workarounds T_T
22:27 tuxayo         IIUC a validation file was provided by a Debian package, it's not the case. So everyone up to date need to have it from swagger.io. But it's down.
22:28 tuxayo         Is that a correct summary?
22:28 aleisha        https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23653#c11 this is the workaround that worked for me
22:28 huginn         Bug 23653: major, P5 - low, ---, tomascohen, In Discussion , Plack stopped working - JSON validation timeout
22:30 tuxayo         Thanks for testing aleisha How long since you update or created the OS (Debian) of you dev env? Same question for lukeG
22:32 tuxayo         "Reported: 	2019-09-20"
22:32 tuxayo         Nevermind, it's been here since a long time and only biting us now.
22:33 aleisha        i recently made a new devbox that is stretch, i was using jessie until about 2 (?) months ago maybe
22:33 aleisha        not sure if that is relevant?
22:42 tuxayo         It seems the issue was quite old and only happened with network issues. And so retrying worked.
22:45 tuxayo         Hopefully the core issue could be resolved quickly:
22:45 tuxayo         https://github.com/swagger-api/swagger.io/issues/281
22:46 tuxayo         Because it will only take a package revision to reship the validation file in the Debian packages.
22:46 tuxayo         It's only a license to state.
23:22 mtj            hey #koha, ill have a go at building a new json-validator today
23:22 aleisha        thanks mtj
23:23 tuxayo         mtj++
23:24 dcook_         Yikes this swagger.io issue is nasty
23:25 mtj            https://downforeveryoneorjustme.com/swagger.io
23:25 dcook_         Nope
23:25 dcook_         swagger.io is fine
23:25 dcook_         But the particular url is not
23:25 mtj            https://swagger.io/v2/schema.json
23:25 dcook_         http://swagger.io/v2/schema.json
23:25 mtj            hmm, yeah
23:27 dcook_         Going to do a variant of aleisha's workaround
23:27 dcook_         Or yours rather lol
23:27 dcook_         What a morning
23:27 wahanui        a morning is always someone's afternoon
23:27 mtj            oof, wil build pkg now
23:28 mtj            tuxayo: thanks for logging the bug with swagger.io
23:30 mtj            ..they seem to have a license in the repo, i think its just not included in JSON::Validator.module?
23:30 mtj            https://github.com/swagger-api/swagger.io/blob/wordpress/getting-started/license.md
23:31 tuxayo         mtj: I couldn't find schema.json
23:31 tuxayo         In a few repos of https://github.com/swagger-ap
23:31 tuxayo         *https://github.com/swagger-api
23:36 mtj            yeah, me too ^ :/
23:41 dcook_         So this problem only happens when Plack restarts?
23:41 dcook_         Well starts I guess
23:42 dcook_         I have an instance that uses JSON::Validator via CPAN, and it has its cache..
23:42 dcook_         Too bad ashimema isn't around
23:43 dcook_         Looks like he released JSON::Validator on CPAN a few times..
23:44 hayley         dcook_ for me the site was working fine in the morning and then I went to change password for a user and it stopped working - plack hadn't recently restarted afaik
23:44 dcook_         hayley: I suppose JSON::Validator is loaded into memory by the workers rather than the main process
23:44 dcook_         So chances are that worker must've been died and re-created and then started failing..
23:45 hayley         that sounds right dcook_
23:47 dcook          So looks like JSON::Validator::OpenAPI is the file with this line "use constant SPECIFICATION_URL => 'http://swagger.io/v2/schema.json'"
23:47 dcook          Invoked by $validator->load_and_validate_schema()...
23:48 dcook          Hello...
23:48 dcook          local $args->{schema} = $args->{schema} || SPECIFICATION_URL;
23:49 dcook          We could provide our own URL..
23:49 dcook          Or maybe I'm misreading this all..
23:50 * dcook        just thinks it's crazy to be forced to load data from a third-party URL
23:51 dcook          tuxayo and mtj: So what problem are you guys facing right now?
23:52 dcook          Can't even find JSON::Validator::OpenAPI on CPAN..
23:53 dcook          But it comes with libjson-validator-perl
23:56 dcook          Hmmm
23:56 dcook          The documentation says it defaults to http://json-schema.org/draft-04/schema# and not http://swagger.io/v2/schema.json but that's not right..
23:56 dcook          Note that http://json-schema.org/draft-04/schema does resolve...
23:56 tuxayo         dcook: «So chances are that worker must've been died and re-created and then started failing..»
23:56 tuxayo         Doesn't that mean that all production instances of Koha with plack will end up failing???
23:56 dcook          Yup :D
23:56 dcook          Got to love a ticking time bomb
23:58 dcook          I'm still missing something..
23:58 dcook          http://swagger.io/v2/schema.json uses http://json-schema.org/draft-04/schema#...