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-11-07

09:38 sandbergja joined #evergreen
10:40 alynn26 joined #evergreen
10:42 alynn26 joined #evergreen
11:01 pinesol News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-11-07T11:00:51,274639219-0500 -0>
11:27 jeff Anyone have a favorite thermal printer that prints on sticky paper? Our go-to was the Epson TM-T88 ReStick series, but that and the Star models we've looked at to replace it are both becoming difficult to find. I think the Epson one is being discontinued, unclear if the other is just a temporary shortage.
11:31 jeff MAXStick paper seems to be similar to the ReStick.
12:04 jihpringle joined #evergreen
12:27 collum joined #evergreen
12:37 tlittle joined #evergreen
12:39 khuckins joined #evergreen
12:40 Bmagic After upgrading a test machine from 3.1 to 3.3 - it was noticed that the subject browse results are different and in a different order. Is that expected? (after upgrade, reingest was performed and completed)
12:40 jwoodard joined #evergreen
12:49 * csharp stopped working on testing hopeless holds because he just couldn't do it anymore
12:49 stephengwills holding off on that, eh?
12:50 yboston joined #evergreen
12:52 csharp stephengwills: just trying out a joke I thought of when the word "hopeless" was in every commit message :-)
13:16 Dyrcona OK. I was about to look at the release notes again out of curiosity.
13:17 Dyrcona Actually, that's not a bad idea: looking at the release notes. I haven't really looked at the 3.3 and 3.4 notes, yet.
13:18 Dyrcona Apparently, I have looked at the 3.3 release notes, since a couple of the section links show up as "visited" in my browser. :)
13:20 Dyrcona Nothing about browse in there, but steps about update to Pg 9.6 or later that i should do on my training and test database servers. Bmagic++ # for serendipity
13:21 berick Bmagic: there was some browse code refactoring in 3.3
13:22 berick intention was to avoid any changes, but some may have snuk in
13:22 berick @band add Snuk
14:39 sandbergja I'm curious about how Windows users would contribute to antora-ized docs
14:39 Bmagic I wouldn't be surprised if the lunr repo get's wrapped into the default UI before too long anyway
14:39 * csharp plays the Inception soundtrack whenever Bmagic speaks
14:40 sandbergja Building antora seems like a lot to ask of casual documentation contributors to test their changes
14:40 Bmagic sandbergja: contribution hurdles remain the same
14:40 sandbergja (not that our current stack isn't also a lot to ask)
14:40 Bmagic I've been recommending folks use ascidocfx https://asciidocfx.com/
14:49 jihpringle +1 from me
14:49 stephengwills +1 Marchon
14:50 sandbergja +1 from me!
14:51 abneiman ok - hearing no objections to the general concept, let's toss some action items in
14:51 abneiman #action abneiman will prod gmcharlt about the test server
14:51 abneiman Bmagic and remingtron, are you working on the nav? are there others who want to help here?
14:52 Bmagic I believe there are 70+ links/lines needed
14:52 Bmagic we could divide and conquer. Anyone who wants to help... can!
14:53 sandbergja Bmagic: would they just need access to the working repo to be able to help with that task?
19:00 jeff (and wasn't an unreleased api with docs updated in 2016)
21:00 sandbergja joined #evergreen
21:36 sandbergja joined #evergreen
23:01 pinesol News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-11-07T23:00:51,224589584-0500 -0>

Results for 2019-11-06

08:49 * csharp googles pysip2
08:49 jeff csharp: https://github.com/berick/pysip2
08:50 csharp jeff: thanks!
08:51 jeff still need to do testing with our actual SIP clients, but very handy when doing dev / iterating on something / debugging something, etc.
08:52 jeff sipsh% start
08:52 jeff Disconnected from localhost
08:52 jeff Connect OK
08:52 jeff Login OK
08:52 jeff Server is online
08:52 jeff sipsh% checkout G880610001556 thing1
08:52 jeff (etc)
08:52 csharp nice
08:53 csharp I've been using https://clcohio.org/sip-testing-tool/ for a while, but it runs on Windows and I haven't gotten it working with wine, which is to say that I only run it in my Win10 VM
08:53 csharp that has definitely helped me track down some issues though
08:57 * Dyrcona uses https://github.com/Dyrcona/PHPSIP2
08:58 Dyrcona And, I recently wrote a little thing in C to login via SIP2 to use with haproxy as a check program. I may share that at some point.
08:59 * Dyrcona has looked/used pysip2 and it is nice. Shell mode is cool.
10:27 Dyrcona Whee! Configuring bridges with netplan....
10:28 Dyrcona I think a lot of the change happening in GNU/Linux today is change for the sake of change, and not because the new thing is necessarily better than the old thing.
10:46 sandbergja joined #evergreen
11:01 pinesol News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-11-06T11:00:54,963721722-0500 -0>
11:06 csharp any reason *not* to do "npm audit" when npm recommends doing that?
11:06 csharp *npm audit fix* that is
11:08 csharp npm just partially answered my question: 1 package update for 15 vulnerabilities involved breaking change
11:13 rlefaive_ joined #evergreen
11:36 Dyrcona csharp: Yeahp. Never do what npm suggests. It breaks things.
11:37 csharp terran and I are testing carousels on current master - we create the carousel and the carousel mapping, then we ran the refresh carousels srfsh script - no change in the OPAC - what are we missing?
11:37 csharp Dyrcona: thanks
11:38 csharp do we need to manually change OPAC templates to see stuff?
11:38 Dyrcona No idea, but did you try clearing your browser's cache?
11:39 csharp yeah, we tried it
11:39 csharp also, are the 'built-in' carousels presumed to have an associated bucket? (we see no rows in container.biblio_record_entry_bucket)
11:40 csharp bug 1851524
11:40 gmcharlt bug 1851524
11:40 pinesol Launchpad bug 1851524 in Evergreen "Carousels: bucket not created when adding a carousel" [Medium,New] https://launchpad.net/bugs/1851524
11:40 csharp gmcharlt: we'll test that directly
11:41 gmcharlt csharp++
11:45 Dyrcona csharp++ gmcharlt++
11:46 Dyrcona passwords-in-logfiles--
15:38 mmorgan name must also be unique
15:40 BAMkubasa thanks mmorgan
15:53 khuckins joined #evergreen
15:56 jeff also, at least in the XUL client changing the name of an existing duration rule (and max fine perhaps also?) can lead to errors when displaying circ data in item status. i don't think i've tested that in the web client.
15:56 jeff (we just avoided renaming them after discovering that a while ago)
16:02 jeff miker: we are using (a scaled down version of) friends in production here now.
16:03 jeff (going back to the "check out someone else's holds for them" conversation from... August or so)
16:03 Dyrcona :)
16:03 sandbergja joined #evergreen
16:06 BAMkubasa "can lead to errors when displaying circ data in item status" well, I suppose I'll be able to tell you for sure soon if the house burns down. I just went through and renamed all of ours to have consistent nomenclature in preparation for adding new ones for auto-renewal
16:10 * jeff nods
16:11 jeff the issue was viewing recent circs for an item where the action.circulation row had names of rules that no longer existed in the corresponding config.* tables.
16:12 jeff it was an annoying but non-fatal error message or two when viewing a recent circ that had a "former" rule name present.
16:16 * mmorgan was curious and so edited a duration rule name on a test system.
16:17 mmorgan I'm not seeing an error pop up in item status. I do see that the Duration Rule field in item status detail shows as blank after the rule is edited.
16:17 BAMkubasa BAMkubasa was foolhardy and edited them all on production
16:17 BAMkubasa :)
16:26 mmorgan BAMkubasa lives dangerously ;-)
19:00 sandbergja joined #evergreen
20:03 sandbergja joined #evergreen
22:07 sandbergja joined #evergreen
23:01 pinesol News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-11-06T23:00:54,100505946-0500 -0>
23:36 sandbergja joined #evergreen

