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 149 150

Results for 2019-09-26

09:35 Dyrcona During MVLC's migration, I found phone numbers entered as "The number in the field above is the student ID."  I guess because phone number was below the ID field in the old ILS. :)
09:36 Dyrcona Today, I've been asked to regularize some call number labels.  Something I've done a number of times before. It really exercises one's regex fu.
09:38 * Dyrcona considers "cheating" by dumping the rows to a CSV, mangling them manually, and generating a SQL update script from the CSV.
09:46 Dyrcona On the plus side, production and test data are the same for a change.
09:48 mmorgan1 joined #evergreen
09:54 sandbergja joined #evergreen
09:55 yboston joined #evergreen
10:20 berick heh, i felt so bleeding edge on 9.6.  i'm already crusty.
10:21 Dyrcona Maybe we'll skip 11 and go straight to 12?
10:22 Dyrcona Heh. Nigels' may go to 11. Mine go to 12. :)
10:22 csharp I'm testing 11 right now - but I might chicken out and go from 9.5 to 9.6 :-/
10:22 berick Dyrcona++
10:23 csharp @ana none more black
10:23 pinesol csharp: Noblemen croak
19:06 cmalm joined #evergreen
21:54 sandbergja joined #evergreen
22:06 sandbergja joined #evergreen
23:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
23:35 sandbergja joined #evergreen

Results for 2019-09-25

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

Results for 2019-09-24

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

Results for 2019-09-23

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

Results for 2019-09-22

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

Results for 2019-09-21

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

Results for 2019-09-20

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

Results for 2019-09-19

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

Results for 2019-09-18

09:39 sandbergja joined #evergreen
10:06 yboston joined #evergreen
10:59 yboston joined #evergreen
11:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:06 Christineb joined #evergreen
11:09 yboston joined #evergreen
11:19 Bmagic Dyrcona: ha!
16:20 jvwoolf left #evergreen
16:26 yboston joined #evergreen
16:31 jeffdavis There's a commit on bug 1727557 that disables the Download Block List button so I suspect PINES is just doing without that feature.
16:31 pinesol Launchpad bug 1727557 in Evergreen 3.3 "Web Client: Download Block List causes unresponsive page with large file" [High,Confirmed] https://launchpad.net/bugs/1727557
17:07 mmorgan left #evergreen
17:10 sandbergja_ joined #evergreen
17:49 agoben joined #evergreen
20:28 abowling1 joined #evergreen
20:34 abowling joined #evergreen
21:00 sandbergja joined #evergreen
23:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
23:22 sandbergja joined #evergreen

Results for 2019-09-17

