| Time |
Nick |
Message |
| 05:06 |
|
mrisher joined #evergreen |
| 06:01 |
pinesol |
News from qatests: Failed Running perl live tests <http://testing.evergreen-ils.org/~live//archive/2020-09/2020-09-17_04:00:03/test.49.html> |
| 07:25 |
|
rjackson_isl_hom joined #evergreen |
| 07:33 |
csharp |
fg |
| 07:38 |
|
Dyrcona joined #evergreen |
| 07:39 |
Dyrcona |
That "neat trick" ain't so neat. The strings are never actually zero. If I'd just used the actual process IDs instead of being too clever, by using pgrep, it would have worked. |
| 07:50 |
|
collum joined #evergreen |
| 07:51 |
|
collum joined #evergreen |
| 08:34 |
|
mmorgan joined #evergreen |
| 08:34 |
|
alynn26 joined #evergreen |
| 08:34 |
Dyrcona |
My syslog situation appears to be that /var/log/syslog got too big to rotate. Other files have rotated. /var/log/syslog is currently 61GB in size. |
| 08:35 |
Dyrcona |
Not sure what to do with that other than to truncate it and see what happens. |
| 08:39 |
|
mantis1 joined #evergreen |
| 08:39 |
* Dyrcona |
also wonders about the 6.8GB in /var/log/syslog.1 |
| 08:39 |
|
rfrasur joined #evergreen |
| 08:44 |
Dyrcona |
Accumulating 6.8GB of logs on an "unused" server at the normal loglevel in a single day seems like a bit much..... |
| 08:59 |
Dyrcona |
Hm.. I also did the upgrade on the day that logrotate had the problem. That could be part of the reason for the large size, but I'll never know, now. |
| 09:00 |
|
collum joined #evergreen |
| 09:14 |
Dyrcona |
No, on to another server and another "problem." I want to find the domain sockets for each of my PostgreSQL instances on my development server with 4 versions installed. If I just run psql, I always connect to Pg 12. |
| 09:18 |
Dyrcona |
Ok. They're under /run/postgresql/ and not /var/run/postgresql/ |
| 09:18 |
Dyrcona |
Now, to vacuum full on Pg 10 and Pg 9.6. |
| 09:20 |
Dyrcona |
I think it's bad that you specify the socket file or the socket port with the --port option. I'd expect a separate --socket option for the socket file, but what do I know? :) |
| 09:22 |
Dyrcona |
Either the man page for psql lies or vacuumdb doesn't accept the socket file as an option: could not connect to database postgres: invalid integer value "/run/postgresql/.s.PGSQL.5434" for connection option "port" |
| 09:24 |
Dyrcona |
Either the manpage lies, or I don't understand. I guess I make the connection over TCP. |
| 09:25 |
Dyrcona |
vacuum++ |
| 09:25 |
Dyrcona |
typos-- |
| 09:34 |
|
nfBurton joined #evergreen |
| 09:45 |
|
nfBurton55 joined #evergreen |
| 09:45 |
|
jvwoolf joined #evergreen |
| 09:47 |
|
alynn26_away joined #evergreen |
| 09:52 |
|
dbwells_ joined #evergreen |
| 09:59 |
csharp |
Dyrcona: I learned when running multiple versions of PG that psql checks /var/lib/postgresql/<version> and /etc/postgresql/<version> for the highest number and tries to run that version |
| 10:07 |
Dyrcona |
csharp: I've found that it seems to use whatever is on port 5432. |
| 10:07 |
Dyrcona |
Unless --port is specified. |
| 10:08 |
csharp |
ah - yeah - that's probably the first thing it looks at |
| 10:28 |
|
alynn26_away joined #evergreen |
| 10:31 |
csharp |
has anyone looked into adding a batching/chunking feature to action triggers? it currently just tries to process unreasonably large swaths of data with no regard for whether it can actually handle it |
| 10:32 |
berick |
csharp: there have been discussions in the past re: performing the grouping up front in the database instead of collecting *all the things* to figure out the grouping |
| 10:32 |
berick |
never made it past dicussion though |
| 10:33 |
csharp |
I'm about to try to process a backlog of account expire notices for 392K patrons (covid-related delay, of course) and right now I'm planning to hack the A/T filters to check *a* field that I'll enter data in/remove data from |
| 10:33 |
csharp |
berick: good to know |
| 10:34 |
berick |
ideally it would process one group of events to completion, then start on the next. that'll take some work. |
| 10:35 |
|
dbwells joined #evergreen |
| 10:37 |
Dyrcona |
csharp berick: I think A/T is the wrong way to do this. Just run a perl script that talks directly to the database. |
| 10:38 |
Dyrcona |
Also, I don't think A/T does bundling/chunking. I had a patron with 123 items out blow up on max_stanza_size when doing the autorenewal email. |
| 10:38 |
berick |
well sure but that's not an option for everyone |
| 10:38 |
Dyrcona |
berick: Sure it is if it comes with Evergreen. |
| 10:39 |
* csharp |
assumes berick was referring to perl chops |
| 10:40 |
csharp |
@band add Perl Chops |
| 10:40 |
pinesol |
csharp: Band 'Perl Chops' added to list |
| 10:40 |
Dyrcona |
Back to my patron with 123 items out: the template_output.data was only about 25k, but I suspect it was repeated 123 times in the ejabberd message, plus XML overhead that would have easily been 2-3MB or larger. |
| 10:40 |
Dyrcona |
I set max stanza size on that utility server to 10MB. |
| 10:42 |
Dyrcona |
When this "crashes," the action trigger runner hands up for a while, and no other events get processed, and it can also affect event definitions, depending on the granularity settings. |
| 10:43 |
Dyrcona |
I've mentioned it here before and opened a Lp bug, but no tuits. |
| 10:46 |
Dyrcona |
Is anyone using Ubuntu 18.04 in production? I suspect so, but I don't actually know. |
| 10:47 |
Dyrcona |
My folks are leery of upgrading because of issues on our training server. |
| 10:47 |
|
AFloyd__ joined #evergreen |
| 10:48 |
Bmagic |
Dyrcona: I was about to ask the exact same question! |
| 10:48 |
Bmagic |
we've been shying away from 18.04 for Evergreen bricks, in favor of 16.04 - for a reason I cannot remember. But for the DB, 18.04 no prob |
| 10:50 |
Dyrcona |
Bmagic: I actually thought you might be using 18.04. I'm relatively confident that 18.04 is safe, but.... |
| 10:51 |
Dyrcona |
No one wants to be first.... :( |
| 10:52 |
berick |
we're using 18.04 on the bricks |
| 10:52 |
berick |
other servers pending |
| 10:53 |
berick |
wasn't aware there were any issues |
| 10:53 |
Dyrcona |
berick: Thanks! That's good to know. |
| 10:53 |
Dyrcona |
I honestly don't think the "issues" we've had on training have anything to do with 18.04, but you know how it goes. |
| 10:53 |
|
terranm joined #evergreen |
| 10:55 |
csharp |
we're moving everything to 18.04 over the next few weeks |
| 10:56 |
berick |
16.04 will reach of standard support in no time |
| 10:57 |
Dyrcona |
Yes, and 20.04 has been out for 5 months, and Pg 9.6 is EOL in Noveber 2021, and Pg 13 comes out soon, and .... :) |
| 11:03 |
gmcharlt |
https://evergreen-ils.org/evergreen-3-6-beta1-available/ |
| 11:03 |
jeff |
gmcharlt++ |
| 11:04 |
Dyrcona |
gmcharlt++ |
| 11:04 |
Bmagic |
gmcharlt++ |
| 11:04 |
|
alynn26_away joined #evergreen |
| 11:04 |
|
AFloyd__ joined #evergreen |
| 11:05 |
|
AFloyd__ joined #evergreen |
| 11:08 |
gmcharlt |
JBoyer++ |
| 11:08 |
gmcharlt |
terranm++ |
| 11:08 |
gmcharlt |
mmorgan++ |
| 11:09 |
mmorgan |
gmcharlt++ |
| 11:09 |
mmorgan |
JBoyer++ |
| 11:09 |
mmorgan |
terranm++ |
| 11:10 |
jeff |
JBoyer++ terranm++ mmorgan++ |
| 11:10 |
terranm |
gmcharlt++ JBoyer++ mmorgan++ |
| 11:10 |
JBoyer |
gmcharlt++ terranm++ mmorgan++ |
| 11:11 |
JBoyer |
@oprah plusses |
| 11:11 |
pinesol |
JBoyer: Zoia knows how to make fusilli. |
| 11:11 |
JBoyer |
alas. |
| 11:11 |
agoben |
gmcharlt++ terranm++ mmorgan++ JBoyer++ |
| 11:13 |
Dyrcona |
terranm++ mmorgan++ JBoyer++ |
| 11:38 |
dbwells |
gmcharlt++ terranm++ mmorgan++ JBoyer++ |
| 11:42 |
gmcharlt |
Bmagic: I've discovered a nice little side effect of the Anotora-ization: it's resulted in the size of the release tarball decreasing by ~10M |
| 11:44 |
Dyrcona |
Bmagic++ |
| 11:51 |
csharp |
gmcharlt++ |
| 11:53 |
gmcharlt |
berick: assuming you have the creds, could you approve my request to join the Evergreen project on poeditor and further grant me privs to import XML files? |
| 11:53 |
|
dbwells joined #evergreen |
| 11:54 |
berick |
gmcharlt: i'll sure give it a shot |
| 11:54 |
gmcharlt |
thanks! |
| 11:56 |
berick |
gmcharlt: let me know if what I just did worked |
| 11:59 |
gmcharlt |
berick: hmm, let's letting me act as a contributor, but no access to import to English as far as I can tell |
| 12:00 |
|
nfBurton joined #evergreen |
| 12:01 |
berick |
hm, it won't let me make you an admin, i guess since I don't 'own' the project |
| 12:01 |
berick |
gmcharlt: ok i added you as an english contributor. maybe that'll do it |
| 12:02 |
dbwells |
gmcharlt: I just bumped you to be an admin. |
| 12:02 |
gmcharlt |
dbwells++ |
| 12:02 |
gmcharlt |
dbwells: can you confirm that https://poeditor.com/projects/po_edit?id_language=43&id=218177 is where I'd want to do an import once I generate the XMB file? |
| 12:03 |
berick |
dbwells: how, pray tell? |
| 12:03 |
gmcharlt |
and are we doing anything special to handle differences between release branches for the eg2 translations? |
| 12:05 |
berick |
oh, pffth, dbwells is the project owner |
| 12:05 |
berick |
gmcharlt: no, not yet anyway |
| 12:06 |
dbwells |
gmcharlt: I think that looks right, but these are not well-tread grounds by any means. |
| 12:06 |
gmcharlt |
ok |
| 12:06 |
dbwells |
berick might know better. |
| 12:06 |
gmcharlt |
I'll keep my fingers and toes crossed |
| 12:06 |
gmcharlt |
but first step - need to deal with an issue where the AOT compiler expects a tweak in order to allow strings to be exported |
| 12:07 |
dbwells |
gmcharlt: Actually, maybe here instead?: https://poeditor.com/projects/import?id=218177 |
| 12:08 |
gmcharlt |
dbwells: ah, thanks - that does look more likely |
| 12:08 |
berick |
yeah, i belive that's the spot (https://poeditor.com/projects/import?id=218177) |
| 12:15 |
|
rjackson_isl_hom joined #evergreen |
| 12:16 |
|
khuckins joined #evergreen |
| 12:19 |
pinesol |
[evergreen|Galen Charlton] make npm run export-strings happier - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=6f73091> |
| 12:20 |
dbwells |
gmcharlt: I contacted POEditor a while back to ask for advice about multi-branch, and the only thing they had to suggest was the judicious use of tags. I think it may be worth tagging your import with '3.6' or 'rel_3_6' so we can start to see how that plays out, probably applying the tag to "All". |
| 12:22 |
gmcharlt |
dbwells: OK, I've done an import with a rel_3_6 tag |
| 12:22 |
|
_bott_ joined #evergreen |
| 12:22 |
gmcharlt |
I had also done an untagged import just before you spoke up... so we'll see what happens |
| 12:26 |
dbwells |
Cool, I think that will be fine. Did you also do the "Also import translations in..." option for English? |
| 12:26 |
|
khuckins joined #evergreen |
| 12:26 |
gmcharlt |
dbwells: ah, no. I gather I should? |
| 12:26 |
gmcharlt |
ah, I see it documented on the wiki |
| 12:27 |
gmcharlt |
ok, that's now done |
| 12:28 |
dbwells |
Yeah, I think it can be done together or separate for that bit. |
| 12:29 |
dbwells |
That looks happier. |
| 12:33 |
dbwells |
I think the tagging seems to have worked also, with 49 terms being no longer current. Sounds about right, but not seeing a way yet to see just the non-rel_3_6 terms to get an idea what those 49 are, and see if they make sense. |
| 12:34 |
gmcharlt |
may trying string exports from rel_3_5 and rel_3_4 and uploading with appropriate tags might do it |
| 12:34 |
gmcharlt |
and then being careful about how to handle terms that are marked obsolete during import |
| 12:35 |
gmcharlt |
noting that I did _not_ remove any such obsolete terms when I did the import just |
| 12:37 |
csharp |
Dyrcona: thanks for the tip to work outside A/T for this - that might be more doable than all the hacking I was looking at |
| 12:37 |
dbwells |
Just scrolling through, found a few. One example, "Login Type..." is no longer current, while "Login Type" is. Looks perfectly reasonable as something which might have changed over the last couple years. |
| 12:39 |
dbwells |
Yeah, if we want to support multiple branches, then terms will just build up, and once we get them tagged, that seems fine to me, overall. |
| 12:41 |
jeffdavis |
Dyrcona: since you were having max children problems, I wonder if this would help with your oversized syslog woes: https://git.evergreen-ils.org/?p=working/OpenSRF.git;a=shortlog;h=refs/heads/user/berick/lpxxx-c-backlog-speedbump |
| 12:41 |
|
rfrasur joined #evergreen |
| 12:44 |
Dyrcona |
rfrasur: wb! |
| 12:44 |
rfrasur |
ty! My connection to the [internet] feels laggy today. So rebooted. I might be the laggy one. |
| 12:54 |
|
terranm joined #evergreen |
| 13:02 |
agoben |
Reminder that the EOP/TEP board meeting will be in about an hour. |
| 13:02 |
agoben |
^EOB not EOP, sorry. |
| 13:05 |
Bmagic |
Dyrcona: berick: I remember what it was: email was broken in 18.04 |
| 13:06 |
Dyrcona |
Bmagic: Yes, but email is fixed in 18.04, now. |
| 13:06 |
Bmagic |
gmcharlt: those were probably the unused images |
| 13:06 |
Bmagic |
Dyrcona: sweet! That's sorta new right? like within the last 12 months? |
| 13:11 |
Dyrcona |
Bmagic: I was looking for the bug and can't seem to find it, but yeah, I think it went in earlier this year. |
| 13:13 |
Dyrcona |
Bmagic: Lp 1801163 When Lp search fails for Fix Released bugs, git log helps. :) |
| 13:13 |
pinesol |
Launchpad bug 1801163 in Evergreen 3.5 "SendEmail A/T reactor broken for recent version of Encode::MIME::Header" [High,Fix released] https://launchpad.net/bugs/1801163 |
| 13:14 |
jeff |
bug 1801163 |
| 13:14 |
jeff |
yeah. |
| 13:14 |
jeff |
though i found it via launchpad, surprisingly enough. |
| 13:15 |
Dyrcona |
In Lp's defense, I may have only had Fix Committed checked when I did the broad search for "email." I tried looking for email send earlier, because I was thinking of the Perl module name, not the reactor....TMI.... I know. :) |
| 13:16 |
Dyrcona |
Ayup... Fix Committed.... My bad. :) |
| 13:17 |
|
jvwoolf1 joined #evergreen |
| 13:23 |
Bmagic |
Therefore, I can summize that 18.04 will only work correctly on Evergreen >=3.3.6, >=3.4.2 and >=3.5 and beyond |
| 13:26 |
Dyrcona |
Bmagic: The ubuntu 18.04 patches are easily backported to 3.2. |
| 13:27 |
Bmagic |
oh nice |
| 13:31 |
|
dbwells joined #evergreen |
| 13:33 |
|
dbwells_ joined #evergreen |
| 13:37 |
|
jlundgren joined #evergreen |
| 13:38 |
|
sandbergja joined #evergreen |
| 13:41 |
|
cowens joined #evergreen |
| 13:43 |
|
nfBurton7 joined #evergreen |
| 13:45 |
|
tlittle joined #evergreen |
| 13:55 |
agoben |
5 minutes until the EOB/TEP meeting. |
| 13:59 |
gmcharlt |
typing around that cat... as usual, this time of afternoon |
| 14:00 |
rhamby |
cats are very helpful for typing things, I know because they tell me so |
| 14:00 |
agoben |
#startmeeting EOB/Evergreen Project Board meeting for 2020-09-17, agenda: https://wiki.evergreen-ils.org/doku.php?id=governance:minutes:2020-09-17 |
| 14:00 |
pinesol |
Meeting started Thu Sep 17 14:00:19 2020 US/Eastern. The chair is agoben. Information about MeetBot at http://wiki.debian.org/MeetBot. |
| 14:00 |
pinesol |
Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. |
| 14:00 |
|
Topic for #evergreen is now (Meeting topic: EOB/Evergreen Project Board meeting for 2020-09-17, agenda: https://wiki.evergreen-ils.org/doku.php?id=governance:minutes:2020-09-17) |
| 14:00 |
pinesol |
The meeting name has been set to 'eob_evergreen_project_board_meeting_for_2020_09_17__agenda__https___wiki_evergreen_ils_org_doku_php_id_governance_minutes_2020_09_17' |
| 14:00 |
agoben |
#topic Roll Call |
| 14:00 |
|
Topic for #evergreen is now Roll Call (Meeting topic: EOB/Evergreen Project Board meeting for 2020-09-17, agenda: https://wiki.evergreen-ils.org/doku.php?id=governance:minutes:2020-09-17) |
| 14:00 |
agoben |
Use the #info command to provide name and affiliation |
| 14:00 |
agoben |
#info agoben = Anna Goben, Evergreen Indiana |
| 14:00 |
tlittle |
#info tlittle = Tiffany Little, PINES |
| 14:00 |
JBoyer |
#info JBoyer = Jason Boyer, Equinox |
| 14:00 |
jlundgren |
#info Jeanette Lundgren, CW MARS |
| 14:00 |
rhamby |
#info rhamby = Rogan Hamby, Equinox |
| 14:00 |
nfBurton7 |
#info nfBurton7 = Chris Burton, NFPL |
| 14:00 |
gmcharlt |
#info gmcharlt = Galen Charlton, Equinox |
| 14:00 |
jvwoolf1 |
#info jvwoolf = Jessica Woolford, Bibliomation |
| 14:00 |
cowens |
#info cowens = Chris Owens, COOL/BPL |
| 14:01 |
terranm |
#info terranm = Terran McCanna, PINES |
| 14:02 |
agoben |
Anyone heard from dluch? |
| 14:02 |
rfrasur |
#info rfrasur = Ruth Frasur, Evergreen Indiana, ECDI |
| 14:02 |
dluch |
#info dluch = Debbie Luchenbill, MOBIUS |
| 14:02 |
agoben |
#topic Approval of Minutes |
| 14:02 |
|
Topic for #evergreen is now Approval of Minutes (Meeting topic: EOB/Evergreen Project Board meeting for 2020-09-17, agenda: https://wiki.evergreen-ils.org/doku.php?id=governance:minutes:2020-09-17) |
| 14:02 |
dluch |
Sorry, I got caught up in something and didn't pay attention to time! |
| 14:02 |
agoben |
#info Minutes from 2020-08-20 meeting: https://evergreen-ils.org/meetings/evergreen/2020/evergreen.2020-08-20-14.00.html |
| 14:03 |
agoben |
Corrections, updates, suggestions? |
| 14:03 |
agoben |
No worries, just wanted to make sure we had all of the committee members signed in :) |
| 14:04 |
JBoyer |
None here |
| 14:04 |
tlittle |
None here. |
| 14:04 |
agoben |
#startvote Accept minutes from 2020-08-20? yes, no |
| 14:04 |
pinesol |
Begin voting on: Accept minutes from 2020-08-20? Valid vote options are yes, no. |
| 14:04 |
pinesol |
Vote using '#vote OPTION'. Only your last vote counts. |
| 14:04 |
dluch |
None here, either |
| 14:04 |
agoben |
#vote yes |
| 14:04 |
tlittle |
#vote yes |
| 14:04 |
dluch |
#vote yes |
| 14:04 |
JBoyer |
#vote yes |
| 14:04 |
cowens |
#vote yes |
| 14:04 |
jvwoolf1 |
#vote yes |
| 14:04 |
jlundgren |
#vote yes |
| 14:05 |
gmcharlt |
#vote yes |
| 14:05 |
agoben |
#endvote |
| 14:05 |
pinesol |
Voted on "Accept minutes from 2020-08-20?" Results are |
| 14:05 |
pinesol |
yes (8): JBoyer, agoben, cowens, tlittle, jlundgren, jvwoolf1, gmcharlt, dluch |
| 14:06 |
agoben |
#topic Chair Report |
| 14:06 |
|
Topic for #evergreen is now Chair Report (Meeting topic: EOB/Evergreen Project Board meeting for 2020-09-17, agenda: https://wiki.evergreen-ils.org/doku.php?id=governance:minutes:2020-09-17) |
| 14:06 |
agoben |
#info No updates here. |
| 14:06 |
agoben |
#topic Financial Report |
| 14:06 |
|
Topic for #evergreen is now Financial Report (Meeting topic: EOB/Evergreen Project Board meeting for 2020-09-17, agenda: https://wiki.evergreen-ils.org/doku.php?id=governance:minutes:2020-09-17) |
| 14:06 |
gmcharlt |
#info No substantial changes to our financial position since the last meeting. |
| 14:06 |
gmcharlt |
#info Draft of grant report to SFC available to board members here: https://docs.google.com/document/d/1NEJaLNGFNzZPjVFVD2OOOhfAjP41ALVnSBGN6rVQssI/edit |
| 14:07 |
gmcharlt |
if you're a board member and that link doesn't work for you, let me know |
| 14:07 |
gmcharlt |
would appreciate review by end of week unless the rest of you are inclined to give a +1 during this meeting |
| 14:07 |
gmcharlt |
upon review, I'll wrap it up in some TEP letterhead and submit it |
| 14:08 |
jvwoolf1 |
Looks good to me |
| 14:08 |
gmcharlt |
#info Still working on tax return; now targetting 9/25 to have a draft ready for reivew by board officers and any other intrested board members |
| 14:08 |
gmcharlt |
and that's it, unless there are questions |
| 14:08 |
agoben |
Sounds good. And I don't have any additions or changes at this time so I'd be alright if the committee wanted to vote on that today |
| 14:08 |
dluch |
Looks good to me, other than needing to remove an s from the second word |
| 14:09 |
tlittle |
Looks good to me |
| 14:09 |
dluch |
Got it. :-) |
| 14:09 |
JBoyer |
+1 from me |
| 14:09 |
cowens |
+1 |
| 14:09 |
jlundgren |
do you need to include the total $ of expenditures or remaining balance for the report? |
| 14:09 |
gmcharlt |
there is always that one typo, at least in any documents I author |
| 14:09 |
|
terranm joined #evergreen |
| 14:09 |
nfBurton7 |
+1 |
| 14:09 |
agoben |
That's fair. Adding a balance line-item would be good. |
| 14:09 |
tlittle |
+1 |
| 14:10 |
jlundgren |
+1 |
| 14:10 |
agoben |
+1 |
| 14:10 |
dluch |
+1 |
| 14:10 |
JBoyer |
jlundgren++ |
| 14:10 |
gmcharlt |
I've now added a sentence to supply the balance |
| 14:10 |
agoben |
++ |
| 14:10 |
tlittle |
gmcharlt++ |
| 14:10 |
jvwoolf1 |
jlundgren++ |
| 14:10 |
agoben |
I think you're good to go once you add the headers! |
| 14:10 |
jvwoolf1 |
gmcharlt++ |
| 14:10 |
dluch |
gmcharlt++ |
| 14:11 |
jlundgren |
gmcharlt++ |
| 14:11 |
gmcharlt |
ok. I'll email the list once the report has been submitted |
| 14:11 |
agoben |
gmcharlt++ |
| 14:11 |
terranm |
gmcharlt++ |
| 14:11 |
agoben |
And we'll be on the lookout for the 990 draft shortly |
| 14:11 |
agoben |
Anything else on the fiscal front? |
| 14:12 |
gmcharlt |
no |
| 14:12 |
agoben |
Thank you for all of your work on that! |
| 14:12 |
agoben |
#topic SFC Updates |
| 14:12 |
|
Topic for #evergreen is now SFC Updates (Meeting topic: EOB/Evergreen Project Board meeting for 2020-09-17, agenda: https://wiki.evergreen-ils.org/doku.php?id=governance:minutes:2020-09-17) |
| 14:12 |
agoben |
I don't have anything here; does anyone else? |
| 14:12 |
gmcharlt |
none from me |
| 14:12 |
JBoyer |
No |
| 14:12 |
tlittle |
No. |
| 14:12 |
agoben |
ok, moving on then. |
| 14:12 |
agoben |
#topic Release Manager update |
| 14:12 |
|
Topic for #evergreen is now Release Manager update (Meeting topic: EOB/Evergreen Project Board meeting for 2020-09-17, agenda: https://wiki.evergreen-ils.org/doku.php?id=governance:minutes:2020-09-17) |
| 14:13 |
agoben |
Cheers on the 3.6 beta drop! |
| 14:13 |
tlittle |
Yay! |
| 14:13 |
gmcharlt |
#info 3.6-beta was released on 2020-09-17 |
| 14:13 |
dluch |
So exciting! |
| 14:13 |
gmcharlt |
#info Bug Squashing Week will run the week of 2020-09-21 |
| 14:13 |
gmcharlt |
featureful release |
| 14:13 |
agoben |
Very much so |
| 14:14 |
gmcharlt |
the main thing I would like to highlight in terms of long term implications is the new Bootstrap OPAC skin |
| 14:15 |
gmcharlt |
most notably, discussions about (a) when to make it the default skin and (b) when/if to deprecate, then remove the TPAC skin |
| 14:15 |
gmcharlt |
so, I'm raising this mostly as an FYI for the Board, but it is the one factor where they may be some community disagreement |
| 14:15 |
agoben |
Same with the new staff only catalog, right? |
| 14:16 |
gmcharlt |
indeed |
| 14:16 |
agoben |
As far as it being up in the air on final default status, anyway. |
| 14:16 |
gmcharlt |
yeah |
| 14:16 |
agoben |
Looking forward to seeing it all in action! |
| 14:17 |
agoben |
I know some of the other members of the team are on today, any comments from you? |
| 14:17 |
nfBurton7 |
As long as the current TPAC is available, it shouldn't be much of an issue moving it to default because you can always roll back? |
| 14:17 |
terranm |
I think Galen said it all gmcharlt++ |
| 14:17 |
JBoyer |
Nothing much to add. Looking forward to it being finished and available. :) |
| 14:17 |
gmcharlt |
nfBurton7: yeah, the question of default isn't that big of a deal, IMO |
| 14:18 |
agoben |
Congrats to you all on all of the hard work so far. I know I'm excited to see several of the features in action officially! |
| 14:18 |
gmcharlt |
the bigger question is how long multiple OPAC skins can reasonably be supported by the community |
| 14:18 |
nfBurton7 |
Yeah, I think a longer term for the TPAC is valid because others built their OPAC off of it |
| 14:18 |
gmcharlt |
as we've historically /not/ have a great experience trying to maintain two separate primary OPAC skins |
| 14:19 |
gmcharlt |
and we're not presently setup up to do theming as (relatively) easily as (say) WordPress |
| 14:19 |
nfBurton7 |
I'm hoping to eventually maybe lol |
| 14:19 |
nfBurton7 |
Like have a page for style choices so a librarian could do it |
| 14:20 |
terranm |
nfBurton7++ PINES is really looking forward to moving to it |
| 14:20 |
agoben |
++ |
| 14:20 |
agoben |
Anything else on the release front then? |
| 14:20 |
gmcharlt |
none from me |
| 14:20 |
jvwoolf1 |
nfBurton7++ |
| 14:20 |
jvwoolf1 |
gmcharlt++ |
| 14:20 |
agoben |
#topic Hack-A-Way Update |
| 14:20 |
|
Topic for #evergreen is now Hack-A-Way Update (Meeting topic: EOB/Evergreen Project Board meeting for 2020-09-17, agenda: https://wiki.evergreen-ils.org/doku.php?id=governance:minutes:2020-09-17) |
| 14:20 |
agoben |
#info Registration is currently open for the Hack-A-Way |
| 14:21 |
agoben |
rhamby, do you have other updates about the HAW? |
| 14:21 |
rhamby |
I sent an update to the list but the short version is that we are moving ahead on all fronts. |
| 14:21 |
rhamby |
Some content will be out in the next few weeks to show folks how to setup their own sessions. |
| 14:22 |
rhamby |
Also the surveys indicated some areas people are interested in common work groups so we may reach out to some community members who would be qualified to lead those discussions. |
| 14:22 |
agoben |
#info Full update here: http://list.evergreen-ils.org/pipermail/board/2020-September/000150.html |
| 14:22 |
rhamby |
The list of intersts is pretty long though and will probably have to be scaled back lest it become a mini-conference. |
| 14:22 |
rhamby |
interests even |
| 14:22 |
terranm |
rhamby++ |
| 14:23 |
dluch |
rhamby++ |
| 14:23 |
JBoyer |
rhamby++ |
| 14:23 |
rhamby |
We will capture all the info for future events though. |
| 14:23 |
tlittle |
rhamby++ |
| 14:23 |
agoben |
rhamby++ |
| 14:23 |
gmcharlt |
rhamby++ |
| 14:23 |
jvwoolf1 |
rhamby++ |
| 14:23 |
jlundgren |
rhamby++ |
| 14:23 |
jvwoolf1 |
Looking forward to it! |
| 14:23 |
tlittle |
Agreed! |
| 14:24 |
agoben |
#topic 2021 Conference Committee |
| 14:24 |
|
Topic for #evergreen is now 2021 Conference Committee (Meeting topic: EOB/Evergreen Project Board meeting for 2020-09-17, agenda: https://wiki.evergreen-ils.org/doku.php?id=governance:minutes:2020-09-17) |
| 14:24 |
agoben |
Ok, dluch, how'd it go? |
| 14:24 |
dluch |
I talked with Mark Champa, the Director of Sales and Marketing for Loews. Krystal, the sales person with whom we initially worked, is still on leave. |
| 14:24 |
dluch |
We chatted about their attitude toward canceling - namely that events in 2021 are not considered force majure, since they're currently holding events (WHY?!) Anyway, he asked if I could tell him about the Evergreen Community, which I did, and about budget cuts and travel restrictions, etc. |
| 14:24 |
dluch |
He's reviewing our contract terms and so forth and will get back to me ASAP. I was hoping this morning, since I told him we were meeting today, but I guess it'll be this afternoon or tomorrow, since I haven't heard yet. |
| 14:25 |
dluch |
There will be the financial penalty, but he'll look at what might be able to be done, especially if we book for 2022. I will email the Board list as soon as I hear back from him. I was clear that our next penalty deadline was October 9 and that we definitely wanted to make our official decision to cancel and/or reschedule before then. |
| 14:26 |
cowens |
Are you thinking maybe no financial penalty if we book for 2022? |
| 14:27 |
JBoyer |
I wouldn't assume so though hopefully it's significantly more reasonable that it would otherwise be. |
| 14:27 |
nfBurton7 |
What is the October 9th penalty? |
| 14:27 |
dluch |
No, I'm pretty sure there will be one. But maybe they can reduce the amount we'll owe by canceling before Oct. 9. I really couldn't get a sense about it from him. Though he was very nice. |
| 14:27 |
agoben |
I guess we'll wait and watch. Thanks for starting the conversation. |
| 14:27 |
dluch |
$29K-something |
| 14:27 |
nfBurton7 |
yikes |
| 14:27 |
agoben |
That was the increase. |
| 14:27 |
dluch |
Yeah |
| 14:27 |
agoben |
If we cancel by then, it's still almost $60K |
| 14:27 |
dluch |
Well, minus the deposit we already paid |
| 14:28 |
tlittle |
I'm sorry, so if we cancelled right now the penalty would be...29k? |
| 14:28 |
tlittle |
Unless they cut us a deal, right? |
| 14:28 |
agoben |
No, $60K |
| 14:28 |
tlittle |
Oh, gotcha. Thanks, I was getting confused |
| 14:28 |
JBoyer |
It goes up by 29k on 10/9 |
| 14:28 |
agoben |
It'll be closer to $90K if we wait. And we don't have that kind of money. |
| 14:29 |
tlittle |
Definitely |
| 14:29 |
dluch |
Right. And I told him that, too. |
| 14:29 |
agoben |
Hoping they'll be reasonable about a reschedule! |
| 14:29 |
dluch |
Got my fingers and toes crossed. But he did indicate we aren't the first groups to ask about this and for them to consider |
| 14:30 |
terranm |
dluch++ These are difficult and stressful conversations. Thank you for doing what you can. |
| 14:30 |
agoben |
Alright, we'll see what comes. Thanks again, dluch! |
| 14:30 |
dluch |
(though not what they decided, of course) |
| 14:30 |
dluch |
You're welcome! |
| 14:30 |
jvwoolf1 |
dluch++ |
| 14:30 |
agoben |
dluch++ |
| 14:30 |
tlittle |
dluch++ |
| 14:30 |
jvwoolf1 |
That couldn't have been very much fun |
| 14:30 |
cowens |
dluch++ |
| 14:30 |
gmcharlt |
dluch++ |
| 14:30 |
rhamby |
dluch++ |
| 14:30 |
jlundgren |
dluch++ |
| 14:30 |
JBoyer |
dluch++ |
| 14:30 |
agoben |
#topic Outreach Committee |
| 14:30 |
|
Topic for #evergreen is now Outreach Committee (Meeting topic: EOB/Evergreen Project Board meeting for 2020-09-17, agenda: https://wiki.evergreen-ils.org/doku.php?id=governance:minutes:2020-09-17) |
| 14:30 |
rhamby |
I sent an update to the list but one thing I neglected to mention was that the idea was proposed for a User Group style online event. There is a lot of support right now but we are waiting until after the Hack-A-Way to discuss it more so that we can take our experience with Hopin.to into consideration. |
| 14:31 |
agoben |
#info The Outreach report is available here: http://list.evergreen-ils.org/pipermail/board/2020-September/000149.html |
| 14:31 |
dluch |
jvwoolf1: No, and I was super-nervous, lol, but he was very pleasant about not having gotten my email and in the conversation! :-) |
| 14:31 |
|
alynn26_away joined #evergreen |
| 14:31 |
rhamby |
And it sounds like we may have to keep the idea of an online conference like event in mind for next year as a distinct possibility as well. |
| 14:31 |
dluch |
Yup |
| 14:32 |
agoben |
I have it on my notes to revisit the possiblity of a project sub to hop.in and the like once we know the status of the 2021 conference, so we should have that up for review in Oct/Nov. |
| 14:32 |
rhamby |
Yep. |
| 14:33 |
agoben |
Anything else from or for outreach? |
| 14:33 |
rhamby |
We're getting a lot of experience with the platforms and use needs in a short time but adapt and push forward is all we can do. |
| 14:33 |
rhamby |
Nope, that's it. |
| 14:33 |
agoben |
++ |
| 14:33 |
dluch |
rhamby++ |
| 14:33 |
agoben |
Thanks! rhamby++ |
| 14:33 |
gmcharlt |
rhamby++ |
| 14:33 |
JBoyer |
rhamby++ |
| 14:33 |
cowens |
rhamby++ |
| 14:33 |
jlundgren |
rhamby++ |
| 14:33 |
jvwoolf1 |
rhamby++ |
| 14:33 |
tlittle |
rhamby++ |
| 14:34 |
agoben |
ok, on to old business. |
| 14:34 |
agoben |
#topic Unfinished Business : NFP Status - 1023 submission status |
| 14:34 |
|
Topic for #evergreen is now Unfinished Business : NFP Status - 1023 submission status (Meeting topic: EOB/Evergreen Project Board meeting for 2020-09-17, agenda: https://wiki.evergreen-ils.org/doku.php?id=governance:minutes:2020-09-17) |
| 14:34 |
agoben |
Slightly disappointing news. |
| 14:34 |
agoben |
#info 1023 application is still pending. The IRS is still working on applications from late March, so maybe next month we'll hear something. |
| 14:34 |
agoben |
The date for applications under active review is currently anything submitted prior to March 24, 2020. |
| 14:35 |
dluch |
Getting closer! |
| 14:35 |
agoben |
Inch by inch, I guess. |
| 14:35 |
|
nfBurton joined #evergreen |
| 14:36 |
agoben |
They're remarkably Definite about not wanting you to contact them for a status update... |
| 14:36 |
agoben |
(Until the case has been assigned, anyway.) |
| 14:37 |
agoben |
Kicking the can on that then. |
| 14:37 |
agoben |
#topic New Business |
| 14:37 |
|
Topic for #evergreen is now New Business (Meeting topic: EOB/Evergreen Project Board meeting for 2020-09-17, agenda: https://wiki.evergreen-ils.org/doku.php?id=governance:minutes:2020-09-17) |
| 14:37 |
agoben |
I have none. Anyone else? |
| 14:37 |
JBoyer |
No |
| 14:37 |
tlittle |
None here. |
| 14:37 |
dluch |
Nope! |
| 14:38 |
agoben |
Ok, well, thanks to everyone who's mid-project, again. We appreciate your extra time and effort! |
| 14:38 |
agoben |
#topic Next meeting |
| 14:38 |
|
Topic for #evergreen is now Next meeting (Meeting topic: EOB/Evergreen Project Board meeting for 2020-09-17, agenda: https://wiki.evergreen-ils.org/doku.php?id=governance:minutes:2020-09-17) |
| 14:38 |
agoben |
#info Our next formal meeting will be on October 15, 2020. |
| 14:38 |
agoben |
#endmeeting |
| 14:38 |
|
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 |
| 14:38 |
pinesol |
Meeting ended Thu Sep 17 14:38:46 2020 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
| 14:38 |
pinesol |
Minutes: http://evergreen-ils.org/meetings/evergreen/2020/evergreen.2020-09-17-14.00.html |
| 14:38 |
pinesol |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2020/evergreen.2020-09-17-14.00.txt |
| 14:38 |
pinesol |
Log: http://evergreen-ils.org/meetings/evergreen/2020/evergreen.2020-09-17-14.00.log.html |
| 14:38 |
gmcharlt |
agoben++ |
| 14:38 |
JBoyer |
agoben++ |
| 14:38 |
tlittle |
agoben++ |
| 14:38 |
dluch |
agoben++ |
| 14:38 |
cowens |
agoben++ |
| 14:38 |
jlundgren |
agoben++ |
| 14:38 |
agoben |
gmcharlt++ |
| 14:39 |
agoben |
JBoyer+ |
| 14:39 |
agoben |
tlittle++ |
| 14:39 |
jvwoolf1 |
agoben++ |
| 14:39 |
agoben |
dluch++ |
| 14:39 |
nfBurton |
agoben++ |
| 14:39 |
agoben |
cowens++ |
| 14:39 |
|
cowens left #evergreen |
| 14:39 |
agoben |
jlundgren++ |
| 14:39 |
agoben |
jvwoolf1++ |
| 14:39 |
agoben |
nfBurton++ |
| 14:39 |
agoben |
rhamby++ |
| 14:39 |
rhamby |
agoben++ |
| 14:39 |
agoben |
We now return you to your regularly schedule Evergreen chat. |
| 14:40 |
rfrasur |
EOB/TEP++ agoben++ |
| 14:40 |
|
jlundgren left #evergreen |
| 14:58 |
|
jweston joined #evergreen |
| 14:58 |
|
akilsdonk joined #evergreen |
| 14:59 |
|
miker joined #evergreen |
| 14:59 |
|
rhamby joined #evergreen |
| 14:59 |
|
abneiman joined #evergreen |
| 14:59 |
|
phasefx joined #evergreen |
| 15:46 |
Dyrcona |
The delete portion of the Lp 1482757 upgrade script has been running for over 3 hours on a Pg 10 database. I only have 1,375,274 asset.uris to delete. Doesn't seem like that many to me. |
| 15:46 |
pinesol |
Launchpad bug 1482757 in Evergreen 3.4 "Loading records with located URIs should not delete and recreate call_numbers" [Low,Confirmed] https://launchpad.net/bugs/1482757 |
| 15:52 |
Dyrcona |
Also, that delete does not take the foreign key on serial.item into account. Should it? |
| 15:53 |
Dyrcona |
We don't have any, but think I'll mention that on the bug if it is not already in the discussion. |
| 15:57 |
|
sandbergja joined #evergreen |
| 16:00 |
rhamby |
Dyrcona: speed wise that should probably be a left join with where null, a note in with 1.3 million I can easily see taking hours and hours |
| 16:00 |
rhamby |
the left join would be ... well, way faster |
| 16:00 |
rhamby |
s/note in/not in/ |
| 16:00 |
rhamby |
speed on not in is horrible |
| 16:02 |
Dyrcona |
rhamby: I was thinking of that. For a select it doesn't seem to make much difference on 9.6. |
| 16:03 |
Dyrcona |
I'm going to stop it, change it, and try again. |
| 16:03 |
Dyrcona |
rhamby++ |
| 16:07 |
Dyrcona |
That also makes it easier to deal with serial.item if that's needed, too. |
| 16:08 |
Dyrcona |
I should have timed this... Oh, well. |
| 16:09 |
Dyrcona |
Much better. That one just finished. |
| 16:09 |
rhamby |
yeah, orders of magnitude faster :) |
| 16:10 |
rhamby |
and yeah, I can't imagine why you wouldn't want to check against serial.uri since it's FKed there |
| 16:10 |
rhamby |
serial.item rather |
| 16:10 |
rhamby |
man, my fingers just hate me today |
| 16:10 |
mmorgan |
Dyrcona++ rhamby++ |
| 16:11 |
rhamby |
mmorgan++ for taking that bug on, it's an irksome one |
| 16:11 |
mmorgan |
Indeed it is! |
| 16:11 |
Dyrcona |
OK. I'll push a branch later unless mmorgan beats me to it. |
| 16:12 |
mmorgan |
Dyrcona: Please feel free! |
| 16:12 |
Dyrcona |
I'm going to run a few deletes with and without the code on a couple of Pg versions. |
| 16:49 |
|
dbwells joined #evergreen |
| 17:02 |
|
mantis1 left #evergreen |
| 17:18 |
|
mmorgan left #evergreen |
| 17:26 |
jeff |
If you don't need the data from the joined table, a NOT EXISTS (SELECT 1 FROM table WHERE ... ) can be faster than the JOIN. Either will be faster than a big NOT IN, though. |
| 17:27 |
jeff |
(he says, without looking at the query in question) |
| 17:49 |
jeff |
looks like at least as of 10 the planner gets the same plan with either NOT EXISTS or LEFT JOIN in the simple case I have in my head. |
| 18:01 |
pinesol |
News from qatests: Failed Running perl live tests <http://testing.evergreen-ils.org/~live//archive/2020-09/2020-09-17_16:00:02/test.49.html> |
| 21:19 |
|
_bott_1 joined #evergreen |
