Evergreen ILS Website

IRC log for #evergreen, 2020-12-01

| 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
06:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
06:02 rjackson_isl_hom joined #evergreen
07:18 alynn26 joined #evergreen
07:45 Dyrcona joined #evergreen
07:53 rfrasur joined #evergreen
08:43 mmorgan joined #evergreen
09:29 mantis2 joined #evergreen
09:31 jvwoolf joined #evergreen
09:37 Bmagic jeff: re: new copies made available filling holds in the wrong order. The damage is already done, but I wonder if it would do the right thing if you used this cronjob during the day: ./hold_targeter.pl --osrf-config $SRF_CORE --retarget-interval '2 days' --soft-retarget-interval '2 hours'
09:39 Bmagic When the hold targeter runs, it should* be processing the rows in some sort of "order by" order based upon a complex set of library settings, right?
09:46 Dyrcona Is there some kind of targeting done when the copies are updated? I don't think so, but....
09:49 jeff not that I'm aware of... just the normal cron job that retargets holds that were last targeted more than X ago (and targeting of new holds and manual retargeting)
10:03 jvwoolf1 joined #evergreen
11:49 Cocopuff2018 joined #evergreen
12:04 jihpringle joined #evergreen
12:06 terranm joined #evergreen
13:00 sandbergja joined #evergreen
14:49 shulabear joined #evergreen
14:50 JBoyer FYI, Dev meeting starting in about 10 minutes
14:50 Cocopuff2018 joined #evergreen
14:59 miker Dyrcona: only with "retarget local holds" and "retarget all statuses" checkin modifiers. nothing magical (that'd be ... a lot)
15:00 JBoyer It's that time
15:00 Dyrcona Yeahp.
15:00 JBoyer #startmeeting 2020-12-01 - Developer Meeting, Agenda Available at https://wiki.evergreen-ils.org/do​ku.php?id=dev:meetings:2020-12-01
15:00 pinesol Meeting started Tue Dec  1 15:00:32 2020 US/Eastern.  The chair is JBoyer. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00 pinesol Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00 Topic for #evergreen is now  (Meeting topic: 2020-12-01 - Developer Meeting, Agenda Available at https://wiki.evergreen-ils.org/dok​u.php?id=dev:meetings:2020-12-01)
15:00 pinesol The meeting name has been set to '2020_12_01___developer_meeting__agenda_​available_at_https___wiki_evergreen_ils_​org_doku_php_id_dev_meetings_2020_12_01'
15:00 JBoyer #topic Introductions
15:00 Topic for #evergreen is now Introductions (Meeting topic: 2020-12-01 - Developer Meeting, Agenda Available at https://wiki.evergreen-ils.org/dok​u.php?id=dev:meetings:2020-12-01)
15:00 csharp #info csharp = Chris Sharp, GPLS
15:00 JBoyer #info JBoyer = Jason Boyer, Equinox
15:00 abowling #info abowling = Adam Bowling, Emerald Data Networks
15:00 Dyrcona #info Dyrcona = Jason Stephenson, CW MARS
15:01 berick #info berick Bill Erickson, KCLS
15:01 miker #info mike = Mike Rylander, EOLI
15:01 shulabear #info shulabear = Shula Link, GCHRL
15:01 miker #info miker = Mike Rylander, EOLI
15:01 mmorgan #info mmorgan = Michele Morgan, NOBLE
15:01 rhamby #info rhamby = Rogan Hamby, EOLI
15:01 mantis2 #info mantis = Gina Monti, Bibliomation
15:01 phasefx #info phasefx = Jason Etheridge, EOLI
15:02 terranm #info terranm = Terran McCanna, PINES
15:02 JBoyer With no action items from our last meeting we'll go right to updates
15:02 JBoyer #topic Evergreen Release Info
15:02 Topic for #evergreen is now Evergreen Release Info (Meeting topic: 2020-12-01 - Developer Meeting, Agenda Available at https://wiki.evergreen-ils.org/dok​u.php?id=dev:meetings:2020-12-01)
15:03 sandbergja joined #evergreen
15:03 berick i can offer a bit on the EG side
15:03 JBoyer Dyrcona has a question about 3.7 beta and release dates, and I think I saw a message about that recently
15:03 JBoyer berick++
15:03 berick indeed, proposed schedule emailed
15:03 Dyrcona berick++
15:03 terranm berick++
15:03 berick and related terranm propesed dates for feedback fest and bug squash week
15:04 sandbergja terranm++
15:04 sandbergja berick++
15:04 berick February 8-12  and March 8-12 respectively
15:04 Dyrcona Those dates also work for me. terranm++
15:05 berick so i'll update the general EG roadmap page with these dates
15:05 terranm Cool, I'll put them on the community calendar
15:06 mmorgan berick++
15:06 mmorgan terranm++
15:06 JBoyer #info proposed dates email thread: https://georgialibraries.markma​il.org/message/ke4aaxb45g6ec3j6
15:06 JBoyer Someday I'll look this stuff up before the meeting starts. Not today!
15:07 Dyrcona :)
15:07 JBoyer I'm also +1 to the recommended dates.
15:07 Dyrcona I hit refresh on the agenda as the meeting started.
15:07 JBoyer I at least get a little more ahead than that so I can write up a command script, heh.
15:08 JBoyer If there are no more Eg updates or questions about it, we'll move on to Docs
15:08 JBoyer #topic Documentation Updates
15:08 Topic for #evergreen is now Documentation Updates (Meeting topic: 2020-12-01 - Developer Meeting, Agenda Available at https://wiki.evergreen-ils.org/dok​u.php?id=dev:meetings:2020-12-01)
15:09 JBoyer Who would like to expand on the changes to the DIG meeting format, or have I been punk'd by old data?
15:09 * JBoyer looks for hidden camera
15:10 JBoyer Looks like that means it's time to discuss business of a newer nature.
15:10 JBoyer #topic New Business
15:10 Topic for #evergreen is now New Business (Meeting topic: 2020-12-01 - Developer Meeting, Agenda Available at https://wiki.evergreen-ils.org/dok​u.php?id=dev:meetings:2020-12-01)
15:11 JBoyer terranm, would you like to talk about the signed off bugs list?
15:11 terranm Sure. We have a bit of a backlog in patches that are tested and signed off but not committed. Michele has been highlighting some of the more urgent fixes in email.
15:11 terranm Would it be reasonable to ask each core committer to commit to checking and committing at least one signed off patch per month? (At least until we're keeping up with them?)
15:12 JBoyer Seems reasonable to me.
15:12 csharp +1
15:12 berick terranm: i like the idea.  maybe a good dev list heads-up / discussion
15:12 sandbergja joined #evergreen
15:12 mmorgan +1
15:13 terranm With great power comes great responsibility
15:13 JBoyer I also really like the list of 10 that mmorgan is keeping. Don't want to wade through the long list, here's 10 to pick from!
15:13 Dyrcona It's all right with me. I started looking at some this week in between other things.
15:13 mmorgan Low hanging fruit!
15:13 csharp The List of Ten
15:14 terranm mmorgan++
15:14 berick yeah, the list is great
15:14 JBoyer terranm++
15:14 JBoyer mmorgan++
15:14 JBoyer was there anything you wanted to add about it mmorgan or just make folks aware, which we now ought be?
15:15 Dyrcona mmorgan++
15:15 mmorgan Just wanted to keep folks attention on them :)
15:15 JBoyer +1
15:16 terranm Thanks all!
15:16 csharp might be worth using the bug assignment feature to let other committers know you're working on a bug
15:16 mmorgan terranm++
15:17 sandbergja Just a note that we should update this wiki page with the expectation that core committers review one signedoff patch/month (unless we think it will just be a temporary need): https://wiki.evergreen-ils.org/doku.php?id=cont​ributing:core_committer_responsibilities&amp;s[]=committers
15:17 Dyrcona I don't think it should be  permanent requirement of being a committer.
15:17 sandbergja (I don't think we'll ever *not* have a backlog of signedoff bugs, but I've been pretty pessimistic lately hahaha)
15:17 terranm :)
15:17 JBoyer Also, a big +1 to mentioning both the request to check / commit a minimum of 1 bug per month and updates on the "top 10" on the dev list to remind everyone, especially since it's December.
15:17 tlittle joined #evergreen
15:18 csharp yeah, I think the intention is enough without codifying something
15:18 mmorgan I agree using the assignment feature is great for keeping track.
15:18 sandbergja that makes sense
15:18 csharp meaning I agree with Dyrcona
15:18 JBoyer I don't know that it should be a requirement but it does seem like something attainable to try to do, which could stand to be mentioned.
15:18 Dyrcona Also, definitely assign bugs to yourself when looking at them.
15:19 berick JBoyer: ditto
15:19 terranm More like a goal than a requirement
15:19 JBoyer terranm++
15:19 berick "flight hours"
15:19 csharp there you go
15:21 JBoyer Ok, any other items to discuss before announcements are announced?
15:22 JBoyer #topic Announcements
15:22 Topic for #evergreen is now Announcements (Meeting topic: 2020-12-01 - Developer Meeting, Agenda Available at https://wiki.evergreen-ils.org/dok​u.php?id=dev:meetings:2020-12-01)
15:22 JBoyer #info Next meeting is 2021-01-05
15:22 JBoyer And that's all I have unless anyone is excited about anything in particular.
15:22 jeffdavis Sorry, I was afk - there was a question about security releases
15:23 jeffdavis i.e. whether to do a round of them in Dec
15:23 JBoyer Oh, right, didn't make the agenda.
15:23 Dyrcona Yes, there was such a question, but I wasn't sure if we should broach it here, but why not?
15:24 JBoyer I do think dropping them right before Christmas is a pretty rough time.
15:25 JBoyer People with an eye to exploiting bugs usually have more free time around the holidays than the people that apply the patches, so to speak.
15:25 Dyrcona Yeah, and this was my motivation for asking about the 3.7 release.
15:25 csharp Dyrcona: we can speak in pig latin to obscure what we're aying-say
15:26 Dyrcona :)
15:26 jeffdavis I believe there are a few pending security fixes, I'd support a release in Jan esp if that helped get more of the fixes committed
15:26 csharp sounds reasonable to me
15:27 JBoyer With the 3.7 timeline I think it would definitley be fine to look at the Jan point release.
15:27 Dyrcona I agree with security releases in January rather than waiting for March.
15:27 csharp also, is it safe to assume that January would be the next window for point releases generally?
15:28 Dyrcona csharp: Thst's OK with me.
15:28 JBoyer Seems that way, unless a flurry of activity takes place in the next 13-14 days, which would be unusual for December.
15:28 csharp yeah
15:29 JBoyer Ok, so skipping December and planning to make January a security release, does that sound like a good plan to everyone present?
15:29 berick so we have security and the Top Ten Challenge for Jan.
15:30 csharp yes
15:30 csharp also the 100 pushup challenge and New Year's resolutions
15:30 Dyrcona I'm going to assign myself an action to set dates in Lp for the next point releases, and add a 3.4.6 security release.
15:30 JBoyer csharp++
15:30 csharp Dyrcona++
15:30 terranm Dyrcona++
15:31 Dyrcona #action Dyrcona to assign release dates in Launchpad for 3.6.2, 3.5.3, and 3.4.6 releases.
15:31 Dyrcona Hmm... Maybe I can't or didn't do it right?
15:31 JBoyer I don't recall if meetbot is down with that unless you're chair.
15:31 csharp Dyrcona: that should work I think
15:31 JBoyer #action Dyrcona to assign release dates in Launchpad for 3.6.2, 3.5.3, and 3.4.6 releases.
15:32 JBoyer Or it got bored and wondered off...
15:32 csharp Marvin the Meetbot?
15:32 Dyrcona Maybe there's no feedback with action?
15:32 JBoyer oh, that could be.
15:32 csharp that's my impression
15:33 JBoyer Now you're double gonna do it, I guess. :)
15:33 Dyrcona :)
15:33 JBoyer Ok, We've all got some things we can start looking at and hopefully the next point releases will be packed with good stuff and 3.7 will be another big release.
15:34 JBoyer Hurrah!
15:34 JBoyer #endmeeting
15:34 Topic for #evergreen is now Welcome to the #evergreen library system channel! | We are publicly logged: http://irc.evergreen-ils.org/evergreen | Large pastes at http://paste.evergreen-ils.org | Can't speak? Make sure your nickname is registered and that you are identified to freenode services: https://freenode.net/kb/answer/registration
15:34 pinesol Meeting ended Tue Dec  1 15:34:18 2020 US/Eastern.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
15:34 pinesol Minutes:        http://evergreen-ils.org/meetings/evergr​een/2020/evergreen.2020-12-01-15.00.html
15:34 pinesol Minutes (text): http://evergreen-ils.org/meetings/evergr​een/2020/evergreen.2020-12-01-15.00.txt
15:34 pinesol Log:            http://evergreen-ils.org/meetings/evergree​n/2020/evergreen.2020-12-01-15.00.log.html
15:34 mantis2 left #evergreen
15:34 terranm JBoyer++
15:34 abowling jboyer++
15:34 mmorgan JBoyer++
15:34 berick jboyer++
15:34 shulabear jboyer++
15:34 Dyrcona JBoyer++
15:35 csharp JBoyer++ # efficiency :-)
15:35 phasefx JBoyer++
15:35 JBoyer On occasion, csharp. ;)
15:36 Dyrcona Yeahp, the action is in the minutes twice.
15:36 JBoyer Ah, well. Perhaps I'll only list it three times under Actions from the last meeting. :D
15:39 Dyrcona Heh.
15:39 Dyrcona And, Lp subtracted a day from the dates I chose for the releases, but whatever.
15:40 JBoyer Reminds me of a fun early-days web client bug re: birthdays. :)
15:41 rjackson_isl_hom joined #evergreen
15:43 Dyrcona timezones-- ;)
15:53 Dyrcona miker: Are you still working on bug 1808055 ?
15:53 pinesol Launchpad bug 1808055 in Evergreen "Search queries containing a filter in a subquery/group may drop the filter" [Undecided,Confirmed] https://launchpad.net/bugs/1808055 - Assigned to Mike Rylander (mrylander)
16:19 Bmagic JBoyer++
16:19 Dyrcona So what should I do with a bug that was fixed by a patch on a different bug? Fix Released or Invalid?
16:20 Dyrcona And, for those following along at home. It's a private security bug.
16:21 Dyrcona It was also fixed several releases ago.
16:22 Dyrcona I will a) make it a public security bug, b) mark it fix released for the release where I think it was fixed, and c) remove the other "affected" releases as no longer affected.
16:48 jeff Were the reasons it was a private security bug clearly communicated as a security issue in the release notes for the release where it was fixed?
16:49 Dyrcona jeff: I don't think so. It was fixed as a result of a patch to a different bug and then it was overlooked: https://bugs.launchpad.net/evergreen/+bug/1729889
16:49 pinesol Launchpad bug 1729889 in Evergreen 3.2 "Looks like an MD5 hash of a password field is being displayed in record holds grid" [Undecided,Fix released]
16:52 jeffdavis Looks like actor.usr_activity only tracks the most recent web client login, not all such logins?
16:54 jeff jeffdavis: check the transient column on the relevant config.actor_usr_activity_type (from memory)
16:54 jeff config.usr_activity_type
16:55 jeff you'll likely want to modify those. the defaults are not suitable for all environments.
16:56 jeffdavis jeff++
16:56 jeffdavis yes, looks like the websocket login types are transient by default
17:01 Dyrcona jeff: I'm signing out if you want to continue that conversation tomorrow.
17:13 mmorgan left #evergreen
18:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:00 sandbergja joined #evergreen
18:22 jeffdavis Another day, another method for exhausting open-ils.actor drones. :(
18:51 jeffdavis bug 1896285
18:51 pinesol Launchpad bug 1896285 in Evergreen "Use batch methods for multi-row grid actions" [Wishlist,New] https://launchpad.net/bugs/1896285
19:33 sandbergja joined #evergreen
20:19 sandbergja joined #evergreen
21:47 sandbergja joined #evergreen

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