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

Results for 2019-10-22

09:53 Bmagic https://hub.docker.com/r/mobiusoffice/evergre​en-ils/tags?page=1&ordering=last_updated
10:22 nfBurton joined #evergreen
10:28 sandbergja joined #evergreen
10:32 pinesol News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-10-22T10:04:33,122124693-0400 -0>
10:32 pinesol News from qatests: Failed Log Output: osrfsys.log <http://testing.evergreen-ils.org/~li​ve/test.76.html#2019-10-22T10:04:33,164852976-0400 -2>
10:37 yboston joined #evergreen
10:54 abowling_ joined #evergreen
10:57 tlittle joined #evergreen
11:09 sandbergja joined #evergreen
11:17 alynn26 joined #evergreen
11:31 alynn26_away joined #evergreen
11:42 berick sandbergja: question about org-family-select.component.spec.ts .. were the "fixture.whenStable().then(() ... " checks solving a specific problem?  i ask because those are causing the (naive) linter to throw erros
11:42 berick sandbergja: see http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-10-22T10:04:33,122124693-0400%20-0
11:43 berick i have tried commenting out the if block and the tests continue to work
11:43 berick i'm wondering if we can just remove those checks
11:44 berick test runner, i mean, not linter
11:52 gmcharlt link to the slides for my presentation: https://bit.ly/evghack19leap
11:55 * dbs is intrigued by the slides, but they leave out the destination of the leap!
11:58 Dyrcona :)
12:43 dbs Dyrcona: maybe I'm really forgetting my git, but the workflow I'm intending is: 1. Checkout a clean rel_3_3 branch 2. Merge the rel_3_4 branch on top of it
12:43 Dyrcona dbs: Why?
12:43 Dyrcona Just checkout rel_3_4.
12:43 dbs Testing the upgrade path from rel_3_3 to rel_3_4 for those who install from git
12:44 Dyrcona That's not how you upgrade.
12:44 Dyrcona Well, now how I upgrade.
12:44 dbs Funny, that's how I've upgraded ever since we moved to git
12:57 sandbergja I'd been fiddling with an angular unit test auto-generator at the time, so the timing is suspicious. :-)
12:57 Dyrcona hurrah for looking at diffs before committing... I found a "bug" in my README changes.
13:05 _bott_ joined #evergreen
13:05 berick sandbergja: ok, cool, i'll push a patch to remove them, for now anyway, so we can un-break the test server
13:05 csharp berick: https://pastebin.com/i2Q4Hfme
13:06 sandbergja berick++
13:07 csharp berick: https://bugs.launchpad.net/evergreen/+bug/1712861

Results for 2019-10-21

09:45 phasefx miker: I pulled up the 1777698 bug by accident and was mangling the fix commited status
09:50 miker phasefx: I've set it back to fix-committed ... is that what you meant?
09:51 phasefx miker++ yeah, meant i wasn't sure of the state, too braindead to parse your pushed to which branches statement
09:52 miker csharp: did you get a chance to test 1773191 further after fixing the comma typo? (also, I want to look a the sort change -- looking at the diff alone there's not enough context...)
09:53 miker phasefx: ah, gotcha. yeah, I'll add fix-committed to all
09:55 pinesol [evergreen|Michele Morgan] LP#1657171 - Normalize right and left single and double quotes - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=41f088d>
09:55 pinesol [evergreen|Chris Sharp] LP#1657171 - Adding upgrade script - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=a3206c0>
10:05 agoben joined #evergreen
11:02 agoben Indy is on EDT right now
11:02 agoben Bill's going to talk in about 30 minutes
11:02 rfrasur I've lived in Indiana for "awhile."  I dunno anything about any of this.  We like to call it "Mitch Daniels Time"
11:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:03 Dyrcona Wake me up when it's "Miller Time."  ... On second thought, don't. :)
11:03 berick @quote random
11:03 pinesol berick: Quote #170: "<berick> IDL. it's what's for dinner" (added by bshum at 01:28 PM, July 21, 2017)
21:04 sandbergja joined #evergreen
21:53 sandbergja joined #evergreen
22:16 sandbergja joined #evergreen
23:02 pinesol News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-10-21T23:00:55,792076215-0400 -0>
23:02 pinesol News from qatests: Failed Log Output: osrfsys.log <http://testing.evergreen-ils.org/~li​ve/test.76.html#2019-10-21T23:00:55,833855268-0400 -2>
23:46 sandbergja joined #evergreen

Results for 2019-10-20

00:52 sandbergja joined #evergreen
05:59 jweston joined #evergreen
10:45 sandbergja joined #evergreen
11:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
14:12 sandbergja joined #evergreen
15:29 sandbergja joined #evergreen
16:56 sandbergja joined #evergreen
17:23 sandbergja joined #evergreen
19:48 sandbergja joined #evergreen
22:48 sandbergja joined #evergreen
23:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>

Results for 2019-10-19

02:32 sandbergja joined #evergreen
04:08 sandbergja joined #evergreen
09:08 aabbee joined #evergreen
11:03 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:51 sandbergja joined #evergreen
18:33 sandbergja joined #evergreen
19:19 sandbergja joined #evergreen
23:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>

Results for 2019-10-18

