Evergreen ILS Website

IRC log for #evergreen, 2025-11-21

| Channels | #evergreen index | Today | | Search | Google Search | Plain-Text | summary | Join Webchat

All times shown according to the server's local time.

Time Nick Message
03:00 collum joined #evergreen
04:28 beardicus joined #evergreen
05:01 collum joined #evergreen
06:17 collum joined #evergreen
08:42 JBoyer joined #evergreen
09:02 mantis joined #evergreen
09:06 collum joined #evergreen
09:24 Dyrcona joined #evergreen
09:48 kmlussier joined #evergreen
09:49 kmlussier Good morning #evergreen! Happy Friday!
09:49 kmlussier @coffee [someone]
09:49 * pinesol brews and pours a cup of El Salvador Nombre de Dios, and sends it sliding down the bar to jmurray-isl
09:49 kmlussier @tea [someone]
09:49 * pinesol brews and pours a pot of Organic Bangkok (Green Tea with Coconut, Ginger and Vanilla), and sends it sliding down the bar to jweston (http://ratetea.com/tea/harney/bangkok/2217/)
09:49 kmlussier @dessert [someone]
09:49 * pinesol grabs some Walker's Pure Butter Shortbread for troy
10:15 * jmurray-isl hearts good coffee.  ;)
10:16 jmurray-isl Good coffee is also necessary when having to deal with the Vogons of the State...
10:27 Bmagic kmlussier++
10:55 Christineb joined #evergreen
11:47 goood berick++ # belatedly, for soon returning to redisrf+streams
11:55 kmlussier goood: What happened to eeevil?
11:59 goood kmlussier: that guy? he's on thin ice. what a jerk! ;)
12:02 kmlussier goood: Yeah, he had his moments, but we generally got along. But that miker guy is real trouble.
12:05 * goood is still salty that freenet took "miker" away after years of use :(
12:09 collum joined #evergreen
13:24 goood Dyrcona / Bmagic: https://bugs.launchpad.net/evergreen/+bug/2132031 may be relevant to your interests, re upgrading to 3.16 and/or backporting some bits to 3.15
13:24 pinesol Launchpad bug 2132031 in Evergreen "SQL Problems Applying Fix From 1847805" [High,New]
13:46 csharp_ @who will create an upgrade script for that upgrade script?
13:46 pinesol goood will create an upgrade script for that upgrade script.
13:46 csharp_ pinesol: makes sense
13:46 pinesol csharp_: Have you run autogen.sh?
13:47 csharp_ pinesol: tryna get rid of that
13:47 pinesol csharp_: I see nothing, I know nothing!
13:47 csharp_ pinesol: clearly
13:47 pinesol csharp_: Thank you csharp_! But our princess is in another castle!
13:48 Dyrcona goood++
13:51 csharp_ “Why do you call me good?” Jesus answered. “No one is good—except God alone.
13:51 csharp_ oh, you said "goood"
14:10 collum joined #evergreen
14:29 Bmagic goood++  gmcharlt++ # we did a dump/restore to solve that problem and attempt to make the state of the DB as clean as possible. I'll read the patch more thoroughly as time allows. But I'm wondering if we need to apply it ahead of upgrading to 3.16?
14:30 Lorne joined #evergreen
14:30 Bmagic I mean, sooner rather than later. Like when the standard upgrade time would be for us to go to 3.16 (a year from now or something)
14:42 Dyrcona Bmagic: I don't think it helps unless it replaces the 1501 upgrade script.
15:30 mantis left #evergreen
15:35 goood Bmagic: you want to make sure the effect of the changes in the standalone XXXX script (also embedded in the baseline schema and the modified 1501) are in effect. you can run it first if you have nominally-broken rules with RETURNING in them, or last, but in the end you want the function-forced names for the rules, and the rules should not have RETURNING in them.
15:36 goood Dyrcona: 1501 is modified in the branch, as is the 3.15-3.16 upgrade script (for later upgraders)
15:37 goood then, with the updated pcrud code, we're future-proof (except for the unfulfilled goal of being able to say RETURNING on deletes against protected tables -- that's not stably possible due to ... what I said in the commit message)
15:41 Bmagic goood++
15:49 Dyrcona joined #evergreen
16:13 collum joined #evergreen
16:34 pinesol News from commits: Docs: updates staff catalog search imageto show Library Groups and Shelving Location... <http://git.evergreen-ils.org/?p=Ev​ergreen.git;a=commitdiff;h=d662c24​089332b9504ea424b355c5935c7215c68>
17:18 kmlussier left #evergreen
17:57 jeffdavis Has anyone experimented with adjusting proxy_buffer_size and related settings in nginx config?
17:58 jeffdavis We've just been using the defaults but I'm getting an "upstream sent too big header" error during Shibboleth logout. Increasing the proxy_buffer_size helps but I don't know what side effects that might have.
18:55 collum joined #evergreen
20:17 collum joined #evergreen

| Channels | #evergreen index | Today | | Search | Google Search | Plain-Text | summary | Join Webchat