Results for 2019-11-05

10:09 sandbergja joined #evergreen
10:46 cmalm_ joined #evergreen
10:58 sandbergja joined #evergreen
11:02 pinesol News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-11-05T11:00:47,494219474-0500 -0>
11:30 Christineb joined #evergreen
11:58 collum joined #evergreen
12:02 aabbee joined #evergreen
14:54 Christineb I think those might be missing from some versions
14:55 berick Christineb: are you/Mark setting the Record Type to Acq or Bib records?
14:56 Bmagic Is there a trick to it? We have a library who used the 3.1.10 Dojo interface to overlay the copies and it worked. Now, with 3.3 it doesn't
14:58 Bmagic fails silently. If you say it works, then there might be something wrong with the file. I will spend the time to run the scenario on a test machine and grep the logs at the fail point (if it's confirmed working for you)
15:00 csharp soooo, dev meeting? or are there not enough of us around today?
15:00 gmcharlt my inclination is to reboot it (the dev meeting) and reschedule for next week or the following week
15:01 * csharp agrees
20:06 cmalm_ joined #evergreen
20:49 sandbergja joined #evergreen
22:12 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-11-05T23:01:18,259796996-0500 -0>
23:26 sandbergja joined #evergreen

Results for 2019-11-04

10:30 alynn26 joined #evergreen
10:37 sandbergja_ joined #evergreen
10:44 jvwoolf joined #evergreen
11:02 pinesol News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-11-04T11:00:49,172469610-0500 -0>
11:18 Christineb joined #evergreen
11:46 devted berick: Looking at your new "Angular staff catalog 3.4 project docs update" wiki  page:
11:46 devted https://wiki.evergreen-ils.org/doku.php?i​d=dev:browser_staff:angular_staff_catalog
18:45 sandbergja_ joined #evergreen
19:05 sandbergja joined #evergreen
21:02 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-11-04T23:01:04,280402285-0500 -0>

Results for 2019-11-03

04:02 dickreckard joined #evergreen
11:01 pinesol News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-11-03T11:00:50,565415696-0500 -0>
12:46 sandbergja_ joined #evergreen
13:07 sandbergja__ joined #evergreen
17:19 sandbergja_ joined #evergreen
18:32 sandbergja_ joined #evergreen
20:21 sandbergja_ joined #evergreen
20:59 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-11-03T23:00:52,404926244-0500 -0>
23:41 sandbergja_ joined #evergreen

Results for 2019-11-02

04:19 haishu joined #evergreen
10:13 sandbergja_ joined #evergreen
10:52 haishu joined #evergreen
11:01 pinesol News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-11-02T11:00:50,064216516-0400 -0>
11:11 sandbergja_ joined #evergreen
11:51 haishu joined #evergreen
12:29 haishu joined #evergreen
14:48 haishu joined #evergreen
15:14 haishu joined #evergreen
16:24 sandbergja_ joined #evergreen
17:00 pinesol News from qatests: Failed Installing OpenSRF pre-requisites <http://testing.evergreen-ils.org/~l​ive/test.7.html#2019-11-02T16:47:44,856488290-0400 -0>
17:00 pinesol News from qatests: Failed Building OpenSRF <http://testing.evergreen-ils.org/~l​ive/test.9.html#2019-11-02T16:47:44,882936330-0400 -2>
17:00 pinesol News from qatests: Failed Running OpenSRF build tests <http://testing.evergreen-ils.org/~li​ve/test.10.html#2019-11-02T16:47:44,909810621-0400 -4>
17:00 pinesol News from qatests: Failed creating opensrf user and environment <http://testing.evergreen-ils.org/~li​ve/test.12.html#2019-11-02T16:47:44,936427686-0400 -6>
17:00 pinesol News from qatests: Failed configuring ejabberd <http://testing.evergreen-ils.org/~li​ve/test.15.html#2019-11-02T16:47:44,962970358-0400 -8>
17:00 pinesol News from qatests: Failed creating jabber users <http://testing.evergreen-ils.org/~li​ve/test.16.html#2019-11-02T16:47:44,989511137-0400 -10>
17:00 pinesol News from qatests: Failed configuring OpenSRF <http://testing.evergreen-ils.org/~li​ve/test.17.html#2019-11-02T16:47:45,016073489-0400 -12>
17:00 pinesol News from qatests: Failed start opensrf <http://testing.evergreen-ils.org/~li​ve/test.18.html#2019-11-02T16:47:45,042727156-0400 -14>
17:00 pinesol News from qatests: Failed stop opensrf <http://testing.evergreen-ils.org/~li​ve/test.19.html#2019-11-02T16:47:45,069158721-0400 -16>
17:00 pinesol News from qatests: Failed start opensrf <http://testing.evergreen-ils.org/~li​ve/test.20.html#2019-11-02T16:47:45,096066252-0400 -18>
17:00 pinesol News from qatests: Failed test opensrf <http://testing.evergreen-ils.org/~li​ve/test.21.html#2019-11-02T16:47:45,122674404-0400 -20>
17:00 pinesol News from qatests: Failed configuring websockets <http://testing.evergreen-ils.org/~li​ve/test.22.html#2019-11-02T16:47:45,149069869-0400 -22>
17:00 pinesol News from qatests: Failed stop opensrf <http://testing.evergreen-ils.org/~li​ve/test.23.html#2019-11-02T16:47:45,175347807-0400 -24>
17:00 pinesol News from qatests: Failed Installing Evergreen pre-requisites <http://testing.evergreen-ils.org/~li​ve/test.26.html#2019-11-02T16:47:45,201707844-0400 -26>
17:00 pinesol News from qatests: Failed Installing AngularJS web client - Expected 6 errors but encountered 7. <http://testing.evergreen-ils.org/~li​ve/test.28.html#2019-11-02T16:47:45,228136916-0400 -28>
17:00 pinesol News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-11-02T16:47:45,255064670-0400 -30>
17:00 pinesol News from qatests: Failed Building Evergreen <http://testing.evergreen-ils.org/~li​ve/test.30.html#2019-11-02T16:47:45,281373629-0400 -32>
17:00 pinesol News from qatests: Failed Running Evergreen tests <http://testing.evergreen-ils.org/~li​ve/test.31.html#2019-11-02T16:47:45,307649979-0400 -34>
17:00 pinesol News from qatests: Failed Installing Evergreen <http://testing.evergreen-ils.org/~li​ve/test.32.html#2019-11-02T16:47:45,334457385-0400 -36>
17:00 pinesol News from qatests: Failed Change File Ownership <http://testing.evergreen-ils.org/~li​ve/test.33.html#2019-11-02T16:47:45,361042906-0400 -38>
17:00 pinesol News from qatests: Failed Installing Dojo <http://testing.evergreen-ils.org/~li​ve/test.35.html#2019-11-02T16:47:45,387946469-0400 -40>
17:00 pinesol News from qatests: Failed configure apache <http://testing.evergreen-ils.org/~li​ve/test.36.html#2019-11-02T16:47:45,414694368-0400 -42>
17:00 pinesol News from qatests: Failed configure EG OpenSRF <http://testing.evergreen-ils.org/~li​ve/test.37.html#2019-11-02T16:47:45,441102263-0400 -44>
17:00 pinesol News from qatests: Failed configure EG Action/Trigger <http://testing.evergreen-ils.org/~li​ve/test.38.html#2019-11-02T16:47:45,467363740-0400 -46>
17:01 pinesol News from qatests: Failed Create Evergreen Database <http://testing.evergreen-ils.org/~li​ve/test.41.html#2019-11-02T16:47:45,494027527-0400 -48>
17:01 pinesol News from qatests: Failed Running pgTAP tests <http://testing.evergreen-ils.org/~li​ve/test.42.html#2019-11-02T16:47:45,520683723-0400 -50>
17:01 pinesol News from qatests: Failed start opensrf <http://testing.evergreen-ils.org/~li​ve/test.43.html#2019-11-02T16:47:45,547273560-0400 -52>
17:01 pinesol News from qatests: Failed Running autogen.sh <http://testing.evergreen-ils.org/~li​ve/test.44.html#2019-11-02T16:47:45,573966702-0400 -54>
17:01 pinesol News from qatests: Failed Restarting Apache - Expected 1 errors but encountered 2. <http://testing.evergreen-ils.org/~li​ve/test.45.html#2019-11-02T16:47:45,600498703-0400 -56>
17:01 pinesol News from qatests: Failed test EG opensrf <http://testing.evergreen-ils.org/~li​ve/test.46.html#2019-11-02T16:47:45,627155773-0400 -58>
17:01 pinesol News from qatests: Failed Running pgTAP live tests <http://testing.evergreen-ils.org/~li​ve/test.47.html#2019-11-02T16:47:45,654193088-0400 -60>
17:01 pinesol News from qatests: Failed Running settings-tester.pl <http://testing.evergreen-ils.org/~li​ve/test.48.html#2019-11-02T16:47:45,680723795-0400 -62>
17:01 pinesol News from qatests: Failed Running perl live tests <http://testing.evergreen-ils.org/~li​ve/test.49.html#2019-11-02T16:47:45,707536638-0400 -64>
17:01 pinesol News from qatests: Failed Gathering log summary <http://testing.evergreen-ils.org/~li​ve/test.50.html#2019-11-02T16:47:45,734281643-0400 -66>
17:01 pinesol News from qatests: Failed Log Output: config.log <http://testing.evergreen-ils.org/~li​ve/test.51.html#2019-11-02T16:47:45,761152831-0400 -68>
17:49 sandbergja_ joined #evergreen
18:20 sandbergja_ joined #evergreen
19:33 haishu joined #evergreen

Results for 2019-11-01

07:56 Dyrcona Well, disabling user triggers may have helped. I'm not sure. It's still going on an update of action.aged_circulation, which has no user triggers to disable IIRC.  I may have to disable all triggers to get a real performance boost.  I will try that next.
07:56 csharp Dyrcona: yeah - same here - it's still running (since 2pm yesterday)
07:56 csharp the action.circulation update completed, but it's still chewing on aged circ
07:58 Dyrcona Yeah, mine has been going about the same length of time. I'm going to disable all triggers on both tables for my next test when this one finishes.
08:05 Dyrcona I'm tempted to just stop this one and start over. I have more databases I can "break." :)
08:08 Dyrcona Mine had been going 18h 41m before I stopped it just now.
08:12 Dyrcona 'Cause, honestly, if it doesn't knock 6 or more hours off the run time, it's not worth it.
08:15 csharp oh - ok
08:16 Dyrcona I mean it's easier to report on true/false, versus true/false/null. :)
08:16 csharp makes sense
08:18 Dyrcona So, my next test has started on  an "optimized" 9.6 instance on my test db server.
08:21 csharp another factor in my situation is that my staging/testing DB is under-specced compared to production - a consequence of our new environment
08:21 csharp I can probably change it without trouble, but that comes with overhead
08:22 Dyrcona Well, I have 128GB of RAM and 6TB of spinning rust on my test db server. Production is 768GB of RAM and 1.3TB of NVMe SSD, mirrored in a ZFS pool. So, yeah, test is slower for me, too. :)
08:23 Dyrcona Not sure what the RAID is on the test db server. It's configured via hardware, and I never checked. The "joy" of leftover hardware.
08:23 csharp yeah
08:24 Dyrcona I put optimized in quotes, 'cause optimizing Postgres still feels like voodoo to me.
08:24 csharp it's definitely voodoo
09:57 csharp we just don't have any with autorenewal = true
10:23 Dyrcona Well, probably because of the other bug about aged circulation. We patched that already.
10:51 sandbergja joined #evergreen
11:02 pinesol News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-11-01T11:00:50,114348425-0400 -0>
11:23 csharp yeah 162M rows in aged_circulation... I will *not* be applying that update during the upgrade window
11:24 csharp paraphrasing Sonny in the Godfather: "Reports will just have to suffer!"
11:25 csharp and actually, I plan to run these in batches before the upgrade happens so it won't be an issue
21:37 sandbergja_ joined #evergreen
22:44 haishu joined #evergreen
22:48 sandbergja_ joined #evergreen
23:01 pinesol News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-11-01T23:01:06,384001843-0400 -0>
23:31 haishu joined #evergreen