10:21 jvwoolf joined #evergreen
10:22 Dyrcona joined #evergreen
10:26 Dyrcona Well, this is crazy: An update of 1,198 bib records ran much faster on a Pg10 database that is using default settings than it did on a Pg9.6 database using optimized settings on the same server, I mean like 10 orders of magnitude faster.
10:27 Dyrcona Both have had statistics recalculated.  I suppose running it once isn't much of a test, but....
10:29 Dyrcona Well, "10 order of magnitude" should be more like 10x....
10:30 csharp that's encouraging
10:30 Dyrcona And unrelated to Evergreen: Ubuntu 19.10 hasn't resolved my WiFi issues with the mismatched protocols....
10:31 Dyrcona I suppose that is encouraging, and maybe I'll just upgrade us to Pg10 in production instead of 9.6.
10:31 Dyrcona Both database were upgraded from Pg 9.5, as an additional data point.
10:38 csharp good to know - we're running 3.4 on PG11 in a test environment, but I plan to target 10 on the next reinstall
10:39 Dyrcona I've got Pg 11 on this server, too. Other than doing pg_upgrade, I've not messed with it.
10:39 Dyrcona 9.5, 9.6, 10, 11 on the same server
10:40 Dyrcona Old mail servers with 6TB of disk space make decent test DB servers. :)
10:55 Stompro Thanks csharp, I don't see any mention of the preferred lib feature in the commit message.  And looking at the code I cannot tell if the @pref_ou is no longer passed as part of the search, or if it just gets included in a way that I cannot see when sent to the database.
11:03 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:08 pinesol [evergreen|Josh Stompro] LP#1555791 - Hide Print List from checkout screen - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=8195d83>
11:08 pinesol [evergreen|Galen Charlton] LP#1555791: add release notes entry - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=7a4dd11>
11:11 collum joined #evergreen
11:32 nfBurton joined #evergreen
11:33 Christineb joined #evergreen
11:44 Stompro jeffdavis, we also had a small local change to decouple the search lib with the pref lib, so when users log into their accounts, they still search consortium by default.
11:49 rfrasur joined #evergreen
12:03 Stompro nfBurton, we do have our 856$9's set for the owning system.  On 2.10, a search would include located URI records based on the preferred search lib, no matter what the search lib is set to.  I can log in to my account, which sets the preferred lib to by home library in system A, then I can change my search lib to system B , branch 1 and I will get copies for System B, Branch 1, but ebooks for system A.
12:09 Stompro jeffdavis, I just tested and you are correct about pref lib not effecting physical holdings, I was wrong about that.  But it did include the ebook records (on the 2.10 system).
12:11 jihpringle joined #evergreen
12:12 Stompro Interesting, on 3.3.4, I'm able to see both sets of 856 links (one scoped for system A, one for system B) if I have a preferred lib for system A and and search lib for system B.
12:15 Dyrcona Stompro: Did you update the bib record vis attr field during the upgrade?
17:12 Stompro Yes, I'm just trying to spot where in the "Eliminate staged search" commit the pref_lib located URI feature is implemented.  If it still exists then I should be able to spot where it is used.  It used to be passed to search.query_paerser_fts as an argument.
17:19 jvwoolf left #evergreen
17:28 Stompro I see where the uri as copy global flag gets used in QueryParser, https://git.evergreen-ils.org/?p=workin​g/Evergreen.git;a=blob;f=Open-ILS/src/p​erlmods/lib/OpenILS/Application/Storage​/Driver/Pg/QueryParser.pm;hb=HEAD#l1482
17:28 Stompro I wonder if there needs to be a section that checks for pref_lib and inserts pref_lib and descendents into the luri_org visibility attribute test.
18:07 jeffdavis It seems like query parsing ignores pref lib in 3.0+. AFAICT pref lib does not affect which records are included in search results (pref lib is not silently added to your search scope), it only affects display of holdings/located URIs on whatever records are already in the result set. I think it's debatable whether this behavior is correct.
18:07 jeffdavis It's different from pre-3.0 but I don't know if I necessarily want to see Library A results if I have selected Library B as my search scope.
18:07 jeffdavis (different from luri's at least)
21:17 sandbergja joined #evergreen
22:58 remingtron joined #evergreen
22:58 dbwells_ joined #evergreen
23:31 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>

Results for 2019-10-17

09:58 aabbee joined #evergreen
10:01 jeff joined #evergreen
10:11 sandbergja joined #evergreen
10:11 mdriscoll We have had several occasions of postgres crashing with out of memory errors.  I probably need to tweak some settings in postgresql.conf, but the interesting thing is the searches that caused the oom.  One was a really huge bunch of text, several others were obvious attemps at SQL injection.
10:13 mdriscoll I fed one of the searches into a test server.  It didn't run out of memory, but the search stayed running in the database even though the front end timed out.  I had to restart postgres to get it to go away, pg_cancel did not work on it. Load average was high while this was running.
10:22 jeff I would consider reproduceable searches like that a denial of service issue worth reporting as a private security bug.
10:23 mdriscoll Jeff: thanks.  Will do.
10:23 jeff Interesting that pg_cancel_backend did not seem to have an effect.
10:48 mdriscoll Jeff: I don't think I tried a fast shutdown.  There weren't any issues with startup.
10:57 Christineb joined #evergreen
11:01 jeff mdriscoll: good to hear!
11:03 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:25 sandbergja joined #evergreen
11:56 stephengwills joined #evergreen
12:06 jihpringle joined #evergreen
13:33 yboston joined #evergreen
13:55 JBoyer jeffdavis++
14:44 sandbergja_ joined #evergreen
15:49 Stompro terran++ thanks for testing my self check changes.
16:22 jvwoolf left #evergreen
16:30 yboston joined #evergreen
16:53 khuckins joined #evergreen
19:07 cmalm joined #evergreen
22:37 sandbergja joined #evergreen
23:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>

Results for 2019-10-16

11:01 aabbee joined #evergreen
11:01 * berick updates 1846806
11:02 csharp berick++
11:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:04 tlittle joined #evergreen
11:45 jihpringle joined #evergreen
12:00 sandbergja joined #evergreen
16:26 dbs yay, modify_migrated_user_password does the right thing in the password reset flow: https://gitlab.com/evergreen-library-system/ever​green-library-system/blob/rel_3_4/Open-ILS/src/p​erlmods/lib/OpenILS/Application/Actor.pm#L1491
16:44 Bmagic Anyone know if there is an LP entry for patron self registration notification AT to staff? Seems pretty straightforward in terms of implementing. Almost could be implemented solely in the database AT definition
16:49 Bmagic but bug 1821093 might need to be solved first, otherwise, let the email/texts rip
16:49 pinesol Launchpad bug 1821093 in Evergreen "Patron Self Registration form needs captcha" [Undecided,Confirmed] https://launchpad.net/bugs/1821093
17:16 Stompro joined #evergreen
17:38 aabbee joined #evergreen
19:17 jihpringle joined #evergreen
20:11 cmalm joined #evergreen
21:42 sandbergja joined #evergreen
22:41 sandbergja joined #evergreen
23:03 pinesol News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-10-16T23:01:40,911865881-0400 -0>
23:03 pinesol News from qatests: Failed Running perl live tests <http://testing.evergreen-ils.org/~li​ve/test.49.html#2019-10-16T23:01:40,940294206-0400 -2>

Results for 2019-10-15

08:47 Dyrcona Um... I don't think the following is supposed to happen:
08:50 Dyrcona Using Chromium 77 with a normal tab, I get a blank window when I go to Local Administration with a recent checkout of master.  If I reload, I get "Welcome to Webby."  The link to go to the splash page seems to do nothing. I tried emptying the cache and hard reload.
08:51 Dyrcona Using Firefox 69.0.3 and a Private Window to login to the same evergreen instance, I get prompted to register the workstation again when I go to Local Administration.  After registering the workstation, clicking Use Now, and logging in again, it seems to work.
08:56 Dyrcona That's on a test system set up at CW MARS last week with Pg 10 for the database, Ubuntu 16.04 for the brick vms, and haproxy in front of the bricks.
08:57 Dyrcona I have some VMs that I built on my laptop Sunday that I can also test with, and I will do so in a bit.
09:00 Dyrcona Trying again with Chromium 77, an Incognito Window, and the default admin, rather than a Global Administrator that I added, seems to just work.
09:00 yboston joined #evergreen
09:01 Dyrcona Yeah, I only get the blank screen with my added global administrator account....
09:28 csharp gotcha
09:31 miker Dyrcona: .has_[work_]perm_at is the bane of my existence...
09:32 agoben We've got a library that's having trouble with offline mode not caching the workstation info.  If they log in and *then* go offline, it works fine, but if they haven't logged in on a given day, it's wiped out.  Any suggestions?
09:32 miker we should add a short circuit test for -1 in those
09:34 agoben Note: the workstation registration isn't also disappearing, just the offline info.
09:36 Dyrcona miker: It checks for -1 in joins, but it doesn't short circuit the way that super user does.
09:37 Dyrcona agoben: Do they do something locally to clear the cache? Windows policies, maybe?
09:51 JBoyer There's probably a better way to deal with those.
09:52 Dyrcona Well, it was quick enough to insert for the two accounts that I made.
09:55 mdriscoll joined #evergreen
10:04 Dyrcona We're also using Pg 10 on this test cluster, and so far, no problems.
10:09 sandbergja joined #evergreen
10:13 cmalm joined #evergreen
10:58 sandbergja joined #evergreen
11:03 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
12:01 jihpringle joined #evergreen
12:08 sandbergja joined #evergreen
12:11 aabbee joined #evergreen
13:16 jwoodard joined #evergreen
13:22 jwoodard left #evergreen
13:24 jwoodard joined #evergreen
13:32 jeffdavis Here's a strange bug. On 3.3, after adding a title to your basket, a subsequent search is giving us an internal server error. Removing the cartcache cookie makes the error go away. We're only seeing this when load-balancing between multiple servers.
13:33 jeffdavis Call to [open-ils.storage.biblio.multic​lass.staged.search_fts.atomic] failed for session [...], thread trace [1]: Can't call method "opac_visible" on an undefined value at /usr/local/share/perl/5.22.1/OpenILS/Appl​ication/Storage/Driver/Pg/QueryParser.pm line 1177.
13:35 jeffdavis hm, wonder if it is a locale thing...
13:49 jeffdavis looks like default_locale in opensrf.xml was set to en-CA in our multi-server environment but en-US in single-server test environments; changing to en-US seems to be avoiding the issue so far; never had a problem with en-CA there until now though
14:57 nfBurton joined #evergreen
15:07 yboston joined #evergreen
15:31 jeffdavis Definitely seeing much higher open-ils.actor drone counts on 3.3. I increased max_children from 50 to 75 but we're still hitting that new limit (currently hovering just below it on 2 out of 3 production servers).
15:34 Dyrcona jeffdavis: It's the web staff client.
15:36 Dyrcona jeffdavis: Ours is 60 per drone, so 120 per brick.
15:37 dbs jeffdavis / Dyrcona: do you know how many simultaneous users you have, to help figure out a rough drone-per-user rule of thumb?
18:08 sandbergja_ joined #evergreen
19:53 b_bonner left #evergreen
20:13 JBoyer_ joined #evergreen
23:03 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
23:52 sandbergja joined #evergreen

Results for 2019-10-14

09:55 sandbergja joined #evergreen
10:33 khaun joined #evergreen
10:39 _bott_ joined #evergreen
10:40 khaun test
10:42 * rhamby waves hi
10:43 khaun Ah, thanks. Been too long since I've done IRC chatting, wasn't sure if lack of Voice would keep me from talking.
10:43 khaun I have a question about PINES specifically, would this be a good channel to ask? Or is there another / better one?
10:50 Dyrcona You could ask here if it's a technical, Evergreen thing and not policy-related.
10:51 khaun Ah, okay. It's more on the technical side. Basically, how would I download/export information for all copies of a given item, across the whole system?
10:52 khaun I'm searching for "digital talking book player" and it gives 265 results from all the different branches and systems. I'd like to get it all in one place, rather than having to copy/paste from the search results.
11:03 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:04 _bott_ left #evergreen
11:04 Dyrcona Are you in the web staff client or the patron OPAC?
11:05 _bott_ joined #evergreen
11:17 Dyrcona Assuming you're in the web staff client and not XUL.
11:18 khaun Huh... Something weird is going on, I blame my browser. I reloaded it, and it did show the status column for a second until the page finished loading
11:23 Dyrcona khaun: There's a related bug requesting the ability to add items to a bucket from a catalog search: https://bugs.launchpad.net/evergreen/+bug/1721262
11:23 pinesol Launchpad bug 1721262 in Evergreen "WISH LIST - Create Item Bucket From Catalog Search" [Undecided,New]
11:26 bos20k joined #evergreen
11:33 yboston joined #evergreen
12:30 khuckins joined #evergreen
17:07 yboston joined #evergreen
18:33 sandbergja joined #evergreen
22:29 sandbergja joined #evergreen
23:03 pinesol News from qatests: Failed Installing Evergreen pre-requisites <http://testing.evergreen-ils.org/~li​ve/test.26.html#2019-10-14T23:01:06,073077046-0400 -0>
23:03 pinesol News from qatests: Failed Building Evergreen <http://testing.evergreen-ils.org/~li​ve/test.30.html#2019-10-14T23:01:06,099441875-0400 -2>
23:03 pinesol News from qatests: Failed Running Evergreen tests <http://testing.evergreen-ils.org/~li​ve/test.31.html#2019-10-14T23:01:06,125858900-0400 -4>
23:03 pinesol News from qatests: Failed Installing Evergreen <http://testing.evergreen-ils.org/~li​ve/test.32.html#2019-10-14T23:01:06,152266974-0400 -6>
23:03 pinesol News from qatests: Failed Installing Dojo <http://testing.evergreen-ils.org/~li​ve/test.35.html#2019-10-14T23:01:06,179655752-0400 -8>
23:03 pinesol News from qatests: Failed configure apache <http://testing.evergreen-ils.org/~li​ve/test.36.html#2019-10-14T23:01:06,206916195-0400 -10>
23:03 pinesol News from qatests: Failed configure EG Action/Trigger <http://testing.evergreen-ils.org/~li​ve/test.38.html#2019-10-14T23:01:06,233205440-0400 -12>
23:03 pinesol News from qatests: Failed Create Evergreen Database <http://testing.evergreen-ils.org/~li​ve/test.41.html#2019-10-14T23:01:06,259589482-0400 -14>
23:03 pinesol News from qatests: Failed Running pgTAP tests <http://testing.evergreen-ils.org/~li​ve/test.42.html#2019-10-14T23:01:06,286914512-0400 -16>
23:03 pinesol News from qatests: Failed Running autogen.sh <http://testing.evergreen-ils.org/~li​ve/test.44.html#2019-10-14T23:01:06,313276431-0400 -18>
23:03 pinesol News from qatests: Failed Running pgTAP live tests <http://testing.evergreen-ils.org/~li​ve/test.47.html#2019-10-14T23:01:06,339633531-0400 -20>
23:03 pinesol News from qatests: Failed Running settings-tester.pl <http://testing.evergreen-ils.org/~li​ve/test.48.html#2019-10-14T23:01:06,367517914-0400 -22>
23:03 pinesol News from qatests: Failed Running perl live tests <http://testing.evergreen-ils.org/~li​ve/test.49.html#2019-10-14T23:01:06,394068348-0400 -24>
23:03 pinesol News from qatests: Failed Log Output: srfsh.log <http://testing.evergreen-ils.org/~li​ve/test.58.html#2019-10-14T23:01:06,422282956-0400 -26>
23:15 sandbergja joined #evergreen

Results for 2019-10-13

03:07 bshum joined #evergreen
06:24 _bott_ joined #evergreen
10:57 sandbergja joined #evergreen
11:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
12:12 Christineb joined #evergreen
13:47 sandbergja joined #evergreen
14:36 sandbergja joined #evergreen
21:32 jboyer-isl joined #evergreen
22:20 sandbergja joined #evergreen
22:53 sandbergja joined #evergreen
23:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
23:42 sandbergja joined #evergreen

Results for 2019-10-12

04:59 stephengwills joined #evergreen
06:17 stephengwills joined #evergreen
10:07 sandbergja joined #evergreen
11:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
12:38 sandbergja joined #evergreen
12:47 Dyrcona joined #evergreen
16:15 jonadab joined #evergreen
19:11 sandbergja joined #evergreen
22:40 sandbergja joined #evergreen
23:03 sandbergja joined #evergreen
23:31 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
23:35 sandbergja joined #evergreen
23:53 sandbergja joined #evergreen

Results for 2019-10-11

10:57 miker dang, they must have a really long name! ;)
11:00 mmorgan Nothing looks unusual about the patron record. Any other log to look at for more information?
11:01 berick Bobby Tables cousin, Little Bobby Zillion Zero-Width Spaces
11:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:04 Dyrcona mmorgan: Increase max_stanza_size in ejabberd.{yml,cfg}
11:08 berick mmorgan: it's very odd.  anything look unusual in the edit form?  super long values, maybe stat cats?.  I'd also check the rows in actor.usr_setting for that user, could be some chaos there.
11:12 Dyrcona Is this a staff account with lots of copy templates, perchance?
11:53 jihpringle joined #evergreen
11:53 rfrasur mmorgan - you've done good work.  It sounds like that patron really might be magic.  ish.
11:55 bos20k joined #evergreen
11:56 mmorgan Fortunately, this is a test patron, but some real patrons can have records that are just as, err, busy, if not busier!
11:57 * mmorgan would like to open a lp bug, but is not sure what to report.
11:57 berick mmorgan: Dyrcona's suggestion of raising the ejabberd max stanza size is the fix you need for now
11:57 berick and there's already an LP re: the pendin' chunkin' / bundlin' work
11:59 * mmorgan will pass that on to our systems manager.
21:13 stephengwills joined #evergreen
21:46 stephengwills joined #evergreen
22:20 stephengwills joined #evergreen
23:31 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
23:42 sandbergja joined #evergreen
23:56 jvwoolf joined #evergreen

