Evergreen ILS Website

Search in #evergreen

Channels | #evergreen index




Results

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

Results for 2015-05-20

00:35 jihpringle joined #evergreen
04:02 gsams joined #evergreen
05:17 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
07:22 graced joined #evergreen
07:27 jboyer-isl joined #evergreen
07:50 rjackson_isl joined #evergreen
10:37 bshum We get a network failure
10:37 bshum Can't call method \"id\" on an undefined value at /usr/local/share/perl/5.14.2/Open​ILS/Application/Circ/Circulate.pm line 2536.
10:38 bshum Looking at that line in Circulate.pm, I find that it's attempting something with the dont_change_lost_zero
10:38 jeff can you reproduce on a test system and try with and without that setting enabled?
10:39 Bmagic When we migrate lost items, we make the status "missing"
10:39 bshum jeff: I'll see if I can find the same item in our test system.  Not sure if it's synced enough
10:40 Dyrcona bshum: I believe the key is in your 3rd line.

Results for 2015-05-19

02:49 Callender_ joined #evergreen
04:57 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
07:40 sarabee joined #evergreen
07:48 jboyer-isl joined #evergreen
08:00 mrpeters joined #evergreen
08:52 ericar_ joined #evergreen
09:01 jwoodard joined #evergreen
09:11 Newziky joined #evergreen
09:12 csharp eeevil: I definitely see a difference post-fix for bug 1438136 on my test server (http://next.gapines.org), but when I applied it to PINES production just now, I'm still seeing long-running queries - I'll try and dig up a core query and EXPLAIN ANALYZE it
09:12 pinesol_green Launchpad bug 1438136 in Evergreen "OPAC searching significantly slowed by adding format filters" (affected: 1, heat: 6) [High,New] https://launchpad.net/bugs/1438136
09:14 montgoc1 joined #evergreen
09:17 maryj joined #evergreen

Results for 2015-05-18

11:23 Bmagic I wonder if the order needs to specify the system in order for the query to identify the shelving ID
11:24 tsbere Dunno.
11:24 tsbere Can't even speculate at this point. ;)
11:58 berick Bmagic: csharp: fyi, pushed more fixes to bug 1373690 (edi template).  thanks again for all the testing
11:58 pinesol_green Launchpad bug 1373690 in Evergreen "Direct EDI generation for ACQ orders -- AKA kill ruby webrick" (affected: 1, heat: 8) [Undecided,New] https://launchpad.net/bugs/1373690 - Assigned to Bill Erickson (berick)
12:01 kmlussier Webby is very slow this morning. Is work being done on it?
12:02 phasefx kmlussier: don't think so
12:16 phasefx seems to be okay to me; running to lunch :)
12:18 csharp well, the biggest problem with branch level copy locations I've seen is that, when combined with system-level cataloging, the copies can end up belonging to another branch's location (when locations are named the same across branches) - but that's fixed in bug 778989
12:18 pinesol_green Launchpad bug 778989 in Evergreen "Owning lib of asset.copy_location not visible in Item Attributes Editor UI" (affected: 3, heat: 16) [Medium,Fix released] https://launchpad.net/bugs/778989
12:27 csharp berick: I'm afraid I'm going to have to wait for Leslie to get back to test correctly - I don't want to risk placing actual orders and confusing people because I don't know what I'm doing :-/
12:27 csharp but that said,
12:27 csharp berick++
12:28 sandbergja joined #evergreen
12:31 kmlussier phasefx: Works now. Thanks!
12:31 kmlussier phasefx++
14:52 csharp Bmagic++
14:54 Bmagic gotta stop giving me karma, it's gonna get destroyed, lol
14:54 berick hah
14:54 Bmagic let's do all this EDI testing after the karmapocolypse
14:58 * berick promises to manually carry over Bmagic's EDI karma
14:58 Bmagic haha, I'm just kidding, I dont care
14:58 berick ok, down to the last (obvious) problem.  fixing..
15:48 bshum https://bugs.launchpad.net/bugs/1456289 - if memory serves, Bmagic and I saw this on 2.7 too, and it's cause autogen.sh wasn't run on the system with apache restarted
15:48 pinesol_green Launchpad bug 1456289 in Evergreen "Tpac "edit" link on record screen does not save changes" (affected: 1, heat: 6) [Undecided,New]
15:49 kmlussier Ah! I recall that one.
15:50 bshum I'll put a note on the bug to that effect I guess
15:50 bshum And we can probably close it with invalid.
16:01 bshum gmcharlt: eeevil: mllewynn tells me that the vandelay loader for web client works fine (we tested it on our test server).
16:01 bshum She also says that the flat text editor doesn't stay as the default option when opening additional records (aka, remain checked)
16:01 bshum But otherwise, the sprint2 stuff so far, so good
16:06 Bmagic berick: 2.7.0
16:07 mrpeters left #evergreen
16:08 berick Bmagic: thanks
16:14 tsbere Basically a single-machine brick
16:14 tsbere I can't even see an *attempt* at making the call in the server logs.
16:16 berick seems like the CONNECT is failing / not returning, so the .begin is never attempted
16:17 jeff tsbere: what specific pcrud-based interface(s) are you testing with?
16:18 tsbere Parts creation. Apparently from any interface you can create parts.
16:22 bshum Parts... sigh.
16:33 * tsbere glares at the javascript console of the staff client and the lineless "Transaction begin error" that tells him nothing about which of the four possible points that is generated did so
16:44 * tsbere glares even more as now everything is working
16:44 tsbere and nobody changed anything. I have just been trying to find logs.
17:07 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
17:10 ldwhalen joined #evergreen
17:12 mmorgan left #evergreen
17:26 ldwhalen joined #evergreen

Results for 2015-05-17

02:43 bshum Also, pie is awesome.
03:27 jeff pie++
03:27 jeff cruft--
05:08 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
07:25 jeff landed at ORD.
12:49 pinesol_green [evergreen|Jane Sandberg] Docs: Added hard due dates docs - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=9d88f62>
15:05 tsbere joined #evergreen
16:50 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
16:58 Carson joined #evergreen
18:11 Carson left #evergreen
21:21 dcook joined #evergreen

Results for 2015-05-15

15:46 abowling left #evergreen
15:49 collum joined #evergreen
16:48 pgardella joined #evergreen
17:04 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
17:23 mmorgan left #evergreen
17:23 collum joined #evergreen
17:35 graced joined #evergreen

Results for 2015-05-14