08:48 jvwoolf joined #evergreen
08:53 sandbergja joined #evergreen
09:18 tlittle joined #evergreen
09:19 csharp any major sites running PG 10+?  I'm upgrading our next-release test servers to Ubuntu 18.04 which comes with 10 and I'm trying out PG11
09:31 yboston joined #evergreen
09:49 Stompro joined #evergreen
10:14 * Dyrcona shakes his fist at slow websites and networks everywhere.
10:35 bshum That's what I think too
10:36 bshum Getting the community to standardize on PG9.6 was the latest official step
10:36 bshum For the next release
10:36 Dyrcona bshum and I have rune the tests, and JBoyer found a bug with Vandelay that tests don't cover.
10:36 bshum And we fixed that
10:36 bshum At least I think it went into master
10:36 Dyrcona Yeah, we did fix it.
11:00 Dyrcona Bmagic: I don't use sendmail, so I don't know, but I doubt it.
11:01 Dyrcona Bmagic: You could search your logs for something like "No recipient addresses found in header"
11:01 Bmagic looking
11:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:04 Bmagic Nothing like that in the logs
11:05 Dyrcona You searched all of the logs, not just Evergreen logs?
11:05 Bmagic /var/log/mail.log*
11:18 mmorgan What Dyrcona said:)
11:19 Dyrcona Thing is, you might want the main event to trigger but not the notification event, and I've not looked at how filters interact with those.
11:20 Bmagic the filter sounds attractive
11:21 Dyrcona Well, all right, there is 1 email bug assigned to me, that I think I'm going to drop for now.  I also need to take a look at the 9 other bugs and get some testing scheduled, but other things have been a higher priority....
11:29 jeff I may pick that up, if it's the one I think it is.
11:31 Dyrcona jeff: https://bugs.launchpad.net/evergreen/+bug/1466502
11:31 pinesol Launchpad bug 1466502 in Evergreen "Replace Email::Send with Email::Sender" [Wishlist,Confirmed]
12:04 Dyrcona mmorgan Stompro: You can specify subqueries.
12:06 Dyrcona Pretty much all of our custom filters have an '-and' : [ {"-exists" : { "select" : ....
12:06 Stompro Dyrcona, could you share your custom filters please, I would love to see examples.
12:07 berick Bmagic: FYI, https://git.evergreen-ils.org/?p=worki​ng/Evergreen.git;a=shortlog;h=refs/hea​ds/user/berick/el-integrate-circa-3.4 -- wasn't really ready to start talking about it, but I'm hoping to start testing locally before too long
12:07 jihpringle joined #evergreen
12:08 Bmagic berick++ # is there more on this topic that I am not aware of?
12:09 berick Bmagic: no, so far it's just been a local project.
12:25 berick at least enough to support the staff work flow we need
12:25 Bmagic and just recently got serious about it
12:28 Bmagic Now I have to re-plan my freed 6-18 month future. Thanks a lot berick!
12:30 berick heh, well, let me know if you have questions, etc.  eyes and testing obviously appreciated
12:31 * berick should probably post a tech doc to the repo
12:39 jvwoolf joined #evergreen
13:18 nfBurton joined #evergreen
13:21 khuckins joined #evergreen
14:29 khuckins joined #evergreen
14:54 jeffdavis How do you all handle Postgres upgrades? Do you just do pg_dump and restore to a new cluster, or use pg_upgrade, or...?
14:58 mmorgan1 joined #evergreen
15:00 Dyrcona jeffdavis: When I upgraded from Pg 9.2(?) to Pg 9.5 I also got new servers, so I did a dump and restore. I have done some test upgrades using pg_upgrade and that seems to work, too. I'm planning to use pg_upgrade to go from 9.5 to 9.6 (or maybe 10) before we upgrade to Evergreen 3.4 next spring.
15:01 Dyrcona Having replication makes it more interesting, though you can disable replication, upgrade the software on the replicant, to a pg init db, and start replication over from scratch if anything goes wrong.
15:03 gmcharlt jeffdavis: we use pg_upgradecluster most of the time
15:04 jihpringle joined #evergreen
15:16 bwillis joined #evergreen
15:20 bwillis I am trying to add some new Z39.50 targets in Evergreen.  I am using the The Z39.50 Target Directory compiled by IndexData (http://irspy.indexdata.com/) I have had success connecting to only one of several targets that I have tested.  I don't know if the directory information is incorrect or if the targets I selected require authorization.  Can
15:20 bwillis anyone recommend one or more targets that your system is currently using?
15:22 jeffdavis Dyrcona, gmcharlt: thanks!
15:29 bwillis53 joined #evergreen
15:33 bwillis3856 joined #evergreen
18:18 khuckins joined #evergreen
21:36 sandbergja joined #evergreen
22:56 sandbergja joined #evergreen
23:03 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
23:28 jamesrf joined #evergreen

Results for 2019-09-16

10:53 tlittle26 joined #evergreen
10:56 Dyrcona On training it looks like out a/t runner is set to parallel of 3, but the daily runner last night failed to create any events in the database, though the log shows it doing so.  After about 11 minutes, however, no active transaction messages start showing up.
10:59 Dyrcona The timeout used in the a/t runner script looks like 180 minutes: 10800.
11:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:12 yboston joined #evergreen
11:54 rjackson_isl joined #evergreen
11:54 rfrasur joined #evergreen
22:15 sandbergja joined #evergreen
22:47 sandbergja joined #evergreen
22:56 gmcharlt joined #evergreen
23:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
23:24 gmcharlt joined #evergreen
23:47 jeff__ joined #evergreen

Results for 2019-09-15

00:49 kip joined #evergreen
00:54 gmcharlt joined #evergreen
01:26 sandbergja joined #evergreen
11:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:23 sandbergja joined #evergreen
11:52 sandbergja joined #evergreen
13:21 sandbergja joined #evergreen
20:16 jamesrf joined #evergreen
20:27 khaun1980 joined #evergreen
22:38 sandbergja joined #evergreen
23:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>

Results for 2019-09-14

09:19 sandbergja joined #evergreen
11:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
12:30 sandbergja joined #evergreen
23:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>

Results for 2019-09-13

10:41 khuckins joined #evergreen
10:51 Christineb joined #evergreen
10:59 rfrasur joined #evergreen
11:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:04 StomproJ sandbergja, I posted my working branch to #1739288
11:13 sandbergja StomproJ++
11:39 rfrasur joined #evergreen
17:25 berick once booked, it will provide a link to the resource configuratoin
17:25 berick w/ the id of id of the ID of the resource type included in a gridFilters parameter
17:28 miker berick++
17:34 jeffdavis Thanks! I'll look at that.
17:37 jeffdavis miker: btw I ran into a problem testing the self edit branch (couldn't avoid the group application perm block even by explicitly granting the necessary group perm to my test user). But I haven't ruled out a local config issue so trusting others' testing so far.
18:17 yboston joined #evergreen
18:35 sandbergja joined #evergreen
19:14 HomerPublic joined #evergreen
20:41 sandbergja joined #evergreen
21:38 sandbergja joined #evergreen
22:37 sandbergja joined #evergreen
23:01 pinesol News from qatests: Failed Installing Evergreen pre-requisites <http://testing.evergreen-ils.org/~li​ve/test.26.html#2019-09-13T23:00:35,957871887-0400 -0>
23:01 pinesol News from qatests: Failed Building Evergreen <http://testing.evergreen-ils.org/~li​ve/test.30.html#2019-09-13T23:00:35,984300358-0400 -2>
23:01 pinesol News from qatests: Failed Running Evergreen tests <http://testing.evergreen-ils.org/~li​ve/test.31.html#2019-09-13T23:00:36,010826868-0400 -4>
23:01 pinesol News from qatests: Failed Installing Evergreen <http://testing.evergreen-ils.org/~li​ve/test.32.html#2019-09-13T23:00:36,037847027-0400 -6>
23:01 pinesol News from qatests: Failed Installing Dojo <http://testing.evergreen-ils.org/~li​ve/test.35.html#2019-09-13T23:00:36,064223614-0400 -8>
23:01 pinesol News from qatests: Failed configure apache <http://testing.evergreen-ils.org/~li​ve/test.36.html#2019-09-13T23:00:36,090612948-0400 -10>
23:01 pinesol News from qatests: Failed configure EG Action/Trigger <http://testing.evergreen-ils.org/~li​ve/test.38.html#2019-09-13T23:00:36,116895895-0400 -12>
23:01 pinesol News from qatests: Failed Create Evergreen Database <http://testing.evergreen-ils.org/~li​ve/test.41.html#2019-09-13T23:00:36,145694949-0400 -14>
23:01 pinesol News from qatests: Failed Running pgTAP tests <http://testing.evergreen-ils.org/~li​ve/test.42.html#2019-09-13T23:00:36,172049700-0400 -16>
23:01 pinesol News from qatests: Failed Running autogen.sh <http://testing.evergreen-ils.org/~li​ve/test.44.html#2019-09-13T23:00:36,200934410-0400 -18>
23:01 pinesol News from qatests: Failed Running pgTAP live tests <http://testing.evergreen-ils.org/~li​ve/test.47.html#2019-09-13T23:00:36,227835077-0400 -20>
23:01 pinesol News from qatests: Failed Running settings-tester.pl <http://testing.evergreen-ils.org/~li​ve/test.48.html#2019-09-13T23:00:36,254165199-0400 -22>
23:01 pinesol News from qatests: Failed Running perl live tests <http://testing.evergreen-ils.org/~li​ve/test.49.html#2019-09-13T23:00:36,280521322-0400 -24>
23:01 pinesol News from qatests: Failed Log Output: srfsh.log <http://testing.evergreen-ils.org/~li​ve/test.58.html#2019-09-13T23:00:36,306714957-0400 -26>
23:53 jvwoolf joined #evergreen

Results for 2019-09-12

09:44 aabbee joined #evergreen
09:46 rfrasur joined #evergreen
10:52 Dyrcona csharp++ # For sharing the proxy config.
11:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:18 csharp @praise Testing Success
11:18 * pinesol Testing Success LOVES the RESISTANCE!
11:20 jamesrf joined #evergreen
11:21 Dyrcona heh
11:21 Dyrcona @who loves the Resistance?
19:48 cmalm joined #evergreen
20:08 ejk__ joined #evergreen
21:12 stephengwills joined #evergreen
23:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>

Results for 2019-09-11

10:55 Dyrcona Something's definitely wrong with our ldirectord, but we have the latest version as far as I can tell, and the memory leaks were supposedly fixed years ago.
10:56 Dyrcona csharp: Are the rumors I hear that you run a custom ldirectord true?
11:00 rfrasur joined #evergreen
11:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:13 stephengwills joined #evergreen
11:21 Dyrcona backscatter--
11:31 yboston joined #evergreen
17:56 khuckins joined #evergreen
18:21 nfBurton joined #evergreen
18:53 cmalm_ joined #evergreen
23:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>

Results for 2019-09-10

10:34 Dyrcona berick: Should move the IDL commit to my other branch? I think putting the IDL fixes in one place is better.
10:37 berick i'd probably leave it in both and comment to that affect in LP1835085
10:39 Dyrcona OK.
10:41 phasefx_ random aside, the live tests for today did finish, but the ssh call to invoke installer_installer.sh remotely is hanging
10:41 Dyrcona I'm going to check a few more things on the server, make sure the IDL is valid, etc....
10:41 Dyrcona joined #evergreen
10:42 phasefx_ all tests passed
10:42 Dyrcona between resold and my wifi, It's a wonder I can do anything.
10:42 Dyrcona and typos, yay! :)
10:43 Dyrcona phasefx: good news.
10:58 tlittle47 joined #evergreen
10:59 Dyrcona action.open_circulation and circbyyr need auto_renewal added.
11:00 * Dyrcona will add them to the IDL branch.
11:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:04 Christineb joined #evergreen
11:11 Dyrcona This seems weird to me.  The action.open_circulation view is defined as select * from action.circuation where checkin_time is null order by due_date.  However, auto_renewal and auto_renewal_remaining don't show up in the column list. Does it need to be recreated, I wonder?
11:13 Dyrcona Same thing with action.billable_circulations....
13:44 jeff but we don't use metarecord holds much (and have them turned off for patrons, mostly)
13:45 collum joined #evergreen
13:57 bos20k joined #evergreen
14:26 mmorgan reproducibility++
14:27 mmorgan I was able to reproduce the NOT CONNECTED log entries by copying the xul client and web client copy template user settings to a test user. After clicking Add Holdings on a few bib records, I saw the error :)
14:28 mmorgan The xul templates are BIG
14:34 csharp @who is NOT CONNECTED TO THE NETWORK!!!?
14:34 pinesol gsams__ is NOT CONNECTED TO THE NETWORK.
14:35 * mmorgan also often feels that way :)
21:25 remingtron_ joined #evergreen
22:02 book` joined #evergreen
22:16 book`_ joined #evergreen
23:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
23:52 jvwoolf joined #evergreen

Results for 2019-09-09

07:04 agoben joined #evergreen
07:07 collum joined #evergreen
07:13 rjackson_isl joined #evergreen
07:18 bshum Oh hmm, I guess I didn't notice that pgTap failure with testing the password
07:18 bshum Quick guess is that the ID for the user we're testing moved when we added in the additional test users for the basic api auth testing :)
07:28 bshum Yup, id moved from 187 to 195.  Same thing happened last time we added new test users to concerto
07:28 bshum Might be a good time to rewrite the test to use another identifier to track that test user for validation
07:28 bshum Rather than ID
08:07 bshum gmcharlt: Pushed a third commit onto https://git.evergreen-ils.org/?p=workin​g/Evergreen.git;a=shortlog;h=refs/heads​/user/bshum/lp1817645-perl-test-fixes
08:08 bshum It should fix the test for passwd storage too
08:08 bshum And hopefully future proof it against further ID changes
08:09 csharp bshum++
08:09 bshum csharp: It was a fun little thought exercise :D
08:10 csharp I like those kinds of problems too
08:10 bshum I needed the practice for pgTap test writing
08:11 bshum Probably more ways to skin the cat, but baby steps...
08:11 csharp after the second week of October, when an 11-month-long leadership program I've been doing ends, my attention will be less divided and I'll be able to get serious about EG development again :-)
08:12 bshum Fun times!  :)
08:12 bshum Okay, off to the office for more fun and games in other SQL lands...
10:15 Dyrcona fine generator still running for over an hour. If it's still running at 11:00, I'll stomp on it, too.
10:22 Dyrcona So, here's a branch with the changes that I'm talking about not showing up: user/dyrcona/lp1835085-aut​o_renewal-not-desk_renewal
10:23 Dyrcona It's in the working repo, of course. The top commit has the template changes and the previous commit has back end changes.
10:24 Dyrcona I have also verified that I am testing with an auto-renewed circulation, i.e. I've verified the field in the database.
10:24 Dyrcona If it matters, I've been testing with the commits applied to Evergreen 3.2.8.
10:25 csharp @dessert add Browser Cookies
10:25 pinesol csharp: The operation succeeded.  Dessert #59 added.
10:26 csharp @dessert add Syntactic Sugar
10:39 Dyrcona What I'm seeing in the summary pane is an empty Renewal Type.  In the circ history list, Renewal? is false.
10:40 Dyrcona desk_renewal is false and auto_renewal is true on this particular circulation.
10:40 Dyrcona It's also the most recent circulation.
11:01 pinesol News from qatests: Failed Running pgTAP live tests <http://testing.evergreen-ils.org/~li​ve/test.47.html#2019-09-09T11:00:43,578501076-0400 -0>
11:01 pinesol News from qatests: Failed Running perl live tests <http://testing.evergreen-ils.org/~li​ve/test.49.html#2019-09-09T11:00:43,606230460-0400 -2>
11:06 Dyrcona And, killed the fine generator....
11:07 Dyrcona Storage has no running drones....figures....
11:08 Dyrcona I think I'm going to drop the parallel setting for the fine generator. I assume this is that bug that berick suspects but has not pinpointed with OpenSRF::MultiSession.
11:57 aabbee joined #evergreen
12:05 mmorgan joined #evergreen
12:08 jihpringle joined #evergreen
12:29 terranm Bmagic++ for setting up bug squashing test server! https://docs.google.com/spreadsheets/d/1qYNGrJB​t42_ArQzbwlcnKxS3TobDnmquSXZzopOkZh4/edit#gid=0
12:29 Bmagic ty!
12:34 collum_ joined #evergreen
12:36 bos20k joined #evergreen
15:22 Bmagic berick++
15:31 gmcharlt bshum: thanks for the work over the weekend. I've variously cherry-picked your patches or pushed alternative approaches
15:31 gmcharlt in particularly, I've elected not to add a new install-from-CPAN-dep for now
15:34 pinesol [evergreen|Galen Charlton] LP#1817645: (follow-up) avoid hardcoding user ID in a live_t test - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=a8f6ccf>
15:34 pinesol [evergreen|Ben Shum] LP#1817645: fix live perl test for basic auth API - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=c9404f6>
15:34 pinesol [evergreen|Galen Charlton] LP#1817645: adjust live_t remoteauth checks - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=0af1850>
15:40 Dyrcona Well, I think I figured out the mystery of auto_renewal not being set. it looks like the circ object is combcirc, which lacks the field, though I'm pretty sure that I added it to our IDL on training, but I'll double check.
15:41 Dyrcona Yep. I added it to the IDL on training, so why doesn't it show up in AngularJS?
15:41 Dyrcona It's in both IDLs, AFAICT.
15:52 Dyrcona Is it the grid? Does the grid need to be made aware of the field? Something to look into tomorrow morning.
15:58 Dyrcona No, that doesn't seem to be the problem, either.
16:14 pinesol [evergreen|Thomas Berezansky] Ensure "Reshelved" copies are still reshelving - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=2d000a9>
16:23 bshum gmcharlt++ # I like your fixes too :)
16:24 bshum I think I tried it that way for the auth passwd test this morning but got hung up on all the single quote extra quotes and other stuff so I gave up and declared from the beginning
16:25 JBoyer <Homer>Doh!</Homer>
16:25 JBoyer At least that's a simple commit to learn a lesson on. :/
16:27 bshum JBoyer++ # commit more, be happy :)
17:03 bshum It doesn't appear to have been setup with LP
17:03 bshum That whole process needs to be refactored anyways given how much is now supposed to be done in the new Poeditor site
17:03 bshum And is undocumented
17:08 pinesol [evergreen|Galen Charlton] Translation updates - newpot - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=a272265>
17:08 pinesol [evergreen|Galen Charlton] Translation updates - po files - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=33aeb89>
17:09 mmorgan left #evergreen
17:18 sandbergja joined #evergreen
17:40 sandbergja joined #evergreen
20:37 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-09-09T23:00:55,734252544-0400 -0>
23:01 pinesol News from qatests: Failed Running perl live tests <http://testing.evergreen-ils.org/~li​ve/test.49.html#2019-09-09T23:00:55,762498360-0400 -2>