Results for 2019-10-10

10:37 Dyrcona Eh, nope. Configuration issue. Needed to change - to CONS in the default config.
10:37 Dyrcona It's working, now.
10:41 mmorgan left #evergreen
11:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
12:04 sandbergja joined #evergreen
12:05 jihpringle joined #evergreen
12:23 Bmagic berick: what's wrong with ES 7xx?
19:04 cmalm joined #evergreen
19:29 StomproJosh joined #evergreen
20:14 sandbergja joined #evergreen
23:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
23:40 sandbergja joined #evergreen

Results for 2019-10-09

10:10 jvwoolf1 joined #evergreen
10:15 sandbergja joined #evergreen
10:20 cmalm joined #evergreen
11:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:16 sandbergja joined #evergreen
11:36 jvwoolf joined #evergreen
11:39 sandbergja joined #evergreen
17:00 mmorgan left #evergreen
17:15 sandbergja If a user doesn't have the COPY_STATUS_LOST.override permission, that means that they can't check in any items with Lost status, right?
17:43 Bmagic sandbergja: I believe that's right. Or deal with changing the copy status away from LOST
17:47 Bmagic Has this come up before "Expected an identifier but found 'lead' instead" during the "npm run test" step in Open-ILS/web/js/ui/default/staff/  -  complains about cat/bucket/record/app.js:702 which is let lead = { orig_marc_xml : $scope.lead.marc_xml };
17:53 berick Bmagic: 'let'
17:53 berick not OK for phantomjs
17:53 Bmagic let needs to be expressed 'let' ?
19:58 sandbergja_ joined #evergreen
22:48 sandbergja joined #evergreen
23:26 sandbergja joined #evergreen
23:32 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
23:39 stephengwills_ joined #evergreen
23:40 bwicksall joined #evergreen