00:33 kmlussier berick: For the list of first-time contributors during the State of Evergreen tomorrow, I think at least one of the doc commits today came from a first-time contributor.
02:18 bshum parts++ # omg what????
02:20 kmlussier This is what happens when bshum starts drinking at the eg conference.
05:07 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
07:30 gsams joined #evergreen
08:40 mmorgan joined #evergreen
08:45 mrpeters joined #evergreen

Results for 2015-05-13

01:16 tsbere_ joined #evergreen
01:18 tsadok joined #evergreen
01:19 ningalls__ joined #evergreen
04:53 pinesol_green` Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
07:24 mrpeters joined #evergreen
07:50 TaraC joined #evergreen
08:00 rjackson_isl joined #evergreen
13:27 sandbergja joined #evergreen
13:29 bbqben joined #evergreen
13:30 kmlussier Shared Google Doc for notes on QA discussion https://docs.google.com/document/d/1i4RnCl7klNPf​7cCC9ZK0c13dt6dwYLs7238pSptrurQ/edit?usp=sharing
13:44 ldw I have a pgTap test here does not rely on in db data to test: http://git.evergreen-ils.org/?p=working/Evergreen​.git;a=blob;f=Open-ILS/src/sql/Pg/t/acq_fund_amou​nt_test.pg;h=8eb37ca45a8a6adb2ff75f19e38ac5d8d7ae​8946;hb=5ef37d6bb5d17b06ac5b00f8a11973c0db423e38
13:47 Dyrcona joined #evergreen
13:49 Dyrcona Grabbing 0917
13:55 buzzy joined #evergreen
13:58 pinesol_green` [evergreen|Galen Charlton] LP#800706: add index to serial.record_entry.record - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=b6e9559>
13:58 pinesol_green` [evergreen|Galen Charlton] LP#800706: add regression test - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=4ad53f4>
13:58 pinesol_green` [evergreen|Jason Stephenson] LP#800706: Stamping upgrade script - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=aca6cb9>
13:59 csharp @blame add $who stole bshum's tux doll!
13:59 pinesol_green csharp: The operation succeeded.  Blame #19 added.
14:00 Dyrcona @blame 19 csharp
14:06 sandbergja yboston: thanks so much!
14:15 nuentoter joined #evergreen
14:16 Dyrcona ldw++
14:16 csharp PINES testing checklists link from this page: http://pines.georgialibraries.org/upgrade-2.7
14:17 RoganH joined #evergreen
14:19 nuentoter joined #evergreen
14:22 Dyrcona fixing_four_year_old_bugs++

Results for 2015-05-12

17:03 abowling left #evergreen
17:04 Stompro_home eeevil, he might be a little late getting back to pdx, he just dropped of jeff and I around 1:45, we waited until 12:30 to depart to see if the 3rd person signed up was going to show up.
17:09 mmorgan left #evergreen
17:11 pinesol_green` Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
17:26 eeevil Stompro_home: thanks!
18:47 dkyle_ joined #evergreen
19:12 buzzy joined #evergreen

Results for 2015-05-11

05:14 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
07:30 graced joined #evergreen
07:55 rjackson_isl joined #evergreen
08:30 ericar joined #evergreen
16:55 * kmlussier checks
16:56 csharp joined #evergreen
16:56 kmlussier berick: I usually update http://wiki.evergreen-ils.org/doku​.php?id=contributing:contributors. There are a few more names there over the past year, but a couple may have been late-adds.
16:56 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
16:57 Stompro csharp, I would like to help with the debian packaging work, I saw you added that to the dev hackfest page of proposals.
16:57 csharp Stompro++ # awesome!  I'm excited to hear that
16:58 Stompro It looks like there are only 3 cpan modules left, Business::OnlinePayment::Paypal, Business::Stripe and Class::DBI::Frozen::301... I've been reading up on debian perl packaging, I wonder if packaging needed bugs have been filed for those 3 yet?

Results for 2015-05-10

04:59 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
07:13 gsams joined #evergreen
07:43 Stompro_home joined #evergreen
08:12 Stompro_home joined #evergreen

Results for 2015-05-09

16:26 bmills joined #evergreen
17:04 Stompro_home joined #evergreen
17:09 bmills joined #evergreen
17:17 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
17:33 book` joined #evergreen
17:45 abhi_ joined #evergreen
17:46 abhi_ hi

Results for 2015-05-08

16:45 bmills1 joined #evergreen
16:52 Stompro My wife just told me I just missed a call from "Microsoft" looking to update my computer, I love talking to those guys, I'm sad I missed it.
16:59 mmorgan Oh, those "Microsoft" guys really annoy me.
17:02 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
17:06 buzzy soon ... https://twitter.com/Evergreen​ILS/status/596782856396869632
17:07 Stompro buzzy++, first use of the #evgils15 tag, I've been waiting for it to turn up.
17:10 kmlussier I've opened up voting for which cookies I should make for the MassLNC development partners. More details here https://plus.google.com/+Kat​hyLussier/posts/PCk6Ya3Zivs
23:13 bshum Once we package new maintenance releases later this month, I expect that it'll be smoother sailing for installation on Debian Jessie.
23:15 nuentoter ok
23:15 nuentoter so for me to have a better installation experience right now would you recommend wheezy?
23:16 bshum nuentoter: For Debian, yes, I believe Wheezy has been better tested by different folks who use Debian.
23:16 bshum I personally use Ubuntu primarily.  So I'll caveat that I've only lightly tested Debians.
23:16 bshum Though I know others can speak for Debian
23:17 nuentoter most of my linux experience up until now has only been for very basic things on someones computer running crunchbang which is slick but technical
23:17 nuentoter i used ubuntu for a few years about 6-7 years ago for work
23:25 nuentoter ok so tonight i shall download wheezy and resume working on installing of jessie after you folks update

Results for 2015-05-07