Results for 2019-10-31

10:15 jvwoolf joined #evergreen
10:50 yboston joined #evergreen
11:00 jvwoolf joined #evergreen
11:02 pinesol News from qatests: Failed Installing AngularJS web client - Expected 6 errors but encountered 7. <http://testing.evergreen-ils.org/~li​ve/test.28.html#2019-10-31T11:00:53,501226777-0400 -0>
11:02 pinesol News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-10-31T11:00:53,543262504-0400 -2>
11:12 sandbergja joined #evergreen
11:42 jihpringle joined #evergreen
11:49 awitter joined #evergreen
12:45 Dyrcona :)
12:45 csharp UPDATE action.circulation SET auto_renewal = FALSE WHERE auto_renewal IS NULL; - still on that - next is aged circs which is way larger a table
12:45 csharp wondering if we can disable triggers somewhere before this is run?
12:45 Dyrcona Going from 3.2.4 to 3.2.8 with those updates takes about 22 hours on my test db server.
12:46 Dyrcona csharp: That's a good idea. I don't think anything depends on the values of those desk_renewal or auto_renewal fields trigger-wise.
12:46 csharp yeah - just thinking the same thing
12:47 csharp in other news it just got dark as night outside - methinks something wicked this way comes
12:51 JBoyer even better.
12:51 csharp JBoyer: I thought about that approach too - just doing it in advance of the upgrade
12:53 JBoyer Dyrcona, I can see that, if it will complete fast enough. GIven that there's precious little visibility to staff though (until after the update is finished anyway, Dyrcona++ for the IDL updates) I wouldn't let it keep me up very late, or services down very long.
12:54 Dyrcona We usually plan on things being down all night when we upgrade, but I'm going to look into disabling triggers and try it on a test db. I've got plenty of those to mess with. :)
12:57 csharp yeah, trying the disable triggers approach too right now
12:58 csharp I don't mind being down all night either, but without those updates, the 3.3-3.4 upgrade took me like 5 minutes running the scripts manually
12:58 Dyrcona I've identified 5 triggers.
19:15 cmalm joined #evergreen
19:56 sandbergja joined #evergreen
20:42 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-31T23:00:47,528691059-0400 -0>
23:27 sandbergja joined #evergreen

Results for 2019-10-30

