| Time |
Nick |
Message |
| 06:00 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 06:57 |
|
bgillap_ joined #evergreen |
| 06:58 |
|
bgillap__ joined #evergreen |
| 07:15 |
|
rjackson_isl_hom joined #evergreen |
| 07:26 |
|
collum joined #evergreen |
| 08:20 |
|
Dyrcona joined #evergreen |
| 08:34 |
|
mmorgan joined #evergreen |
| 08:39 |
|
mantis joined #evergreen |
| 09:29 |
|
jvwoolf joined #evergreen |
| 10:17 |
|
rfrasur joined #evergreen |
| 11:23 |
mantis |
I have a question for those who have libraries using storage lockers for curbside service. We had a couple of companies reach out about us generating patron information in a csv for them regularly, and it looks like they need all patron data instead of the data of patrons who have holds. Does anyone have experience with these lockers? We're not sure about sending them all the patron information. |
| 11:25 |
jeff |
I would avoid a vendor who has that requirement. |
| 11:28 |
Dyrcona |
So, send them the 20GB CSV.... They won't be able to deal with it most likely. :) |
| 11:29 |
* Dyrcona |
mostly agrees with jeff. Out consortium has policies about this sort of thing, but I'm not sure how they would apply to a situation like this. |
| 11:30 |
abneiman |
mantis: it's been my experience from the service provider side that some service providers ask for WAY more than they need (it's a business case for them) and you can & should insist on only giving them the precise info they need to run their services. And if they won't accept that, as jeff says, I wouldn't work with them. |
| 11:34 |
Dyrcona |
My suspicion is that mantis doesn't have the option of not working with the vendor. That some member libraries are already are working with such vendors, and they now expect the consortium to send the data. |
| 11:36 |
mantis |
Dyrcona: yeah that's basically it |
| 11:37 |
mantis |
I was planning on emailing the director about it and hopefully he didn't purchase the lockers already |
| 11:37 |
mantis |
thanks for everyone's thoughts about it |
| 11:37 |
mantis |
abneiman++ |
| 11:37 |
mantis |
jeff++ |
| 11:37 |
mantis |
Dyrcona++ |
| 11:38 |
collum |
I'm curious about how often this data has to be sent. It seems like it would be outdated fairly quickly. |
| 11:59 |
pinesol |
[opensrf|Galen Charlton] LP1940146: (follow-up) remove a math_xul_client file from .gitignore - <http://git.evergreen-ils.org/?p=OpenSRF.git;a=commit;h=04524df> |
| 12:10 |
mantis |
collum: I know one wanted it sent daily |
| 12:26 |
gmcharlt |
https://evergreen-ils.org/opensrf-3-2-2-released/ |
| 12:41 |
|
collum joined #evergreen |
| 12:46 |
|
collum joined #evergreen |
| 12:51 |
Dyrcona |
gmcharlt++ |
| 14:50 |
csharp_ |
gmcharlt++ |
| 14:50 |
|
terranm joined #evergreen |
| 14:53 |
|
JBoyer_ joined #evergreen |
| 14:53 |
JBoyer_ |
Sweet. Looking forward to frequent reconnects with meetbot running. |
| 14:53 |
jeff |
I will not be able to make some of today's dev meeting, but I did want to mention that XUL excision is back on my radar after our upgrade later this month. |
| 14:54 |
terranm |
jeff++ |
| 14:54 |
JBoyer_ |
jeff++ |
| 14:55 |
|
tsadok joined #evergreen |
| 14:57 |
csharp_ |
@band add There Is No Dana Only XUL |
| 14:57 |
pinesol |
csharp_: Band 'There Is No Dana Only XUL' added to list |
| 14:57 |
|
shulabear joined #evergreen |
| 14:59 |
csharp_ |
jeff: is that because your staff will be fully migrating from XUL or is it a time/availability issue for you? |
| 15:00 |
|
sandbergja joined #evergreen |
| 15:00 |
jeff |
bit of both, i hope... but mostly the latter |
| 15:01 |
csharp_ |
gotcha |
| 15:01 |
JBoyer |
The clock says it's meeting time. Just finished my script and some of us have a meeting at 4 that can't be missed, so lets do a thing. |
| 15:02 |
JBoyer |
#startmeeting 2021-11-09 - Developer Meeting, Agenda Available at https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2021-11-09 |
| 15:02 |
pinesol |
Meeting started Tue Nov 9 15:02:00 2021 US/Eastern. The chair is JBoyer. Information about MeetBot at http://wiki.debian.org/MeetBot. |
| 15:02 |
pinesol |
Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. |
| 15:02 |
pinesol |
The meeting name has been set to '2021_11_09___developer_meeting__agenda_available_at_https___wiki_evergreen_ils_org_doku_php_id_dev_meetings_2021_11_09' |
| 15:02 |
JBoyer |
#topic Introductions |
| 15:02 |
JBoyer |
#info JBoyer = Jason Boyer, EOLI |
| 15:02 |
terranm |
#info terranm = Terran McCanna, PINES |
| 15:02 |
JBoyer |
And you, and you, and you? |
| 15:02 |
mmorgan |
#info mmorgan = Michele Morgan, NOBLE |
| 15:02 |
abneiman |
#info abneiman = Andrea Buntz Neiman, Equinox |
| 15:02 |
gmcharlt |
#info gmcharlt = Galen Charlton, EOLI |
| 15:02 |
csharp_ |
#info csharp = Chris Sharp, GPLS |
| 15:03 |
alynn26 |
#info alynn26 = Lynn Floyd, Evergreen Indiana |
| 15:03 |
berick |
#info berick = Bill Erickson, KCLS |
| 15:03 |
sandbergja |
#info sandbergja = Jane Sandberg, LBCC |
| 15:04 |
JBoyer |
Feel free to #info up if you're joining us later. |
| 15:04 |
JBoyer |
#topic Action Items from Last Meeting |
| 15:04 |
JBoyer |
#info shulabear will test out the staff client in Microsoft Edge |
| 15:04 |
JBoyer |
Any luck in this testing pursuit shulabear? |
| 15:04 |
JBoyer |
Who I just noticed didn't say anything above, so may not be available... |
| 15:05 |
Dyrcona |
#info Dyrcona = Jason Stephenson, CW MARS |
| 15:05 |
JBoyer |
We can come back to this if shulabear is available later. |
| 15:05 |
JBoyer |
Release talk! |
| 15:05 |
JBoyer |
#topic OpenSRF Release Updates |
| 15:05 |
JBoyer |
OpenSRF 3.2.2 has been released! |
| 15:05 |
JBoyer |
gmcharlt++ |
| 15:05 |
JBoyer |
Any other words you'd like to share, gmcharlt? |
| 15:05 |
terranm |
gmcharlt++ |
| 15:05 |
berick |
gmcharlt++ |
| 15:05 |
gmcharlt |
just that I've started a rel_3_3 series |
| 15:06 |
mmorgan |
gmcharlt++ |
| 15:06 |
JBoyer |
I'd like to remind everyone that there are also some signed off OpenSRF patches that could be poked at, etc. |
| 15:06 |
gmcharlt |
if nothing else, the Java & Python deprecation would warrant a new major release stream |
| 15:07 |
JBoyer |
Speaking of, |
| 15:07 |
JBoyer |
#topic Evergreen Release Updates |
| 15:08 |
JBoyer |
Evergreen 3.8.0 has also been released! |
| 15:08 |
sandbergja |
release_team++ |
| 15:08 |
Dyrcona |
gmcharlt++ |
| 15:08 |
JBoyer |
I don't have much to add, anyone else on the release team want to add anything? |
| 15:08 |
JBoyer |
gmcharlt++ # again |
| 15:08 |
terranm |
release_team++ |
| 15:08 |
sandbergja |
gmcharlt++ |
| 15:10 |
JBoyer |
In that case we can move on to a quick LP update |
| 15:10 |
JBoyer |
#topic Launchpad Snapshot as of noon-ish Eastern |
| 15:10 |
* JBoyer |
#info Open Bugs - 2512 |
| 15:10 |
JBoyer |
#info Pull Requests - 78 |
| 15:10 |
JBoyer |
#info Signed-off Bugs - 39 |
| 15:10 |
JBoyer |
Huh. Not sure how I /me'd that one ... |
| 15:10 |
|
shulabear joined #evergreen |
| 15:10 |
JBoyer |
v |
| 15:10 |
JBoyer |
#topic Launchpad Changes Since Last Meeting |
| 15:10 |
JBoyer |
#info Bugs Added - 49 |
| 15:11 |
JBoyer |
#info Pull Requests Added - 15 |
| 15:11 |
JBoyer |
v |
| 15:11 |
JBoyer |
#info Sign-offs Added - 3 |
| 15:11 |
JBoyer |
#info Fixes Committed - 9 |
| 15:11 |
shulabear |
#info shulabear = Shula Link, GPLS/GCHR |
| 15:11 |
JBoyer |
I need to find a client that will allow me to paste multiple lines.... |
| 15:11 |
Dyrcona |
JBoyer: Pidgin |
| 15:12 |
JBoyer |
Dyrcona, I'll check it out. |
| 15:12 |
JBoyer |
shulabear, any word on staff client functionality in MS Edge? |
| 15:13 |
shulabear |
Everything I tested - which was, admittedly, mainly circ and OPAC functions - worked fine in Edge |
| 15:13 |
JBoyer |
shulabear++ |
| 15:13 |
terranm |
shulabear++ |
| 15:13 |
JBoyer |
Those are things that see a lot of use |
| 15:14 |
shulabear |
The LocalAdmin panel seemed in order, too. |
| 15:14 |
gmcharlt |
shulabear++ |
| 15:15 |
mmorgan |
shulabear++ |
| 15:15 |
Dyrcona |
shulabear++ |
| 15:15 |
JBoyer |
We may revisit the topic of Edge support later since we have several larger new business items today. |
| 15:16 |
JBoyer |
#topic New Business |
| 15:16 |
JBoyer |
#info Updating Evergreen for Newer PostgreSQL Versions ( lp 1937294 ) |
| 15:16 |
pinesol |
Launchpad bug 1937294 in Evergreen "Updating Evergreen for Newer PostgreSQL Versions" [Undecided,New] https://launchpad.net/bugs/1937294 - Assigned to Jason Stephenson (jstephenson) |
| 15:16 |
JBoyer |
At a guess, Dyrcona ? |
| 15:16 |
JBoyer |
Hey, the agenda has been updated. :D |
| 15:16 |
Dyrcona |
:) |
| 15:17 |
JBoyer |
(and I sure did miss those 2 point release announcements. :-/ ) |
| 15:17 |
Dyrcona |
Yeah, so I know that JBoyer had mentioned wanting to have a look at some of the tests. I just wanted to see if anyone else is interested in having a look. If not, I will. |
| 15:18 |
Dyrcona |
It's important that we get moving on more recent PostgreSQL support in Evergreen because 9.6 is EOL on Thursday, and 10 is EOL in about a year. |
| 15:18 |
JBoyer |
I think the one I was kind of poking at during my last few hours at the hackaway may have been updated already. I'd like to have a look at more of them, but that's probably a couple weeks off. |
| 15:19 |
csharp_ |
upgrading to 10 over the next month or so |
| 15:19 |
Dyrcona |
JBoyer: OK. I can revisit the tests with more recent master and update the bug. |
| 15:19 |
Dyrcona |
We're running 10 in production, FWIW. |
| 15:19 |
csharp_ |
Dyrcona++ |
| 15:20 |
JBoyer |
Dyrcona++ |
| 15:20 |
Dyrcona |
In testing newer Pg releases, I've noticed performance gains in some areas and performance degradation in some others. |
| 15:21 |
Dyrcona |
I'm inclined at the moment to add support for newer releases in 3.9 regardless of whether or not all of the performance issues have been addressed. We can sort that out later. |
| 15:21 |
JBoyer |
+1 |
| 15:22 |
Dyrcona |
Maybe we can get a more comprehensive test suite along the way? |
| 15:22 |
JBoyer |
What did you have in mind, pgtap, live db, something else? |
| 15:23 |
JBoyer |
(Aside from "some of everything" because that would be great, but... ;) ) |
| 15:24 |
Dyrcona |
I'd like to figure out a way to combine pgtap with plprofiler. However, I got no output with plprofiler on Pg 14, but haven't had time to investigate. |
| 15:25 |
Dyrcona |
Testing performance can be tricky because some issues don't crop up until you have thousands or millions of records. |
| 15:26 |
alynn26 |
There is work on a large dataset for testing for Evergreen. |
| 15:26 |
Dyrcona |
I'm going to info the link to the Google drive folder where I've been making notes about what I've done so far. |
| 15:26 |
JBoyer |
Yeah, a performance testing suite might be something that has to be put together and expected to run on live-ish data, not so much for concerto. That would still be a useful thing. (and wouldn't necessarily need to be tied to any particular verison) |
| 15:26 |
Dyrcona |
#info Dyrcona's notes on PostgreSQL testing: https://drive.google.com/drive/folders/1sRZ8P1RHCOcZx42DxUehvOpoNkJJnfqn |
| 15:28 |
|
bgillap joined #evergreen |
| 15:28 |
Dyrcona |
So, in the meantime, I'll look at fixing the tests on newer Pg versions. It looks like the breakage is identical for Pg 12 through Pg 14. |
| 15:30 |
|
bgillap_ joined #evergreen |
| 15:30 |
JBoyer |
I know the version numbering change is somewhat symbolic, but it does feel like they're a lot more comfortable breaking things lately. We've hit issues with 10 in the past and now 12+ in just the last couple of years. |
| 15:31 |
|
bgillap_ left #evergreen |
| 15:31 |
|
bgillap_ joined #evergreen |
| 15:31 |
Dyrcona |
Eleven also has issues with Evergreen, just not as many. |
| 15:32 |
JBoyer |
I assume the next topic is closely related even though it's coming at things from a slightly different angle. |
| 15:32 |
Dyrcona |
Yeah, might as well move on. |
| 15:32 |
JBoyer |
#info array_accum Aggregate and PostgreSQL 14 ( lp 1947595 ) |
| 15:32 |
pinesol |
Launchpad bug 1947595 in Evergreen "array_accum Aggregate and PostgreSQL 14" [Undecided,New] https://launchpad.net/bugs/1947595 |
| 15:33 |
Dyrcona |
This one is more concrete. There's a branch on that bug that replaces our custom array_accum function with array_agg from Pg. If someone would like to look at it, that would be great! |
| 15:35 |
JBoyer |
It does seem pretty straightforward, does anyone want to volunteer to put a test system together to make sure that 2-3 calls of array_accum work the way we think they do? (which they almost certainly do) |
| 15:35 |
JBoyer |
I can get to it in a week or two if not. |
| 15:37 |
JBoyer |
I'd like to add that *anywhere* we have a func that largely duplicates (or because of age, exactly duplicates) an internal function we do whatever we can to remove it. I keep giving evergreen.upper and .lower sideeye but I know it's something to do with consistency in the face of multiple potential Unicode implementations, etc. |
| 15:38 |
JBoyer |
#action JBoyer will test out the branch in lp 1947595 |
| 15:38 |
pinesol |
Launchpad bug 1947595 in Evergreen "array_accum Aggregate and PostgreSQL 14" [Undecided,New] https://launchpad.net/bugs/1947595 |
| 15:38 |
JBoyer |
Moving on with less than 20 before I vanish, |
| 15:38 |
JBoyer |
#info Hackaway followup: Automating point release notes (abneiman) |
| 15:38 |
JBoyer |
abneiman ? |
| 15:39 |
JBoyer |
(And I am going to just push any further Edge support discussion to December at this point) |
| 15:40 |
abneiman |
nothing to report, just wanted to make sure those not at Hackaway knew that this was a conversation point - since apparently release-notes-gathering was a factor in delaying 3.7.2/3.6.5 - so if anyone in the dev community has thoughts or tuits around that, please share :) |
| 15:40 |
JBoyer |
abneiman++ |
| 15:40 |
abneiman |
the gist being "yes! we should automate point release notes more, in some manner" |
| 15:41 |
csharp_ |
yes - we developers need to be adding release notes documentation as we fix bugs as well as add features |
| 15:41 |
csharp_ |
a big question was where those would live and how to rejigger the building process for point releases to deal with them |
| 15:43 |
csharp_ |
but the current process of documenters who may not have deep tech knowledge were having to reverse engineer release notes based on reading git commit messages |
| 15:44 |
csharp_ |
...is not optimal |
| 15:44 |
csharp_ |
(sorry, finished that sentence without remembering how I started it :-) ) |
| 15:44 |
JBoyer |
Is there an LP for this? That doesn't exactly lend it more urgency but does make it harder to forget if it's a high priority or similar. |
| 15:44 |
csharp_ |
not that I'm aware of |
| 15:44 |
csharp_ |
I can open one |
| 15:44 |
abneiman |
I don't think there's an LP but i can make one |
| 15:45 |
abneiman |
jinx csharp_ |
| 15:45 |
csharp_ |
abneiman: be my guest |
| 15:45 |
Dyrcona |
What csharp_ and abneiman said. :) |
| 15:45 |
JBoyer |
Rock, paper, scissors, we need a pinesol plugin |
| 15:45 |
csharp_ |
@decide csharp_ or abneiman |
| 15:45 |
pinesol |
csharp_: That's a tough one... |
| 15:45 |
abneiman |
:) will do |
| 15:45 |
JBoyer |
abneiman++ |
| 15:45 |
JBoyer |
csharp_++ |
| 15:45 |
csharp_ |
abneiman++ |
| 15:45 |
terranm |
There is a "needsreleasenotes" tag that bug wranglers and testers can start using more, too |
| 15:45 |
mmorgan |
bug 1948674 |
| 15:45 |
pinesol |
Launchpad bug 1948674 in Evergreen "Improve release building automation" [Undecided,New] https://launchpad.net/bugs/1948674 |
| 15:46 |
csharp_ |
heh - *my* bug, even |
| 15:46 |
mmorgan |
csharp_ is fast! |
| 15:46 |
csharp_ |
time travel is definitely real guyz |
| 15:46 |
abneiman |
terranm++ yes, that too |
| 15:46 |
JBoyer |
terranm, as I (possibly mis-)understand it this is more about massaging all of the existing release notes so it's easier to build releases, it's less about getting devs to write the notes. |
| 15:47 |
JBoyer |
(which they should be doing, yes!) |
| 15:47 |
JBoyer |
mmorgan++ |
| 15:48 |
abneiman |
it's a little of both - for point releases, where only a short sentence is really called for, a dev should write a short "release note: words here" message .... and then hopefully that can be additionally automated in the future, but the first step is helpful to those manuallly assembling point release notes |
| 15:49 |
csharp_ |
#info Launchpad bug 1948674 in Evergreen "Improve release building automation" [Undecided,New] https://launchpad.net/bugs/1948674 |
| 15:49 |
pinesol |
Launchpad bug 1948674 in Evergreen "Improve release building automation" [Undecided,New] |
| 15:49 |
terranm |
Yes, the content has to be there in order for automation to work, so both |
| 15:49 |
JBoyer |
So if anyone is interested in helping out review the wiki pages about releases or release notes to see what's being done today. (One or both may be labeled 2.something. That's still the current stuff for now...) |
| 15:49 |
csharp_ |
use Developer::Mind::Reading; |
| 15:50 |
abneiman |
csharp_++ |
| 15:50 |
JBoyer |
Any last minute urgent and short topics before I reveal the surprising announcement that awaits us? |
| 15:50 |
JBoyer |
too late! |
| 15:50 |
JBoyer |
#topic Announcements |
| 15:50 |
JBoyer |
#info next meeting is December 14th, 2021 |
| 15:51 |
JBoyer |
Thanks everyone |
| 15:51 |
JBoyer |
#endmeeting |
| 15:51 |
pinesol |
Meeting ended Tue Nov 9 15:51:07 2021 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
| 15:51 |
pinesol |
Minutes: http://evergreen-ils.org/meetings/evergreen/2021/evergreen.2021-11-09-15.02.html |
| 15:51 |
pinesol |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2021/evergreen.2021-11-09-15.02.txt |
| 15:51 |
pinesol |
Log: http://evergreen-ils.org/meetings/evergreen/2021/evergreen.2021-11-09-15.02.log.html |
| 15:51 |
terranm |
JBoyer++ |
| 15:51 |
mmorgan |
JBoyer++ |
| 15:51 |
Dyrcona |
JBoyer++ |
| 15:51 |
abneiman |
JBoyer++ |
| 15:51 |
* JBoyer |
disappears |
| 15:52 |
csharp_ |
JBoyer++ |
| 15:52 |
shulabear |
jboyer++ |
| 15:53 |
gmcharlt |
JBoyer++ |
| 16:30 |
|
jvwoolf left #evergreen |
| 16:53 |
bgillap_ |
Does anyone have an opensrf systemd script I can look at... with like sip and stuff? |
| 16:54 |
bgillap_ |
app servers never come back nice and I have to go restart stuff by hand every time. |
| 16:54 |
bgillap_ |
had a power outage today that reminded me. |
| 16:54 |
bgillap_ |
I think we're on like 3-6-1-1 or 11 something or other. |
| 17:02 |
|
mmorgan left #evergreen |
| 17:21 |
JBoyer |
bgillap_, check out https://github.com/HitScan/systemd-evergreen |
| 17:22 |
JBoyer |
shouldn't be version-specific, though you'll want to make sure that they cover your needs (may need to remove some things from Requires or things along those lines) |
| 17:23 |
JBoyer |
they've been developed and well-tested against single server setups, but will likely need tweaking for production use. |
| 18:02 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
