Evergreen ILS Website

Search in #evergreen

Channels | #evergreen index




Results

Result pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148

Results for 2020-11-20

06:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
07:13 rjackson_isl_hom joined #evergreen
08:12 collum joined #evergreen
08:16 collum_ joined #evergreen

Results for 2020-11-19

02:48 devted joined #evergreen
03:35 troy__ joined #evergreen
04:58 mrisher joined #evergreen
06:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
07:22 rjackson_isl_hom joined #evergreen
08:03 rfrasur joined #evergreen
08:17 Stompro joined #evergreen
16:57 Bmagic mmorgan++
17:00 berick mmorgan: k, well, hm
17:00 mmorgan Dyrcona++
17:01 berick mmorgan: could be an issue with the CHROME_BIN environment variable.  it's set in the play, so it should just work, but i've had the odd case of environment settings not working in ansible
17:01 berick there's a possible workaround...
17:04 berick mmorgan: something like this could fix it https://gist.github.com/berick/c​d39e855697e077491d69ae4107021c3
17:05 berick or you could just comment out the 2 blocks that run 'npm run test'
17:05 berick since you don't have to run the tests to install
17:10 mmorgan berick: Ok, thanks for the suggestions. I'll try that tomorrow.
17:10 mmorgan berick++
17:10 mmorgan Good night #evergreen!
17:41 Cocopuff2018 joined #evergreen
17:52 stompro_ joined #evergreen
18:00 jihpringle joined #evergreen
18:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:07 mllewellyn left #evergreen
19:45 jihpringle joined #evergreen
22:15 sandbergja joined #evergreen

Results for 2020-11-18

06:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
07:20 rjackson_isl_hom joined #evergreen
08:13 rfrasur joined #evergreen
08:38 mmorgan joined #evergreen
17:40 berick gmcharlt++ # thanks!
17:42 stompro_ joined #evergreen
17:50 sandbergja joined #evergreen
18:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:36 serflog joined #evergreen
18:36 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
19:30 sandbergja_ joined #evergreen

Results for 2020-11-17

02:31 ejk_ joined #evergreen
03:15 Bmagic joined #evergreen
03:33 devted joined #evergreen
06:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
07:18 rjackson_isl_hom joined #evergreen
08:02 rfrasur joined #evergreen
08:27 mmorgan joined #evergreen
17:07 jihpringle70 joined #evergreen
17:13 mmorgan left #evergreen
17:58 sandbergja joined #evergreen
18:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:50 Cocopuff2018 joined #evergreen
19:25 Bmagic joined #evergreen

Results for 2020-11-16

06:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
07:12 rjackson_isl_hom joined #evergreen
08:01 rfrasur joined #evergreen
08:28 mantis2 joined #evergreen
17:39 dickreckard joined #evergreen
17:47 jihpringle joined #evergreen
17:48 jonadab joined #evergreen
18:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:59 sandbergja joined #evergreen

Results for 2020-11-15

06:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
17:32 Cocopuff2018 joined #evergreen
18:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
21:05 Christineb joined #evergreen

Results for 2020-11-14

06:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
08:34 book`_ joined #evergreen
08:34 BigRig joined #evergreen
08:35 abneiman_ joined #evergreen
12:07 Cocopuff2018 joined #evergreen
16:48 Cocopuff2018 joined #evergreen
18:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
19:30 sandbergja joined #evergreen
23:34 sandbergja joined #evergreen

Results for 2020-11-13

00:35 sandbergja joined #evergreen
01:00 sandbergja joined #evergreen
04:52 khuckins joined #evergreen
06:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
07:18 rjackson_isl_hom joined #evergreen
08:03 collum joined #evergreen
08:10 mmorgan joined #evergreen
09:54 csharp based on a discussion here, we did combine our KPAC customizations into a megacommit, but that was better than the sprawl that was there before
09:55 csharp the principle I try to work from is thinking of a "feature" (or fix) as a unit
09:58 Dyrcona csharp: Yes, I try to do that, and then a year or two later, everything gets squashed into 1 megacommit. :)
09:59 Dyrcona Right now, I'm deciding between making a branch for one of my test VMs with modifications from the production configuration or just use a sed script. I'm leaning toward a branch.
10:01 Dyrcona What I should probably do at this point is split the configuration changes, i.e. those touching Open-ILS/examples from the custom code, i.e. just about everything else.
10:03 Dyrcona I used to maintain separate branches for configuration vs. custom templates and code modifications, then it all ended up in one branch, and over time the commits got squashed and squashed again until it all ended up in 1 commit.
10:04 csharp THERE CAN BE ONLY ONE (commit)
11:03 Dyrcona Y'know, now would also be a good time to convert our logos from JPEG to PNG.
11:13 csharp yeah, releases are Wednesday if you're around - if not, no big
11:20 Dyrcona OK. We'll see how things go.
11:20 JBoyer Speaking of releases... lp 1904220 is a very simple thing to test
11:20 pinesol Launchpad bug 1904220 in Evergreen 3.5 "determine_booking_status in OpenILS::Application::Circ::Circulate breaks when changing router names" [Medium,New] https://launchpad.net/bugs/1904220
11:49 Dyrcona Also, sed++ imagemagick++
12:08 Christineb joined #evergreen
17:37 mmorgan left #evergreen
17:42 Bmagic mmorgan++
17:42 Bmagic csharp++
18:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
19:51 sandbergja joined #evergreen
20:48 sandbergja joined #evergreen
21:34 sandbergja joined #evergreen

Results for 2020-11-12

06:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
07:16 rjackson_isl_hom joined #evergreen
08:06 rfrasur joined #evergreen
08:14 alynn26 joined #evergreen
17:13 mmorgan1 left #evergreen
17:27 sandbergja joined #evergreen
17:29 khuckins_ joined #evergreen
18:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:30 mmorgan joined #evergreen
18:37 mmorgan1 joined #evergreen
20:13 mmorgan joined #evergreen

Results for 2020-11-11

00:10 abowling1 joined #evergreen
00:18 dbwells_ joined #evergreen
05:16 jeff_ joined #evergreen
06:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
08:37 collum joined #evergreen
09:35 Cocopuff2018 joined #evergreen
12:17 abowling joined #evergreen
16:55 jeff joined #evergreen
16:55 devted joined #evergreen
16:55 Bmagic joined #evergreen
18:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
21:10 mrisher joined #evergreen
22:03 sandbergja joined #evergreen

Results for 2020-11-10

03:04 Hello joined #evergreen
03:04 Hello left #evergreen
05:25 troy__ joined #evergreen
06:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
07:19 rjackson_isl_hom joined #evergreen
08:36 mmorgan joined #evergreen
08:45 Dyrcona joined #evergreen
10:48 Dyrcona That's how I interpreted jeff's comment about it being "accidental" yesterday.
10:49 mmorgan The "accident", seamless capture of equivalent copies, is a much preferred behavior. Without the op-capture, staff members find it hugely time consuming to match barcodes, and frustrating to not be able to fill a hold when they can't find the exact copy.
10:49 Dyrcona One person's bug is another's feature. :)
10:51 miker confirmed that there are significant performance implications. I can see a way to make it work, maybe, but lots of testing on various sized data sets would be needed ... the change is small in lines of code (probably 2) but big in terms of potential impact
10:53 miker mmorgan: I can absolutely understand that! the baseline expectations today are much different than 2004 ... op-capture /at all/ was unthinkably magical back then (to staff used to ... a certain proprietary ILS) :)
10:56 csharp also, PINES was in the middle of courier paralysis at the time that feature was added (if I know my history)
10:57 csharp after the courier delays were improved, the need for stalling disappeared (we just this summer turned it off)
10:59 mmorgan And now we have COVID quarantines, causing long delays with items needing to travel to fill holds, so we just recently turned it on, never having used it before :)
11:01 * mmorgan is happy to open a bug, and would be happy to test 2-ish lines of code on a large data set :)
11:02 csharp yeah, some of the courier delays have definitely returned
11:03 Dyrcona csharp: While you're here, can I ask a couple of questions about Quipu?
11:08 stompro_ joined #evergreen
11:16 miker mmorgan: having looked, it's going to be a lot more than 2 lines ;)
11:21 miker the main problem is, when you're capturing holds you're not saying "here's a hold, capture any copy at this location" you're saying "here's a copy, give me holds it could fill in proximity order". when stalling is enabled what you're really saying is "the PL-to-copy proximity must be 0". the current copy part is separate. here's what the code does:
11:22 miker 1) first look for holds that target the copy in hand. hold onto that list for later
11:23 miker 2) sort holds the copy in hand could fill by "best-ness" per best-hold-sort-order and proximity adjustment rules
11:23 miker 3) run the permit tests on the "best" ordered holds, and return the first permitted
11:25 miker 4) if no "best" ordered holds passed the permit tests, look at that first directly-targetted, stashed list and run the permit tests on those, returning the first that passes
11:29 mmorgan Hmm. More -ish, than 2, then ;-)
11:29 miker and (2) is where we run into problems. we're sorting holds-for-this-copy, and stalling specifically says "only look at holds for this copy where the proximity is 0".  The directly-targeted hold test comes later and, again, is only about this copy in hand.
11:30 stompro__ joined #evergreen
11:30 miker (note, there are some short cuts / optimizations in the actual code -- we merge the lists, we don't do 2 separate loops -- but that's just code ordering stuff)
11:33 mmorgan Maybe 0) could identify equivalent copies and proceed to 1) for that set of copies? Just brainstorming...
11:33 miker we never actually see the desired hold in either list, because ALL the info we have is 1) the copy in hand 2) the stalling interval for this location. everything else is derived. adjacent copies are never seen because we're never looking from the point of view of the /holds/ on the pull list, we're looking from the point of view of the copy in hand
11:33 stompro_ joined #evergreen
14:06 jeffdavis strongly considering ripping out the level 0 version on prod servers, this problem is not going away
14:08 Dyrcona We made it stop by deleting a closed date that was causing the problem. It seems to happen when it latches onto a closed date as an open date or something.
14:09 Dyrcona I'm not sure how to explain it, really.
14:10 Dyrcona One thing I noted in testing is that it didn't matter if it was a multi-day closing or a single day closing that fell on the particular date.
14:11 jeffdavis hm, noticing that the apparent problem libraries have no open hours at all in actor.hours_of_operation
14:12 Dyrcona jeffdavis: That's one thing that will do it. In our case it was a library open only 1 day/week.
14:13 jeffdavis These libraries are doing circs but have no open hours, seems like that is going to be a problem for setting a due date.
15:13 sandbergja make -f Makefile.install fossa?
15:13 Dyrcona :)
15:14 Dyrcona So, I guess the question is when to merge the branches and fork the rel_3_3 and rel_3_7 branches, and maybe we don't need an answer today.
15:14 JBoyer Looks like some more testing is needed to get those branches in, but that should easily be achievable by the ~3.7 timefram.e
15:15 JBoyer "Looks like" meaning they're not all signed off yet, but I imagine they'll be no trouble.
15:15 gmcharlt yeah, and easy enough to get OpenSRF 3.3 out the door sooner than EG 3.7
15:16 JBoyer #agreed The removal of Python and Java will be a part of the 3.3 OpenSRF and 3.7 Evergreen releases
15:16 Dyrcona I think it's worth mentioning again that if you test the Focal Fossa branches, you are effectively testing all 3, since the Focal branches depend on the Python and Java branches.
15:16 abowling #info abowling = Adam Bowling, Emerald Data Networks
15:17 JBoyer Do all 3 need to be applied manually or does the fossa branch basically include the others?
15:17 * JBoyer goes to look after lazygoogling
15:18 Dyrcona JBoyer: The Fossa branch includes the other two, yes.
15:18 JBoyer Excellent, ok. So easy to test then.
15:18 berick good summary http://list.evergreen-ils.org/pipermail​/evergreen-dev/2020-October/000053.html
15:19 JBoyer berick++
15:19 JBoyer ok, hopefully some Ubuntu VMs will be spun up and those branches taken for a spin. Any further OpenSRF discussion?
15:30 JBoyer Does anyone have any further information to bring to the table re: Pg10+ ?
15:30 JBoyer I know there are a couple production upgrades in the planning phases, but haven't heard anything else.
15:31 csharp we won't be moving to it until late winter/early spring at this point
15:31 Dyrcona We're sticking with 9.6 for now. I have a test server with 9.6 through 12 installed.
15:31 csharp Dyrcona++ # pioneering
15:31 Dyrcona Um, 9.6 through 13, now. I installed 13 last month.
15:32 Dyrcona I'm not sure how we should go about benchmarking things, but I can say that performance seems to change quite a bit on 12 versus 9.6 and 10.
15:33 JBoyer odd benchmarking aside, you haven't noticed anything like the changes in Pg10 where things we were doing in 9.6 and below would just blow up anywhere, correct?
15:34 Dyrcona Not so far. It looks like we've caught those. I haven't seen anything just blow up on 12, either, and I've been using it as my main test db.
15:34 JBoyer That's promising.
15:35 jihpringle joined #evergreen
15:36 JBoyer Ok. If there's no more discussion to be had about Pg10 I feel like we've already covered the Fossa / -Python / -Java discussions, does anyone have any new business that didn't hit the agenda?
17:03 Bmagic found this in the logs: Not changing edi_account because we found (2) matching vendacct(s), one of which being on the edi_account we already had
17:03 Bmagic followed by: changing edi_account from 104 to 103 based on vendacct 'xxxxxx' (2 match(es)) - there we go! That's the smoking gun
17:05 mmorgan left #evergreen
18:13 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:23 jihpringle joined #evergreen
18:46 devted Closed Dates Editor question: question: Is it normal to see past emergency closings with unprocessed portions in the Closed Dates Editor? (ie, 1/34 holds)
18:47 devted Closed Dates Editor question #2: Also, is it normal to see past emergency closings with 0/0 processed portions in the Closed Dates Editor?

Results for 2020-11-09

06:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
07:21 rjackson_isl_hom joined #evergreen
07:28 collum joined #evergreen
07:35 collum joined #evergreen
17:27 Stompro joined #evergreen
17:44 jihpringle joined #evergreen
17:55 dbwells joined #evergreen
18:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:44 jihpringle joined #evergreen
19:35 dbwells joined #evergreen
20:16 Stompro joined #evergreen

Results for 2020-11-08

04:00 ejk_ joined #evergreen
04:00 Christineb joined #evergreen
04:12 jeffdavis joined #evergreen
06:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
15:36 Stompro joined #evergreen
18:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:10 book` joined #evergreen
19:06 sandbergja joined #evergreen
19:42 Stompro joined #evergreen
19:57 sandbergja joined #evergreen
21:33 sandbergja joined #evergreen
23:40 pinesol [evergreen|Katie Greenleaf Martin] Docs: LP1826256 Change 'catalogue' to 'catalog' - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=b7bbff1>