05:04 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
07:12 kmlussier Good morning #evergreen
07:30 graced joined #evergreen
07:35 jboyer-isl joined #evergreen
10:45 kmlussier Ah, I forgot about that bug.
10:46 bshum kmlussier: These bugs haunt my dreams.
10:46 jwoodard NTLC aka North Texas Library Consortium in case everyone cannot read my mind or auto guess acronyms ;)
10:46 bshum jwoodard: I've had some passing familiarity with NTLC ;)
10:55 akilsdonk joined #evergreen
10:56 bshum jwoodard: So my recommendation is to mention the issue up your chain of support, and see if they can test your bib/item and see if there are problems with the reingest on that record.
10:57 bshum Something like: SELECT COUNT(*) FROM biblio.record_entry WHERE deleted = FALSE AND id NOT IN (SELECT source FROM metabib.record_attr_vector_list);
10:57 bshum Would tell you how many bibs (which are not deleted) do not have a proper corresponding metabib.record_attr_vector_list entry
10:58 bshum I just ran that on our systems and came up with 13 bibs, which makes me a little sad.
10:58 csharp yay! 0 in PINES
10:59 * csharp fully expected to see more than 0
10:59 bshum csharp: Amazing!
11:02 bshum In case you wanted the exact bib IDs for those missing entries
11:02 mmorgan bshum++
11:03 bshum mmorgan: Yeah, if you follow rjackson_isl's steps in his comment on that bug for a post-2.6 system, you can repair those missing entries.
11:03 berick csharp: have you done any additional testing on EDI since your last comments in bug #1342227 ?
11:03 pinesol_green Launchpad bug 1342227 in Evergreen "Setting up EDI Fails with Ruby version > 1.8" (affected: 2, heat: 14) [Undecided,New] https://launchpad.net/bugs/1342227
11:04 jwoodard bshum: Already sent an email. Proper training and database access are one of the many thing on my list of things to accomplish.
11:04 jwoodard bshum++  kmlussier++
11:15 jeff but i think it's pretty rare. we have two.
11:16 * bshum thanksfully has 0
11:16 bshum And I'll go back to blissfully not thinking about billing weirdness.
11:17 csharp berick: no - I didn't put together a good way to test on the stock EG master machine I was on
11:17 csharp berick: I was able to see the daemon running, though
11:18 mmorgan Whew! we have 0 for jeff's query :)
11:19 sarabee joined #evergreen
11:20 csharp 0 for jeff's query here too

Results for 2015-05-05

11:22 sandbergja joined #evergreen
11:31 buzzy joined #evergreen
11:52 kitteh_ joined #evergreen
11:54 yboston Hello everyone, DIG will need access to a test server running 2.8.x, I suspect we may be able to use webby? Any other recommendations?
11:55 tsbere yboston: kmlussier may be willing to spin up one of the masslnc test boxes for ya, though those don't get the web client going currently.
11:55 yboston tsbere: thanks
11:56 kmlussier yboston: The server on the community servers page already has 2.8. But, as tsbere said, it doesn't have webby.
11:56 kmlussier I usually use webby for web client docs.
14:30 dbs https://bugs.launchpad.net/evergreen/+bug/1031335 I think?
14:30 pinesol_green Launchpad bug 1031335 in Evergreen 2.7 "Email templates should always escape headers" (affected: 2, heat: 10) [Undecided,Confirmed]
14:32 dbs tsbere: around, but not in a headspace to recall or revisit library/copy ranking design decisions very effectively
14:47 mmorgan Anyone around to poke webby? I was hoping to test a few things, but can't login :-(
14:58 mmorgan Hey, webby's back! Thanks to whoever poked!
14:58 eeevil mmorgan: the drive's filled up, I'm looking for places to free space now
14:58 eeevil it'll die before too long ;)
14:59 mmorgan Aww. That's sad :-(
14:59 bshum Like a balloon inflating till it explodes.
14:59 bshum *pop*
15:01 mmorgan When dev servers get endearing names like 'webby', it's sad when they go away.
15:03 berick mmorgan: wait til you're testing on "widdlepuppy"
15:05 mmorgan widdlepuppy? I can't stand it! ;-)
15:14 eeevil mmorgan: ok, it should stay up for a while, cleared about 500MB. we'll look at increasing space generally soon
15:15 mmorgan eeevil++
16:36 mrpeters left #evergreen
16:45 vlewis joined #evergreen
17:00 mmorgan left #evergreen
17:07 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
17:23 Newziky left #evergreen
17:43 bmills1 joined #evergreen
20:08 nuentoter joined #evergreen

Results for 2015-05-04