Results for 2019-09-08

05:00 pinesol News from qatests: Failed Installing OpenSRF pre-requisites <http://testing.evergreen-ils.org/~l​ive/test.7.html#2019-09-08T04:45:37,588967130-0400 -0>
05:00 pinesol News from qatests: Failed Building OpenSRF <http://testing.evergreen-ils.org/~l​ive/test.9.html#2019-09-08T04:45:37,616133766-0400 -2>
05:01 pinesol News from qatests: Failed Running OpenSRF build tests <http://testing.evergreen-ils.org/~li​ve/test.10.html#2019-09-08T04:45:37,643261966-0400 -4>
05:01 pinesol News from qatests: Failed creating opensrf user and environment <http://testing.evergreen-ils.org/~li​ve/test.12.html#2019-09-08T04:45:37,670052378-0400 -6>
05:01 pinesol News from qatests: Failed configuring ejabberd <http://testing.evergreen-ils.org/~li​ve/test.15.html#2019-09-08T04:45:37,697153810-0400 -8>
05:01 pinesol News from qatests: Failed creating jabber users <http://testing.evergreen-ils.org/~li​ve/test.16.html#2019-09-08T04:45:37,724083776-0400 -10>
05:01 pinesol News from qatests: Failed configuring OpenSRF <http://testing.evergreen-ils.org/~li​ve/test.17.html#2019-09-08T04:45:37,751685289-0400 -12>
05:01 pinesol News from qatests: Failed start opensrf <http://testing.evergreen-ils.org/~li​ve/test.18.html#2019-09-08T04:45:37,778719304-0400 -14>
05:01 pinesol News from qatests: Failed stop opensrf <http://testing.evergreen-ils.org/~li​ve/test.19.html#2019-09-08T04:45:37,805681747-0400 -16>
05:01 pinesol News from qatests: Failed start opensrf <http://testing.evergreen-ils.org/~li​ve/test.20.html#2019-09-08T04:45:37,832641068-0400 -18>
05:01 pinesol News from qatests: Failed test opensrf <http://testing.evergreen-ils.org/~li​ve/test.21.html#2019-09-08T04:45:37,859382142-0400 -20>
05:01 pinesol News from qatests: Failed configuring websockets <http://testing.evergreen-ils.org/~li​ve/test.22.html#2019-09-08T04:45:37,886279588-0400 -22>
05:01 pinesol News from qatests: Failed stop opensrf <http://testing.evergreen-ils.org/~li​ve/test.23.html#2019-09-08T04:45:37,913149142-0400 -24>
05:01 pinesol News from qatests: Failed Installing Evergreen pre-requisites <http://testing.evergreen-ils.org/~li​ve/test.26.html#2019-09-08T04:45:37,940167346-0400 -26>
05:01 pinesol News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-09-08T04:45:37,966866093-0400 -28>
05:01 pinesol News from qatests: Failed Building Evergreen <http://testing.evergreen-ils.org/~li​ve/test.30.html#2019-09-08T04:45:37,993893592-0400 -30>
05:01 pinesol News from qatests: Failed Running Evergreen tests <http://testing.evergreen-ils.org/~li​ve/test.31.html#2019-09-08T04:45:38,021016559-0400 -32>
05:01 pinesol News from qatests: Failed Installing Evergreen <http://testing.evergreen-ils.org/~li​ve/test.32.html#2019-09-08T04:45:38,048219354-0400 -34>
05:01 pinesol News from qatests: Failed Change File Ownership <http://testing.evergreen-ils.org/~li​ve/test.33.html#2019-09-08T04:45:38,075283659-0400 -36>
05:01 pinesol News from qatests: Failed Installing Dojo <http://testing.evergreen-ils.org/~li​ve/test.35.html#2019-09-08T04:45:38,103904901-0400 -38>
05:01 pinesol News from qatests: Failed configure apache <http://testing.evergreen-ils.org/~li​ve/test.36.html#2019-09-08T04:45:38,130485884-0400 -40>
05:01 pinesol News from qatests: Failed configure EG OpenSRF <http://testing.evergreen-ils.org/~li​ve/test.37.html#2019-09-08T04:45:38,157130237-0400 -42>
05:01 pinesol News from qatests: Failed configure EG Action/Trigger <http://testing.evergreen-ils.org/~li​ve/test.38.html#2019-09-08T04:45:38,183979995-0400 -44>
05:01 pinesol News from qatests: Failed Create Evergreen Database <http://testing.evergreen-ils.org/~li​ve/test.41.html#2019-09-08T04:45:38,210903690-0400 -46>
05:01 pinesol News from qatests: Failed Running pgTAP tests <http://testing.evergreen-ils.org/~li​ve/test.42.html#2019-09-08T04:45:38,239757579-0400 -48>
05:01 pinesol News from qatests: Failed start opensrf <http://testing.evergreen-ils.org/~li​ve/test.43.html#2019-09-08T04:45:38,266705784-0400 -50>
05:01 pinesol News from qatests: Failed Running autogen.sh <http://testing.evergreen-ils.org/~li​ve/test.44.html#2019-09-08T04:45:38,293294847-0400 -52>
05: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-09-08T04:45:38,319808447-0400 -54>
05:01 pinesol News from qatests: Failed test EG opensrf <http://testing.evergreen-ils.org/~li​ve/test.46.html#2019-09-08T04:45:38,346509683-0400 -56>
05:01 pinesol News from qatests: Failed Running pgTAP live tests <http://testing.evergreen-ils.org/~li​ve/test.47.html#2019-09-08T04:45:38,373125960-0400 -58>
05:01 pinesol News from qatests: Failed Running settings-tester.pl <http://testing.evergreen-ils.org/~li​ve/test.48.html#2019-09-08T04:45:38,399692248-0400 -60>
05:01 pinesol News from qatests: Failed Running perl live tests <http://testing.evergreen-ils.org/~li​ve/test.49.html#2019-09-08T04:45:38,426314366-0400 -62>
05:01 pinesol News from qatests: Failed Gathering log summary <http://testing.evergreen-ils.org/~li​ve/test.50.html#2019-09-08T04:45:38,453108549-0400 -64>
05:01 pinesol News from qatests: Failed Log Output: config.log <http://testing.evergreen-ils.org/~li​ve/test.51.html#2019-09-08T04:45:38,479855669-0400 -66>
10:44 bshum Well that seems like a Debian problem to me :)
11:38 sandbergja joined #evergreen
12:03 pinesol [evergreen|Jane Sandberg] Docs: cleaning up headings in 3.4 release notes - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=3f4a956>
12:04 sandbergja bshum++ #catching db errors over the weekend
15:52 bshum Hmm, so installing LWP::Protocol::https from CPAN for Ubuntu 16.04 works fine, but on 18.04 it doesn't change anything and the test still fails :(
16:01 GreyAzazel joined #evergreen
16:02 GreyAzazel left #evergreen
16:05 r_mcauliffe joined #evergreen
16:25 bshum The distro installed version from 18.04 is 6.07 also
16:25 bshum Same as the one from CPAN
16:25 csharp oh
16:25 bshum I checked the actual code bits too, and they're the same
16:26 bshum So I think it's a problem with the IO::Socket::SSL
16:26 bshum Or one of the other related perl bits
16:27 bshum And something newer in 18.04 is reacting to the bad code in a different way than on 16.04
16:29 bshum Maybe this is the right approach:  https://stackoverflow.com/question​s/47662461/how-to-accept-self-sign​ed-certificates-with-lwpuseragent
16:30 bshum Having LWP::UserAgent accept the default generated SSL cert
16:30 bshum Though, I guess the SSL cert hostname might vary from test system to system... so that could be weird.
16:30 bshum And also "localhost" wouldn't match the SSL cert
16:30 bshum Seems problematic
16:32 bshum So yeah, I'm back to my suggestion to not do the test against https since it doesn't work consistently across all the testbeds
16:32 bshum And also the more I look at the eg_vhost.conf addition where we're putting a staff login to lookup user data with and having the credentials just sitting out there, that's questionable to me too
16:32 bshum For an out of the box install that is
16:40 bshum Oh I see, the docs are in TechRef, no release notes :\
16:42 kirchmeierl joined #evergreen
16:46 kirchmeierl joined #evergreen
17:18 bshum Hmm
17:23 bshum https://git.evergreen-ils.org/?p=workin​g/Evergreen.git;a=shortlog;h=refs/heads​/user/bshum/lp1817645-perl-test-fixes
17:23 bshum Those two commits worked for me on Ubuntu 18.04
17:23 bshum Retesting the whole branch on fresh Ubuntu 16.04 next
17:29 r_mcauliffe Hey Guys, I'm trying to install opensrf on debian-buster. Got the install working correctly, the make file needed to adjust the libgcrypt package for buster (Happy to upload my makefile changes to git soon). Everything installed correctly, and was following the install guide on the web and came across this problem while trying to start it:
17:30 r_mcauliffe Subroutine section_pkg redefined at (eval 921) line 4 (#1)
17:30 r_mcauliffe (W redefine) You redefined a subroutine.  To suppress this warning, say
17:41 bshum Or sending an email to the general or dev mailing lists  :)
17:42 bshum I'm just a casual volunteer who's poking at things in my offtime
17:42 r_mcauliffe will do, thank you bshum !
17:44 bshum Sure thing
17:44 bshum I haven't seen rabbitmq before, but I do know that OpenSRF is pretty specialized into how it is using (or abusing) ejabberd for messaging between the various bits
18:04 bshum jeffdavis: gmcharlt: So my branch works for solving the perl livetest for basic auth api on Ubuntu 16.04 and 18.04.  I have to test wider with Debian, but I don't have my cool Ansible setup for Debian finished yet to make the install simple and breezy
18:05 bshum I still have my doubts about using https for the test against localhost and ignoring the cert anyways, plus also now dumping additional pre-req stuff onto the installs that I'm not sure we will use everywhere
18:05 bshum But eh, working code wins?  :D
18:53 r_mcauliffe well rabbitmq would use erlang rather than ejabberd, but a very cut down version of it. I was just thinking if there is a product that could be usable that would suit evergreens purpose than something y'all have to maintain, might be worth looking into. But like I said VERY new to this, so my opinion counts for diddly squat lol
19:09 r_mcauliffe left #evergreen
19:40 sandbergja joined #evergreen
20:05 sandbergja joined #evergreen
20:13 sandbergja joined #evergreen
20:48 sandbergja joined #evergreen
23:01 pinesol News from qatests: Failed Running pgTAP live tests <http://testing.evergreen-ils.org/~li​ve/test.47.html#2019-09-08T23:00:57,525131392-0400 -0>
23:01 pinesol News from qatests: Failed Running perl live tests <http://testing.evergreen-ils.org/~li​ve/test.49.html#2019-09-08T23:00:57,553207498-0400 -2>