Results for 2020-11-07

01:22 pinesol` joined #evergreen
01:23 dickreckard joined #evergreen
01:24 csharp joined #evergreen
06:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
06:59 csharp joined #evergreen
18:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
21:11 Stompro joined #evergreen

Results for 2020-11-06

03:38 bshum joined #evergreen
06:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
07:16 rjackson_isl_hom joined #evergreen
07:52 rfrasur joined #evergreen
08:08 csharp miker: we are, yes
16:20 mrisher joined #evergreen
16:20 mrisher joined #evergreen
17:35 mmorgan left #evergreen
18:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:37 jihpringle joined #evergreen
20:36 Stompro joined #evergreen

Results for 2020-11-05

02:55 abowling1 joined #evergreen
06:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
06:44 OGsizzle joined #evergreen
06:45 OGsizzle left #evergreen
07:32 rfrasur joined #evergreen
14:06 alynn26 Things are going good. Busy
14:06 dluch alynn26++
14:06 kgmartin I am doing well & have a bit of time this afternoon if anyone has a bitesize project idea :)
14:06 abneiman I took a covid test today since I was a poll worker for three days... my nose still hurts, lol (sorry for the TMI)
14:07 adurrence ouch!
14:07 dluch Awesome. kgmartin++
14:07 dluch Ugh, abneiman, i'm sorry!
17:08 mmorgan left #evergreen
17:37 dbwells joined #evergreen
17:53 stompro_ joined #evergreen
18:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:05 jihpringle joined #evergreen
19:25 jihpringle joined #evergreen
21:22 Core4997 joined #evergreen

Results for 2020-11-04

16:51 stompro_ joined #evergreen
17:02 mmorgan left #evergreen
17:54 sandbergja jeff: Koha has that feature (a setting called RecordLocalUseOnReturn).  I'd be curious what Koha libraries who have implemented that feature think of it
18:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
20:51 sandbergja joined #evergreen
20:52 Stompro joined #evergreen
21:41 sandbergja joined #evergreen

Results for 2020-11-03

06:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
07:25 Dyrcona joined #evergreen
07:26 Dyrcona Yay for backups!
07:58 collum joined #evergreen
17:13 dbwells joined #evergreen
17:20 mmorgan left #evergreen
17:21 jvwoolf left #evergreen
18:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:12 dbwells joined #evergreen
18:24 dbwells joined #evergreen
18:34 RBecker joined #evergreen

Results for 2020-11-02

06:00 pinesol News from qatests: Failed Installing Evergreen pre-requisites - Expected 1 errors but encountered 3. <http://testing.evergreen-ils.org/~live//arch​ive/2020-11/2020-11-02_04:00:03/test.26.html>
07:13 rfrasur joined #evergreen
08:01 mantis1 joined #evergreen
08:17 collum joined #evergreen
16:49 Dyrcona I'll see what I can put together and email it to you. It's composed of multiple pieces in different repositories.
17:03 mmorgan left #evergreen
17:08 dbwells Dyrcona++
18:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
22:01 sandbergja joined #evergreen
22:25 sandbergja joined #evergreen

Results for 2020-11-01

02:43 mrisher joined #evergreen
02:44 mrisher joined #evergreen
03:00 laurie joined #evergreen
06:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
16:04 serflog joined #evergreen
16:04 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
18:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
20:33 sandbergja joined #evergreen
20:44 sandbergja joined #evergreen

Results for 2020-10-31

06:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:18 Guest85425 joined #evergreen
19:47 sandbergja joined #evergreen
19:52 sandbergja joined #evergreen

Results for 2020-10-30

06:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
07:12 rjackson_isl_hom joined #evergreen
07:25 agoben joined #evergreen
08:24 mmorgan joined #evergreen
15:46 mmorgan left #evergreen
16:12 mantis1 left #evergreen
17:04 sandbergja joined #evergreen
18:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:16 sandbergja joined #evergreen

Results for 2020-10-29

06:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
06:32 dbwells joined #evergreen
06:38 dbwells joined #evergreen
07:22 rjackson_isl_hom joined #evergreen
11:05 Dyrcona Guess it goes back....
11:07 Dyrcona Oh, wait. This is different. It's doing something. I guess the Security Violations didn't mean anything.
11:10 Dyrcona So, when I tried the grub option to recover the OS, it said it couldn't find a live image.
11:12 Dyrcona When I booted from the USB using the BIOS, it gave me several screens of "Security Violation" with an "OK" option. After the second of those, it started the self test. After the self test, it wanted to connect to WiFi to download the recovery image.
11:12 Dyrcona It's showing no progress on that front, though.
11:13 Dyrcona Looks like it locked up.
12:03 Christineb joined #evergreen
15:59 dbwells joined #evergreen
16:36 sandbergja joined #evergreen
17:11 mmorgan left #evergreen
18:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
19:24 dbwells joined #evergreen

Results for 2020-10-28

06:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
07:12 rjackson_isl_hom joined #evergreen
07:12 agoben_ joined #evergreen
08:26 mantis1 joined #evergreen
16:24 csharp @dessert [band]
16:24 * pinesol grabs some boxes of Samoa cookies for Friday Changes
16:29 berick @who gave [dessert] to [band] for [dunno]
16:29 * pinesol dickreckard gave grabs some coffee frappes for berick to Dark-Alley Unicode Codepoints for It reads like a Nigerian 419 scam, but I think it is a sincere question sent to the wrong list.
16:52 pinesol [evergreen|Mike Rylander] LP#1508208: Only look at holds that age protection allows - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=c166c9e>
16:52 pinesol [evergreen|Jason Etheridge] LP#1508208: live_t/ test for this branch - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=f07a788>
17:11 mmorgan left #evergreen
18:00 serflog joined #evergreen
18:00 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
18:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:00 pastebot joined #evergreen
18:17 Dyrcona joined #evergreen
19:01 sandbergja joined #evergreen

Results for 2020-10-27

06:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
07:14 agoben joined #evergreen
07:17 rjackson_isl_hom joined #evergreen
08:00 rfrasur joined #evergreen
08:11 sandbergja joined #evergreen
08:14 pinesol [evergreen|Jane Sandberg] Docs: adding information about 3.6 features from the release notes - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=5e85cc2>
08:32 mmorgan joined #evergreen
08:39 mantis1 joined #evergreen
09:01 Dyrcona joined #evergreen
14:11 rhamby If anyone else wishes to join the Release Manager discussion w are in the Hopin event righ tnow.
14:11 tlittle joined #evergreen
14:46 jihpringle joined #evergreen
14:52 csharp jeff: I'm about to test your ancient fix to bug 1013786 - do you still stand by that patch :-)
14:52 pinesol Launchpad bug 1013786 in Evergreen "tpac: Check for password strength at login" [Medium,Confirmed] https://launchpad.net/bugs/1013786 - Assigned to Chris Sharp (chrissharp123)
14:53 * csharp missed a question mark in there somewhere
14:58 jeff I didn't even think I had code on that bug. Looking!
17:48 Dyrcona Looks like it needs to be updated for more recent systemd versions. That said, I've never used it. I have a shell script to run systemd in the background.
17:53 jeffdavis Adding an [Install] block to the websocketd-osrf.service file containing "WantedBy=multi-user.target" seems to do the trick, but I'm unsure if that is the correct solution.
17:54 Dyrcona jeffdavis: That's more or less correct. You could specify other targets, probably make it start before opensrf or apache or whatever.
18:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:01 jeff jeffdavis: I think you use org unit opt-in. Have you encountered slow patron searches, especially when searching by email? It may or may not be something that's being caused by our specific ratio of opted-in to not-opted-in users, etc... but thought I'd ask.
18:03 jeff Where "slow" is > 30 seconds to complete a patron search by email when opt-in is enabled.
18:05 jeffdavis jeff: we do use opt-in. I don't think patron search is notably slow. I just did a consortium-wide email search and got results in about 4 seconds.

Results for 2020-10-26

06:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
06:59 agoben_ joined #evergreen
07:14 rjackson_isl_hom joined #evergreen
07:59 mmorgan joined #evergreen
16:52 mantis1 left #evergreen
17:13 rjackson_isl_hom joined #evergreen
17:29 mmorgan left #evergreen
18:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:24 sandbergja joined #evergreen
19:18 rjackson_isl_hom joined #evergreen
20:10 annagoben joined #evergreen

Results for 2020-10-25

02:54 book` joined #evergreen
02:55 abowling joined #evergreen
15:34 jeff joined #evergreen
18:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:52 mrisher joined #evergreen
20:51 sandbergja joined #evergreen
22:09 sandbergja joined #evergreen