00:08 sarabee joined #evergreen
05:09 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
07:42 ericar joined #evergreen
07:51 graced joined #evergreen
07:55 jboyer-isl joined #evergreen
09:30 bshum Though I'm unsure if maybe there were weird permission issue or something.
09:31 Dyrcona Well, I got several errors about stuff not being installed/not able to be opened without the sudo.
09:31 Dyrcona With sudo, it just worked.
09:31 bshum You testing with Ubuntu 12.04 or 14.04?
09:37 bshum Alright, so I can't find the branch anywhere, so I must have just been modifying a local copy Evergreen-README on lupin directly. We can diff those changes against master and get a branch started though.
09:42 RoganH joined #evergreen
09:54 Dyrcona 14.04
09:55 bshum Dyrcona: I pushed a collab branch with the changes I started to http://git.evergreen-ils.org/?p=work​ing/Evergreen.git;a=shortlog;h=refs/​heads/collab/bshum/README-webclient
11:32 Shirleyh joined #evergreen
11:42 jjk Good morning
11:42 jeff jjk: good morning!
11:43 jjk I'm attempting to upgrade an older 2.3 install to the current version but have run into issues with the database schema updates.  I'm hoping some folks here can point me in the right direction.
11:45 jjk I have a test database that started at 2.3.5 and I've successfully run the schema updates all the way up to 2.3.12.
11:47 jjk When trying to upgrade the schema using 2.3-2.4.0-upgrade-db.sql I quickly receive the following errors:
11:47 jjk psql:version-upgrade/2.3-2.4.0-upgrade-db.sql:96: NOTICE:  extension "tsearch2" already exists, skipping
11:47 jjk psql:version-upgrade/2.3-2.4.0-upgrade-db.sql:98: ERROR:  cannot drop extension tsearch2 because other objects depend on it
11:48 jjk I've not found much in the way of similar issues.
11:53 bshum jjk: So that sounds like you have something custom in your database that relies on tsearch2 extension
11:54 bshum I found something like that when we upgraded as well, some locally created views for reporting had used that extension and needed to be rewritten
11:55 * bshum upgraded forever ago and doesn't remember how he ultimately identified all the things that used that extension.
11:57 jjk bshum: Thanks.  I'll look at the reports.
11:58 TaraC joined #evergreen
12:01 bshum jjk: Out of curiosity, what version of PostgreSQL are you using for your tests?
12:01 bshum (i.e. did you also test upgrading your postgresql installation to newer versions 9.1+)
12:02 bshum And you might find it interesting
12:02 bshum To try the drop extension directly
12:02 bshum And see if it spits back what is still depending on it
12:03 bshum Hmm
12:03 bshum csharp: Did we archive the old evergreen-admin mailing list?
12:04 bshum csharp: Nevermind, found what I was looking for
12:04 bshum jjk: You might see some value in discussion from this mailing list entry: http://list.evergreen-ils.org/pipermai​l/evergreen-admin/2014-May/000086.html
12:05 jjk bshum: I'm running 9.1 on Debian, specifically 9.1.14-0+deb7u1
12:05 bshum jjk: Based on what they say there, I would check to make sure the search_path is set right, and then see if there's any "DETAIL" that comes up after the "ERROR" part when you try to drop the extension.
12:05 bshum ~search_path
14:08 kmlussier Wow! That was fast. Thanks gmcharlt!
14:08 kmlussier gmcharlt++
14:19 jeffdavis What's the status of NCIPServer?
14:22 kmlussier jeffdavis: We have it in testing now to use with AutoGraphics.
14:22 jeffdavis kmlussier: that's excellent, thank you
14:24 Dyrcona jeffdavis: You can't use the master branch with Evergreen at the moment.
14:24 Dyrcona rangi or someone (me?) has to do some integration. I changed the interfaces a good bit.
14:29 Dyrcona And sometimes different products from the same vendor.
14:31 kitteh_ joined #evergreen
14:31 jeffdavis Dyrcona: ah yes, "standards" that are actually their own special case of https://xkcd.com/927/ -- good times!
14:31 bshum Haha, the hover is funny
14:32 bshum Stompro++ # tested the change for OpenSRF instructions for Ejabberd for Debian Jessie and they look good.  I'll sign and push that on for a future OpenSRF 2.4.1 release.
14:33 Dyrcona Well, I don't even really consider NCIP to be a standard myself. It's list of features that you can implement.
14:34 Dyrcona And every vendor seems to pick their own way to do things, and too many messages are similar, but different.
14:34 Dyrcona So, yeah, we need an actual standard.
15:24 tsbere Bmagic: set passwd = 'new password' ;)
15:24 Bmagic oh, lol
15:24 bshum Bmagic: You can just do UPDATE actor.usr SET passwd = 'something' WHERE id = sillyuser;
15:24 Stompro bshum, it took me a while to add the second example to the docs also... I thought I compiled it and tested how it looked, did you not like how it looked or did it break when you tried it.
15:24 bshum and the function will hash it out for you
15:25 Bmagic great! that worked
15:25 bshum Stompro: I was just trying to see if I could make it more consistent looking with the rest of the styling.
16:44 mmorgan mrpeters: Not an expert, but I don't know of any other way to do that.
16:44 Dyrcona I was going to say that I think it is the only way to do it, but got sidetracked.
16:45 mrpeters mmorgan: i didnt think so either, but so much awesome stuff has been done with the in-staff client configuration menus that i wasnt sure
16:52 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
17:16 pinesol_green [opensrf|Ben Shum] Docs: Keep all source syntax consistent in README - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=ef80e4c>
17:16 pinesol_green [opensrf|Ben Shum] Docs: Add [source, bash] to code blocks that were not defined in README - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=52b6eca>
17:16 pinesol_green [opensrf|Ben Shum] Docs: Emphasize variables and paths consistently in README - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=86e6d84>
17:16 pinesol_green [opensrf|Josh Stompro] LP#1445503 - Updated Ejabberd setup steps for Ejabberd 14.x for Debian Jessie - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=e421bb3>
17:18 pinesol_green [opensrf|Ben Shum] Docs: Fix mailing list link for help in README - <http://git.evergreen-ils.org/?p​=OpenSRF.git;a=commit;h=966fb05>
17:18 bshum I give up on the asciidoc syntax for now.  I will slay that eventually though.
17:18 mmorgan left #evergreen
17:21 bshum So, for the Evergreen bugs targeting issues with Debian Jessie
17:44 pinesol_green [evergreen|Josh Stompro] LP#1445187 - Force disable of deflate - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=b949202>
17:44 pinesol_green [evergreen|Josh Stompro] LP#1362260 - Email::Sender/libemail-send-perl change in Jessie - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=ad879d4>
17:50 pinesol_green [evergreen|Josh Stompro] LP#1445182 Changed Debian Jessie dependency install to use packages for dbi dbd-pgsql. - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=d5089b7>
17:54 bshum Stompro++ # I pushed ahead everything and I seem to be well on my way towards a happy Jessie test server.
18:08 bshum Hmm
18:10 bshum Looks like we'll need to create a file for 000.english.pg94.fts-config.sql
18:10 bshum In order for PG 9.4 to be used when creating the database
18:11 bshum To test, I've just copied the 93 one to be named 94 and seeing how that goes.
18:25 bshum I appended my findings to the bug
18:30 bshum Stompro: I set https://bugs.launchpad.net/evergreen/+bug/1445150 back to Triaged while we test the last little bit I think we need to create a working database on PG 9.4 using the scripts.
18:30 pinesol_green Launchpad bug 1445150 in Evergreen 2.7 "Debian Jessie includes Postgresql 9.4 - update software dependency makefile" (affected: 1, heat: 6) [Medium,Triaged]
18:31 bshum When we get time, someone else should check that initial working branch, and then make any special adjustments.
18:31 bshum Otherwise, as far as I can see, I have a functional Evergreen install on Debian 8.0 Jessie

Results for 2015-05-03

04:54 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
09:08 Dyrcona joined #evergreen
09:19 Dyrcona I'm looking at the we staff client installation instructions for the server and wonder if anyone has tried it with the latest stable version of Node.js?
09:19 Dyrcona that should be "web staff client"

Results for 2015-05-02

12:52 dbs I don't see how it could even take that long, I suspect there's some other reason you're seeing that savings :)
12:53 dbs yeah
12:53 Dyrcona I mean it was 0.6 ms faster than the previous version.
12:53 Dyrcona At least in a couple of tsbere's tests.
12:53 dbs right, I get that, I just don't think that has to do with a seq scan against config.copy_status :)
12:54 Dyrcona Anyway, since you wrote the original he wanted to know what you though of it, and I think he wanted to ask why it was based on 10 before.
12:54 Dyrcona But, he should speak for himself, really. I just happen to be paying attention and he isn't at the moment.
15:20 * Dyrcona just got back from a nice walk.
16:16 dcook__ joined #evergreen
16:30 dcook joined #evergreen
17:12 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>

Results for 2015-05-01