Results for 2019-09-07

09:08 aabbee joined #evergreen
09:28 csharp bshum++
11:02 pinesol News from qatests: Failed Running pgTAP live tests <http://testing.evergreen-ils.org/~li​ve/test.47.html#2019-09-07T11:00:49,903620999-0400 -0>
11:02 pinesol News from qatests: Failed Running perl live tests <http://testing.evergreen-ils.org/~li​ve/test.49.html#2019-09-07T11:00:49,931658935-0400 -2>
12:05 bshum Hmm
12:06 bshum So that PGTap test isn't so bad to fix.  We're missing some closing parenthesis in the tests
12:06 bshum And one of the test parameters returned a different result than the actual thing being matched
12:06 bshum I guess an Inactive patron returns "not_found" rather than "blocked"
12:07 * bshum makes a patch to toss on followup
12:07 bshum And then I'll see what this perl live test is balking at next :)
12:22 bshum Hmm
12:23 bshum That live perl test failure seems more complicated
12:23 bshum https://bugs.launchpad.net/eve​rgreen/+bug/1817645/comments/1
12:23 pinesol Launchpad bug 1817645 in Evergreen "Configurable patron auth and retrieval" [Wishlist,Fix committed]
12:24 bshum In jeffdavis comments on the feature, they described a bug with LWP::Protocol::https that required a newer version from CPAN to resolve, 6.07 and greater
12:24 bshum Couple issues... that dependency isn't in the core Makefile.install for the various distros
12:25 bshum But also, on Ubuntu 18.04, I have the latest version of that package, and I'm still unable to get successful test results from the API test
12:25 * bshum pushes the pgtap fix patch first, and then goes to contemplate lunch
12:29 pinesol [evergreen|Ben Shum] LP#1817645: Fix pgtap tests - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=1421240>
12:41 bshum So it's definitely the certificate error affecting the running of the test
12:41 bshum Changing the endpoint to http://localhost (without the https) allowed it to succeed
12:43 bshum I'd be tempted to let that be the permanent change for the purposes of the test, since the access is restricted to localhost only anyways
12:43 bshum and in a real productive environment, someone should be changing it to have a real SSL cert, have real auth user to look up data (rather than the default admin account), etc.
12:43 bshum So........... hmm, I'll ponder that
12:43 bshum While I eat my sandwich :D
13:38 jeffdavis I think the Ubuntu package for LWP::Protocol::https is installed as a dependency when you install libwww-perl, so should be available on any system running OpenSRF. It would make sense for Makefile.install to the later non-buggy version from CPAN though.
13:54 jeffdavis Switching to http doesn't feel great but it does still confirm whether the API endpoint is returning correct responses, which is the purpose of the test.
15:54 sandbergja joined #evergreen
18:27 bshum jeffdavis: I haven't read enough and finished spinning older distro VMs, but if the bug is only from those SSL checks, then switching to http for the test would resolve for everybody's tests
18:28 bshum Without needing to upgrade that package
18:28 bshum And if I've already got the latest package on 18.04 and it's still broken, that seems like there's something deeper problematic with it than just the version
18:34 bshum also systemd-- # apt.systemd.daily install is super annoying
18:39 * bshum finishes setting up fresh Ubuntu 16.04 to retest
19:41 bshum So much faster to clone virtualbox VMs once they've been compacted down in size, whee!
20:07 bshum Very interesting
20:07 bshum So, on Ubuntu 16.04, changing it to http for the test, definitely makes it work.  So that's consistent
20:08 bshum But also installing LWP::Protocol::https via CPAN and restarting apache, also lets the test proceed happily too
20:08 bshum I wonder why that's different on Ubuntu 18.04 now, hmm
21:43 bshum Reading https://github.com/libwww-perl​/LWP-Protocol-https/issues/47 and based on the source for LWP::Protocol::https, I think it's still broken
21:52 bshum Seems to me that if we're passing the value to ignore SSL cert anyways, we're already not paying attention to the security as part of the test
21:52 bshum So having it go to http instead of https seems moot
22:27 sandbergja joined #evergreen
23:02 pinesol News from qatests: Failed Running pgTAP live tests <http://testing.evergreen-ils.org/~li​ve/test.47.html#2019-09-07T23:00:56,032084177-0400 -0>
23:02 pinesol News from qatests: Failed Running perl live tests <http://testing.evergreen-ils.org/~li​ve/test.49.html#2019-09-07T23:00:56,061217285-0400 -2>