Results for 2019-10-08

09:53 jvwoolf joined #evergreen
10:14 sandbergja joined #evergreen
10:31 jvwoolf joined #evergreen
11:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:08 jihpringle joined #evergreen
11:14 agoben joined #evergreen
12:09 sandbergja joined #evergreen
18:04 abowling left #evergreen
20:15 stephengwills joined #evergreen
22:15 sandbergja joined #evergreen
23:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
23:04 sandbergja joined #evergreen
23:18 sandbergja joined #evergreen
23:31 sandbergja joined #evergreen

Results for 2019-10-07

09:56 Dyrcona When all else fails, replace the default route!
10:02 mmorgan1 joined #evergreen
10:40 gsams joined #evergreen
11:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:11 Christineb joined #evergreen
11:22 sandbergja joined #evergreen
11:28 mmorgan joined #evergreen
14:38 Christineb joined #evergreen
15:06 jvwoolf joined #evergreen
17:13 mmorgan left #evergreen
23:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
23:38 sandbergja joined #evergreen

Results for 2019-10-06

00:24 sandbergja joined #evergreen
00:48 sandbergja joined #evergreen
03:56 sandbergja joined #evergreen
11:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
12:00 sandbergja joined #evergreen
13:06 yar_ joined #evergreen
13:38 sandbergja joined #evergreen
14:23 sandbergja joined #evergreen
16:18 sandbergja joined #evergreen
16:31 sandbergja joined #evergreen
23:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>

