Evergreen ILS Website

IRC log for #evergreen, 2025-03-12

| 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
08:09 ianskelskey joined #evergreen
08:09 ianskelskey left #evergreen
08:31 mmorgan joined #evergreen
08:43 kworstell-isl joined #evergreen
09:03 dguarrac joined #evergreen
09:06 redavis joined #evergreen
09:06 Dyrcona joined #evergreen
09:29 collum joined #evergreen
09:49 jmurray-isl joined #evergreen
10:01 kworstell_isl joined #evergreen
10:17 Dyrcona Apparently, we can add a commit template to the repository, but we cannot enforce it's use.
10:17 Dyrcona Everyone will have to set it locally. I can't force it from gitolite, either. (I just tried with a test repository.)
10:18 redavis Was the goal to enforce it or make it available for use and have it documented as an SOP?
10:19 Dyrcona redavis: The goal is probably to make it available. Even if we could force it, it would still pretty much be optional because the lines are added as comments/suggestions.
10:19 * redavis nods
10:19 redavis Dyrcona++ # thanks for taking it on and working through the bits and pieces of it.
10:22 sleary Dyrcona++
10:45 kworstell_isl_ joined #evergreen
10:54 mantis joined #evergreen
11:08 Christineb joined #evergreen
12:01 mantis left #evergreen
12:16 jihpringle joined #evergreen
12:26 collum joined #evergreen
12:33 jihpringle joined #evergreen
15:00 jihpringle joined #evergreen
15:10 Dyrcona I've reviewed Bmagic's branch on Lp 2073561, and I have no objections to it. I wonder if I should just push it or add a signoff and let someone else also have a look? jeffdavis seemed interested.
15:10 pinesol Launchpad bug 2073561 in Evergreen "Incorrect content in the config.coded_value_map after applying the upgrade script from 3.12.3 to 3.13.0" [High,Confirmed] https://launchpad.net/bugs/2073561 - Assigned to Jason Stephenson (jstephenson)
15:10 Dyrcona I tried both restoration methods since I had two upgraded dbs to play with and both work.
15:11 Dyrcona I think I'll add a signoff with a note that we should get this in before the next releases.
15:11 redavis Dyrcona, possible for you to add the signoff and check back in a few days prior to feature freeze?
15:11 redavis Dyrcona++
15:11 jeffdavis I'm confident about the excising-1416 part but I'm not gonna have time to test/signoff the fix script.
15:11 Dyrcona I don't think feature freeze would hold this up. It's a bug fix and AFAICTL it doesn't affect strings either.
15:13 Dyrcona Well, I had a question about leaving a mostly empty upgrade script in the repo, but it makes sense after I thought about it and the motivation for doing so.
15:13 Dyrcona I'll push a signoff and if no one gets to it by next week, I'll push it for the freeze anyway.
15:14 redavis Dyrcona++
15:15 Dyrcona We might want to add a caveat to the release notes that the examples may not work exactly as written depending on how your PostgreSQL is set up.
15:15 Dyrcona You might need additional connection parameters, for instance.
15:45 redavis I'm looking at permission group settings in a 3.13.8 system and 3.14.2 system. In the 3.13.8 system, the depth selector for non-inherited permissions isn't populated. In 3.14.2, it is. I'm not finding anything in LP to account for the difference. Any ideas?
16:05 jihpringle joined #evergreen
16:15 Dyrcona redavis: The same data, just different Evergreen versions?
16:15 redavis No. Diff datasets. I put in a request with their server admin.
16:16 redavis They have an additional org unit level, so maybe that has something to do with it? I dunno. Just going to skip over that right now and work on something else.
16:16 Dyrcona Yeah, I'd put it down to different datasets.
16:17 Dyrcona I have  a plan to get rid of our extra org unit level.
16:17 redavis And I'm also working on a test server that might not get the same loving care as production.
16:18 redavis Yeah. I'm pretty hopeful that the continued work on library groups might make an extra level obsolete at some point.
16:21 Dyrcona Ours is a hangover from the previous commercial ILS. They (we) ran two server instances split into western and central regions. Because it could not handle the full load. Then (I think) there was some kind of ILL connector to enable loans between the two.
16:22 redavis Back in the good ol' days. Also, my issue with this was a performance issue. I just needed to wait longer. (ugh)
17:05 mmorgan left #evergreen
18:12 jihpringle joined #evergreen

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