Results for 2019-09-06

11:01 berick Dyrcona: you have to raise the upload size..
11:02 berick e.g.         client_max_body_size 25m;
11:02 Dyrcona nginx, I presume.
11:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:02 Dyrcona berick: How's Dorian treating you? My family's in the thick of it in Wilmington.
11:02 berick well, what I posted was for uploading files for import
11:02 berick not sure if that's what you meant
15:02 pinesol [evergreen|Galen Charlton] LP#1840327: add release notes - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=b577e78>
15:02 Dyrcona Ah... That will do it.
15:20 zbanks joined #evergreen
15:27 csharp Dyrcona: https://drive.google.com/file/d/1GBwpFLxP​Z79sBsP0zcXSdX-_eGm4OWnl/view?usp=sharing - the second indicator column is misaligned
15:28 csharp if I remove some of the long text in one of the fields (or reduce the zoom enough) it corrects
15:29 csharp I also played with the CSS padding in dev tools and corrected it that way too
15:30 csharp the problem didn't exist in the new ng staff catalog when I tested that on one of the "problem" records
15:30 csharp but does in the AngJS version on current-ish master
15:33 Dyrcona csharp: Maybe that's what they were trying to explain to me yesterday. I was told it happens with tags that have a second indicator.
15:34 Dyrcona I looked at the MARC edit view and not that one, let me look at the bibs they sent me again.
15:34 Dyrcona I also was not sent screen shots.
16:09 jeff Dyrcona, csharp: does this happen in the opac, or only in the web staff client?
16:09 Dyrcona Haven't checked the OPAC.
16:10 jeffdavis gmcharlt: bug 1662297 is a bugfix rather than a feature request, but the pullrequest would involve changes to the install process so may be worth a look for the 3.4 beta (you know, in all that spare time you have right now)
16:10 pinesol Launchpad bug 1662297 in Evergreen "Install directory hardcoded in web client build and tests" [Low,Confirmed] https://launchpad.net/bugs/1662297
16:12 Dyrcona Well, my OPAC isn't returning results for tcn searches and I did not make a note of the titles, plus I'm off the clock, so not putting much more effort into it. :)
16:22 bwicksall joined #evergreen
16:30 Dyrcona And, I just got a Firefox update to install. If I remember, I'll look at that again on Monday.
17:20 pinesol [evergreen|Galen Charlton] LP#1817645: (follow-up) sync schema update script - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=56bab3e>
17:20 pinesol [evergreen|Galen Charlton] LP#1817645: stamp schema update - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=e850739>
17:20 pinesol [evergreen|Galen Charlton] LP#1817645: add release notes - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=46c8e3a>
17:22 gmcharlt jeffdavis: re 1662297, I'm willing to consider it for the 3.4-rc, but won't make it into the beta given the time I would need to test it properly
17:22 jeffdavis ok
17:37 * gmcharlt claims 1181
17:42 pinesol Showing latest 5 of 8 commits to Evergreen...
18:15 jeffdavis gmcharlt++
21:09 tlittle joined #evergreen
22:36 sandbergja joined #evergreen
23:02 pinesol News from qatests: Failed Create Evergreen Database <http://testing.evergreen-ils.org/~li​ve/test.41.html#2019-09-06T23:00:54,913184280-0400 -0>
23:16 bshum Oops, well that's fun.  Duplicate key constraint in the seed data
23:28 bshum Looks like some stuff snuck back in after the cleanup done in eee5c5948ca
23:29 pinesol bshum: [evergreen|Dan Wells] LP#1759343 Clean up data seed values - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=eee5c59>
23:31 bshum That led to the duplicate settings error
23:31 bshum Removing them again should fix things up
23:39 pinesol [evergreen|Ben Shum] LP#1816475: Cleanup 950.data.seed-values.sql - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=5d9bc66>
23:59 bshum And much better on my test server :)
23:59 * bshum sleeps more happily now

