Evergreen ILS Website

IRC log for #evergreen, 2019-12-03

| 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
00:15 sandbergja joined #evergreen
02:52 book` joined #evergreen
06:44 agoben joined #evergreen
07:08 rfrasur joined #evergreen
07:17 Dyrcona joined #evergreen
07:20 rjackson_isl joined #evergreen
08:32 jvwoolf joined #evergreen
08:39 mllewellyn joined #evergreen
09:06 mantis1 joined #evergreen
09:43 yboston joined #evergreen
09:53 mllewellyn joined #evergreen
09:54 jvwoolf1 joined #evergreen
10:06 rfrasur joined #evergreen
10:06 mllewellyn left #evergreen
10:06 berick anyone know if this meeting ever happened?  not finding any minutes.  https://wiki.evergreen-ils.org/do​ku.php?id=dev:meetings:2019-07-02
10:08 csharp berick: nothing I can see
10:09 berick just wondering what needs to be copied over..
10:09 Dyrcona Nothing in my local chat logs.
10:09 berick i think I missed a meeting somewhere in the last couple months
10:09 Dyrcona We've missed a few as a community, too.
10:10 gmcharlt after the meeting I'm currently in, I'll put together an agenda for a meeting today and post it here and on the list
10:10 gmcharlt *dev meeting today
10:10 berick gmcharlt++
10:11 csharp I am away doing PINES trainings this afternoon, so I'm going to miss this one :-(
10:11 berick "today in PINES training we learn IRC"
10:12 csharp "ok, y'all just hang tight for about 45 mins..."
10:20 sandbergja joined #evergreen
11:01 pinesol News from qatests: Failed Building Evergreen <http://testing.evergreen-ils.org/~li​ve/test.30.html#2019-12-03T11:00:45,642733428-0500 -0>
11:01 pinesol News from qatests: Failed Running Evergreen tests <http://testing.evergreen-ils.org/~li​ve/test.31.html#2019-12-03T11:00:45,670095784-0500 -2>
11:01 pinesol News from qatests: Failed Installing Evergreen <http://testing.evergreen-ils.org/~li​ve/test.32.html#2019-12-03T11:00:45,697174167-0500 -4>
11:01 pinesol News from qatests: Failed Installing Dojo <http://testing.evergreen-ils.org/~li​ve/test.35.html#2019-12-03T11:00:45,724417964-0500 -6>
11:02 pinesol News from qatests: Failed configure apache <http://testing.evergreen-ils.org/~li​ve/test.36.html#2019-12-03T11:00:45,751807836-0500 -8>
11:02 pinesol News from qatests: Failed configure EG Action/Trigger <http://testing.evergreen-ils.org/~li​ve/test.38.html#2019-12-03T11:00:45,779140022-0500 -10>
11:02 pinesol News from qatests: Failed Create Evergreen Database <http://testing.evergreen-ils.org/~li​ve/test.41.html#2019-12-03T11:00:45,806399243-0500 -12>
11:02 pinesol News from qatests: Failed Running pgTAP tests <http://testing.evergreen-ils.org/~li​ve/test.42.html#2019-12-03T11:00:45,833616012-0500 -14>
11:02 pinesol News from qatests: Failed Running autogen.sh <http://testing.evergreen-ils.org/~li​ve/test.44.html#2019-12-03T11:00:45,861887222-0500 -16>
11:02 pinesol News from qatests: Failed Running pgTAP live tests <http://testing.evergreen-ils.org/~li​ve/test.47.html#2019-12-03T11:00:45,889208650-0500 -18>
11:02 pinesol News from qatests: Failed Running settings-tester.pl <http://testing.evergreen-ils.org/~li​ve/test.48.html#2019-12-03T11:00:45,916017334-0500 -20>
11:02 pinesol News from qatests: Failed Running perl live tests <http://testing.evergreen-ils.org/~li​ve/test.49.html#2019-12-03T11:00:45,942780711-0500 -22>
11:02 pinesol News from qatests: Failed Log Output: srfsh.log <http://testing.evergreen-ils.org/~li​ve/test.58.html#2019-12-03T11:00:45,969839648-0500 -24>
11:02 phasefx I'm going to change that to report just the first error :)
11:04 phasefx though in this case, the webifier is not catching the true first error, which is Err:106 http://ftp.us.debian.org/debian stretch/main amd64 libgd-graph-perl all 1.48-2
11:04 phasefx Hash Sum mismatch
11:15 sandbergja joined #evergreen
11:16 yboston joined #evergreen
11:23 Dyrcona phasefx: Try apt-get update on the machine if the script isn't doing it.
11:24 phasefx script is doing that
11:25 phasefx timing wise, the vm has already been wiped; we didn't get the report until that happened, cause the ssh that pushes the script just sits there until the machine is refreshed.  haven't worked that out yet :-/
11:35 jeff dbwells, Dyrcona: do you recall the reasons behind 1) creating an explicit link between billings and adjustments, and 2) applying payments out of order (largest first) when mapping payments to billings for an xact? I've been digging through comments and commits and bug comments and figured I'd ask you both as well.
11:38 Dyrcona jeff: On 2, that was me. I figured if you paid a lot, you wanted to pay the highest bills, first. It would be more likely to remove penalties that way.
11:39 jeff ah. how would it be more likely to remove penalties?
11:39 jeff or, I guess which penalties? maybe we don't use the ones here you have in mind.
11:43 Dyrcona Where I worked at the time, and where I work now, block patrons with more than $10 or so in fines.
11:45 Dyrcona Since at the point that code runs, there's no way to link payments with bills, paying the highest bills first seemed as logical as other method.
12:03 jihpringle joined #evergreen
12:14 gerlevi joined #evergreen
12:17 dbwells jeff: That link causes some complications, for sure.  I believe it was added with at least two goals in mind.  First, it could provide a guarantee against adjusting the same billing twice.  Second, there were use cases where overdue fines were allowed to be adjusted, but replacement costs were not, and it was hoped that this linkage would give clarity to which parts of the bill were adjusted, and which parts were actually paid (or still
12:17 dbwells owed).  That concern was magnified in cases involving multiple org units doing the billing.  There are certainly other ways to handle these concerns, some of which may be better :)
12:29 jeff thanks, that helps!
12:38 jvwoolf1 left #evergreen
12:39 sandbergja joined #evergreen
12:47 khuckins joined #evergreen
13:03 gmcharlt agenda for today's dev meeting; please feel free to add to it
13:03 gmcharlt https://wiki.evergreen-ils.org/do​ku.php?id=dev:meetings:2019-12-03
13:29 mantis2 joined #evergreen
13:31 mantis1 joined #evergreen
13:33 tlittle joined #evergreen
13:35 jvwoolf joined #evergreen
13:57 dbs I posted 3.4.1 versions of some of the manuals to https://wiki.evergreen-ils.or​g/doku.php?id=evergreen-docs (asciidoctor failed with a fatal error trying to build the single manual, and unfortunately it doesn't provide a useful traceback)
14:09 khuckins joined #evergreen
14:32 remingtron dbs++
14:45 khuckins joined #evergreen
14:52 gmcharlt dev meeting in 8 minutes
14:56 plux joined #evergreen
14:58 plux11 joined #evergreen
15:01 gmcharlt let's do this
15:01 gmcharlt #startmeeting Evergreen Develpment Meeting 2019-12-03
15:01 pinesol Meeting started Tue Dec  3 15:01:12 2019 US/Eastern.  The chair is gmcharlt. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01 pinesol Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:01 Topic for #evergreen is now  (Meeting topic: Evergreen Develpment Meeting 2019-12-03)
15:01 pinesol The meeting name has been set to 'evergreen_develpment_meeting_2019_12_03'
15:01 gmcharlt #info Agenda is https://wiki.evergreen-ils.org/do​ku.php?id=dev:meetings:2019-12-03
15:01 gmcharlt #topic Introductions
15:01 Topic for #evergreen is now Introductions (Meeting topic: Evergreen Develpment Meeting 2019-12-03)
15:01 gmcharlt please introduce yourself using the form "#info irc_nick = name, optional affiliation"
15:02 JBoyer #info JBoyer = Jason Boyer, EOLI
15:02 gmcharlt #info gmcharlt = Galen Charlton, EOLI
15:02 alynn26 #info alynn26 = Lynn Floyd, Evergreen Indiana
15:02 berick #info berick = Bill Erickson, KCLS
15:02 remingtron #info remingtron = Remington Steed, Hekman Library (Calvin University)
15:02 dbwells #info dbwells = Dan Wells, Hekman Library (Calvin University)
15:03 phasefx #info phasefx = Jason Etheridge, EOLI
15:03 Dyrcona #info Dyrcona = Jason Stephenson, CW MARS
15:04 gmcharlt so, starting the slate fresh
15:04 gmcharlt #topic OpenSRF
15:04 Topic for #evergreen is now OpenSRF (Meeting topic: Evergreen Develpment Meeting 2019-12-03)
15:04 gmcharlt #info OpenSRF 3.2.0 was released on 2019-10-01
15:06 gmcharlt so as far as recent bugs are concerned
15:07 gmcharlt I see a couple installation-related things, including a pullrequest for Devuan support and issues registering ejabberd users as root on Ubuntu
15:07 dbs #info dbs = Dan Scott, Laurentian University
15:07 gmcharlt is there anything that folks see as a particularly pressing issue at the moment?
15:09 Dyrcona I think we should be looking ahead to adding SASL and new style authentication for OpenSRF and ejabberd.
15:09 Dyrcona But, time... :(
15:10 gmcharlt Dyrcona: so going beyond the contents of bug 1703411?
15:10 pinesol Launchpad bug 1703411 in OpenSRF "OpenSRF: XMPP Non-SASL auth is being phased out" [Medium,Confirmed] https://launchpad.net/bugs/1703411
15:12 Dyrcona Not necessarily beyond that bug, no. (I had to read it again.)
15:12 gmcharlt ok, just wanted to make sure that there weren't desiderata that should at least be added to LP
15:12 Dyrcona mod_legacy_auth hasn't been removed from ejabberd, yet, but it is not documented any longer.
15:13 gmcharlt #info SASL/new-style-authentication support (see bug 1703411) identified as a potential priority given that mod_legacy_auth is deprecated (and now, undocumented) in recent ejabberd
15:13 pinesol Launchpad bug 1703411 in OpenSRF "OpenSRF: XMPP Non-SASL auth is being phased out" [Medium,Confirmed] https://launchpad.net/bugs/1703411
15:13 gmcharlt anything else before we move on to Evergreen?
15:14 gmcharlt #topic Evergreen
15:14 Topic for #evergreen is now Evergreen (Meeting topic: Evergreen Develpment Meeting 2019-12-03)
15:14 gmcharlt handing the floor over to berick and (in spirt) csharp to discuss 3.5
15:14 berick hi
15:14 berick i've put the proposed schedule on the general roadmap page
15:15 berick https://wiki.evergreen-ils.org/do​ku.php?id=faqs:evergreen_roadmap
15:15 berick let me know if there are concerns
15:15 berick ditto the EG dev calendar
15:15 berick also added a pile of stuff to the feature roadmap
15:15 berick https://wiki.evergreen-ils.org/doku​.php?id=faqs:evergreen_roadmap:3.5
15:16 berick most recent being more piles of angular ports
15:16 berick Any other features expected for 3.5 should go into this list
15:17 berick and get tagged with the 3.5 milestone in LP
15:17 berick still pretty early in the cycle.  next group activity will be Feedback Fest in Jan.
15:17 berick but i'm sure we'll have plenty to discuss before then
15:18 berick any questions for me?
15:18 berick oops, Feedback Fest in Feb. not Jan.
15:19 gmcharlt berick: next you'll be telling us that general release is on April Fool's Day!
15:19 gmcharlt ;)
15:19 berick that's the beauty, who knows if I'm making it up!
15:19 Dyrcona :)
15:19 berick the Neutral Chaos release
15:20 gmcharlt any questions / comments for berick regarding 3.5?
15:20 Dyrcona I hope to add something to the roadmap, soon. I want to actually make progress on it before I do, however.
15:20 yboston joined #evergreen
15:21 gmcharlt great
15:21 gmcharlt so, moving on to maintenance releases, anything to say here?
15:23 dbwells We still have one blocker for dropping 3.1 releases
15:24 gmcharlt dbwells: namely bug 1773191?
15:24 pinesol Launchpad bug 1773191 in Evergreen "Untranslatable Last Billing Type values" [Undecided,New] https://launchpad.net/bugs/1773191
15:24 dbwells Yes.  Actually, I see there is a security bug as well.
15:25 gmcharlt yeah
15:25 dbwells It seems like both are close, so just highlighting in hopes that someone can push them over the finish line.
15:26 gmcharlt both bugs have progress, indeed
15:27 gmcharlt I can provide forward progress for the security bug
15:28 gmcharlt and we can nudge csharp to see if he's progressed any further with testing for 1773191
15:28 gmcharlt #action gmcharlt will apply various code changes and nudges regarding the remaining webstaffblocker bugs
15:29 dbwells gmcharlt++
15:29 remingtron gmcharlt++
15:30 Dyrcona gmcharlt++
15:31 gmcharlt ok, moving o
15:31 gmcharlt #topic Hatch
15:31 Topic for #evergreen is now Hatch (Meeting topic: Evergreen Develpment Meeting 2019-12-03)
15:31 gmcharlt floor back to you, berick
15:32 berick hatch..
15:33 berick fwiw, we'll be going live on using the omnibus hatch branch merged into our EG code
15:33 berick along w/ the hatch 0.3.2 build
15:33 berick i know there's some other interested parties in moving that bug forward
15:33 gmcharlt commit ade63709f4b51b jumps out at me
15:33 berick hoping we can help root out any final issues and encourage some confidence in the bug overall
15:33 berick done a fair amount of use and testing so far
15:34 gmcharlt was there anything adding dupes? and if so, should there be code checking that the new constraint is not violated?
15:34 gmcharlt or is that patch just belt-and-suspenders?
15:34 berick belt-and-suspenders ... i had a dupe on a dev VM but I was fairly confident it was not from natural causes
15:35 berick i can certainly add a check or at least an \echo
15:36 gmcharlt thanks
15:37 berick anyway, that's what I would expect to be the next hatch release
15:37 gmcharlt #info more eyes are wanted on the Hatch omnibus branch for bug 1830391
15:37 pinesol Launchpad bug 1830391 in Evergreen "Hatch omnibus circa 3.3 (Java updates and more)" [Undecided,New] https://launchpad.net/bugs/1830391
15:38 gmcharlt so, moving on
15:38 gmcharlt #topic Review of specific bugs
15:38 Topic for #evergreen is now Review of specific bugs (Meeting topic: Evergreen Develpment Meeting 2019-12-03)
15:39 gmcharlt #info The SIP2 changes to accommodate a Hoopla change has a pull request at https://bugs.launchpad.net/evergreen/+bug/1853363
15:39 pinesol Launchpad bug 1853363 in Evergreen "SIP2: add setting to specify overriding certain flag fields" [Wishlist,New]
15:39 gmcharlt so, I brought this one up for two reasons
15:39 gmcharlt first, for eyes on the pull request
15:40 gmcharlt second, now that there's been a couple weeks since Hoopla started informing their customers about the fact that they will be taking certain additional flags into account
15:40 gmcharlt ... whether there are Evergreen users out there who ultimately are just fine with the status quo in Evergreen
15:41 gmcharlt i.e., that patrons who have blocks or lost cards in Evergreen will start getting blocked in Hoopla
15:41 Dyrcona This one is one our RADAR at CW MARS. I was going to wait to see if any one here started complaining about Hoopla blocking patrons unexpectedly.
15:42 * gmcharlt makes a note to never got caught in the beam of the caps-lock radar
15:42 berick on our radar too
15:42 berick heh
15:42 Dyrcona I think you'd want to block patrons from using Hoopla if they're blocked in Evergreen, but what I think is not always what members want or expect.
15:42 alynn26 It's one I'm watching,
15:42 Dyrcona heh.. Well, it's an acronym/abbreviation....
15:42 gmcharlt ah
15:43 gmcharlt ok, it sounds like there's sufficient interest in the work-around, dirty as it may be
15:43 gmcharlt so yeah, I reiterate my plea for eyes on the pull request
15:43 gmcharlt I note that in _principle_ we could really go for broke and teach Evergreen lots of options for managing SIP2 configuration options
15:44 gmcharlt (and move the settings in-DB)
15:44 alynn26 gmcharlt ++
15:44 gmcharlt but that's probably way more work on support for an old protocol than is warranted
15:45 JBoyer Moving auth in-db sometime may be worth the effort, but yeah, no need to get *too* fancy with SIP.
15:45 Dyrcona I think there's a bug about moving sip settings in-db, or maybe I'm confusing it with something else.
15:45 gmcharlt any other bugs that people would like to highlight?
15:46 gmcharlt Dyrcona: I'm not immediately finding such a bug, not that that means much
15:46 gmcharlt JBoyer: I agree
15:47 Dyrcona Probably just something we've chatted about in the past. :)
15:47 gmcharlt although moving logins-at-least into the DB probably does mean also moving any per-SIP2-terminal-user settings
15:48 JBoyer Mmm. Yeah, too many less-than-institution level settings. :/
15:49 gmcharlt any other bugs to highlight?
15:50 gmcharlt then moving to the final topic
15:50 gmcharlt #topic QA-related bugs
15:50 Topic for #evergreen is now QA-related bugs (Meeting topic: Evergreen Develpment Meeting 2019-12-03)
15:50 gmcharlt this is a carry-over from an earlier version of the agenda, but the LP link for "qaproject"-tagged bugs turns up nothing
15:50 gmcharlt does anybody recall what this is?
15:50 phasefx no bugs there at the moment; I added that to the stock agenda way back when tests failed and no one had the itch to address it
15:51 gmcharlt ah, OK
15:51 phasefx for regressions
15:51 gmcharlt #info The "qaproject" LP tag is meant for bugs stemming from automated test failures that aren't immediately addressed
15:51 gmcharlt phasefx: ^^ fair summary?
15:51 phasefx the live test results page also inlines those bugs
15:51 phasefx gmcharlt++ fair
15:52 gmcharlt ok
15:52 gmcharlt so at the moment, we're golden!
15:53 gmcharlt any other topics that folks would like to raise for the last 8 minutes?
15:53 Dyrcona Except that tests failed earlier today.
15:53 gmcharlt we're not golden! :(
15:53 phasefx I think that may be from debian updates to the repo not being atomic, but I'm not sure
15:53 JBoyer Dyrcona, that was some kind of upstream thing. (Not even npm!)
15:54 phasefx Hash sum mismatch on at least one package
15:54 Dyrcona Yeah, I was gonna add that it was probably distro-specific.
15:54 gmcharlt *sigh*
15:54 phasefx it shouldn't spew the channel with a ton of errors next time though, I have RSS just reporting the first one
15:54 Dyrcona So, we're silver-ish... :)
15:54 gmcharlt I'm not entirely kidding when I say that I wish the Javascript ecosystem had just adopted CPAN
15:55 phasefx poor JSAN
15:56 sandbergja_ joined #evergreen
15:56 gmcharlt ok, it sounds like we've hit the end... (just in time for sandbergja to join us!)
15:56 gmcharlt so, thanks, folks!
15:57 gmcharlt #endmeeting
15:57 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:57 pinesol Meeting ended Tue Dec  3 15:57:00 2019 US/Eastern.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
15:57 pinesol Minutes:        http://evergreen-ils.org/meetings/evergr​een/2019/evergreen.2019-12-03-15.01.html
15:57 pinesol Minutes (text): http://evergreen-ils.org/meetings/evergr​een/2019/evergreen.2019-12-03-15.01.txt
15:57 pinesol Log:            http://evergreen-ils.org/meetings/evergree​n/2019/evergreen.2019-12-03-15.01.log.html
15:57 Dyrcona gmcharlt++
15:57 JBoyer gmcharlt++
15:57 berick gmcharlt++
15:57 phasefx gmcharlt++
15:58 dbwells gmcharlt++
16:17 mantis1 left #evergreen
16:54 jvwoolf left #evergreen
17:00 sandbergja_ joined #evergreen
17:26 rfrasur joined #evergreen
17:28 cmalm joined #evergreen
17:29 sandbergja_ joined #evergreen
17:31 cmalm joined #evergreen
17:43 sandbergja_ joined #evergreen
19:22 cmalm joined #evergreen
20:42 sandbergja joined #evergreen
21:22 rfrasur joined #evergreen
22:09 sandbergja joined #evergreen
23:12 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>

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