Results for 2020-10-24

05:07 mrisher joined #evergreen
06:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
10:45 jvwoolf joined #evergreen
16:27 yboston joined #evergreen
18:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
23:06 sandbergja joined #evergreen

Results for 2020-10-23

00:04 dbwells joined #evergreen
00:08 dbwells joined #evergreen
02:46 dbwells joined #evergreen
06:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
07:11 rjackson_isl_hom joined #evergreen
07:41 dbwells joined #evergreen
08:02 Dyrcona joined #evergreen
09:32 dbwells joined #evergreen
10:06 jonadab joined #evergreen
10:20 sandbergja joined #evergreen
10:55 pinesol [evergreen|Bill Erickson] LP1855737 Don't send error object across shared worker port - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=d5d7985>
12:10 jihpringle joined #evergreen
12:15 sandbergja Is there a way to verify that a particular ORDERS acq.edi_message was created using the new edi_order_pusher?  Is an empty jedi column a good way to tell?
12:17 csharp hmm
12:19 Dyrcona I've got rows with status = complete jedi = empty and edi = <content>, so what csharp said. :)
12:20 csharp the original pusher puts data in the jedi column and the new one doesn't
12:21 sandbergja Excellent!  Thanks!
12:21 csharp same here - and the earliest one is right around the time we transitioned to non-JEDI ordering
12:21 csharp sandbergja: you also know about --test-mode on the new pusher, right?
12:22 sandbergja yes!  that was super helpful
12:22 csharp good
12:22 sandbergja Oh man, I think we are all switched over to the new EDI system!
14:21 mmorgan Dyrcona: csharp: In case you were planning a trip to Salem this year, don't: https://www.thrillist.com/news/nation/sa​lem-massachusetts-closed-halloween-2020
14:22 Dyrcona mmorgan: I know, and I was in Salem on Wednesday.
14:22 mmorgan Folks are still coming in droves :-/
14:23 Dyrcona I'm not surprised. I took a relative to Salem for a medical test.
14:25 Dyrcona "October has been canceled."
14:28 * mmorgan made the mistake of driving through on Saturday, rather, crawling through...
14:29 Dyrcona Heh.
17:09 csharp joined #evergreen
17:17 mmorgan left #evergreen
17:39 yboston joined #evergreen
18:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
21:51 sandbergja joined #evergreen
23:25 dluch joined #evergreen
23:25 Bmagic joined #evergreen