Results for 2019-09-05

10:59 jeff ...or a logins table, and avoid updating actor.workstation on each and every login.
10:59 jeff but useful any way you spell it.
11:00 mmorgan At the very least a create date would be useful.
11:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:02 jeff all the metadata.
11:02 jeff create date, creating user, etc. :-)
11:04 zbanks joined #evergreen
13:12 rsoulliere joined #evergreen
13:12 Dyrcona berick: PhantomJS is dead, i.e. archived, and the person who was going to take it over and modernize it, gave up.
13:13 * Dyrcona considered doing so, since it uses Qt Webkit, but no time....
13:13 Dyrcona We should find an alternative for testing JS, like headless Chromium if that really is an option.
13:13 berick Dyrcona: i agree
13:14 Dyrcona Again, I'm short on time, so.... It's easy for me to say these things. :)
13:19 khuckins joined #evergreen
14:17 dluch dbs++
14:17 rsoulliere I will have more info about the server situation.
14:17 remingtron dbs++
14:17 dluch Then sandberja made a copy of the docs on a test page, http://docs-testing.evergreen-ils.org/.  Thanks, sandberja!
14:17 dluch sandbergja++
14:17 jweston dbs++
14:17 dluch Thanks, rsoulliere
14:17 remingtron sandbergja++
14:33 dluch gmcharlt++
14:33 dluch #info Documentation server needs
14:34 dluch I wasn't sure who added this one, but rsoulliere, it was you, I assume
14:34 rsoulliere At Mohawk, library access to servers required to maintain the docs is being questioned by IT. We are still negotiating with our IT overlords to regain access. Could http://docs-testing.evergreen-ils.org be made the live docs server since it is working? In fact, we should probably have multiple servers at a few institutions in a mirror set up for mo
14:34 rsoulliere re  reliability/redundancy going forward.
14:34 dluch Take it away!
14:37 dluch redundancy does sound like a good idea
14:37 gmcharlt rsoulliere: from the perspective of a member of the infrastructure team... we would be happy to accommodate
14:37 gmcharlt specificaly, working out a plan to put on a new docs VM on the hosting platform that GPLS and BOR are kindly continuing to donate to the project
14:37 dluch gmcharlt: I was just in the middle of typing a question about that.  Good, thanks!
14:38 gmcharlt if docs-testing becomes the new one, we'll need to plan on moving it to the new GPLS hosting anyway, but we can readily sort out such details
14:39 rsoulliere Was there any assistance you needed from me by working on the server or developing a git repo with the tools/instructions for setting up? Or was that covered?
14:39 dluch so, is that something the infrastructure team can take on to tackle?
14:40 gmcharlt yeah, in conjunction with rsoulliere (and yeah, I think we would want help and/or infodumps to make sure that the setup is suitable for the docs needs)
19:27 stephengwills joined #evergreen
20:56 HomerPublic joined #evergreen
21:40 dbs gmcharlt: https://bugs.launchpad.net/evergreen/+bug/1517298 has a working patch for Matomo, although ideally it would use OU settings instead of config.tt2
21:40 pinesol Launchpad bug 1517298 in Evergreen "Catalogue should support Matomo, a privacy-sensitive alternative to Google Analytics" [Wishlist,New]
23:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
23:59 jeff joined #evergreen