10:13 yboston joined #evergreen
10:26 jvwoolf joined #evergreen
10:47 sandbergja joined #evergreen
11:02 pinesol News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-10-30T11:00:51,705085251-0400 -0>
11:03 berick [91m30 10 2019 04:43:51.445:ERROR [launcher]: [39mNo binary for ChromeHeadless browser on your platform.
11:03 berick Please, set "CHROME_BIN" env variable.
11:04 berick phasefx: ^--
11:05 berick L'Ubuntue
11:05 phasefx so do we actually need to install chromium?
11:06 phasefx or should we, rather?
11:06 berick phasefx: it should be installed w/ the makefile installer
11:06 berick just have to tell the test engine how to find it
11:06 phasefx berick++
11:06 JBoyer Currently the -developer target installs it, I need to add a -tester instead.
11:07 phasefx fwiw, the tester is calling the -developer target
11:13 JBoyer I'm surprised that not finding chromium could possibly cause ELIFECYCLE though. Usually it just runs the tests in firefox instead and goes on,
11:14 phasefx I'm going to fire off the installer now; we'll get one more RSS error, but I can inspect the  state of the vm then and look for chromium
11:15 JBoyer I am also fairly certain that Debian and L'Ubuntue use different filenames. The package names are different and I don't think Debian uses a -browser suffice
11:15 JBoyer suffix, either.
11:15 sandbergja joined #evergreen
11:16 phasefx but I can say chromium is in the package list when the tester gathers the list of installed packages (it used to be chromium-browser; I thought chromium was a game)
11:17 JBoyer It is a game, but I think Debian added a suffix to the game no one (statistically) installs, while Ubuntu went the opposite direction.
11:17 phasefx in that case.. https://packages.debian.org/st​retch/amd64/chromium/filelist says it should be /usr/bin/chromium
11:19 * phasefx aborted the install, http://testing.evergreen-ils.org/~live/ looks awesome :)
11:19 Dyrcona I was getting ELIFECYCLE the other day after updating node and doing npm install.
11:20 JBoyer phasefx, I don't suppose you totally blew away /usr/local/lib/node_modules and so on? that's what it took to un-stick one of my dev servers. :/
11:20 Dyrcona I had to blow the pre-existing Node installation away and reinstall the new one: https://pastebin.com/AXMCWyHC
11:22 JBoyer Ah, not that then. :)
11:22 Dyrcona Nope, guess not...
11:24 Dyrcona Chromium has been acting "strange" for me on Ubuntu 19.10 lately, but I haven't rebooted since I noticed it, just logged out and back in (for an unrelated reason).
11:31 phasefx alright, new test running with CHROME_BIN set
11:32 * phasefx should add an env dump at the end along with the installed debian and cpan packages
11:33 phasefx be funny if installing chromium unsets my CHROME_BIN :)
11:38 JBoyer Chrome was in, but now CHROME_BOUT
11:39 phasefx it's an ELF on a shelf
11:41 Dyrcona phasefx++
11:43 phasefx we are such nerds
11:43 Dyrcona Indeed!
11:44 Christineb joined #evergreen
11:44 Dyrcona Which reminds me to tell JBoyer that I wrote the C program to login via SIP2 and set it up as haproxy check program on my test system. I statically linked it because of the chroot.
11:48 JBoyer Dyrcona, not too lousy to track down the necessary libraries, eh?
11:50 Dyrcona Well, the sip2 login only requires libc...
11:52 Dyrcona The other programs in the chroot require about 38 libraries.
12:08 jihpringle joined #evergreen
12:10 khuckins joined #evergreen
12:12 nfBurton joined #evergreen
13:03 pinesol News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-10-30T12:49:55,792101429-0400 -0>
13:03 pinesol News from qatests: Failed Log Output: osrfsys.log - Expected 3 errors but encountered 6. <http://testing.evergreen-ils.org/~li​ve/test.76.html#2019-10-30T12:49:55,833819643-0400 -2>
13:46 jeffdavis I'm awed and a little frightened by the wide_hold_data SQL query: https://git.evergreen-ils.org/?p=Evergr​een.git;a=blob;f=Open-ILS/src/perlmods/​lib/OpenILS/Application/Storage/Publish​er/action.pm;h=213ed59e;hb=HEAD#l2155
13:46 Dyrcona :)
13:47 Dyrcona jeffdavis are you perchance chasing a bug where copies don't show up on the hold shelf that should?
13:47 mmorgan Heh.
13:47 jeffdavis yep, just testing that fix locally before putting in production
13:49 Dyrcona We've been running it in production for a few months.
13:52 jeffdavis yeah I'm not worried about it at all, just following local procedure - I expect we'll have it in prod tonight :)
14:20 miker jeffdavis: the fun thing is that the query is performant! :)
22:05 serflog joined #evergreen
22:05 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
22:13 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-30T23:00:46,869129834-0400 -0>
23:12 sandbergja joined #evergreen
23:44 sandbergja joined #evergreen

Results for 2019-10-29

10:13 berick mmorgan: yes
10:14 mmorgan berick++
10:14 mmorgan Thanks, we'll give it a try.
10:15 * JBoyer has that one in his sights. Even has one of those danged Dymos to finally properly test it.
10:21 berick note to self, rebase that one again post-Ang8
10:28 jwoodard joined #evergreen
11:02 pinesol News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-10-29T11:00:54,549210501-0400 -0>
11:08 yboston joined #evergreen
11:20 gmcharlt is anybody uploading translations to Launchpad at the moment?
11:21 gmcharlt I'm getting some notifications that Launchpad's Rosetta is complaining about some malformed POT files
16:22 Dyrcona Bmagic++
16:22 Dyrcona remingtron++
16:23 Bmagic dbwells++ remingtron++ sandbergja++
16:23 Bmagic JBoyer: where is that branch where you setup the FF and Chromium tests? Are you using selenium?
16:24 JBoyer Already in master, just using karma and the karma (browser)-launcher plugins
16:25 Bmagic ty
16:25 Dyrcona sandbergja++
21:39 sandbergja joined #evergreen
21:57 sandbergja joined #evergreen
22:47 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-29T23:00:59,932723625-0400 -0>
23:14 sandbergja joined #evergreen

Results for 2019-10-28