Results for 2020-10-22

00:34 sandbergja joined #evergreen
01:38 sandbergja joined #evergreen
01:57 sandbergja joined #evergreen
06:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
07:22 rjackson_isl_hom joined #evergreen
08:28 rfrasur joined #evergreen
08:34 mmorgan joined #evergreen
16:17 dbwells joined #evergreen
16:57 sandbergja joined #evergreen
17:03 mmorgan left #evergreen
18:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:21 sandbergja joined #evergreen
22:26 sandbergja joined #evergreen

Results for 2020-10-21

00:39 mrisher joined #evergreen
00:39 mrisher joined #evergreen
01:09 sandbergja joined #evergreen
06:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
06:16 yar joined #evergreen
06:23 RBecker joined #evergreen
06:23 devted joined #evergreen
09:37 Dyrcona Except....I see the queries running that match that SQL exactly. However, I don't see any calls to the storage method in the logs. Also, there are two definitions for the function!
09:38 Dyrcona https://git.evergreen-ils.org/?p=Evergreen.gi​t;a=blob;f=Open-ILS/src/perlmods/lib/OpenILS/​Application/Storage/Publisher/actor.pm#l350
09:38 Dyrcona "That's a bingo!"
09:39 Dyrcona Well, one of those similar loops. At least I have something to test.
09:40 mmorgan Dyrcona++
09:40 Dyrcona Also, I'm not clear on the difference between api level 1 and api level 0. How would I know which is being used?
09:51 Dyrcona request open-ils.storage open-ils.storage.actor.org​_unit.closed_date.overlap 207, "2020-10-16T16:30:43-0400"
09:52 Dyrcona This one "hangs" on my test server.
09:54 Dyrcona And, there's a query running from time to time checking "random" dates.
09:54 Dyrcona Now, to see what's so special about 2020-10-16.
09:55 mantis1 joined #evergreen
14:30 Dyrcona So, I can consistently make open-ils.storage.actor.org​_unit.closed_date.overlap spin for this one org unit with a date of 2020-10-16.
14:31 Dyrcona Now, to figure out why.
14:33 Dyrcona Killing the drone is the only reliable way to stop it.
14:33 Dyrcona I just got lucky on my test server last time that I canceled the postgres backend.
14:33 JonGeorg This was an issue from a while back, so I was looking through my notes. The issue was when we tried to manually run the command. This is from an inherited system. There are no errors in syslog. So I'm thinking it was an error with how I was attempting to run the command manually, as we were trying to see if an update to the bookbag had been
14:33 JonGeorg populated or not. It was telling me the error was on line78 which is the "$log = new Loghandler($logFile);" line and I couldn't find any reference to that function anywhere. I think I might have gone down a rabbit hole over nothing. I'll do some more checking to make sure it's working correctly.
14:38 Dyrcona JonGeorg: I'm not find any script by the name of bookbag_update.pl i the source code.
17:05 sandbergja joined #evergreen
17:06 mmorgan left #evergreen
17:39 berick terranm++ bug-wrangle-mania++
18:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
19:14 jihpringle joined #evergreen
19:38 dbwells joined #evergreen
20:16 dbwells joined #evergreen