Results for 2019-09-04

10:49 rhamby_ one could argue that the creation of a distinction between upper and lowercase was just a bad idea .....
10:50 Bmagic In writing as well.....
10:55 khuckins joined #evergreen
11:02 pinesol News from qatests: Failed Running Evergreen tests <http://testing.evergreen-ils.org/~li​ve/test.31.html#2019-09-04T11:00:52,122990657-0400 -0>
11:05 sandbergja joined #evergreen
11:16 sandbergja Hmmm... looks like I forgot to stamp the upgrade script for carousels when I pushed it yesterday
11:18 Dyrcona sandbergja: Easy enough to fix.
11:18 yboston joined #evergreen
11:19 sandbergja I can plan to do that later today
11:27 sandbergja And also look into the failed qa test
11:30 csharp @who failed the QA test?
11:30 pinesol jeff_ failed the QA test.
11:31 mmorgan If our usernames were normalized, we could blame jeff ;-)
11:41 csharp @blame the usernames
11:41 pinesol csharp: the usernames must eat cottage cheese!
18:16 jihpringle joined #evergreen
19:23 sandbergja joined #evergreen
20:58 sandbergja joined #evergreen
23:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
23:54 sandbergja joined #evergreen

Results for 2019-09-03

08:56 pinesol csharp: [evergreen|Remington Steed] LP#1721036: Add url to item tags (DB, IDL, and OPAC link) - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=d87ad5f>
08:56 csharp (fix for bug 1721036 )
08:56 pinesol Launchpad bug 1721036 in Evergreen "Add the ability for copy tags to be links" [Wishlist,Fix committed] https://launchpad.net/bugs/1721036
08:57 csharp I trusted the signoff without additional testing, and now I've learned not to do that :-/
09:00 JBoyer joined #evergreen
09:05 jvwoolf joined #evergreen
09:07 dbwells csharp: autogen and/or reporter IDL issue?
10:40 JBoyer-alt left #evergreen
11:11 JBoyer-alt joined #evergreen
11:11 Christineb joined #evergreen
11:12 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:16 yboston joined #evergreen
11:17 Dyrcona berick: If you're around.... So, we had an incident with the load balancer this morning. And, now I've had reports of a couple of staff being logged out of Evergreen. I'm looking into it, and don't know if they're related.  Thought maybe we could followup with the email discussion in here.
11:21 * berick replied on-list for completeness sake
22:33 bshum gmcharlt: I added some thoughts on https://bugs.launchpad.net/evergreen/+bug/1830749 and proposed how we might note the PG minimum version in the release notes when they are compiled. I wasn't sure how best to include high level content like that based on the current design
22:33 pinesol Launchpad bug 1830749 in Evergreen "increase minimum version of PostgreSQL for Evergreen 3.4" [Wishlist,Confirmed]
22:33 bshum Maybe something to ponder for next release notes automated building.
22:41 pinesol Showing latest 5 of 17 commits to Evergreen...
22:41 pinesol [evergreen|Bill Erickson] LP1832897 Carousel local admin link repair - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=b81a489>
22:41 pinesol [evergreen|Jane Sandberg] LP1832897: Marking some carousel fields required in the IDL - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=c33fce5>
22:41 pinesol [evergreen|Mike Rylander] LP1832897: Belt-and-suspenders for making sure max_items is set - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=94fb41c>
22:41 pinesol [evergreen|Mike Rylander] LP1832897: Avoid query errors related to optional carousel filters - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=dc8457e>
22:41 pinesol [evergreen|Jane Sandberg] LP1832897: One more carousel local admin link repair - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=6631e78>
23:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
23:34 jvwoolf joined #evergreen
23:40 sandbergja joined #evergreen

