Evergreen ILS Website

IRC log for #evergreen, 2019-02-21

| 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
05:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
07:04 littlet joined #evergreen
07:18 agoben joined #evergreen
07:21 pinesol` joined #evergreen
07:22 egbuilder joined #evergreen
07:22 drigney joined #evergreen
07:22 maryj joined #evergreen
07:22 phasefx_ joined #evergreen
07:22 pastebot joined #evergreen
07:22 jgoodson joined #evergreen
08:14 bos20k joined #evergreen
08:19 Dyrcona joined #evergreen
08:52 bdljohn1 joined #evergreen
08:53 bdljohn joined #evergreen
08:55 mmorgan joined #evergreen
08:59 terran joined #evergreen
09:09 aabbee joined #evergreen
10:06 jvwoolf joined #evergreen
10:08 jwoodard joined #evergreen
10:18 stephengwills joined #evergreen
10:21 bdljohn joined #evergreen
10:21 beanjammin joined #evergreen
10:21 yboston joined #evergreen
10:31 Dyrcona joined #evergreen
10:37 bdljohn left #evergreen
10:37 bdljohn joined #evergreen
10:44 bdljohn1 joined #evergreen
10:46 bdljohn joined #evergreen
10:55 Christineb joined #evergreen
11:04 jihpringle joined #evergreen
11:16 khuckins joined #evergreen
11:33 bos20k_ joined #evergreen
11:35 bos20k__ joined #evergreen
11:49 seymour joined #evergreen
11:53 sandbergja joined #evergreen
11:59 jvwoolf joined #evergreen
12:10 beanjammin joined #evergreen
12:32 berick dbwells: heads up for https://git.evergreen-ils.org/?p=workin​g/Evergreen.git;a=shortlog;h=refs/heads​/user/berick/lp1806087-sql-file-rename
12:33 berick fixes an issue with one of the sql upgrade script file names
12:33 dbwells berick: thanks, I'll get it in.
12:34 * Dyrcona just pushed a commit to master, rel_3_2 and rel_31, so if you're working on that you might to fetch again.
12:35 pinesol [evergreen|McCanna] LP#1784893 Reporter - External Documentation Links - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=2ea5dd1>
12:37 pinesol [evergreen|Bill Erickson] LP1806087 Repair SQL upgrade script file name - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=c85d6a5>
12:39 berick dbwells++
12:39 Dyrcona berick++ dbwells++ tmccanna++
12:44 dkyle1 left #evergreen
13:00 csharp calling 1153
13:07 pinesol Showing latest 5 of 13 commits to Evergreen...
13:07 pinesol [evergreen|Kathy Lussier] LP#1787479: Relocate t_view.tt2 file - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=a76e331>
13:07 pinesol [evergreen|Adam Bowling] LP#1787479: Adds customization for multipage print label printing and fixes the issue - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=1e24809>
13:07 pinesol [evergreen|Adam Bowling] LP#1787479: Fixes print label template customization saving for local storage - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=b4de131>
13:07 pinesol [evergreen|Adam Bowling] LP#1787479 Final fixes for print label customizations. Corrects duplication of pcrud objects - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=71e0eac>
13:07 pinesol [evergreen|Chris Sharp] LP#1787479: Stamping upgrade script - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=fed895c>
13:11 terran joined #evergreen
13:30 * mmorgan is looking at preferred names in the patron edit screen.
13:30 mmorgan When I show Suggested Fields, I only see first and last preferred names.
13:31 mmorgan When I show All Fields, I see preferred prefix, first, middle, last and suffix.
13:31 mmorgan I'd like to see all five fields appear in Suggested fields, but don't see any ou settings. Am I missing something?
13:37 berick mmorgan: IIRC, the pref name settings follow the main name settings
13:37 berick meaning, it doesn't have its own settings
13:40 mmorgan berick: ok, that would make sense, but I'm not seeing that it follows the primary name fields on 2 different 3.2 systems.
13:42 mmorgan I will check again and open a bug if I still see the same behavior.
13:57 yboston joined #evergreen
13:59 hbrennan joined #evergreen
14:08 hbrennan hello?
14:09 hbrennan joined #evergreen
14:11 Dyrcona hbrennan: Goodbye?
14:11 hbrennan Dyrcona: hi :)
14:12 hbrennan I dunno what's happening. Supposed to be a EOB meeting but I haven't seen activity in 15 min
14:13 Dyrcona Yeah, it's on the calendar. Dunno, either.
14:14 hbrennan There are a bunch of emails from today about it. There was talk about rescheduling and I must be mis-reading things.
14:14 JBoyer hbrennan, sorry, enough people were out / busy that it was canceled. I thought terran was going to update the calendar but may not have done it yet.
14:15 hbrennan JBoyer: Well Mike's email said "reschedule meeting or work through items by email" ... by starting to work through on email I assumed that meant still a meeting
14:15 hbrennan I'm confused. But I'm used to it.
14:16 JBoyer The work through via email is the COI that we've had since before the last meeting and getting some kind of committee to gather nominations for the next election.
14:16 csharp @decide VMWare vSphere or William Shakespeare
14:17 pinesol csharp: go with William Shakespeare
14:17 csharp pinesol++
14:19 JBoyer "Whether 'tis nobler in the execution to operate upon the silicon or in the lofty heights of those clouds held above..."
14:20 csharp JBoyer++
14:21 terran hbrennan: sorry, I added a canceled note to the agenda but not the calendar
14:22 JBoyer Ah, that's what I mis-remembered.
14:26 csharp @quote add <JBoyer> "Whether 'tis nobler in the execution to operate upon the silicon or in the lofty heights of those clouds held above..."
14:26 pinesol csharp: The operation succeeded.  Quote #196 added.
14:27 berick heh
14:28 hbrennan terran: No worries. I've got fires to stomp out anyway. Next week I'm having my replacement shadow me and then I'm out of here! Yikes!
14:28 terran hbrennan: Noooo! :(
14:29 hbrennan terran: But not EOB! I'll do my darndest to stay on until my term ends naturally
14:29 terran hbrennan: you said you'd serve your EOB term out until April, right?
14:29 csharp hbrennan: no one can replace you!
14:29 terran Oops
14:29 hbrennan csharp: :P
14:29 terran hbrennan: okay, good, then we only have to get 5 (?) new board members this year?
14:30 * csharp would consider doing it again
14:30 csharp I never was duly elected :-)
14:30 * csharp joins Gerald Ford in the corner
14:31 hbrennan terran: Yikes. Yeah we were already starting with a weird year of having to replace one more than normal.
14:31 hbrennan csharp++ Yes do it.
14:31 terran hopefully jvwoolf decides to come back after the baby or we'll have another! :)
14:33 JBoyer Speaking as one of the 3 most recently elected (and potentially only returning!) members, I would love to see some folks with experience cme back.
14:34 hbrennan JBoyer: Agreed. I can't step up to serve any more than a seat filler, unfortunately
14:37 JBoyer :)
14:39 * csharp cheers on pg_basebackup to move a bit faster restoring on a test server
14:39 csharp go! go! go!
14:45 * Dyrcona uses pg_restore, but has used pg_basebackup, and the latter is probably faster.
14:47 JBoyer pg_restore -j $BIG_NUM is really nice.
14:58 csharp pg_basebackup is basically rsync with WAL streaming on the side
14:58 csharp or acts that way, anyway ;-)
15:00 Dyrcona I usually use -j 8 with pg_restore.
15:00 Dyrcona There's always that one index that takes forever. :)
15:01 csharp yeah
15:01 JBoyer csharp, well, if the db is going to be hooked up to streaming rep afterword pg_basebackup is by far the best way to go, but for a testing server I figure it's quicker to let the metabib.real_full_rec index rebuild than transfer every byte of data. :)
15:02 csharp you may be right
15:03 csharp I've done it different ways over the years - pg_basebackup is nice because it has a progress meter and when you're done, it just starts up and you're good
15:03 Dyrcona Well, that's how you set up the rep server: pg_basebackup, then fire it up.
15:03 csharp right
15:04 Dyrcona That's the couple of times I've used pg_basebackup. For our test/development db server, I just restore a dump every Sunday morning.
15:04 JBoyer There's certainly appeal there, just waiting for pg_restore to go away without knowing where it's at is a little annoying (other than peeking at pg_stat_activity, which is no replacement for a progress bar)
15:09 Dyrcona pgrep -af postgres
15:19 JBoyer That's a handy one. Calling pgrep -af postgres | wc -l in a loop will give you a countdown, which is sort of like progress. :)
15:20 Dyrcona Well, I like the output to see which ones are doing anything and which ones are idle.
15:20 Dyrcona That's how I know there's always that one index that takes forever.
15:24 csharp yeah, with the -j option it flies through everything else, but that single proc just takes forever
15:26 jeff single large table.
15:26 jeff (likely, ime)
15:27 csharp @band add Single Large Table
15:27 pinesol csharp: Band 'Single Large Table' added to list
15:27 csharp @blame [band]
15:27 pinesol csharp: Classic Honey Black wants the TRUTH?! Classic Honey Black CAN'T HANDLE THE TRUTH!!
15:27 jeff it does a dependency-aware parallelization of the various objects/actions in the toc, but afaik no single toc item gets parallelized.
15:27 csharp right - that makes sense
15:28 csharp which is why doing -j 32 on my 64-core DB server is so unsatisfying :-P
15:28 Dyrcona Well, I suspect it has something to do with metabib.real_full_rec.
15:28 JBoyer It does.
15:29 Dyrcona At some point, you end up having your disk throughput be your limiting factor.
15:29 csharp that took 104m22.436s for a clone of PINES production
15:55 khuckins joined #evergreen
16:34 kmlussier joined #evergreen
16:34 kmlussier parts++ parts++ parts++
16:34 * mmorgan waves to kmlussier
16:34 berick haha
16:35 berick kmlussier++
16:35 berick who was that masked bandit?
16:35 mmorgan kmlussier++
16:36 mmorgan @karma parts
16:36 pinesol mmorgan: Karma for "parts" has been increased 4 times and decreased 1 time for a total karma of 3.
16:36 Dyrcona I missed it.
16:36 Dyrcona :)
16:37 mmorgan parts++
16:37 Dyrcona parts--
16:38 Dyrcona kmlussier++
16:48 jvwoolf Who would like to play "Bug or Feature?"
16:49 sandbergja jvwoolf: who _wouldn't_ like to play "Bug or Feature?"
16:49 jvwoolf We had a library report that an advanced search limiter gets wiped out after they add volumes to an item
16:51 csharp @who would like to play bug or feature?
16:51 pinesol phasefx_ would like to play bug or feature.
16:51 jvwoolf I tested and it looks like the catalog will hold onto the filter if you stay on the results screen, but if you click on a record, it gets wiped out, even if you go back to the results
16:52 mmorgan @decide bug or feature
16:52 pinesol mmorgan: go with feature
16:52 * mmorgan doesn't agree
16:53 sandbergja jvwoolf: do you have an OPAC link you could share?
16:54 sandbergja or is this in the staff client?
16:55 mmorgan If you're getting back to the results screen that came from the filter, it sounds like a bug that the filter doesn't carry back there.
17:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
17:05 mmorgan left #evergreen
17:07 jvwoolf sandbergja: Both places
17:08 jvwoolf Just realized the time though and need to get going. I think I have my answer, though. Will file a bug report tomorrow.
17:09 jvwoolf sandbergja++ mmorgan++
17:21 csharp @blame [band] for [quote random]
17:21 pinesol csharp: Dyrcona and the Sticky Keys broke Evergreen. for Quote #109: "< kmlussier> I live for sanity checks." (added by csharp at 10:06 AM, April 08, 2015)
17:25 Dyrcona heh
18:01 sandbergja_ joined #evergreen
22:02 sandbergja joined #evergreen
23:46 sandbergja joined #evergreen

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