09:28 jvwoolf joined #evergreen
09:59 yboston joined #evergreen
10:00 mmorgan1 joined #evergreen
10:11 berick hoping someone can merge this to fix the Angular test failures:  https://git.evergreen-ils.org/?p=working/​Evergreen.git;a=shortlog;h=refs/heads/use​r/berick/lp1830973-ang8-test-spec-repair
10:11 berick tip commit
10:21 serflog joined #evergreen
10:21 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
10:23 phasefx_ berick: the other errors, should I hard-code exceptions for them?  with angularjs, ERROR LOG: [36m'Error loading shared worker', Event{isTrusted: true}[39m       And the osrfsys one, I think that's test output, that just wasn't reaching the logs preivously but now is (weird)
10:24 sandbergja joined #evergreen
10:24 berick phasefx_: looking..
10:25 * berick waits for the current test cycle to complete
10:26 berick oh duh, we have the history
10:26 phasefx_ berick: http://testing.evergreen-ils.org/~live/archi​ve/2019-10/2019-10-28_04:00:03/test.28.html
10:27 phasefx_ incidentally, the test cycle is probably finished, but ssh doesn't exit from the qa server for some reason; it just drops when the vm is re-created
10:29 berick phasefx_: yes I think we'll need exceptions for that.
10:29 phasefx_ berick: roger that
10:30 berick they don't affect the tests, just the browser trying to grab files that are not grabbable
10:30 * phasefx_ is having trouble testing npm run test on his dev server, problems with Firefox
10:34 phasefx_ berick: I'm just going to point the qa tester to your branch and run it through there, and then push depdning on that
10:34 phasefx_ sidestep my local problems
10:34 berick phasefx_: k, don't know if it matters but it's a bit behind master
10:34 berick i can rebase if you want
10:35 phasefx_ sounds good
10:35 jvwoolf joined #evergreen
10:35 berick k
10:36 berick phasefx_: done
10:36 phasefx_ berick++
10:49 phasefx_ new test is running, we'll probably get the RSS from the previous run shortly
10:51 phasefx or maybe not; that makes sense, since I started a new test so quickly after the refresh, there is no RSS at the moment
10:53 tlittle joined #evergreen
10:54 phasefx maybe one day we can have a farm of test servers, and a script that automatically grabs pullrequest branches and builds them
10:55 phasefx posts a pass/fail summary/tag to the ticket
10:59 dbs phasefx: yes - that would be like github + travis-ci, or gitlab and its built-in continuous integration. would be nice!
10:59 dbs (But as Dyrcona mentioned last time this was brought up, our complex setup might also make it very difficult)
11:00 * phasefx nods nods
11:00 dbs Can the Evergreen docker builds be pointed at arbitrary branches? That might be a way to accomplish the goal
11:01 Dyrcona I believe that they can be.
11:01 Dyrcona But, I'm in a meeting...
11:02 phasefx if not, just pristine debian dockers would do, and we can ssh a build/test script into them with a specific branch like we're doing now
11:02 Christineb joined #evergreen
11:03 phasefx well, not quite like we're doing now; right now I'm hard-coding the branch into eg_*_installer.sh, and we'd probably want that specified elsewhere in the stack
11:04 phasefx or..just use branches for the.. branches.  So we push installer_installer.sh onto pristine servers, and they do the checkout of eg_*_installer.sh script, but no reason they have to do that checkout from the eg_live_tests branch
11:05 phasefx at that point, the live tests might benefit from its own repo
11:06 phasefx or we bundle the installer/test scripts into Evergreen
11:08 pinesol [evergreen|Dan Wells] Translation updates - newpot - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=2f2d48c>
11:08 pinesol [evergreen|Dan Wells] Translation updates - po files - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=500a2a8>
11:08 dbs looking at the diffs for the mobius docker images to move to 3.4.0 as the base, seems like it has its own installer script: https://github.com/mcoia/eg-docker/commi​t/1d86bffefd097b10efb1a5545c96d3a1111a8e​8d#diff-2503b3e50722b93b27b9fd4dc0fa8b7f
11:11 dbs that's good! :)
11:12 dbs Bmagic++ # that docker setup looks like a ton of work, wow
11:13 Bmagic dbs++ # thanks
11:32 pinesol [evergreen|Bill Erickson] LP1830973 Angular 8 org family test spec repair - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=63f7c24>
11:32 phasefx berick: ha, the test run got to where your patch made a difference, looked good, and so I pushed to master, but now I see catastrophic failures floating by (I'm sure unrelated) and I'm like, "of course" :D
11:33 berick of course...
11:35 phasefx E: Failed to fetch http://ftp.us.debian.org/debian/pool/main/libg/l​ibgd-graph-perl/libgd-graph-perl_1.48-2_all.deb  Hash Sum mismatch
11:36 phasefx configure: error: *** yaz not found, aborting
11:37 phasefx why, yboston, why?
11:38 csharp :-)
11:38 berick @blame bad hash
11:38 pinesol berick: bad hash tests their code on the LIVE SERVERS, then blames the user. SAD!
11:39 csharp maybe build an apt-get update into Makefile.install?
11:40 phasefx csharp: in this case, eg_stretch_installer.sh is doing an apt-get update during the build_essentials step
11:40 csharp ah
11:44 rfrasur joined #evergreen
11:57 RFrasur_ joined #evergreen
12:02 mmorgan1 joined #evergreen
12:03 pinesol News from qatests: Failed Installing Evergreen pre-requisites <http://testing.evergreen-ils.org/~li​ve/test.26.html#2019-10-28T11:34:43,429577189-0400 -0>
12:03 pinesol News from qatests: Failed Installing AngularJS web client <http://testing.evergreen-ils.org/~li​ve/test.28.html#2019-10-28T11:34:43,455726414-0400 -2>
12:03 pinesol News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-10-28T11:34:43,482038377-0400 -4>
12:03 pinesol News from qatests: Failed Building Evergreen <http://testing.evergreen-ils.org/~li​ve/test.30.html#2019-10-28T11:34:43,508349985-0400 -6>
12:03 pinesol News from qatests: Failed Running Evergreen tests <http://testing.evergreen-ils.org/~li​ve/test.31.html#2019-10-28T11:34:43,534732576-0400 -8>
12:03 pinesol News from qatests: Failed Installing Evergreen <http://testing.evergreen-ils.org/~li​ve/test.32.html#2019-10-28T11:34:43,561138933-0400 -10>
12:03 pinesol News from qatests: Failed Installing Dojo <http://testing.evergreen-ils.org/~li​ve/test.35.html#2019-10-28T11:34:43,587376698-0400 -12>
12:03 pinesol News from qatests: Failed configure apache <http://testing.evergreen-ils.org/~li​ve/test.36.html#2019-10-28T11:34:43,613852629-0400 -14>
12:03 pinesol News from qatests: Failed configure EG Action/Trigger <http://testing.evergreen-ils.org/~li​ve/test.38.html#2019-10-28T11:34:43,640060414-0400 -16>
12:03 pinesol News from qatests: Failed Create Evergreen Database <http://testing.evergreen-ils.org/~li​ve/test.41.html#2019-10-28T11:34:43,666512618-0400 -18>
12:03 pinesol News from qatests: Failed Running pgTAP tests <http://testing.evergreen-ils.org/~li​ve/test.42.html#2019-10-28T11:34:43,692757602-0400 -20>
12:03 csharp d'oh
12:03 pinesol News from qatests: Failed Running autogen.sh <http://testing.evergreen-ils.org/~li​ve/test.44.html#2019-10-28T11:34:43,718986141-0400 -22>
12:03 pinesol News from qatests: Failed Running pgTAP live tests <http://testing.evergreen-ils.org/~li​ve/test.47.html#2019-10-28T11:34:43,745376591-0400 -24>
12:03 pinesol News from qatests: Failed Running settings-tester.pl <http://testing.evergreen-ils.org/~li​ve/test.48.html#2019-10-28T11:34:43,771672394-0400 -26>
12:03 pinesol News from qatests: Failed Running perl live tests <http://testing.evergreen-ils.org/~li​ve/test.49.html#2019-10-28T11:34:43,797887670-0400 -28>
12:03 pinesol News from qatests: Failed Log Output: srfsh.log <http://testing.evergreen-ils.org/~li​ve/test.58.html#2019-10-28T11:34:43,824191399-0400 -30>
12:04 csharp pinesol: shouldn't say "Failed" so much - bad for morale!
12:04 pinesol csharp: Sorry, we can't do that because, you know, SOFTWARE.
12:04 * phasefx could go back to the single success/fail RSS instead of itemized, but hopefully this would be rare
20:52 sandbergja joined #evergreen
21:11 sandbergja joined #evergreen
21:36 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-28T23:00:50,303670407-0400 -0>

Results for 2019-10-27

10:56 sandbergja joined #evergreen
11:01 Dyrcona joined #evergreen
11:02 Dyrcona So logout doesn't fix the screenshot thing, but turns out "Prt Scrn" is hard-coded to put screenshots in ~/Pictures and doesn't use the dconf-editor settings on Ubuntu.
11:02 pinesol News from qatests: Failed Installing AngularJS web client <http://testing.evergreen-ils.org/~li​ve/test.28.html#2019-10-27T11:00:46,763736987-0400 -0>
11:02 pinesol News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-10-27T11:00:46,810461335-0400 -2>
11:03 pinesol News from qatests: Failed Log Output: osrfsys.log <http://testing.evergreen-ils.org/~li​ve/test.76.html#2019-10-27T11:00:46,855304417-0400 -4>
11:03 Dyrcona Opening Screenshot manually doesn't seem to use the setting, either, but it remembers the last directory you used, so there's that.
11:04 Dyrcona This is relevant because the logout menu goes off-screen in the Angular 8 interfaces, and I took a screenshot to show it. I'll try it again, just to see if it was a one-time fluke.
12:33 bshum Dyrcona: Did you see berick put this in the logs a few days back - https://git.evergreen-ils.org/?p=working/​Evergreen.git;a=shortlog;h=refs/heads/use​r/berick/lp1830973-ang8-test-spec-repair
12:38 book`_ joined #evergreen
13:06 Dyrcona bshum: I don't recall, and I don't think it has anything to do with my situation, since a) I'm not running tests, and b) my problem occurred with npm install, i.e. before you can even get to running tests.
15:12 Dyrcona Yeahp. The npm install issue happened on another VM where I'm upgrading to latest master. I expect it will happen on all of them.
15:17 Dyrcona Here's a sed script to fix it: https://pastebin.com/Kkyv5Y51
15:19 csharp Dyrcona: gmcharlt recommended I do this when I had trouble upgrading to Angular 8: https://pastebin.com/W3Be8aXi
19:35 jonadab joined #evergreen
22:03 sandbergja joined #evergreen
22:52 sandbergja joined #evergreen
23:02 pinesol News from qatests: Failed Installing AngularJS web client <http://testing.evergreen-ils.org/~li​ve/test.28.html#2019-10-27T23:00:46,252703513-0400 -0>
23:03 pinesol News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-10-27T23:00:46,294677355-0400 -2>
23:03 pinesol News from qatests: Failed Log Output: osrfsys.log <http://testing.evergreen-ils.org/~li​ve/test.76.html#2019-10-27T23:00:46,336605195-0400 -4>

Results for 2019-10-26

00:47 sandbergja joined #evergreen
03:25 jvwoolf joined #evergreen
10:41 sandbergja joined #evergreen
11:01 pinesol News from qatests: Failed Installing AngularJS web client <http://testing.evergreen-ils.org/~li​ve/test.28.html#2019-10-26T11:00:46,503611372-0400 -0>
11:01 pinesol News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-10-26T11:00:46,546449989-0400 -2>
11:01 pinesol News from qatests: Failed Log Output: osrfsys.log <http://testing.evergreen-ils.org/~li​ve/test.76.html#2019-10-26T11:00:46,590494878-0400 -4>
13:14 sandbergja joined #evergreen
13:55 pinesol [evergreen|Remington Steed] Docs: Add 3.1.16 point release notes - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=f23217c>
13:55 pinesol [evergreen|Remington Steed] Docs: Add 3.2.10 point release notes - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=b7d9298>
13:55 pinesol [evergreen|Remington Steed] Docs: Add 3.3.5 point release notes - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=67a6d76>
13:55 pinesol [evergreen|Remington Steed] Docs: Adding 3.4.1 release notes - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=744aa58>
17:15 stephengwills left #evergreen
19:03 sandbergja joined #evergreen
21:55 sandbergja joined #evergreen
22:46 Jeff95 joined #evergreen
23:01 pinesol News from qatests: Failed Installing AngularJS web client <http://testing.evergreen-ils.org/~li​ve/test.28.html#2019-10-26T23:00:56,120502586-0400 -0>
23:01 pinesol News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-10-26T23:00:56,162590567-0400 -2>
23:01 pinesol News from qatests: Failed Log Output: osrfsys.log <http://testing.evergreen-ils.org/~li​ve/test.76.html#2019-10-26T23:00:56,204560612-0400 -4>
23:11 jonadab joined #evergreen

Results for 2019-10-25

09:43 jvwoolf joined #evergreen
09:53 sandbergja joined #evergreen
09:59 cmalm joined #evergreen
10:26 pinesol [evergreen|Dan Wells] LP#1846038 Remove extra grid refresh from configuration load - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=07b8435>
10:43 nfBurton joined #evergreen
10:45 sandbergja joined #evergreen
11:01 pinesol News from qatests: Failed Installing AngularJS web client <http://testing.evergreen-ils.org/~li​ve/test.28.html#2019-10-25T11:00:59,505794125-0400 -0>
11:01 pinesol News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-10-25T11:00:59,549875754-0400 -2>
11:01 pinesol News from qatests: Failed Log Output: osrfsys.log <http://testing.evergreen-ils.org/~li​ve/test.76.html#2019-10-25T11:00:59,592928695-0400 -4>
11:20 Dyrcona joined #evergreen
11:24 jvwoolf joined #evergreen
11:27 Christineb joined #evergreen
13:31 yboston joined #evergreen
14:17 Bmagic !!! cburton is right. That's what I was trying to think of. It's a year old now...
14:26 jvwoolf joined #evergreen
14:38 Bmagic is the "mark damaged" issue resolved where the Billing type doesn't include the "Damaged" billing type? Bug 1775425 is marked invalid and bug 1659181 is released but when testing 3.3.4, marking something damaged from the checkin screen doesn't give the damaged billing type
14:38 pinesol Launchpad bug 1775425 in Evergreen "when marking an item damaged/lost it does not give "damaged" or "lost" in the drop down for billing type." [Undecided,Invalid] https://launchpad.net/bugs/1775425
14:38 pinesol Launchpad bug 1659181 in Evergreen "webclient: Marking item damaged does not trigger prompt for billing details" [Medium,Fix released] https://launchpad.net/bugs/1659181
15:21 Bmagic Billing Type ID 7 should be "automatic" when marking something damaged but on my test system it's not selected in the dropdown and it's not even IN the dropdown. Can't find a bug about it which makes me think that I am doing something wrong
15:23 jeff I have seen similar in at least one system. I have it on my list to look into more.
15:58 Bmagic Was it decided somewhere along the timeline to remove the "auto" damaged billing type from the work flow and prompt the user to choose a custom billing type when marking damaged? It sure seems like there should be bug about this.
16:02 sandbergja_ joined #evergreen
20:54 sandbergja joined #evergreen
21:51 sandbergja joined #evergreen
22:14 sandbergja joined #evergreen
23:01 pinesol News from qatests: Failed Installing AngularJS web client <http://testing.evergreen-ils.org/~li​ve/test.28.html#2019-10-25T23:00:58,483085543-0400 -0>
23:01 pinesol News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-10-25T23:00:58,525467156-0400 -2>
23:01 pinesol News from qatests: Failed Log Output: osrfsys.log <http://testing.evergreen-ils.org/~li​ve/test.76.html#2019-10-25T23:00:58,570543567-0400 -4>
23:03 sandbergja joined #evergreen
23:39 sandbergja joined #evergreen

Results for 2019-10-24

10:44 dbs huh, the links for the qatests failures return a 404, is that a known issue?
10:48 collum joined #evergreen
10:48 sandbergja joined #evergreen
10:50 berick dbs: i think that happens if a test is in progress
10:51 collum joined #evergreen
10:56 dbs berick: ahh
11:00 jvwoolf joined #evergreen
11:01 pinesol News from qatests: Failed Installing AngularJS web client <http://testing.evergreen-ils.org/~li​ve/test.28.html#2019-10-24T11:00:47,985113758-0400 -0>
11:01 pinesol News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-10-24T11:00:48,026755118-0400 -2>
11:01 pinesol News from qatests: Failed Log Output: osrfsys.log <http://testing.evergreen-ils.org/~li​ve/test.76.html#2019-10-24T11:00:48,068169737-0400 -4>
11:01 collum_ joined #evergreen
11:02 collum__ joined #evergreen
11:02 Christineb joined #evergreen
11:02 berick I have a fix for the Angular test failures if someone could S/O and merge...
11:03 berick working/user/berick/lp1830​973-ang8-test-spec-repair
11:03 berick note the LP number references the (now-closed) angular 8 bug
11:19 Bmagic agoben++
11:26 stephengwills I’m converting MARC21 to MARCXML w/ the python script and hitting “UnicodeDecodeError: 'marc8_to_unicode' codec can't decode bytes in position 0-156: invalid multibyte character encoding”. is there a way to tell that script to skip the record it’s barfing on and keep processing the file, or is that a bad idea?
11:26 jeff "the python script"?
12:52 Dyrcona Do websockets return http status codes? (maybe I should look that up.)
12:57 JBoyer Dyrcona, maybe the upgrade response? Not sure if that's the initial response or only in response to certain types of request.
12:58 Dyrcona JBoyer: Thanks, but I found a simpler solution. I can tell haproxy to check a different port or even a different server, so I think if I tell it to check port 80, then websockets is down when http is down, which is good enough.
12:58 * Dyrcona is about to test that.
12:59 JBoyer That's how I've always done it in ldirector, yeah. :)
13:03 Dyrcona Yeah, it's working.
13:03 Dyrcona :)
14:21 remingtron awesome
14:22 nfBurton The working repo seems to be missing some npm modules? I haven't been able to build for the staff client. Is there a step
14:22 nfBurton I am missing?
14:23 jeff We've been using the Windows build of Hatch 0.3.2 from Comment 1 in bug 1830391. That installs without error on a 32 bit install of Windows, but then you have a Native Messaging Host that doesn't actually work (and "hatch.bat test" fails).
14:23 pinesol Launchpad bug 1830391 in Evergreen "Hatch omnibus circa 3.3 (Java updates and more)" [Undecided,New] https://launchpad.net/bugs/1830391
14:23 jeff I suspect that I can drop a 32 bit build of OpenJDK in place and it'll then work, but I haven't tested that theory.
14:23 Dyrcona Ok. So, I can connect to the websocket port, but it just hangs.  If I do a HEAD request, I get a 405, which may be good enough.
14:38 berick jeff: let me know how it goes...
14:38 berick perhaps we'll need 2 windows installers
15:14 pinesol nfBurton: [evergreen|Jason Boyer] Stamp upgrade script for LP 1849152 - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=11868e9>
15:20 jeff nfBurton: okay, that matches current master. anything in apache logs when you get the 500 error?
15:23 JBoyer Dyrcona, I'm just noticing your "-developer doesn't install that much..." I added chromium and firefox to that recently, though now that we're discussing it, maybe there should be a -tester target for those... (they're for replacing PhantomJS)
15:24 Dyrcona Yes, there should probably be a -tester or -testing target.
15:24 Dyrcona Or, they could go under -packager, since that's about the only time tests are run other than on the test server.
15:26 JBoyer I suppose we could also expand that target out to include things like pgtap and other things...
15:26 dbs Aren't commit reviewers / signers-off supposed to run tests?
15:27 dbs I guess if we had a travis-ci environment or the like that tested every branch every time they were pushed, that would help alleviate the burden of running tests
15:27 jeff the machine i do dev on isn't always the machine i run tests on.
15:27 jeff but yes, better/easier CI is also a nice goal.
15:28 Dyrcona dbs: I really doubt they do every time, and most new bugs are not caught by the tests. We've also been lax in adding tests.
15:29 Dyrcona gitlab has CI. github has CI.
15:30 Dyrcona I imagine CI for us would be  not so much fun to set up, given how eclectic our codebase is.
15:31 nfBurton @jeff egweb: Context Loader error: Can't locate object method "content" via package "OpenSRF::DomainObject::oilsMethodException"
16:35 nfBurton xenial 16.04
16:36 * jeff attempts to think of creative ways to tie a staff search to a staff user from potentially incomplete logs
16:37 JBoyer incomplete how?
16:38 jeff on the test box in question, i'm pretty sure that some things (at least "gateway" logs) are not being saved.
16:38 jeff (an oversight, not intentional)
16:39 Dyrcona nfBurton: Never mind. What I was thinking of only applies to Debian Stretch and Debian Buster.
16:39 JBoyer Ah, I thought you meant something like rate-limited drops or very short retention periods, etc. So long as you have everything normally in osrfsys.* you've got a connection from username to authtoken.
16:40 jeff yeah, I'm just not sure I've a link from "this search" to "this auth token"
20:11 sandbergja joined #evergreen
22:33 sandbergja joined #evergreen
22:56 jvwoolf joined #evergreen
23:01 pinesol News from qatests: Failed Installing AngularJS web client <http://testing.evergreen-ils.org/~li​ve/test.28.html#2019-10-24T23:00:48,595715594-0400 -0>
23:01 pinesol News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-10-24T23:00:48,642897535-0400 -2>
23:01 pinesol News from qatests: Failed Log Output: osrfsys.log <http://testing.evergreen-ils.org/~li​ve/test.76.html#2019-10-24T23:00:48,690042733-0400 -4>
23:17 sandbergja joined #evergreen

Results for 2019-10-23

07:42 agoben joined #evergreen
08:12 Dyrcona joined #evergreen
08:31 bos20k joined #evergreen
08:32 pinesol News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-10-23T08:04:48,553808689-0400 -0>
08:32 pinesol News from qatests: Failed Log Output: osrfsys.log <http://testing.evergreen-ils.org/~li​ve/test.76.html#2019-10-23T08:04:48,597859892-0400 -2>
08:54 mmorgan joined #evergreen
09:00 tlittle joined #evergreen
09:08 jvwoolf joined #evergreen
09:10 pinesol [evergreen|Bill Erickson] LP1849372 Close all open dialogs on Angular route change - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=2309b60>
09:15 terranm joined #evergreen
09:24 cmalm joined #evergreen
09:24 JBoyer Dyrcona, dbs, depending on what kind of issues you were having yesterday you might have to remove all of /usr/local/lib/node_modules and start fresh. (IF you were trying to work with a post-Angular 8 branch)
09:25 * Dyrcona had no issues yesterday, but that's good to know. I plan to try the upgrade steps this week.
09:25 JBoyer And I've got a branch out there to ditch PhantomJS and test our Angular(JS) code with both of our supported browsers rather than just an old version of one of them. Just can't reasonably do it as part of a production install like we used to.
09:41 stephengwills joined #evergreen
09:42 pinesol [evergreen|Terran McCanna] LP#1806783 Offline: Non-cataloged item receipt printing - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=0581bbf>
09:50 yboston joined #evergreen
10:44 gmcharlt I was allowed access to a slide deck generator == there were cats on it
10:44 gmcharlt ;)
10:44 mmorgan What a surpise ;-)
10:46 dbs I'll open a bug for https://git.evergreen-ils.org/?p=work​ing/Evergreen.git;a=shortlog;h=refs/h​eads/user/dbs/docs_remove_node_source so we can (maybe) add it ot the hack-a-way list of bugs fixed
10:51 dbs Stompro: in my case I was testing against 3.4.0, so pre-Angular8 (and the problem with tests was only with the AngularJS portion)
10:54 Stompro ? dbs - I think you tagged me by accident.
10:55 dbs Stompro: oh damnit, I meant JBoyer -- sorry!
10:55 agoben jeff: I'll be converting all the videos and shipping them tomorrow.
11:06 dluch agoben++
11:08 dluch I think this co-release manager/mentor idea is a good one.  Makes it easier for new folks to have a path in to that sort of thing.
11:10 dluch Which gets to the point of what I was assuming gmcharlt's presentation yesterday was about, increasing involvement
11:11 JBoyer We definitely need to remove the "install the latest..." from that doc, but removing the tests (or rather, making them optional at install time) has been changed here: https://git.evergreen-ils.org/?p=working​/Evergreen.git;a=shortlog;h=refs/heads/u​ser/jboyer/lp1845693-chrome-ang-testing
11:11 jihpringle joined #evergreen
11:11 JBoyer I'm certainly open for alternative ways to word / deal with that though.
11:23 pinesol News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-10-23T11:00:51,858757731-0400 -0>
11:23 pinesol News from qatests: Failed Log Output: osrfsys.log <http://testing.evergreen-ils.org/~li​ve/test.76.html#2019-10-23T11:00:51,900121137-0400 -2>
11:27 dbs JBoyer: looks good enough - could just apply the first commit in my branch to remove the "install the latest" verbiage
11:28 dbs also, JBoyer++ # nice branch
11:32 sandbergja joined #evergreen
11:41 JBoyer gmcharlt++
11:41 JBoyer dbs++
11:56 * JBoyer claims 1196 for wild christmas themed opac buttons
11:58 pinesol [evergreen|Jason Boyer] LP1845693: Test Angular(JS) with modern browsers - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=038227c>
11:58 pinesol [evergreen|Dan Scott] LP#1849506: Remove "Install latest LTS node from source" docs - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=f88df97>
11:58 pinesol [evergreen|Galen Charlton] LP#1845693: (follow-up) clarify what CHROME_BIN should be set to - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=d6a9ed4>
12:06 yboston joined #evergreen
12:06 pinesol [evergreen|Rogan Hamby] loading custom css from library setting - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=485624d>
12:06 pinesol [evergreen|Jason Boyer] Stamp upgrade script for LP 1849152 - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=11868e9>
12:19 jeff should that be behind a more restrictive update permission by default?
12:20 jeff would that be a new bug now that the original is committed?
12:37 rhamby jeff: the css?
20:17 book` joined #evergreen
21:10 sandbergja joined #evergreen
21:25 sandbergja joined #evergreen
23:01 pinesol News from qatests: Failed Installing AngularJS web client <http://testing.evergreen-ils.org/~li​ve/test.28.html#2019-10-23T23:00:52,490855211-0400 -0>
23:01 pinesol News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-10-23T23:00:52,534139946-0400 -2>
23:01 pinesol News from qatests: Failed Log Output: osrfsys.log <http://testing.evergreen-ils.org/~li​ve/test.76.html#2019-10-23T23:00:52,578055607-0400 -4>
23:06 sandbergja joined #evergreen
23:33 Bmagic The hack-away was awesome!!! Thanks everyone! Landed in MO just now!
23:36 devted Yes, it was a really fun few days! Thanks everyone

Results for 2019-10-22

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:54 agoben Glad you can still get on, but frustrating news.
12:54 Dyrcona It's probably a configuration in Chromium thing.
12:54 agoben mmhmm
12:56 sandbergja berick: I think that the whenStable() business might have been autogenerated.  I don't believe they serve any purpose
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
16:47 bshum I know our Node version we checkout is pretty ancient
16:48 bshum For the makefile anyways
16:48 bshum Too new and stuff tends to break
16:48 dbs "npm build prod" was fine but "npm run test" fails due to PhantomJS (I seem to recall that being a known issue)
16:48 dbs This in on Ubuntu Xenial. I'm just following the docs, which tell people to download and use Node LTS
16:49 dbs (https://evergreen-ils.org/documentat​ion/install/README_3_4_0.html#_insta​ll_dependencies_for_web_staff_client)
16:50 bshum I guess that's a bad instruction :)
16:50 bshum We put the specific Node version in the makefile prereqs awhile ago
16:50 bshum Though we should have bumped that a few times ago
16:51 pinesol Launchpad bug 1849372 in Evergreen 3.4 "angular: modals do not automatically close when navigating away from pages" [Medium,Confirmed] https://launchpad.net/bugs/1849372
16:51 dbs ah the advantage of fresh eyes :)
16:51 abowling joined #evergreen
16:51 Dyrcona dbs: I almost never run the tests, and either do node programmers.:)
16:52 bshum dbs: I probably just didn't notice because I ran the "optional developer additions" options during my read-through
16:52 bshum And it tells me to skip that step if I do :D
16:52 abowling joined #evergreen
16:53 * bshum needs more newbies around to keep us honest
16:53 Dyrcona The latest node lts is probably too new for us.
16:53 bshum It definitely is
16:53 JBoyer all of this talk about tests has me thinking about lp 1845693
16:53 pinesol Launchpad bug 1845693 in Evergreen "Replacement needed for PhantomJS" [Undecided,New] https://launchpad.net/bugs/1845693
16:54 bshum Or it was...
16:54 bshum Hmm
16:55 Dyrcona I installed that today, but didn't notice the node version.
16:56 bshum "That's what you get for missing staff meetings, Doctor."
16:56 Dyrcona :)
16:56 dbs So I guess we should get rid of the docs that tell people to manually install node and run tests?
16:56 Dyrcona I was at that meeying.
16:56 Dyrcona dbs: Yes.
16:57 abowling joined #evergreen
16:58 abowling joined #evergreen
17:00 abowling joined #evergreen
17:01 bshum dbs++ # testing the docs
17:02 Dyrcona dbs++
17:04 abowling joined #evergreen
17:10 abowling_ joined #evergreen
17:24 Dyrcona It is probably too new for 3.4 or earlier, though. I have seen that before where upgrading Node and/or npm breaks the installation.
17:24 dbs Dyrcona++
17:25 Dyrcona So, to get the preferred Node for your release of Evergreen use the {distro}-developer prerequisite install step if you're installing from git.
17:26 dbs Right - that's pretty much what I was cutting the branch down to
17:27 dbs Weirdly, on 3.4 I seem to be able to run tests with PhantomJS on the /src/eg2/ dir but not on the /web/js/ui/default/staff/ dir
17:35 dbs Took the minimalist step first to just remove the "install latest LTS node from source" instruction as I'm not 100% confident about the eg2 vs. web/js/ui test situation
17:35 dbs https://git.evergreen-ils.org/?p=work​ing/Evergreen.git;a=shortlog;h=refs/h​eads/user/dbs/docs_remove_node_source
17:36 Dyrcona dbs: PhantomJS is out of date and no loneger maintained.  There are some recent JS constructs that it can't process, and I think one or two have slipped into the AngularJS code.
17:37 Dyrcona I briefly considered taking over the project to update it, but after about half an hour of looking into it, I decided that it would be more work than I'm able to take on right now.
17:41 dbs Right, I get that. I just hate taking out instructions to run tests if they work (which they seem to for /src/eg2/ for some reason)
17:42 dbs But if everyone runs into test failures with /web/js/ui/default/staff then we should stop telling people to test. I just wasn't sure if that was the actual state of things.
17:42 dbs I'll add another commit that removes the "npm run test" steps and related verbiage
17:46 dbs Updated the branch accordingly
20:54 sandbergja joined #evergreen
21:26 sandbergja joined #evergreen
21:40 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-22T23:00:56,173131253-0400 -0>
23:03 pinesol News from qatests: Failed Log Output: osrfsys.log <http://testing.evergreen-ils.org/~li​ve/test.76.html#2019-10-22T23:00:56,214485939-0400 -2>
23:13 sandbergja joined #evergreen
23:53 sandbergja joined #evergreen

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