05:00 collum joined #evergreen
05:14 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
07:48 kmlussier Good morning #evergreen
07:49 kmlussier @coffee y'all
07:49 * pinesol_green brews and pours a cup of Kenya Ndaroini Microlot, and sends it sliding down the bar to y'all
12:18 * tsbere hasn't had much reason to use that part of PHP lately so isn't all that familiar with it personally
12:19 jeff you're the only reason I ran into it just now. ;-)
12:19 jeff PHPSIP2 won't connect to localhost because of it -- simple fix.
12:22 tsbere as I said, lately. I haven't done much with phpsip2 for a while.
12:23 * tsbere also rarely has phpsip2 talk to localhost, for that matter, even when testing things >_>
12:23 berick because i'm not a huge fan of php, i started on this a while back: https://github.com/berick/pysip2
12:23 berick in case anyone prefers python
12:23 berick for sip tseting
16:55 * pinesol_green grabs some Pumpkin Pie for kmlussier
16:55 mmorgan Good idea!
16:55 mmorgan @dessert
16:55 * pinesol_green grabs some wild Alaskan rhubarb pie for mmorgan
16:56 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
17:10 mmorgan left #evergreen
17:20 buzzy joined #evergreen
18:02 kmlussier evergreen-ils.org is quite sluggish at the moment
20:33 jonadab (It updates CPAN and a bunch of related modules.)
20:34 jonadab Oh, I should probably clarify:  since you were using make, I've been assuming that you already installed build-essential or the equivalent system package.
20:34 jonadab So you have gcc and make and all that stuff.
20:35 nuentoter our library is looking to switch very soon to evergreen and i'm setting up a left over computer as a test server to check it out and see what will work for us
20:35 nuentoter pretty sure most of that can preinstalled on this distro
20:35 jonadab Yeah, I'm doing a similar thing to work on migrating our data.
20:36 jonadab nuentoter: Oh, could be.  I use Debian, which doesn't install that stuff by default, but the build-essential metapackage depends on all of it.
20:36 nuentoter im on debian jessie for first time

Results for 2015-04-30