Results for 2020-10-20

06:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
07:20 rjackson_isl_hom joined #evergreen
07:24 yar joined #evergreen
07:34 yar joined #evergreen
17:08 Stompro miker, thanks for the thoughts.
17:14 mmorgan left #evergreen
17:20 dbwells joined #evergreen
18:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:17 jihpringle joined #evergreen
18:27 dbwells joined #evergreen
20:42 Stompro joined #evergreen

Results for 2020-10-19

16:54 sandbergja joined #evergreen
17:09 Stompro The egCore.idl.acsp error went away after I remembered to update /openils/var/web/reports/fm_IDL.xml
17:28 mmorgan left #evergreen
18:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
21:07 sandbergja joined #evergreen
21:37 sandbergja joined #evergreen
21:50 sandbergja joined #evergreen

Results for 2020-10-15

13:15 JBoyer I doi like syslog grouping things together under /var/log/evergreen/... so you can get a good idea what's going on all in one place.
13:15 Dyrcona Some messages still end up in /var/log/apache2/other_vhosts.log or something like that, but that may just be our configuration.
13:16 JBoyer I think I've seen that too. Not sure if they're duplicated or if there's another config option that we're missing somewhere, etc.
13:16 Dyrcona Yeah, I agree for production environments, but for a test/development VM, it's a bit much.
13:16 Dyrcona I suspect they're duplicated, but I'll have to take a few minutes to make sure.
13:16 JBoyer It is annoying that there are so many places that need to be edited in opensrf_core.xml, that's true.
13:17 Dyrcona I have a couple of sed scripts for that. :)
14:45 nfBurton Although there aren't much costs for an online conference, we could probably garner some donations for that as well I mean we were willing to pay more to do the same face to face
14:46 Cowens Just to clarify, agoben, you wrote in the email to the community that we needed $15,000-$20,000 but we are paying out (at least ) $59,000 some, correct?
14:46 agoben I know that donations aren't an option for everyone, so we'll need to consider other options.  Obviously the e-conference is one options, but I'd like us to consider what else might be out there.
14:46 gmcharlt another factor for ongoing support: one of the ways of meeting the IRS' tests for showing that we, as a 501(c)3 charity, have public support, is to have a broad base of contributors
14:47 gmcharlt grants of course are another avenue to pursue
14:47 dluch I was just going to mention grants, lol
14:47 agoben The total is a little over $59,000, yes, but we have over half of that from previous conferences.
14:48 Cowens Thanks

