Time  Nick             Message
01:09 aleisha          hello
05:53 reiveune         hello
06:18 marcelr          hi #koha
06:24 magnuse          \o/
07:34 ashimema         do people not search bugzilla before submitting code ☹️
07:34 Joubu            what happened?
07:39 ashimema         It just annoys me seeing so much duplicate effort all the time
07:39 ashimema         And effort going in opposite directions and ignoring all other ongoing work
08:23 PedroAmorim[m]   o/
08:24 ashimema         I wish I'd read the next team stuff a bit more in depth before voting... that team doesn't make sense to me ☹️
08:31 Annelisterman[m] It is sometimes very difficult to find anything from bugzilla. You'll have to try so many ways to search for the problem you have. Sometimes the bug you are looking for does not contain any of the words you are using.
08:32 Annelisterman[m] or the name of the system preference
08:45 ashimema         in this case a whole bunch of similar and related bugs comes up as you start typing the bug description for submission 😜
08:45 ashimema         anywho.. I'm tired and burnt out so i'm going to step away
08:47 marcelr          ashimema: whats the problem with the roles ?
09:00 Joubu            @later tell kidclamp could you have a look at bug 30556?
09:00 huginn           Joubu: The operation succeeded.
09:51 magnuse          do we have any written guidelines on how to use the koha logo/name in marketing and such?
11:27 marcelr          o/
11:28 ashimema         the db schema sync work you did marcelr
11:28 ashimema         it's hit master now
11:28 ashimema         was your hope for it to get backported.. it's marked as an enhancement but I wasn't 100% sure
11:29 ashimema         it felt like it could clash a lot
11:29 marcelr          ashimema: i wouldnt backport it
11:30 marcelr          it runs on 21.11 btw for me
11:46 ashimema         brill, makes sense
11:46 ashimema         thanks
11:52 thd              tcohen: You restarted portainer?
11:57 thd              s/portainer/test wiki Docker container/
12:24 mtj              hi folks
12:24 thd              hello mt
12:25 thd              hello mtj
12:25 thd              mtj: Do you know about portainer configuration?
12:27 mtj              hiya thd, hmm not too much
12:28 thd              Apparently we have a HEALTHCHECK trigger which is continually restarting the test wiki.
12:29 thd              I am not sure if I triggered the unhealthy condition.
12:32 thd              I was editing LocalSettings.php on the test wiki and some improper setting there would cause the container to fail to start.
12:34 mtj              thd hmm, im not sure i can see the test-wiki container, from my portainer account
12:40 mtj              i can see only 3 containers, im assuming they are all prod - wiki_backend, wiki_db, wiki_es
12:40 mtj              lets wait for tcohen :)
12:41 thd              tcohen is usually around at this hour.
12:41 mtj              we now have an ES8 version of https://tracker.debian.org/pkg/libsearch-elasticsearch-perl
12:42 mtj              topic change ^ :)
12:42 thd              test wiki is wiki_test_backend
12:43 mtj              thd: aah ok... looks like i cant see it from my account
12:56 Joubu            https://paste.koha-community.org/11790
12:56 Joubu            is there any known languages that is not broken in master?
13:03 marcelr          nice test bug on bug 33718
13:03 huginn           04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33718 minor, P5 - low, ---, m.de.rooy, Needs Signoff , _new_Zconn crashes on a bug in t::lib::Mocks::mock_config
13:03 marcelr          a bad mock in t::lib::Mocks
13:23 thd              davidnind++ Blocking all the remaining spam accounts for which a login had not been activated.
13:49 tcohen           thd: I don't see it reloading
13:50 thd              Maybe it finally gave up.
13:51 tcohen           docker service log -f wiki_backend
13:51 tcohen           shows the same container is still alive
13:52 thd              docker ps | grep backend
13:53 thd              ... shows wiki_backend restarting about every 3 minutes after reaching an unhealthy state.
13:53 thd              oops
13:53 thd              s/wiki_backend/wiki_test_backend/
13:55 thd              It maybe my fault from being in the midst of editing the LocalSettings.php file.
13:55 thd              I have a copy of the previous state from 16 March.
13:56 thd              mtj and I do not have permissions for the test wiki containers in the portainer login?
13:56 thd              .
13:58 thd              I mean the browser portainer login.
13:58 thd              We have access on the command line.
13:59 thd              There must be a trigger for restart when the system identifies an unhealthy container restart.
14:00 thd              The spam issue has been managed and the login confirmation fixed.
14:00 thd              s/login confirmation fixed/account confirmation fixed/
14:02 thd              tcohen: Last night I was trying the UserCheck extension which is used to aid blocking spam accounts on Wikipedia.
14:04 thd              tcohen: I created a special script for logging the output of maintainance/update.php to install the database tables for the UserCheck extension.
14:06 thd              tcohen: Trying UserCheck extension was on the test wiki but no problems other than local IP addresses for users which made the UserCheck extension useless.
14:06 thd              tcohen: Most likely, I had an unsaved change from editing LocalSettings.php which left it in a bad state.
14:14 thd              I noticed that the persistent extensions directory seems to partly be shared between both wiki_backend and wiki_test.  Changes I made to symlink an additional extension in wiki_backend was automatically linked in wiki_test_backend.
14:20 tcohen           thd: really?
14:21 tcohen           we have /srv/wiki_test for that
14:21 thd              Yes, I probably forgot.
14:25 thd              The odd thing is that changes to extensions for wiki_backend and wiki_test_backend appeared to be mirrored in the base extensions directory instead of sepearate for wiki and wiki_test.
14:32 lukeg            hi
15:55 reiveune         bye
20:39 cait             caroline++
21:03 caroline         ashimema, am I misunderstanding the purpose of the Needs documenting status? There are a lot of architecture changes that have the status, and I'm closing a bunch of them because there is nothing to add to or change in the manual, but maybe the devs want to add it to some sort of dev documentation?
21:10 davidnind        caroline: I think if dev documentation is required, then it should be a separate status code
22:02 aleisha          hiya
22:03 davidnind        good morning aleisha!
22:17 aleisha          how are you davidnind :)