03:11 tsbere joined #evergreen
03:52 * bshum generally agrees with dbs and tries to remind people about said older bugs.
04:47 book` joined #evergreen
04:59 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
07:06 csharp bshum: argh - I hate launchpad
07:06 * csharp remembered that the issue had been discussed before, but didn't remember the bug and it didn't appear in search results
07:07 csharp so in the old bug I suggested the alternative of commenting out the lines in fm_IDL.xml, but I've changed my mind on that, obviously ;-)
10:12 jeff but have not checked lately.
10:12 jeff what version are you seeing that behavior on?
10:12 krvmga jeff: 2.7.4
10:13 jeff convenient for me to test!
10:13 Dyrcona Hmm. I could check right quick.
10:13 jeff krvmga: i suspect something other than the copy status is to blame, unless you've heavily tweaked your templates.
10:13 bshum I'm pretty sure I remember it displaying when we tested it.  Or rather, it displayed as a bill or something elsewhere.
10:13 bshum And basically that still showed in the same place as items out
10:13 krvmga jeff: our myopac templates are pretty vanilla.
10:16 Dyrcona Well, I just set one of my items to lost on my dev system and it doesn't show up in my list of items out in the OPAC.
10:16 jeff krvmga: tested by checking an item out to a patron and then marking it lost by patron. it is no longer visible under Items Checked Out, but is visible as a bill in the main myopac page at /eg/opac/myopac/main -- under Fines
10:17 * Dyrcona confirms it shows up under fines.
10:17 jeff I get a Title, Author, Checkout Date, Due Date, Date Returned shows (fines accruing) [er, they aren't actually] and there's a balance owed.
10:17 jeff (under Fines)
10:18 Dyrcona Well, the question is should lost items show in items out, or just under fines.
10:19 Dyrcona I'd be more likely to say Long Overdue should show up under items out.
10:19 Dyrcona Or more correctly, "Checked Out."
10:21 krvmga i think the issue has been reported to me incorrectly. i just looked at a test account and the Lost items show up but under Returned/Renewed it says (fines accruing) but under Balance Owed it's showing a replacement cost
10:21 krvmga i think the person who reported it might have gotten confused by "(fines accruing)"
10:22 Dyrcona Well it shouldn't say that. It is an error.
10:22 Dyrcona Maybe it should say "Lost" instead?
10:22 krvmga Dyrcona: is it a bug error or a configuration error on our part, do you think?
10:23 krvmga if it's a bug, i'll report it. i just want to make sure it's not anything we're doing wrong.
10:24 Dyrcona I'd say find out from your staff what the real problem is, and then open a bug.
10:24 Dyrcona We can always set it to invalid if it turns out to be configuration. :)
10:28 krvmga staff are saying that the patron's Lost items show up under Fines (as previously mentioned) but, if a patron looks at Items Checked Out, the screen shows "You have no items checked out."
10:29 krvmga a patron's Lost item is still checked out to the patron, no?
10:30 krvmga maybe this is where not showing Lost in the OPAC is having the impact.
10:31 krvmga i'm testing by turning OPAC visibility back on for Lost for a little while
10:35 jeff i think that "(fines accruing)" is based simply on the lack of a checkin time.
10:35 jeff should be a somewhat easy fix to correct/clarify that.
10:49 jeff hah! there's actually a TODO in the template
10:50 krvmga jeff: lol
10:51 Dyrcona Not surprising. :)
11:00 krvmga ok, i have tested with showing Lost in the OPAC. Lost items are now OPAC visible in our catalog. logging out and logging in again as the test patron. Current Items Checked Out still shows "You have no items checked out". I'm guessing this means OPAC visibility of Lost status has no impact here.
11:00 Dyrcona Sounds like something else is going on.
11:10 kmlussier Although Evergreen considers lost items to still be checked out to the patron, as a patron I don't think I would expect it to show in Items Out. If it is truly lost, it's lost.
11:10 kmlussier I agree with Dyrcona that I would expect long overdue to still display there.
15:16 pinesol_green Launchpad bug 1125270 in Evergreen "Error updating function in 2.0-2.1-upgrade-db.sql for 2.3" (affected: 1, heat: 6) [Low,Triaged]
15:16 bshum I wrote some minor patches to fix those two and even though I sure hope nobody is still on 2.0 or 2.3, it'd be nice to close out those bugs.
15:17 * bshum would have probably just pushed those already, but just checking real quick one last time.
15:30 csharp bshum: so to test bug 1125270, one would need to install 2.0 and run the 2.0 to 2.1 upgrade script?
15:30 pinesol_green Launchpad bug 1125270 in Evergreen "Error updating function in 2.0-2.1-upgrade-db.sql for 2.3" (affected: 1, heat: 6) [Low,Triaged] https://launchpad.net/bugs/1125270
15:30 bshum csharp: If you were being thorough, I suppose yes.
15:30 csharp I mean, it's probably fine to push as-is

Results for 2015-04-29

10:10 Dyrcona Well, more sites are using acq these days, so that experience is changing.
10:15 csharp Dyrcona: have you done any more experimentation with EG on 14.04?  looks to me like most of the bigger issues are fixed...
10:16 csharp I'm working on building our debs on 14.04 and jessie right now, but I'm deep in the weeds of packaging best practices right now
10:16 Dyrcona You mean for acq? If so, no. I don't really have much of a way to test, since I don't actually have any vendor accounts.
10:16 csharp nah, just in general
10:16 Dyrcona In general, I have been running Evergreen on 14.04 with success for about a year.
10:16 csharp I think I have the ruby problem solved for now
10:16 csharp oh good to know
10:16 Dyrcona yep. I saw that.
10:17 Dyrcona I thought about faking an EDI transaction for testing.
10:17 Dyrcona That is, setting up a bogus vendor with a canned order and response to send.
10:17 berick we've deployed 2 ubuntu 14.04 servers to productoin.
10:17 berick soon, soon we'll be free of centos
10:19 csharp I have an aging OpenSRF branch that installed dependencies from EPEL and got it up and running on CentOS
10:19 csharp 6, I think
10:19 csharp but I didn't get as far as Evergreen
10:22 bshum I think for front-end app servers, I'm not too nervous about Ubuntu 14.04.  But for backend utilities, I get a little anxious to test further.
10:22 bshum Acq EDI stuff, sure, but also have to test things like print notice generation, other scripts.
10:22 bshum z39.50, who knows?  :)
10:23 berick bshum: we should be fully migrated by the end of May.  i'll let you know how it goes
10:23 bshum berick++
10:24 csharp oh yeah - z39.50 is broken in 12.04 too, right?
17:15 bshum Hmm
17:16 bshum We can't seem to add any bibs with URIs to lists.
17:16 bshum That's special.
17:16 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
17:18 mmorgan bshum: lp 1246385 ?
17:18 pinesol_green Launchpad bug 1246385 in Evergreen "internal server error when adding an item to a list from within staff client" (affected: 1, heat: 6) [Undecided,Confirmed] https://launchpad.net/bugs/1246385
17:18 bshum No, this is in public side
17:19 bshum If I go to try adding a bib that's a URI (aka, $9 trick), it just stays off the list and I get a refreshed page that still says "add to list"
17:19 mmorgan Oh, ok. sounded familiar. But it's too late in the day...
17:19 bshum I'm going to have to get a test system going with 2.8 stock to see if it's a template issue in our systems, or if it's a 2.8 regression.
17:20 bshum It's not broken on MVLC's or PINES systems, but they're on 2.7ish
17:20 bshum mmorgan: We should probably close that bug.  Since no one's confirmed anything since it was reported "fixed" or at least "not broken" for 2.5.
17:22 mmorgan Oh, probably so.
17:24 mmorgan left #evergreen
17:37 kmlussier bshum: There's a bug for that. And old one
17:38 kmlussier bug 979038
17:38 pinesol_green Launchpad bug 979038 in Evergreen "tpac: Records with a located URI cannot be added to a list" (affected: 3, heat: 18) [Low,Confirmed] https://launchpad.net/bugs/979038 - Assigned to Jeff Godin (jgodin)
17:40 kmlussier Filed that one while C/W MARS and NOBLE were getting ready to go live on Evergreen.
17:40 bshum kmlussier: That sounds more like my problem.
17:40 bshum I didn't notice it on MVLC/PINES cause I was only testing temp lists on there (no account to test real with)
17:40 bshum But temp lists don't even take ours on our systems.
17:40 bshum But maybe that's cause we don't use the temp list warning or whatnots.  Who knows.
17:41 bshum Sigh, oh well.
17:41 * bshum clicks "affects me too" and contemplates dinner.
17:43 kmlussier jeff: Do you still want to be the assignee on that bug?
18:16 bshum csharp: Should we be deprecating https://bugs.launchpad.net/evergreen/+bug/1050384 in favor of your newly filed https://bugs.launchpad.net/evergreen/+bug/1450218
18:16 pinesol_green Launchpad bug 1050384 in Evergreen "Views referenced in reporter UI are not created by default" (affected: 1, heat: 6) [Low,Confirmed]

Results for 2015-04-28

04:21 StomproJosh joined #evergreen
04:23 jeff_ joined #evergreen
04:26 eady joined #evergreen
05:19 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
05:20 TaraC_ joined #evergreen
07:51 jboyer-isl joined #evergreen
08:20 Newziky joined #evergreen
14:20 * csharp dives in and hopes for the best
14:20 jboyer-isl csharp: If that will work, you'll likely have to use \$ because it looks like it's expecting regex syntax, where $ is special.
14:22 berick csharp: record display attributes only affect display :(
14:22 csharp it makes sense to me that it would be regexp syntax, and I'm told that was tried and didn't work, but I'll test it myself
14:22 csharp berick: ah
14:23 csharp hmm - so the acq code expects *no* dollar sign, but the file has them - is there a way to remove them within EG? or would that have to be done externally?
14:23 csharp well, specifically, the DB rejects the '$' character as non-numeric
14:23 csharp so I guess the acq code doesn't know or care
14:24 berick code would have to be added to make that happen within ACQ
14:27 * tsbere loves the vendor "But other <ils> customers have no issues" response - Half the time I get a list of those "other customers" I find they aren't using Evergreen.
14:27 berick acq being what it is, there are a number of vendor-specific hacks in the acq code.  adding one to strip '$' from the price field does not seem crazy.
14:28 tsbere Of course, then there are the vendors that say "But other <ils> customers have no issues" with <ils> *not* being Evergreen. At which point I get to say "That is all well and good. We are using Evergreen, not <other ils>" >_>
14:28 berick or strip all non-numbers
15:26 * csharp creates bug 1449724
15:26 pinesol_green Launchpad bug 1449724 in Evergreen "Acq Record Import Fails because of dollar sign in price field" (affected: 1, heat: 6) [Undecided,New] https://launchpad.net/bugs/1449724
15:45 maryj joined #evergreen
16:12 Newziky1 joined #evergreen
16:22 ericar joined #evergreen
16:34 Newziky1 joined #evergreen
16:47 mrpeters joined #evergreen
16:56 Newziky1 joined #evergreen
17:01 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
17:06 mmorgan left #evergreen
17:36 bbqben joined #evergreen
17:44 Newziky left #evergreen

Results for 2015-04-27

01:52 jeffdavis joined #evergreen
03:09 gsams joined #evergreen
05:03 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
07:34 rjackson_isl joined #evergreen
07:39 graced joined #evergreen
07:39 sarabee joined #evergreen
11:34 csharp berick: I could see that you made a lot of progress on it ;-)
11:34 berick maybe we can get some progress on that at egcon
11:34 csharp I'll totally help with that if I can
11:34 berick yes, you can help test
11:34 csharp perfect
11:34 berick IIRC, there's just a few fields remaining that have to be mapped.
11:34 berick then it's testing time
11:35 csharp awesome
11:37 csharp so once the A/T thing is in place, it might be worth incorporating edi /openils stuff into the standard installation process
11:38 csharp "thing"... "stuff" - technical jargon be damned!
13:37 eeevil has anyone other than gmcharlt looked at LP 1438136?
13:37 pinesol_green Launchpad bug 1438136 in Evergreen "OPAC searching significantly slowed by adding format filters" (affected: 1, heat: 6) [Undecided,New] https://launchpad.net/bugs/1438136
13:37 eeevil or, the linked branch, more correctly
13:40 csharp eeevil: I applied it to a test server and see far faster search times - I don't have an opinion about the implementation beyond that though
13:40 Dyrcona eeevil: I loaded it on my dev system, which is 9.1 and apparently didn't need it, but I can say it caused no problems there.
13:40 eeevil just hoping for a merge before the next point release, is all
13:41 RoganH I can add it to our test and measure results tonight.
13:48 dac joined #evergreen
13:52 kmlussier eeevil: Is C/W MARS in production? If so, would it help if they added a comment to the LP bug reporting that it's working well for them?
13:53 eeevil kmlussier: they're using it, and I think it would. I'm trying to avoid self-merging, but if that's what is needed to get it in, I will
14:05 jonadab_znc joined #evergreen
14:05 jboyer-isl (Also, time works ever against me. :( )
14:05 Dyrcona Well, I have no business signing off, since I obviously didn't look hard enough. :)
14:22 RoganH I was just looking at our current search return numbers but they're even on our low powered test system orders of magnitude faster than csharp's.  I don't know if I'd find anything worth signing off on other than "this didn't screw up an existing system"
14:28 kmlussier After talking to C/W MARS, I'm not comfortable signing off either. They aren't seeing the huge difference between limited searches and non-limited searches anymore. However, they are seeing slower overall search performance since their upgrade.
14:28 kmlussier Since the patch was applied as part of their upgrade, it's difficult for me to know if that change was partially caused by the patch or whether it was due to something else.
14:39 csharp kmlussier: Terran was just testing here, and the challenge was trying to find search terms that weren't already cached by the live server - dunno if that's a factor there, but after a number of tries, Terran definitely sees the difference between pre- and post-fix
14:42 kmlussier csharp: Yeah. I can definitely say that the format limiting problem was resolved. Their format-limited searches were timing out on their test system before their upgrade.
14:43 kmlussier I just don't know if the other reported search slowness was a result of the patch, a result of the upgrade, or the result of something else. Too many moving parts.
14:44 csharp kmlussier: well, the sure fire way to know is with an actual query from the postgres logs
14:44 csharp that can be EXPLAIN ANALYZEd
14:49 kmlussier I'll forward that along to them

Results for 2015-04-25

02:18 ningalls_ joined #evergreen
02:27 eby joined #evergreen
03:05 dkyle joined #evergreen
04:33 pinesol_green Incoming from qatests: Test Failure - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
07:32 _bott_ joined #evergreen
10:42 _bott_1 joined #evergreen
10:43 dkyle1 joined #evergreen
12:47 bshum joined #evergreen
12:48 mceraso joined #evergreen
14:24 gmcharlt joined #evergreen
17:06 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
17:43 bmills joined #evergreen
21:54 pmurray_away joined #evergreen
21:54 pmurray_away joined #evergreen

Results for 2015-04-24

05:08 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
06:24 paxed left #evergreen
07:43 graced joined #evergreen
07:48 rjackson_isl joined #evergreen
16:42 buzzy joined #evergreen
16:46 csharp berick: hmm - I don't know why that choice was made there - we don't have a robots.txt on the EG community mail server
16:51 berick csharp: better safe than sorry, i'm guessing
16:51 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
17:16 mmorgan left #evergreen
18:00 RBecker joined #evergreen
19:19 Newziky left #evergreen

Results for 2015-04-23

01:04 DPearl joined #evergreen
04:14 kmlussier jonadab: Well, there is the Douglas county model for purchasing ebooks - http://douglascountylibrarie​s.org/content/ebooks-and-DCL
04:53 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
07:35 rjackson_isl joined #evergreen
07:45 graced joined #evergreen
07:50 mrpeters joined #evergreen
12:32 csharp tsbere: that's nice to know
12:33 csharp well, one of the selling points on our end for RT is that it's in use by other EG sites, which might lead to some EG/RT integration ideas in the future?
12:34 csharp one of the originally envisioned features of Evergreen was helpdesk integration, but it didn't get very far
12:38 bshum You know, speaking of bib sources...
12:38 bshum Anyone got a test server with 2.8/master around and can test something for me
12:38 bshum So I got a report from our staff that loading bibs is causing the bib source to change to the latest source on merges.
12:38 bshum Instead of staying at the original source.
12:39 bshum During match-only merge.
12:39 bshum I'm getting into it shortly, but curious to see if I can verify that it's not just our systems.
12:39 Dyrcona I could test it, but I'm too busy to do that today.
12:47 bmills1 joined #evergreen
12:54 sandbergja joined #evergreen
13:13 bshum Aha
13:20 bshum But long-term, it sounds like we should file a bug to make this some sort of setting controlled option.
13:21 mllewellyn like a bib source hierarchy
13:24 Dyrcona The bib source change was intended to make records get the bib source selected in the vandelay import because we had fresh records loading (not overlay records) and getting a null bib source.
13:24 Dyrcona The branch was evaluated on that basis, and overlay was not on my radar in the testing that I did.
13:26 bshum I could see avoiding that being helpful.
13:27 * bshum rips it out for now so that mllewellyn's work isn't disrupted.
13:27 bshum I'll file a new bug on the subject in a bit.
14:09 bshum mllewellyn: I filed https://bugs.launchpad.net/evergreen/+bug/1447746 to make sure I didn't forget it.
14:09 pinesol_green Launchpad bug 1447746 in Evergreen "Do not update bib source on match-only merge" (affected: 1, heat: 6) [Undecided,New]
14:10 kmlussier berick (or anyone else who knows the answer): I've seen instructions to install hatch on linux and on windows. Will it also work on macs?
14:11 jeff it is intended to, but I've not been able to test that becase of my ancient version of OS X.
14:12 kmlussier jeff: OK, thank you!
14:15 mllewellyn bshum: thank you
14:15 bshum mllewellyn++ # getting the word out
15:36 berick so, it didin't really take hold for 2.8 for various reasons.
15:36 berick i'd really like some input on the wiki doc before we start forcing anything
15:37 berick and if we're goign to start requiring QA contributions for 2.9, we need to solidify the plan now-ish
15:37 jeff short of boiling the ocean, what do you think our approach should be for "this changes the behavior of something large and complex which has no existing tests"?
15:37 jeff (not that this particular ocean doesn't deserve boiling...)
15:38 berick jeff: do you mean areas of the code where there is no test structure?
15:38 jeff case-by-case exception with a high bar, but discretion to the RM?
15:38 jeff berick: yes, exactly.
15:38 berick honestly, if we could people started on using the test structure we have, that would be a big win
15:38 bshum Speaking of RM, who'll that be for 2.9 :)
15:39 berick bshum: yeah, this conversation makes me think again about nominating RM's earlier in the process
15:40 bshum Yeah, I think we should start thinking like that.
15:40 dbwells If we want the RM to make calls on "tested enough"-ness, we'll more or less need the RM to approve everything.  That's pretty far from what we've done before, but certainly exists in other projects, from what I'm told.
15:40 kmlussier I don't feel qualified to comment on the wiki page, but if there is anything somebody like me can do to help with this, let me know.
15:41 jeff dbwells: I was thinking more along the lines of "has tests == good, anyone can merge", vs "no tests because REASONS, merge is at RM discretion"
15:41 dbwells jeff: makes sense, thanks for clarifying
15:41 gmcharlt dbwells: from somebody who has been RM in such a kind of project... that is a big burden to put on the RM
15:42 dbs Are tests in place for the web staff client, along the lines of https://docs.angularjs.org/guide/unit-testing ?
15:42 dbwells gmcharlt: I can imagine.
15:43 berick expanding on jeff's last comment.. "no tests because no framework exists to test this" would cover a lot things
15:43 berick that would leave a fairly limited number of cases where the RM would have to decide
15:43 gmcharlt now giving the RM more mental space to throw things back if not done enough -- and have those decisions not be nibbled to death by the Ducks of Merge It Now -- is something that would be a step forward
15:44 dbwells the endless nibbling!
15:44 csharp probably an obvious point, but it also raises the bar for a qualified RM
15:44 jeffdavis Is there a tag in LP meaning "has code, needs tests"?
15:44 bshum jeffdavis: needsignoff ?
15:45 jeffdavis Do we want something more specific?
15:46 * gmcharlt is inclined to think so - at least to try it out
15:46 jeffdavis Signoff to me implies "I've tried this, it works on my system."
15:46 gmcharlt "needstest"?
15:46 jeff needstests? needsqa?
15:46 gmcharlt er, needstests
15:46 gmcharlt (not One Test To Rule Them All)
15:46 * csharp is having deja vu
15:46 jeff csharp: that might be bad. is it bad?
15:47 dbs #qualityisjob1
15:49 * gmcharlt tosses out a wild idea
15:49 gmcharlt do we want to make QA the Official Theme (TM) of the dev portion of hackfest/
15:49 gmcharlt ?
15:49 jeff dbs: there are some tests for the angular bits, using karma. commit 75e466e contains one example. i can't say what coverage is like.
15:49 pinesol_green [evergreen|Bill Erickson] LP#1402797 browser client interval parser - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=75e466e>
15:50 bmills1 joined #evergreen
15:50 jeff gmcharlt: if nothing came out of the hackfest but every interested contributor was better equipped to write tests... i'm not sure i'd be disappointed.
15:51 * gmcharlt sources a troop of cats to give out at the conferences
15:51 gmcharlt very special cats
15:51 gmcharlt cats who hiss ... if one does a git push with adding something to t/
15:52 dbwells gmcharlt: I'd be up for QA time during the hackfest.
15:52 csharp #info gmcharlt's Cats of Doom: http://cat.evergreen-ils.org.meowbify.com/
15:52 jeff "QA time" might be easier to pull off. :-)
15:53 jboyer-isl I could certainly use an intro. I felt a little bad about how much went into the "delete acpl" commits without any tests but human ones.
15:53 * gmcharlt is more than happy to put together some starting material for a QA time
15:53 dbwells #action AllTheDevs will read and think about berick's QA page, and come to the conference ready to discuss and take action
15:53 berick you_all++
16:26 jeffdavis I can think of two pieces that might help to get more folks trying it out.
16:26 jeffdavis 1. Documentation. This has been on my todo list for a while.
16:26 jeff jeffdavis: can you summarize your environment with regard to auth methods, what patron identifier is used, and if you have just a single overdrive account for the entire consortium or if you have per-system, and if there's any use of "overdrive advantage" (where systems participate in a large collection but can then ALSO add items that only their patrons get)?
16:26 jeffdavis 2. Testing credentials that can be shared among EG developers.
16:26 dbwells #link https://launchpad.net/overdrive-eg-opac
16:28 dbwells jeffdavis: I think testing credentials would be great.  I'm not sure how many of us have access otherwise to OverDrive.
16:28 * csharp might be able to get credentials, but not sure if he could share them :-/
16:28 jeffdavis I can commit to contacting Overdrive about that.
16:29 jeff My experience with getting API access from them (prod and/or testing) has been... yeah.
16:29 dbwells #info jeffdavis suggests that any potential testers file bugs at the link given above
16:30 jeffdavis They do have a testing environment which in theory shold not be tied to anyone's "real" OverDrive accounts, so it's at least a theoretical possibility, IIUC.
16:30 kmlussier Thanks all!
16:30 * kmlussier needs to disappear
16:30 dbwells #action jeffdavis will pursue contacting OverDrive to ask about test credentials / a test environment
16:30 * csharp too
16:31 dbwells Ok, wrapping things up unless someone speaks up...
16:31 jeffdavis jeff: we have two OverDrive accounts, each used by a different chunk of our libraries

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