Results for 2020-10-14

06:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
06:58 agoben_ joined #evergreen
07:12 rjackson_isl_hom joined #evergreen
07:57 collum joined #evergreen
08:48 rfrasur joined #evergreen
08:56 collum_ joined #evergreen
09:07 Dyrcona joined #evergreen
09:36 Dyrcona Whee! Testing the new brick's OPAC over a ssh tunnel through the load balancer..... Have to adjust the URL to add my local port every time it does a redirect, but otherwise doable.
09:37 Dyrcona The web staff client.... Fuhgeddaboutit.....
09:38 Dyrcona Unless you can get the forwarding working as the root user, which I don't feel like dealing with.
09:42 Dyrcona Kernel update for the laptop. Think I'll install it and reboot. Back in a bit!

Results for 2020-10-13

04:04 jvwoolf1 joined #evergreen
06:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
06:46 jeff Bmagic, rhamby: Looking at this latest commit to match_fingerprints (from about two years ago), the change from '>' to '<' in the sort check seems to now conflict with the recommendation to sort in descending order (in examples and in the die message if the sort check fails):
06:46 jeff https://github.com/EquinoxOpenLibraryInitiativ​e/migration-tools/commit/775c66de891990851afcd​e5fbec9f6a8c6d004c3#diff-8a24e66df071b3db07de2​e015c625fd8ccc6533706ce69c138d4bba6d65869c7L65
06:48 jeff Any thoughts on if the examples/error need to be updated or if the change in comparison operator needs to be reverted?
17:26 mmorgan left #evergreen
17:27 JBoyer mmorgan++
17:31 jihpringle joined #evergreen
17:37 pinesol [evergreen|Galen Charlton] stamp release notes for 3.6.0 - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=e863fd2>
17:37 pinesol [evergreen|Galen Charlton] stamp version-upgrade script for 3.6.0 - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=5697364>
18:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:20 dbwells joined #evergreen
19:01 dbwells joined #evergreen
19:23 drigney joined #evergreen

Results for 2020-10-12

03:10 mrisher joined #evergreen
03:47 mrisher_ joined #evergreen
04:06 mrisher joined #evergreen
06:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
08:17 mantis2 joined #evergreen
09:11 Bmagic @coffee [someone]
09:11 * pinesol brews and pours a cup of NOBLE Coffee, and sends it sliding down the bar to bshum
12:08 csharp I tried changing "use open ':utf8';" to use open ':encoding(UTF-8)';" but that doesn't do it
12:08 csharp (those may be equivalent - my googled documentation was unclear)
12:09 csharp also, the problem may be that the incoming data from the bib records is not marked UTF-8?
13:39 jvwoolf We've got a staff member who's seeing icons in the angular catalog replaced with text, but only in Firefox. Happening on our test server and some community test servers for her. I can't replicate it. Anybody seen this?
13:47 jeff which community test servers? do you have a screenshot? any idea which version of firefox on what OS?
13:58 jvwoolf jeff: The server she mentions is terran-master.gapines.org. Windows 10, Firefox 81.0.1.
13:58 jvwoolf And here's a screenshot: https://photos.app.goo.gl/QTLDjZz6SKFgnhtRA
13:59 jvwoolf Oh and clearing site data (including cookies) didn't fix it.
14:39 terranm joined #evergreen
15:36 mantis2 left #evergreen
16:46 jvwoolf left #evergreen
18:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
20:50 sandbergja joined #evergreen
22:10 sandbergja joined #evergreen
22:13 mrisher joined #evergreen

Results for 2020-10-11

00:55 ejk_ joined #evergreen
06:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
10:39 jeffdavis joined #evergreen
10:39 troy__ joined #evergreen
10:39 gmcharlt joined #evergreen
15:06 mrisher joined #evergreen
17:19 mrisher_ joined #evergreen
17:21 mrisher joined #evergreen
18:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:49 sandbergja joined #evergreen
20:11 sandbergja joined #evergreen
20:21 sandbergja joined #evergreen

Results for 2020-10-10