Results for 2019-10-05

09:08 aabbee joined #evergreen
10:18 sandbergja joined #evergreen
11:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
12:54 sandbergja joined #evergreen
14:07 sandbergja joined #evergreen
14:22 sandbergja joined #evergreen
20:25 sandbergja joined #evergreen
21:33 sandbergja joined #evergreen
22:14 sandbergja joined #evergreen
23:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
23:41 sandbergja joined #evergreen

Results for 2019-10-04

10:46 * mmorgan doesn't understand the utility of barcodes containing spaces, barcodes with leading spaces, even less so.
10:47 mmorgan Do the spaces have some sort of significance?
10:54 sandbergja joined #evergreen
11:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:03 pinesol [evergreen|Dan Briem] LP#1841089 Apply button in Patron Bill History screen is in confusing location - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=313c923>
11:03 jeff mmorgan: it's a mystery!
11:04 jeff mmorgan: in some cases of weird barcodes, i think they're mistakes that went undetected by the owning library due to some quirk of their software or equipment, etc.
11:07 * mmorgan grumbles
17:10 mmorgan left #evergreen
19:12 sandbergja joined #evergreen
19:38 sandbergja joined #evergreen
23:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>

Results for 2019-10-03

09:39 aabbee joined #evergreen
09:57 jeff__ joined #evergreen
10:58 yboston joined #evergreen
11:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:13 sandbergja joined #evergreen
11:21 Christineb joined #evergreen
11:39 khuckins joined #evergreen
15:03 mmorgan1 joined #evergreen
15:27 mmorgan joined #evergreen
17:05 mmorgan left #evergreen
17:36 pinesol [evergreen|Mike Rylander] LP#1836963: reduce the cost of utility functions, speeding up search - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=0dff686>
17:38 pinesol [evergreen|Garry Collum] lp1813056 Fixes Current Date in Date Returned in Circ History CSV - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=0aaf9f8>
17:56 pinesol [evergreen|Jason Stephenson] LP 1827250: Fix Last Captured Hold Check for Holds Shelf - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=83e278e>
18:08 pinesol [evergreen|Jeff Davis] LP#1609556: only include OPAC-visible copies in SRU/Z39.50 holdings - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=39c5b37>
18:56 cmalm_ joined #evergreen
18:58 gsams_ joined #evergreen
20:02 JBoyer_ joined #evergreen
21:35 JBoyer joined #evergreen
21:50 sandbergja joined #evergreen
22:23 sandbergja joined #evergreen
23:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>

Results for 2019-10-02

10:20 oajulia__ joined #evergreen
10:21 oajuli___ joined #evergreen
10:46 rfrasur joined #evergreen
11:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:15 oajulianclements joined #evergreen
11:24 gmcharlt jeffdavis: I've pushed a WIP for you to play with for bug 1846042
11:25 pinesol Launchpad bug 1846042 in Evergreen 3.3 "Angular admin pages need filters" [High,Confirmed] https://launchpad.net/bugs/1846042
11:29 * gmcharlt claims 1192
11:33 gmcharlt JBoyer: I've gone ahead and pushed a fix for bug 1846357, but would appreciate after-the-fact testing
11:33 pinesol Launchpad bug 1846357 in Evergreen "Billing age function reverted in 3.4rc" [Critical,Fix committed] https://launchpad.net/bugs/1846357
11:34 gmcharlt also, I am going to go ahead and branch rel_3_4 now
11:35 pinesol [evergreen|Galen Charlton] LP#1846357: fix circulation and billing aging - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=fcedac0>
15:31 nfBurton Is Hatch 0.3.0 officially released?
15:40 berick nfBurton: no, still waiting on bug 1830391 -- at which point it will jump to 0.3.2
15:40 pinesol Launchpad bug 1830391 in Evergreen "Hatch omnibus circa 3.3 (Java updates and more)" [Undecided,New] https://launchpad.net/bugs/1830391
15:41 gmcharlt OK, haven't heard of no issues and knowing that there's been at least one test of it on Buster, I'm going to cut OpenSRF 3.2.0 now
15:41 nfBurton Oh okay. I've been using a 3.0 in a bug fix for my label printers but couldn't find it anymore. Good to know
15:41 nfBurton Cause the downloads is still at 2.0
15:43 berick gmcharlt++
15:57 gmcharlt I've uploaded OpenSRF 3.2.0
15:57 gmcharlt formal announcement will be done in conjunction with Evergreen 3.4.0
16:10 pinesol [evergreen|Galen Charlton] note minimum OpenSRF version in upgrade instructions - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=8d090d2>
16:13 gmcharlt I am ready to start cutting 3.4.0; does anybody have any immediate further testing they are about to do or know of a reason to hold off on the release?
16:15 JBoyer None here.
16:22 Dyrcona gmcharlt++
17:09 mmorgan left #evergreen
19:11 jeffdavis gmcharlt++ # EG/OpenSRF releases + collab branch for Ang admin page filters
21:45 sandbergja joined #evergreen
22:40 sandbergja joined #evergreen
23:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>

Results for 2019-10-01