Results for 2019-09-02

02:36 sandbergja joined #evergreen
09:03 yboston joined #evergreen
11:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:17 sandbergja joined #evergreen
13:09 yboston joined #evergreen
13:14 sandbergja joined #evergreen
16:07 remingtron_ joined #evergreen
17:28 Christineb joined #evergreen
23:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
23:32 sandbergja joined #evergreen

Results for 2019-09-01

03:40 jyorio joined #evergreen
03:41 akilsdonk joined #evergreen
03:41 miker joined #evergreen
09:11 pinesol [evergreen|Galen Charlton] LP#1790169: ensure that the sort priority actually gets saved - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=1ea0735>
09:11 pinesol [evergreen|Jason Etheridge] lp1790169 call compileSort after closing showColumnDialog - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=001edcb>
09:51 pinesol [evergreen|Remington Steed] LP#1721036: Add url to item tags (DB, IDL, and OPAC link) - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=d87ad5f>
11:10 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:23 sandbergja joined #evergreen
13:44 sandbergja joined #evergreen
14:31 kip joined #evergreen
14:43 sandbergja joined #evergreen
23:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>

Results for 2019-08-31

10:24 sandbergja joined #evergreen
11:03 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
13:01 jonadab joined #evergreen
13:18 sandbergja joined #evergreen
13:26 cmalm joined #evergreen
19:54 sandbergja_ joined #evergreen
21:40 sandbergja joined #evergreen
22:06 sandbergja joined #evergreen
23:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>

Results for 2019-08-30

09:29 pinesol Launchpad bug 1840669 in Evergreen 3.3 "Aging Circulations Removes Auto-Renewal Information" [High,Confirmed] https://launchpad.net/bugs/1840669
09:30 Dyrcona Also, if you feel like bumping the importance of Lp 1835577 that would be fine with me. I'm not sure how important it is, since I don't do reports, myself.
09:30 pinesol Launchpad bug 1835577 in Evergreen 3.3 "Combined Aged and Active Circulations Report Source not Exposed to Auto-Renewal Fields" [Undecided,Confirmed] https://launchpad.net/bugs/1835577
09:33 Dyrcona I also have a branch for Lp 1839002 but haven't added it to the bug, yet, because we haven't tested it. I plan to install it on training at the end of the day today.
09:33 pinesol Launchpad bug 1839002 in Evergreen "auto_renewal field stored as NULL/TRUE. Should be FALSE/TRUE" [High,In progress] https://launchpad.net/bugs/1839002 - Assigned to Jason Stephenson (jstephenson)
09:33 Dyrcona It takes a while to update the existing fields.
09:34 Dyrcona I will likely have something for Lp 1835085 by lunch time.
10:54 Dyrcona What does everything about removing an api in a bug fix. I think this api (open-ils.circ.renew.auto) was added as a result of misunderstanding.  The feature could easily have been implemented with an auto_renewal flag, the same way that sip_renewal and opac_renewal work.
11:02 * Dyrcona "deprecates" it....
11:02 bos20k joined #evergreen
11:03 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:22 bos20k joined #evergreen
11:43 yboston joined #evergreen
11:49 jihpringle joined #evergreen
13:12 yboston joined #evergreen
13:16 Dyrcona gsams: To be clear, auto renewal and OPAC renewal are doing the same thing, so changing the setting for the OPAC renewals affects auto renewals. I was mildly surprised when I saw that in the code this morning, but none of my patches change that behavior.
13:22 * mmorgan realizes she misspoke earlier regarding "all renewals". Should have read *opac* renewals
13:25 * Dyrcona has a branch for that ready, too, but will wait to push it until after we've tested it. May be typos, etc.
13:26 Dyrcona By "push it" I mean to the working repo.
13:30 khuckins joined #evergreen
13:34 yboston joined #evergreen
20:13 sandbergja joined #evergreen
20:23 sandbergja joined #evergreen
22:19 sandbergja joined #evergreen
23:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>

Results for 2019-08-29

10:54 yboston joined #evergreen
10:54 miker mmorgan: they were flushed (all but local storage, for the ws values)
10:55 miker bah, same result in firefox
10:55 Bmagic Everyone knows the real test results come from IE
10:56 miker IE 5, to be exact
10:56 Bmagic "It ain't broke if it works in Internet Explorer"
10:59 Bmagic I installed Windows 95 on a VM recently. Hilarious. IE 1.0
10:59 Dyrcona Pfft... It's just plain broken.
11:00 Bmagic The days when you had to "install" TCP/IP
11:03 pinesol News from qatests: Failed Create Evergreen Database <http://testing.evergreen-ils.org/~li​ve/test.41.html#2019-08-29T11:00:49,587271975-0400 -0>
11:04 Dyrcona Eh, well, the Internet was "new..."
11:04 gmcharlt ^ bah, humbug
11:04 gmcharlt er, ^^^

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 149 150