00:33 sandbergja joined #evergreen
14:07 mrisher joined #evergreen
16:54 sandbergja joined #evergreen
18:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:32 sandbergja joined #evergreen
21:50 jvwoolf1 joined #evergreen

Results for 2020-10-09

00:36 abowling1 joined #evergreen
06:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
06:59 collum joined #evergreen
07:35 mrisher joined #evergreen
07:40 collum joined #evergreen
16:19 sandbergja joined #evergreen
16:52 jvwoolf left #evergreen
16:57 Dyrcona Well, that's enough for now.
18:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:41 gmcharlt noting as a heads-up that I've turned on G Suite / Gmail for the evergreen-ils.org. I've set things up so that email to existing aliases like info@ and gitadmin@ will continue to go through lupin and work as expected, but if you see any cases where it looks like email is being dropped on the floor, let me know

Results for 2020-10-08

03:38 jvwoolf joined #evergreen
03:38 miker joined #evergreen
06:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
07:00 agoben joined #evergreen
07:16 mantis1 joined #evergreen
07:27 rjackson_isl_hom joined #evergreen
15:51 mantis1 left #evergreen
16:21 gmcharlt as a heads-up from the release team, we're thinking of doing the release two days early, i.e., on Monday 10/12 rather than Wednesday
16:22 Bmagic https://www.youtube.com/watch?v=r3Pr1_v7hsw
16:22 gmcharlt additional testing of the RC tarball requested, as well as minimizing further changes to rel_3_6
16:24 gmcharlt I imagine 1893463 will make it in 3.6.0, but I'm reserving the right to cut the release from commit e07ca51538 if something should crop up
16:24 pinesol gmcharlt: [evergreen|Galen Charlton] update Czech translation for Angular staff client - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=e07ca51>
16:24 Bmagic gmcharlt: hook me up with the tarball, I'll test it
16:24 gmcharlt Bmagic: great! it's available from the normal downloads page
16:24 Bmagic oh, THAT tarball
16:25 Bmagic :), no prob
17:04 mmorgan left #evergreen
17:22 Bmagic gmcharlt: look! It's working!
17:27 mrisher_ joined #evergreen
18:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:09 Bmagic gmcharlt: tarball works: https://bugsquash.mobiusconsortium.org/eg/staff/
20:35 mrisher joined #evergreen

Results for 2020-10-07

06:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
07:15 rjackson_isl_hom joined #evergreen
07:59 mantis1 joined #evergreen
08:22 collum joined #evergreen
14:49 JBoyer I'm mid-build on the rc, so I won't be pulling anything, should be fine.
14:49 csharp ok awesome
14:49 JBoyer (finally done with translation, may be finished soon...)
14:50 JBoyer ALSO, csharp++ for testing that one.
14:52 csharp calling 1241
14:58 pinesol [evergreen|Jason Boyer] LP1893463: Prevent duplicated report outputs - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=7ae38e7>
14:58 pinesol [evergreen|Chris Sharp] LP1893463: stamp upgrade script - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=7c0d5ee>
15:17 csharp yeah - looking into an approach now
15:17 Dyrcona csharp++
15:33 jihpringle joined #evergreen
15:40 csharp ok, I have a solution that I just tested - pushed it here: https://git.evergreen-ils.org/?p=working/Ev​ergreen.git;a=shortlog;h=refs/heads/user/cs​harp/lp1893463_upgrade_script_improvements - if someone wants to sign-off
15:40 csharp or I could just shove it in :-)
15:42 csharp JBoyer++ # buildin'
15:43 yar joined #evergreen
15:52 mantis1 left #evergreen
16:00 JBoyer csharp++ teaching me about DISTINCT ON () today. I'm +1 for that change.
16:38 Dyrcona I added just after the BEGIN;
16:38 Dyrcona It'll probably have to go at the top of the combined upgrade script.
16:40 Dyrcona It has to go inside the transaction or it doesn't work, and you get a message to that effect.
16:40 csharp works for me on my test
16:40 jeff I think it can come late in the transaction-- it appearing before the CREATE for the index should be sufficient, but should be tested. I think the effect of setting it late in the transaction is that it "flushes" the pending checks before returning from the SET.
16:40 csharp I'll update the working branch with that
16:42 csharp ok, same git location, force-pushed the single commit with the fix
16:45 Dyrcona berick++ jeffdavis++ # For helping me understand something in a different venue.
17:28 mmorgan left #evergreen
17:43 gmcharlt https://evergreen-ils.org/e​vergreen-3-6-rc-available/
17:48 csharp gmcharlt++
18:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:04 JBoyer joined #evergreen
20:42 Dyrcona joined #evergreen
20:42 Dyrcona @dunno add Your computer account is overdrawn. Please reauthorize.

Results for 2020-10-06

15:51 sandbergja gmcharlt: at this point, yes
15:52 JBoyer sandbergja++
15:52 Dyrcona sandbergja++
15:52 sandbergja although I could totally see it being beneficial to run the test suites we have for code, too
15:52 gmcharlt sandbergja++
15:53 sandbergja but we can get there eventually
15:53 sandbergja :-)

Result pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148