10:21 aabbee joined #evergreen
10:37 sandbergja joined #evergreen
10:53 oajulianclements joined #evergreen
11:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:33 oajulianclements Regarding OpenAthens integration previously discussed on open-ils-dev, I've pushed code at https://github.com/openathens/Evergr​een/tree/openathens-sso-integration and would like to request review of the PR - launchpad #1842297 / github PR 89
11:33 pinesol Launchpad bug 1842297 in Evergreen "OpenAthens integration" [Undecided,In progress] https://launchpad.net/bugs/1842297 - Assigned to Julian Clementson (oajulianc)
11:36 oajulianclements There are new database tables, a new local admin page, new Perl dependencies, new docs page, new logic that intercepts OPAC login, so it's quite substantial.
14:19 JBoyer There we go. That would make it hard to find a date. Until I bookmark that page with a "3.1 EOL Date" in my browser. ;)
14:19 JBoyer csharp++
14:19 JBoyer dbwells++
14:21 Dyrcona csharp: You mentioned trying Pg 10 or 11 recently. I'm setting up a cluster of test VMs, and I'm going to install Pg 10 to test against concerto data. My main goal is figuring out a working haproxy/keepalived config, but I figure that I can test Pg 10 while I'm at it.
14:22 Dyrcona I would use production data, but I don't think I have enough disk space on this old machine.
14:27 csharp currently running 11 on a production-ish 3.4-beta and 10 on a master test server
14:27 csharp so far so good in basic poking-level testing
14:31 Dyrcona Cool! I just finished the package installation.
14:35 pinesol [evergreen|Jane Sandberg] LP1739607: Add missing columns to patron record - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=d33ddf6>
14:37 JBoyer I'm planning to have a Buster / Pg 11 server in my living room in the next couple of days. It may not be exactly production *sized* but it will be of production *worth,* at least locally, heh.
14:43 Dyrcona :)
14:43 Dyrcona I just installed Pg10 on Xenial. The vm host is buster, but that's because the machine was originally squeeze and I upgraded it last week.
14:43 Dyrcona Old db servers make pretty decent VM hosts.
14:47 csharp yeah, definitely
14:48 * csharp gets curious about the i18n bug and plans to test miker's fix asap
14:48 * JBoyer imagines cpu cores diving into a pile of RAM like Scrooge McDuck in his money bin...
14:48 Dyrcona :)
14:48 csharp bug 1773191, that is
15:30 gmcharlt we'll still need a non-ABI-breaking variant for OpenSRF 3.1
15:33 gmcharlt jeffdavis: re 1830642 you set the signedoff tag. should I add your signoff to the commit?
15:34 mmorgan joined #evergreen
15:35 jeffdavis Hm, so I did. That may have been an error.
15:37 jeffdavis Give me a few minutes and I'll see about installing/testing.
15:37 gmcharlt jeffdavis: no worries, I'm testing it myself, I just wanted to attribute the signoff correctly
15:38 khuckins joined #evergreen
15:45 oajulianclements joined #evergreen
15:46 sandbergja gmcharlt: I don't think that I'll be able to totally finish work on 1843938 today or tomorrow
15:48 sandbergja no preference on my end
15:51 pinesol [opensrf|Bill Erickson] LP1830642 Remove variable args from md5sum() - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=3fb9396>
16:33 gmcharlt sandbergja: re bug 1842940, are you in a position to push it now, or do you have any objection to my doing so?
16:33 pinesol Launchpad bug 1842940 in Evergreen 3.3 "Return of the "user can edit themselves" bug" [High,Confirmed] https://launchpad.net/bugs/1842940
16:34 pinesol [evergreen|Jeff Davis] LP#1830642: add tests for authenticating users when password contains percent sign - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=ecb1dcc>
16:34 sandbergja_ joined #evergreen
16:36 sandbergja gmcharlt: I can push that; I wanted to quickly check miker's most recent commit with the UI tweak
16:36 gmcharlt sandbergja: thanks!
16:57 JBoyer sandbergja++
16:57 gmcharlt a bug I really really want independent review of for the 3.4-rc is bug 1845050
16:57 pinesol Launchpad bug 1845050 in Evergreen 3.3 "reporter interface can fail to completely load" [High,Confirmed] https://launchpad.net/bugs/1845050
16:57 JBoyer That's the one I just tested and was planning to push after this db update. :_
16:57 JBoyer :)
16:58 gmcharlt JBoyer: groovy
16:58 pinesol [evergreen|Jeff Davis] LP#1845260: fix error in vandelay.auto_overlay_org_unit_copies db function - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=f7c0d35>
17:33 gmcharlt ok
17:34 gmcharlt at this point, with the exception of 1842940, I'm about to draw a line for 3.4-rc
17:34 gmcharlt if there is anything that I've missed that somebody thinks is critical to the 3.4.0 release, as opposed to something that can reasonably wait for 3.4.1, please speak up
17:40 sandbergja miker++ # the UI fix for 1842940 worked well with all my testing
17:40 sandbergja grabbing 1190
17:41 miker gooooood
17:42 sandbergja haha oops, grabbing 1191
17:42 sandbergja not 1190
19:37 gmcharlt sandbergja++
20:04 pinesol [evergreen|Galen Charlton] Translation updates - newpot - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=6bec537>
20:04 pinesol [evergreen|Galen Charlton] Translation updates - po files - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=52bc686>
20:54 gmcharlt the 3.4-rc is now available for testing
20:54 gmcharlt please test early and often!
20:57 jeff gmcharlt++
21:35 sandbergja joined #evergreen
23:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
23:15 sandbergja joined #evergreen
23:33 jvwoolf joined #evergreen

Results for 2019-09-30

10:02 mmorgan1 joined #evergreen
10:53 Dyrcona It never rains, but it pours.
10:57 Dyrcona joined #evergreen
11:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:03 yboston joined #evergreen
11:04 mmorgan joined #evergreen
11:49 Christineb joined #evergreen
17:17 mmorgan left #evergreen
17:27 sandbergja_ joined #evergreen
22:35 sandbergja joined #evergreen
23:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
23:25 sandbergja joined #evergreen
23:59 sandbergja joined #evergreen

Results for 2019-09-29

09:12 stephengwills left #evergreen
10:01 level3 joined #evergreen
10:01 level3 hi, when I clone the repo and run automake it fails on Ubuntu 18.04. Is there something else I need to do?
11:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:23 level3 sigh
11:58 sandbergja joined #evergreen
12:47 jeff level3: is it failing at a certain step in the README file? are you getting a particular error message?
21:55 sandbergja_ joined #evergreen
22:27 sandbergja joined #evergreen
22:53 sandbergja joined #evergreen
23:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>

Results for 2019-09-28

10:56 stephengwills joined #evergreen
11:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:26 yboston joined #evergreen
14:01 sandbergja joined #evergreen
15:37 sandbergja joined #evergreen
23:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>

Results for 2019-09-27

09:56 Dyrcona We typically don't mess with existing entries, other than fix some bugs with missing fields/links that usually make it into later releases. We add custom entries, though, typically with custom views in the database behind them.
09:57 Dyrcona And, most of those custom entries are for reports, and were added by some other than me, a someone who doesn't work here any more.  I could check and see if we have any that use SQL in the IDL, but it would be only 1 or 2 if we do.
09:58 Dyrcona So, after all of that being said, I guess my preference is for views in the database, though I don't think there's much technical difference. :)
10:00 * Dyrcona is figuring out networking for a test environment. I think I need a custom bridge for the external ip address to be shared by the load balancing vms.
10:00 mmorgan Seems like many paths are used to get data from the db to the end user, and it would be useful to know what the best practice should be.
10:00 yboston joined #evergreen
10:02 Dyrcona I added a view for removing patrons from libraries that are no longer members.  The view is basically open billing summary with the org unit where the money is owed added in. It's for keeping patrons who owe money to other member libraries.
10:50 csharp sometimes lack of tickets doesn't actually mean no one cares :-)
10:51 JBoyer Corrective action through inaction. I can handle that. ;)
10:51 berick we just need to replace the offline list with old timey wanted posters
10:51 Dyrcona And, this test setup that I've been mumbling about is to try out haproxy and keepalived.
10:51 Dyrcona berick++
10:51 Dyrcona Though when one asks me for an ILS recommendation, I suggest a card catalog and paper log book. :)
10:51 JBoyer This here's the DVD kid. Only comes in on down days, really likes the wrasslin' DVDs.
11:01 csharp not sure anyone really knows :-)
11:02 mmorgan miker: Ok, good to know, so there may be some performance benefits if the in-IDL view is large?
11:02 mmorgan as in lots of data.
11:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:02 csharp to de-snark that, I'll clarify that my attempts to optimize things have mostly been unsuccessful despite following docs and expert advice :-/
11:03 miker mmorgan: s/large/complicated/ (usually correlated, obv), yep
11:03 Dyrcona csharp: same here.... I've considered suggesting we hire a consultant to check our Pg configuration.
12:05 Dyrcona You can also just ignore the failure and charge ahead.
12:07 csharp yeah, I'm going down a rabbit hole
12:07 Dyrcona That's OK. I'm building two bridges to nowhere. :)
12:08 JBoyer csharp, berick, Dyrcona: I've looked at using chromium for testing in the past (would allow let and arrow funcs and generally modern JS all around) but I haven't seen a good way to get it installed without half a gui system coming along. If we accept that you'll just have to run the tests separately on a more heavily packaged machine it's a very simple change.
12:08 csharp I think I'll do that and know that we'll have to find a suitable replacement that can run headless testing
12:08 JBoyer Dyrcona, I have been to date, but ignoring errors really isn't my thing. ;)
12:08 csharp JBoyer: I was just reading about https://github.com/karma-ru​nner/karma-chrome-launcher and https://github.com/GoogleChrome/puppeteer
12:09 JBoyer csharp++
12:19 csharp https://github.com/cyrus-a​nd/chrome-remote-interface
12:20 csharp so theoretically, start chromium in headless mode with a remote port on localhost, then use chrome-remote-interface to connect to it
12:21 JBoyer Ah, so the answer is "kind of" :) Looks like a good project.
12:21 csharp seems like a lot, though - also, I might want to blow chromium away as soon as the testing is done - no need for that
12:22 Dyrcona JBoyer, so yeah, it's a fork of a fork of WebKit. :)
12:25 * Dyrcona thinks he'll wait until Monday to actually set up the bridge, since he'll be 50 miles closer to the collocation facility, then.
12:32 csharp so when we get security warnings from NPM, is it advisable to update the versions installed in package-lock.json?
15:28 sandbergja github++ #such lovely search options
15:46 khuckins joined #evergreen
16:26 jvwoolf left #evergreen
16:54 pinesol [evergreen|Andrea Buntz Neiman] Docs: added another contributor - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=7ffaa21>
17:08 mmorgan left #evergreen
17:17 jihpringle joined #evergreen
17:23 yboston joined #evergreen
18:58 sandbergja_ joined #evergreen
22:11 stephengwills joined #evergreen
22:43 book` joined #evergreen
23:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
23:53 gsams joined #evergreen

Results for 2019-09-26

09:35 Dyrcona During MVLC's migration, I found phone numbers entered as "The number in the field above is the student ID."  I guess because phone number was below the ID field in the old ILS. :)
09:36 Dyrcona Today, I've been asked to regularize some call number labels.  Something I've done a number of times before. It really exercises one's regex fu.
09:38 * Dyrcona considers "cheating" by dumping the rows to a CSV, mangling them manually, and generating a SQL update script from the CSV.
09:46 Dyrcona On the plus side, production and test data are the same for a change.
09:48 mmorgan1 joined #evergreen
09:54 sandbergja joined #evergreen
09:55 yboston joined #evergreen
10:20 berick heh, i felt so bleeding edge on 9.6.  i'm already crusty.
10:21 Dyrcona Maybe we'll skip 11 and go straight to 12?
10:22 Dyrcona Heh. Nigels' may go to 11. Mine go to 12. :)
10:22 csharp I'm testing 11 right now - but I might chicken out and go from 9.5 to 9.6 :-/
10:22 berick Dyrcona++
10:23 csharp @ana none more black
10:23 pinesol csharp: Noblemen croak
10:23 Dyrcona csharp: We need more testing on 10, really. No one has really put it through its paces.
10:23 Dyrcona A propos nothing: gnu.org seems to be really slow today.
10:23 csharp 10 probably makes more sense since it's the default in 18.04
10:26 Dyrcona We also "support" it in master/3.4.
10:27 csharp I think you just convinced me :-)
10:46 tlittle42 joined #evergreen
11:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:07 Dyrcona Grrr.... "unexpected EOF while parsing" and I don't see the syntax error....
11:07 yboston joined #evergreen
11:08 berick joined #evergreen
19:06 cmalm joined #evergreen
21:54 sandbergja joined #evergreen
22:06 sandbergja joined #evergreen
23:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
23:35 sandbergja joined #evergreen

Results for 2019-09-25

11:01 csharp that's better
11:01 * JBoyer wishes csharp wasn't so cryptic.
11:02 * csharp is an enigma
11:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:03 berick comcast.. wins?
11:07 jonadab comcast isn't nearly as bad as systemd, though.
11:08 jonadab Well, except for the fact that you can be stuck in a situation where you HAVE to deal with them, I guess.  Which is not true for systemd.  It can be avoided.
16:03 jonadab Dyrcona: We're in a consortium, so no.
16:03 jonadab If I were running it locally, then I would be.
16:03 Dyrcona I see. :)
16:04 Dyrcona I just upgraded an old machine from Debian 7 to Debian 8 so I can use it for some testing, plus I did a little digging at the devuan.org website, so I'm thinking about trying Evergreen with devuan on a vm or two.
16:05 Dyrcona I may upgrade this machine further before I actually use it for anything.
16:11 jvwoolf1 left #evergreen
16:12 khuckins joined #evergreen
16:24 pinesol [evergreen|Andrea Buntz Neiman] Docs: typo corrections and added dev funders - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=05d9bdc>
16:36 yboston joined #evergreen
16:54 sandbergja_ joined #evergreen
17:04 pinesol [evergreen|Jane Sandberg] Docs: Adding contributors and employers; fixing formatting - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=3b1eb13>
17:05 mmorgan left #evergreen
18:00 jihpringle joined #evergreen
21:24 sandbergja joined #evergreen
21:26 sandbergja joined #evergreen
21:56 sandbergja joined #evergreen
23:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
23:06 sandbergja joined #evergreen
23:44 sandbergja joined #evergreen

Results for 2019-09-24

10:58 csharp I agree that it's probably an older slide, but it's not a misreprentation of the status quo
11:00 agoben Agreed
11:02 * JBoyer just got here, was about to say what csharp and agoben just did. :)
11:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:07 gsams joined #evergreen
11:08 cmalm_ joined #evergreen
11:09 jeff Thanks, all! rfrasur++ abneiman++ rhamby++ Bmagic++ csharp++ agoben++ JBoyer++
12:46 abneiman jihpringle: cmalm: I'll ping the appropriate people - thanks for the heads up
12:46 jihpringle thanks :)
12:46 cmalm thank you :)
12:49 mmorgan Segue to a question about offline circulation. The Register Patron screen won't load for me, the blue progress bar continues to spin. I've tested on three of our inhouse servers with the same result. Can others load the offline patron registration screen?
12:57 JBoyer cmalm, jihpringle, demo.evergreencatalog.com has been told to step in line, you should be able to use it now.
12:58 jihpringle looks good, thanks jboyer
12:59 khuckins joined #evergreen
12:59 cmalm thanks, jboyer!
13:02 abneiman JBoyer++
13:19 sandbergja_ joined #evergreen
13:24 jihpringle mmorgan: register patron doesn't load on our 3.3.3 test server either - just get the blue bar
13:27 mmorgan Ok, thanks. I notice it loads just fine on the freshly nudged demo.evergreencatalog.com (3.1.5), but not on our 3.2.8 or 3.3.3 servers
13:29 mmorgan It does load on bugsquash.mobiusconsortium.com (3.3.3). Hmm.
13:33 yboston joined #evergreen
16:56 jeffdavis fix is here: https://git.evergreen-ils.org/?p=workin​g/Evergreen.git;a=commitdiff;h=be262584
16:57 gmcharlt jeffdavis: separate bug, and thanks for the fix!
17:03 jeffdavis bug 1845260
17:03 pinesol Launchpad bug 1845260 in Evergreen "Error in Auto-overlay On-order Cataloguing Copies database function" [Undecided,New] https://launchpad.net/bugs/1845260
17:06 mmorgan left #evergreen
17:13 cmalm_ joined #evergreen
17:16 gsams_ joined #evergreen
17:41 yboston joined #evergreen
20:11 gsams joined #evergreen
23:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>

Results for 2019-09-23

08:16 bos20k joined #evergreen
08:42 mmorgan joined #evergreen
08:54 Dyrcona joined #evergreen
08:56 mmorgan jeff: Regarding the pdf417 barcodes, no app, it's scanned directly into the patron reg screen. We purchased one of these to test: https://www.bayscan.com/data​logic-qd2430-2d-imager.html
09:20 jvwoolf joined #evergreen
09:28 yboston joined #evergreen
10:00 mmorgan1 joined #evergreen
10:48 Dyrcona <pedantic>Probably stderr, not stdout.</pedantic> :)
10:50 Dyrcona Bmagic: I don't find that columns anywhere in the source for Evergreen master. Sounds like you have a custom view or added a column?
10:58 khaun joined #evergreen
11:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:03 jeff mmorgan: interesting. can you elaborate on what they mean with this sentence, based on your experience? "Our driver's license scanner includes programming to assist with parsing your library ILS and quickly, and effectively, registering patrons for library cards."
11:19 mmorgan jeff: They work with you to program the scanner to enter the encoded data in the proper fields on your patron edit screen.
11:25 Bmagic Dyrcona: good call. This helped SELECT *   FROM information_schema.columns where column_name='desired_stop_fines'
21:46 sandbergja joined #evergreen
22:17 sandbergja joined #evergreen
22:28 bwicksall joined #evergreen
23:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
23:10 sandbergja joined #evergreen
23:59 sandbergja joined #evergreen

Results for 2019-09-22

04:32 JBoyer joined #evergreen
09:39 JBoyer joined #evergreen
10:56 JBoyer joined #evergreen
11:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:11 JBoyer joined #evergreen
11:31 sandbergja joined #evergreen
13:10 yboston joined #evergreen
20:43 jamesrf joined #evergreen
20:51 Christineb joined #evergreen
22:07 sandbergja joined #evergreen
23:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>

Results for 2019-09-21

01:03 stephengwills joined #evergreen
05:33 cmalm joined #evergreen
09:18 aabbee joined #evergreen
11:32 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
12:06 sandbergja joined #evergreen
13:13 jweston_ joined #evergreen
13:16 berick_ joined #evergreen

Results for 2019-09-20

10:45 nfBurton Guess not
10:45 nfBurton Makes sense
10:46 nfBurton Still wrapping my head around this. I think I''ve got it though
10:46 mmorgan Post a link to your branch on the bug and add a pullrequest tag so others will know to test it
10:49 nfBurton Dyrcona++ mmorgan++
10:49 nfBurton Thanks!
10:50 Dyrcona I'm planning to spend some time on bugs today, probably this afternoon. I noticed a few things while doing the bugmaster stuff last night that I want to look at.
10:57 jeff we then activated and cleared the activation date on the holds that still had the specific activation timestamp.
10:58 jeff another thing to remember is that the normal process of updating a hold can move the activation timestamp back in time if it was more precise than one second.
10:58 jeff (caught me on a few)
11:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:13 jvwoolf joined #evergreen
11:21 sandbergja joined #evergreen
11:25 jvwoolf joined #evergreen
21:21 jeff because michigan fails there.
21:21 jeff which is an immediate frustration for me.
22:36 sandbergja joined #evergreen
23:03 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>

Results for 2019-09-19

10:33 Christineb joined #evergreen
10:33 khaun joined #evergreen
10:57 sandbergja joined #evergreen
11:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:11 jvwoolf joined #evergreen
11:11 * dbs wonders if setting a circulation policy to a "0 day" loan will result in the due date being the end of today...
11:11 * dbs will try it out
16:15 Dyrcona I'm guessing that Apache is not seeing 127.0.0.1 from nginx but the 192.168.1.X address.
16:16 jeff and, are you running nginx and apache on the same host?
16:17 Dyrcona Yes.
16:18 Dyrcona I'm testing on a standalone server that show the same behavior.
16:19 Dyrcona Eh, no. that's not it.
16:21 gmcharlt sorry for the stupid question, but is mod_remoteip enabled?
16:26 Dyrcona It is, or Apache complains about the RemoteIPHeader directive. I think I've got it. Going to try uisng $remote_addr in nginx config and not $proxy_add_x_forwarded_for.

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