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

Results for 2019-12-20

06:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
06:47 rfrasur joined #evergreen
07:00 agoben joined #evergreen
07:05 rjackson_isl joined #evergreen
16:49 jeff we did a fine forgiveness month in december, and the board just approved $0 overdue fines for youth and young adult materials last night.
16:50 mmorgan :)
17:05 mmorgan left #evergreen
18:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:31 dbwells_ joined #evergreen
18:52 abowling1 joined #evergreen
19:11 abowling joined #evergreen

Results for 2019-12-19

06:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
06:53 remingtron_ joined #evergreen
06:58 agoben joined #evergreen
07:02 rfrasur joined #evergreen
10:20 nfBurton Just click on the top nav bar before hitting the hotkey. We are just finishing RFID enabling our library with PV Supa products
10:20 jeff yes, galen had a candidate fix for that which I was looking at the other day, as part of bug 1437106
10:20 pinesol Launchpad bug 1437106 in Evergreen "keyboard shortcuts in the web staff client" [Undecided,Confirmed] https://launchpad.net/bugs/1437106
10:21 jeff and yes, there is the "just click a menu / navbar area before pressing the hotkey" workaround, but I would like to work to make that no longer necessary.
10:22 jeff mostly because it fails my absurdity test. i feel absurd telling someone about the required workaround. :-)
10:22 Dyrcona If you want "hot keys" for everything, you don't want a browser-based application, just repeatin' myself, I know.....
10:22 dbs nfBurton: right, the issue here is that the Bibliotheca software wants F1 / F2 for its own use, but the web staff client is trapping them first
10:23 Dyrcona Actually, you probably want a GNU Emacs mode. :)
17:18 Dyrcona :)
17:37 sandbergja_ joined #evergreen
17:38 abowling left #evergreen
18:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
20:06 Dyrcona joined #evergreen
21:33 * dbs is so happy to see people talking about password resets
21:34 dbs Oh, for the logs, i was able to resolve the Bibliotheca SmartStation "how do we get the barcodes into the web staff client?" issue

Results for 2019-12-18

00:10 sandbergja_ joined #evergreen
00:25 jvwoolf joined #evergreen
01:36 genpaku joined #evergreen
06:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
06:59 agoben joined #evergreen
07:10 rjackson_isl joined #evergreen
07:20 rfrasur joined #evergreen
17:21 sandbergja_ joined #evergreen
17:31 khuckins_ joined #evergreen
17:32 akilsdonk joined #evergreen
18:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:40 jihpringle joined #evergreen
19:01 cmalm_ joined #evergreen
21:44 sandbergja_ joined #evergreen

Results for 2019-12-17

00:44 sandbergja_ joined #evergreen
04:19 serflog joined #evergreen
04:19 Topic for #evergreen is now Welcome to the #evergreen library system channel! | We are publicly logged: http://irc.evergreen-ils.org/evergreen | Large pastes at http://paste.evergreen-ils.org | Can't speak? Make sure your nickname is registered and that you are identified to freenode services: https://freenode.net/kb/answer/registration
06:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
06:56 agoben joined #evergreen
07:11 Dyrcona joined #evergreen
08:02 rfrasur joined #evergreen
08:13 rhamby every day qa tests succeed a non-denominational spirit entity gets it's wings
08:13 alynn26 lol
08:15 rjackson-isl-hom joined #evergreen
08:17 mantis1 joined #evergreen
14:16 jeff blongwel: were the items checked in with the checkin modifier to retarget local holds? were the transits to another library, or to the checkin library (a la "capture local holds as transits")?
14:16 jeff blongwel: and, what version of Evergreen?
14:25 Dyrcona I'm pretty sure there's a Lp bug for this already, but damned if I can find it: I just encountered a situation where paying off bills on 8 circulations set xact_finish on all but 1 of the transactions, and they were all renewed just before paying the bills.
14:28 Dyrcona Renewal actually generated the bills, since I haven't run the fine generator on this test system.
14:33 jeff doesn't ring a bell. anything (else) unusual about the one transaction?
14:34 jeff renewal operation completed before the bills were paid?
14:34 jeff fine generation on checkin (renewal) doesn't kick off anything async in the background, does it?
14:58 Dyrcona blongwel: I don't think the hold_targeter is at issue, though it might be. We run ours every 15 minutes.
14:58 Dyrcona mmorgan++ I knew there had to be a bug, but Lp search is terrible.
14:58 mmorgan I run across that occasionally, too, usually comes to light when staff try and delete a patron record.
15:02 Dyrcona Well, I found it while looking into a previous patron's circulation being aged for an item after it was renewed to the current patron. I had data from before and was seeing what happened on my test system, so thought I'd "pay" the bills, too.
15:02 Dyrcona And, I think what I was looking into could be considered a bug, depending on your perspective.
15:02 mmorgan1 joined #evergreen
15:04 Dyrcona It's bugs all the way down. :)
16:39 khuckins joined #evergreen
16:52 sandbergja_ joined #evergreen
17:00 mmorgan left #evergreen
18:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:06 Dyrcona joined #evergreen
19:09 cmalm joined #evergreen
19:39 csharp_ joined #evergreen

Results for 2019-12-16

05:10 dbs joined #evergreen
05:10 berick joined #evergreen
05:55 remingtron_ joined #evergreen
06:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
07:12 rjackson_isl joined #evergreen
07:19 rfrasur joined #evergreen
08:41 mmorgan joined #evergreen
14:17 khuckins joined #evergreen
14:26 jeffdavis As much as I dislike npm, I don't know if it's substantially worse on security etc than any other tools/libraries that we use.
14:27 Dyrcona I think it is worse than apt, but I have little proof. There's a real problem of trust, and I trust npm much less than I do apt.
14:28 Dyrcona Also, I think I understand why chromium and firefox were added to the distro *-developer Makefile.install targets, but I'm not so sure I like that, either. If I'm installing via git in production, which I do, and I'm not gonna run tests, those packages are dead weight.
14:29 Dyrcona Not to mention all of the dependencies on those packages.
14:30 Dyrcona I guess that's yet-another-local-patch-branch to maintain.....
14:37 Dyrcona I thought we jumped to Node v12 lately? Is that just in master?
14:37 berick for ang8
14:37 Dyrcona berick++ # I was just about to compare 3.4.1 and master.
14:41 Dyrcona Am I right that upgrading npm breaks the Evergreen install process?
14:41 jeffdavis The browsers were added because they were the best alternative for running tests. There was some discussion about separating out a -tester target but you want devs to run tests; maybe there should be a -developer-minimal target or something instead to allow installing from git without the test stuff.
14:43 Dyrcona jeffdavis: Yes, that's my understanding, and I didn't say much during the discussion. I'm not sure that I want a new dependency target, so I'll live with it for now.
14:44 Dyrcona Hmm... could be a *-git target that is made a requirement of the *-developer targets.....
15:39 gerlevi joined #evergreen
15:58 jvwoolf joined #evergreen
16:22 sandbergja_ joined #evergreen
17:03 mmorgan left #evergreen
18:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
22:13 cmalm joined #evergreen
22:14 sandbergja_ joined #evergreen
22:34 cmalm joined #evergreen

Results for 2019-12-15

00:25 sandbergja_ joined #evergreen
06:00 pinesol News from qatests: Failed Building the AsciiDoc output formats <http://testing.evergreen-ils.org/~live//arch​ive/2019-12/2019-12-15_04:00:02/test.81.html>
10:12 sandbergja_ joined #evergreen
10:40 dbs Ah I think asciidoc is unhappy about the "= Glossary =" heading in root.adoc being followed immediately by another heading (in this case, "= Glossary =" again) with no text in between
10:40 * dbs tries fixing that up
11:05 dbs That should do the trick. Although there are still other problems throwing things off.
11:06 pinesol [evergreen|Dan Scott] Fix doc build for glossary - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=29d5c4e>
11:09 sandbergja_ joined #evergreen
15:53 yar joined #evergreen
16:03 sandbergja_ joined #evergreen
18:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
21:28 sandbergja_ joined #evergreen
23:16 sandbergja_ joined #evergreen

Results for 2019-12-14

01:33 jvwoolf joined #evergreen
03:35 remingtron_ joined #evergreen
03:57 remingtron joined #evergreen
04:44 pinesol News from qatests: Failed Installing OpenSRF pre-requisites <http://testing.evergreen-ils.org/~live//arch​ive/2019-12/2019-12-14_04:00:03/test.7.html>
11:51 sandbergja_ joined #evergreen
13:23 sandbergja_ joined #evergreen
14:32 sandbergja_ joined #evergreen
18:00 pinesol News from qatests: Failed Building the AsciiDoc output formats <http://testing.evergreen-ils.org/~live//arch​ive/2019-12/2019-12-14_16:00:02/test.81.html>
20:36 jvwoolf1 joined #evergreen
20:53 sandbergja_ joined #evergreen
21:10 jvwoolf joined #evergreen

Results for 2019-12-13

00:10 jvwoolf joined #evergreen
00:53 jvwoolf joined #evergreen
01:45 pinesol News from qatests: Failed Building the AsciiDoc output formats <http://testing.evergreen-ils.org/~live//arch​ive/2019-12/2019-12-13_00:56:14/test.81.html>
01:46 phasefx starting now these should be permanent links
02:17 sandbergja joined #evergreen
02:27 sandbergja joined #evergreen
04:03 sandbergja joined #evergreen
06:00 pinesol News from qatests: Failed Building the AsciiDoc output formats <http://testing.evergreen-ils.org/~live//arch​ive/2019-12/2019-12-13_04:00:02/test.81.html>
06:51 collum joined #evergreen
06:55 agoben joined #evergreen
07:06 rjackson_isl joined #evergreen
07:37 rfrasur joined #evergreen
08:17 bwicksall joined #evergreen
08:34 pinesol [evergreen|Remington Steed] Docs: Fix AsciiDoc syntax error in glossary - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=6ad5393>
08:34 mantis1 joined #evergreen
08:36 alynn26 joined #evergreen
08:46 mmorgan joined #evergreen
08:49 mantis1 I asked a question the other day about the Hatch extension for a Mac.  Is it possible once the files are pulled using git that those same files can be compiled into an express installer?
08:51 Dyrcona joined #evergreen
09:02 Dyrcona I'm trying to find a date that would be a good proxy for when we last copied the data from production to a training server that runs the action trigger runners and has been used for training and testing of circulation and cataloging. Can anyone think of a date column that's not likely to have changed?
09:05 Dyrcona Hmm... acq.purchase_order only has 27,012 rows. I can probably list all the dates in there to get an estimate. We have been testing acq on training, too, but there should be only a handful of rows after the data was copied.
09:07 mmorgan Dyrcona: How about the most recent date that shows a production level count of action.circulation rows?
09:07 Dyrcona mmorgan: Um, what?
09:08 mmorgan select date(xact_start), count(*)
13:30 sandbergja joined #evergreen
13:48 khuckins joined #evergreen
14:25 * berick calls 1197
14:37 pinesol Showing latest 5 of 11 commits to Evergreen...
14:37 pinesol [evergreen|Bill Erickson] LP1830391 Hatch core mod import/export repairs - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=878333b>
14:37 pinesol [evergreen|Bill Erickson] LP1830391 Angular Hatch enabled flag lookup repair - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=8e1e39d>
14:37 pinesol [evergreen|Bill Erickson] LP1830391 Warn on dupe workstation settings - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=49b4bf3>
14:37 pinesol [evergreen|Bill Erickson] LP1830391 Angular test spec updates for Hatch store updates - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=71c5401>
14:37 pinesol [evergreen|Bill Erickson] LP1830391 Stamping DB upgrate (hatch omnibus) - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=10c1c8f>
14:44 berick wondering if a web team member could update the Hatch download link on the EG downloads page to https://evergreen-ils.org/downl​oads/Hatch-Installer-0.3.2.exe
14:47 * berick will email if no one's around
14:47 khuckins_ joined #evergreen
14:55 sandbergja joined #evergreen
16:08 mantis1 left #evergreen
16:10 gerlevi joined #evergreen
18:00 pinesol News from qatests: Failed Building the AsciiDoc output formats <http://testing.evergreen-ils.org/~live//arch​ive/2019-12/2019-12-13_16:00:02/test.81.html>
21:28 sandbergja_ joined #evergreen
22:02 sandbergja_ joined #evergreen
22:55 sandbergja_ joined #evergreen

Results for 2019-12-12

00:46 sandbergja joined #evergreen
03:24 sandbergja joined #evergreen
05:31 rfrasur joined #evergreen
06:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
07:01 agoben joined #evergreen
08:00 Dyrcona joined #evergreen
08:11 rfrasur joined #evergreen
10:52 * Dyrcona thinks it might not be so bad after all, but it remains to be seen.
11:14 * mmorgan is still wondering about poprel if miker has any more insight since http://irc.evergreen-ils.org/​evergreen/2019-12-11#i_430114
11:19 miker mmorgan: I won't have time today to really dig into it, but I'll be looking at search stuff next week, so I'll be in the right brain space then (sorry)
11:22 mmorgan Ok, thanks! will keep poking test systems in the meantime
12:08 Christineb joined #evergreen
12:10 mantis1 Got a question regarding Hatch.  My supervisor got an email from an employee asking how to enable the Hatch extension on her browser on her Mac and she led her to these instructions: https://git.evergreen-ils.org/?p=working​/Hatch.git;a=blob;f=INSTALL.adoc;h=2de29​bb97135142c4a014fcbf32ef04287e01871;hb=f​f8eafb089f61930cdf34c374020c1d3eacbd9fb  Thinking about it, most library staff who need to enable Hatch on Macs probably wo
12:10 mantis1 to execute these instructions without some guidance or having someone familar with git to do it.  Has anyone found an alternative that has helped?
16:46 cesardv joined #evergreen
17:06 mmorgan left #evergreen
17:34 jeffdavis too early to be definitive, but it's looking like >90% reduction in open-ils.actor.ou_setting.ancestor_default.batch requests with the fix for bug 1848550, very encouraging
17:34 pinesol Launchpad bug 1848550 in Evergreen "Cache settings more aggressively in web client" [Undecided,New] https://launchpad.net/bugs/1848550
18:00 pinesol News from qatests: Failed Building the AsciiDoc output formats <http://testing.evergreen-ils.org/~li​ve/test.81.html#2019-12-12T18:00:15,895945080-0500 -0>
18:06 cmalm joined #evergreen
18:09 remingtron joined #evergreen
20:39 sandbergja joined #evergreen

Results for 2019-12-11

06:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
06:54 agoben joined #evergreen
07:07 rjackson_isl joined #evergreen
07:31 rfrasur joined #evergreen
09:33 csharp I had some system badness too
09:34 csharp it generated gigs and gigs of xlog that I had to deal with
09:34 Dyrcona Yeahp. That's why my replication server had problems.
09:35 Dyrcona Testing on non-replicated servers went just fine, but took a looooonnngggg time.
09:49 dbs bugged with 1856047 and tweaked the branch commit log and name accordingly
09:57 mmorgan dbs++
10:05 sandbergja joined #evergreen
10:10 Dyrcona dbs: You want me to add the pullrequest tag to bug 1856047 while I'm confirming and targeting it?
10:10 pinesol Launchpad bug 1856047 in Evergreen 3.4 "Updating auto_renewal column added in 3.2.0 can take hours or days on large systems" [Low,Confirmed] https://launchpad.net/bugs/1856047
10:11 Dyrcona I think someone else will have to test it as I don't have any pre-3.2 database dumps available.
10:30 dbs Dyrcona: sure sounds good!
10:30 Dyrcona OK. Done!
10:32 Dyrcona If anyone disagrees with the Importance I assigned to the bug, feel free to change it.
10:52 eby are most using the default max stanza size for ejabberd or does it usually require a bump?
10:59 berick eby: i'm still bumping.  there are edge cases
11:01 eby thanks berick . run into it with some action trigger event creation and wondered if was worth digging into or just happens
11:03 Dyrcona eby: We bump in production, but I usually leave it alone on test VMs.
11:21 Christineb joined #evergreen
11:55 jihpringle joined #evergreen
12:31 khuckins joined #evergreen
15:19 pinesol genpaku stole the decoder ring.
15:20 eby it's definitely the title of the item in the send
15:21 eby was just curious since I noticed SendEmail has encode_utf8 of the text and uses Mime and handles the same title fine
15:23 mmorgan miker: It continues. I hadn't intended a virtual index mapping for the title class on my 3.2.9 test system. I removed that and restarted services. That changed the query for my "symphony" title search, but the query results are exactly the same, so that virtual keyword addition was having no effect. Swapping out the english_nostop for simple made a very slight difference in the rel score for two of the records, but not e
15:27 JBoyer fyi mmorgan, for me that stopped at "two of the records, but not en" in case you wrote much more.
15:27 dbs oh fun, I guess I forgot that "My List" / "View basket" can't display books that only have a located URI, no physical holdings
15:27 mmorgan Ok, thanks, here's the rest:
16:25 dbs doesn't look like it; ebooks are loaded in their own file with just located URIs
16:28 dbs They're all at CONS; I'll try moving some down to SYS1 and BR1
16:29 dbs BOOM
16:31 jeff cute.
16:31 jeff yeah, maybe not a very good test data set for located uris to have them all at top of tree. :-)
16:40 dbs Updated the bug accordingly. Identifying that pattern is 90% of fixing the bug, feels good!
16:42 rfrasur joined #evergreen
16:42 jvwoolf1 left #evergreen
16:44 khuckins joined #evergreen
17:02 mmorgan left #evergreen
17:24 sandbergja_ joined #evergreen
18:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:08 jihpringle joined #evergreen
18:19 jeffdavis There is a Perl live test (20-lp1541559-ebook-api.t) which assumes those ebooks have located URIs at CONS, something to watch for if the concerto data is changed
19:09 cmalm joined #evergreen
19:20 dbs thanks for the heads-up jeffdavis!
19:38 sandbergja joined #evergreen

Results for 2019-12-10

00:33 sandbergja joined #evergreen
00:45 sandbergja joined #evergreen
02:14 sandbergja joined #evergreen
06:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
06:54 agoben joined #evergreen
07:07 rjackson_isl joined #evergreen
07:22 rfrasur joined #evergreen
11:15 miker mmorgan: and, finally, the reason for the change is that there was no real functional difference between sort on pop vs poprel because of the (lack of) scaling before application of the popularity addition. it was all popularity all the time for both, effectively
11:15 mmorgan miker: Any processing needed after changing the global flag?
11:21 * csharp confirms that installing from https://koji.fedoraproject.org/​koji/buildinfo?buildID=1420745 solves the EG and extensions issues
11:25 mmorgan I'm not seeing the effect of popularity I would expect.
11:25 mmorgan I have a 3.2.9 Concerto system. My test search is a title search on symphony, result set is 5 hits.
11:26 mmorgan I give the least relevant hit a popularity score of 5, (added directly in the db to rating.record_badge_score). Global flag search.max_popularity_importance_multiplier is set to the max at 2.0.
11:27 miker mmorgan: you might need to restart services (storage in particular)
11:27 mmorgan My record with the badge is #4 in the poprel sort.
11:27 * mmorgan will restart.
11:42 mmorgan jeff: The popularity score is the highest it can be. If it can't ever push that record higher, than 4 out of 5, then the popularity badge will always be ineffective. We noticed a significantly decreased effect of our popularity badges after upgrading to 3.1
11:42 Dyrcona Part of the troulbe that I had with systemd during out last update was the query to update action.aged_circulations filled up the log space on the replication db server.
11:43 Bmagic That's the code I've created to do the job (sql file and bash sh file)
11:43 Dyrcona Yeah, I'm not sure it needs to be so complicated. Have you tested it on a test db server?
11:44 Bmagic It seems to be working, one of the bugs I found came when updating action.circulation rows with target_copy IDs that don't exist in asset.copy. Stemming from trigger fake_fkey_tgr()
11:44 Bmagic Dyrcona: yep, it's purring like a kitten
11:44 Bmagic and the server is functional wihle it's running. I can renew/circ/etc with no perceived slowness
16:45 mmorgan joined #evergreen
17:05 mmorgan left #evergreen
17:36 rfrasur joined #evergreen
18:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:25 Christineb joined #evergreen
19:07 cmalm_ joined #evergreen
19:33 rfrasur joined #evergreen

Results for 2019-12-09

01:14 sandbergja joined #evergreen
01:58 sandbergja joined #evergreen
06:01 pinesol News from qatests: Failed Installing Evergreen pre-requisites - Expected 1 errors but encountered 3. <http://testing.evergreen-ils.org/~li​ve/test.26.html#2019-12-09T06:00:09,402632214-0500 -0>
07:03 agoben joined #evergreen
07:50 collum joined #evergreen
07:59 mantis1 joined #evergreen
09:05 Dyrcona Well, Chromium also works. :)
09:05 csharp yeah :-)
09:06 rfrasur joined #evergreen
09:29 dbs csharp: I am indeed on F31
09:29 dbs Now trying to remember if I ran into this while I was testing on Windows, however...
09:30 * dbs curses dbs_windows for not having reported back on that
09:39 csharp heh
09:39 JBoyer Quick data point: I tried FF 71 on macOS and did not run into the issue.
09:39 csharp JBoyer: thanks for that confirmation
09:40 * csharp went to start his Windows 10 VM only to realize the station he's on doesn't have one installed yet :-/
09:40 JBoyer So it looks Linux specific at the moment, which, while not great, really is the ideal situation if there *has* to be a problem.
09:40 csharp JBoyer: agreed
09:41 * JBoyer remembers he's standing right next to a Windows laptop, will test right now.
09:42 csharp and Google Music Desktop Player also stopped working on Linux for me, so all the software is breaking
09:42 csharp @who broke the softwares
09:42 pinesol felicia broke the softwares.
09:42 * mmorgan is having flashbacks to those mac dude vs. pc guy commercials
09:45 JBoyer UGH. That old smushbox keyboard is like typing on bugs.
09:46 JBoyer Anyway, FF 71 on Windows was fine.
09:46 JBoyer I was testing on master, to double check, what server versions have you seen issues on?
09:46 remingtron FF 71 on Windows also works fine for me (EG 3.3.1)
09:51 csharp JBoyer++ remingtron++ # thanks for confirming
10:00 mmorgan1 joined #evergreen
12:58 csharp nothing in the audit.log with "deni" (case insensitive)
12:58 * csharp remembers that dbs's alternate nick is denials :-)
12:59 Dyrcona :)
12:59 dbs mmm... https://fedoraproject.org/wiki/How_​to_debug_Firefox_problems?rd=Bug_in​fo_Firefox#Testing_Mozilla_binaries
13:00 dbs could rule out packaging hijinks that way
13:00 dbs FWIW I also saw no difference with SELinux disabled
13:00 * dbs will commence downloading
13:05 dbs hmm. initial testing suggests that the vanilla mozilla version of Firefox 71.0 is not affected
13:06 dbs csharp++ # avoiding log alerts for me - so kind
13:06 csharp dbs: ha!
13:07 csharp dbs: very interesting - so this really must be a Fedora thing
13:07 csharp @who lives in a Fedora bubble?
13:07 pinesol rashma lives in a Fedora bubble.
13:11 dbs however I also created a brand new firefox profile for this, so...
13:13 dbs Hah! And using the same new profile as was created in vanilla FF 71.0 in Fedora's version of FF 71.0 triggers the bug
13:13 dbs I think that's as smoking gun as we can get
13:14 dbs Then the question is: how the heck do we build a minimal reproducible test case for the Fedorans?
13:14 csharp hmmm
13:14 csharp dbs++ # detective work
13:20 JBoyer dbs++
15:46 Dyrcona :)
16:39 yboston joined #evergreen
17:07 mmorgan left #evergreen
18:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:22 dbwells joined #evergreen
18:51 rfrasur joined #evergreen
21:14 sandbergja joined #evergreen

Results for 2019-12-08

01:08 sandbergja joined #evergreen
05:31 rfrasur joined #evergreen
06:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
10:04 rfrasur joined #evergreen
10:57 sandbergja joined #evergreen
11:58 sandbergja joined #evergreen
14:25 sandbergja joined #evergreen
16:37 sandbergja joined #evergreen
18:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
20:18 sandbergja joined #evergreen

Results for 2019-12-07

06:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
08:28 rfrasur joined #evergreen
11:11 rfrasur joined #evergreen
12:14 sandbergja joined #evergreen
16:38 miker mmorgan: only have a second now, and travelling through Monday, but I can provide insight on your poprel question later. feel free to ping me next week if I seem to have forgotten... :)
16:39 miker oh, not here right now... well, for the logs for now, I guess
16:39 miker **poof**
18:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
20:48 sandbergja joined #evergreen
21:29 sandbergja joined #evergreen
21:56 rfrasur joined #evergreen

Results for 2019-12-06

09:53 Dyrcona Bmagic: We are.
09:57 Dyrcona Bmagic: I'm not entirely sure if bug 1801163 applies.
09:57 pinesol Launchpad bug 1801163 in Evergreen "SendEmail A/T reactor broken for recent version of Encode::MIME::Header" [High,Confirmed] https://launchpad.net/bugs/1801163 - Assigned to Jeff Godin (jgodin)
09:58 Dyrcona I'll check since I was about to update a test vm that's on 18.04 anyway.
09:58 Bmagic at this point, 18.04 is still not "fully" functional an issue with Evergreen?
09:59 Dyrcona Well, can we say we support a distro if Evergreen is not fully functional?
09:59 Bmagic It's debatable I'm sure
10:01 pinesol Launchpad bug 1855199 in Evergreen "Vandelay record queuing can fail if spool directory is /tmp" [Medium,Confirmed] https://launchpad.net/bugs/1855199
10:01 Bmagic If they did say that, I probably wouldn't have posed the question here
10:02 berick that's the only 18.04 issue i've encountered on dev machines.  of course, I'm not sending email
10:02 pinesol News from qatests: Failed Building the AsciiDoc output formats <http://testing.evergreen-ils.org/~li​ve/test.81.html#2019-12-06T09:38:30,140377482-0500 -0>
10:02 Dyrcona Bmagic: I would say that Ubuntu 18.04 is affected by 1801163 give that Encode is version 2.88 and Encode::MIME::Header is 2.24.
10:03 Dyrcona It also probably affects Debian Stretch and Buster.
10:03 Bmagic what a bummer
10:13 jeff I'll take a fresh look.
10:13 Dyrcona Yeahp. I think you're right.
10:13 Dyrcona About changing the templates.
10:14 * dbs found that using the Cookie Autodelete extension in Firefox to greylist the test server hostname and then hitting the trash icon for the hostname (keeping localstorage and cookies) fixed the "Possibly unhandled rejection: {"isTrusted":true}" webby white screen problem
10:14 Dyrcona There are a number of related wish list items on Launchpad that would require similarly radical changes.
10:15 Dyrcona dbs: Good to know. I haven't encountered that issue switching from production to test/training servers.
10:18 csharp we're happy to reconfigure our (many) templates if it keeps us from chasing our tail in the future (fwiw)
10:19 * jeff nods
10:21 Dyrcona csharp | jeff: same here.
12:16 gsams joined #evergreen
12:44 dbwells joined #evergreen
13:14 berick tried to recreate the DataCloneError in FF 70 on master, no dice.  pleased to see FF shows shared worker logs along with the main page logs.
13:15 Dyrcona berick: I was just getting ready to test it.
13:16 Dyrcona Except I got an Internal Server Error, so I probably have something broken on my vm.
13:18 Dyrcona I think my problem is ejabberd.
13:20 Dyrcona Cannot connect to server public.localhost: Connection refused
16:13 mmorgan Anyone know why that factor of 1000 was introduced?
16:16 rhamby I have a flippant desire to say because 999 just didn't feel like quite enough but that might because it's Friday afternoon.  :)
16:16 stephengwills left #evergreen
16:17 * mmorgan realizes that Friday afternoon might not be the best time for such a question :)
16:18 mmorgan On a test system, I removed the factor of 1000, and our popular items zoomed right back up to the top of the poprel search.
16:23 mmorgan Anyone else have issues with poprel, or is it just us?
16:27 * mmorgan will open an lp bug, but wanted to look for insight here first.
17:06 mmorgan left #evergreen
18:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:03 sandbergja_ joined #evergreen
18:33 dbwells_ joined #evergreen
19:34 remingtron_ joined #evergreen

Results for 2019-12-05

08:51 mantis1 joined #evergreen
09:14 remingtron Bmagic: I pushed to your Antora collab branch. In particular, I converted the headings to one-line prefix/suffix style, to help with nav work that requires changing heading levels.
09:15 remingtron @later tell sandbergja I pushed to Bmagic's Antora collab branch. In particular, I converted the headings to one-line prefix/suffix style, to help with nav work that requires changing heading levels.
09:15 pinesol remingtron: The operation succeeded.
09:15 mllewellyn joined #evergreen
09:15 mllewellyn left #evergreen
09:16 mllewellyn1 joined #evergreen
09:35 rfrasur joined #evergreen
09:53 sandbergja joined #evergreen
10:33 sandbergja joined #evergreen
11:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:44 Christineb joined #evergreen
12:05 khuckins joined #evergreen
12:17 nfBurton joined #evergreen
14:21 dluch dbs++
14:21 dluch Okay, we'll catch up more on the server move next meeting
14:22 dluch #info Quick update on Antora progress
14:22 sandbergja if anybody needs HTML versions, I can hop onto docs-testing.evergreen-ils.org and generate them there
14:22 sandbergja actually... I should just do that
14:22 dluch sandbergja++
14:22 Cody joined #evergreen
14:22 tkatie217 sandbergja++ please :)
14:26 dluch (I think bmagic is packing up from the offsite meeting we just had.)
14:26 remingtron #link http://antora.mobiusconsortium.org/prod
14:26 Cody Hey all, I'm trying to build a custom catalog search for my local library and struggling with the documentation. http://docs.evergreen-ils.org/re​org/3.0/integrations/index.html seems to be the correct page to start. Is there any way to get JSON or is it only XML?
14:27 remingtron Anyone can help by testing that server and emailing the DIG list (or posting on IRC) any problems they find. There are some obvious ones, and probably many small ones.
14:28 remingtron Cody: Hi! We're holding a Documentation Interest Group meeting here right now, should end shortly, then someone can hopefully answer your question.
14:29 dbs Cody: we're in the middle of a meeting atm but right now there's only XML
14:29 dluch Cody: we're using the IRC channel for the DIG meeting right now, but I'm sure someone can help after!
14:29 dluch lol.  Jinx, remingtron
14:29 sandbergja Cody: no worries!
14:29 dluch Okay, so I'm going to set an action item for all of us on this one
14:30 remingtron dluch: great
14:30 dluch #action Everyone will test the new Antora server and email the DIG list (or IRC) with problems (or suggestions)
14:30 dluch #info We will catch up on other action items and business at the January meeting
14:31 dluch #info January meeting date
14:31 dluch The first Thursday in January is the 1st.  I am definitely not going to be at work that day and assume most of you won't, either.  So, is the following Thursday, January 9, okay with everyone?
14:32 abneiman 9th is fine with me
14:32 jweston dluch the first Thursday is Jan 2nd but moving it to the 9th sounds fine to me
14:33 remingtron sounds good
15:22 jvwoolf joined #evergreen
15:24 rfrasur joined #evergreen
15:27 Dyrcona miker: OK, I see why, and I suspect that would have been it before reading bug 1855329.
15:27 dbs Fun. Switching from our test web staff client back to production, and getting a white screen with "Possibly unhandled rejection: {"isTrusted":true}" in the console when I log in
15:27 pinesol Launchpad bug 1855329 in Evergreen "Followup to bug 1827250, hold shelf issues" [High,New] https://launchpad.net/bugs/1855329
15:28 miker Dyrcona: yeah... too much freedom for the planner. some datasets are super happy with NULLS LAST, but at least 1 not-uncommonly-shaped dataset is super NOT happy
15:31 Dyrcona miker: I'll have a look tomorrow. I have a couple of 9.6 and higher pg databases hanging around. Our production db is still 9.5.
21:33 sandbergja joined #evergreen
21:46 sandbergja joined #evergreen
22:47 sandbergja joined #evergreen
23:02 pinesol News from qatests: Failed Building the AsciiDoc output formats <http://testing.evergreen-ils.org/~li​ve/test.81.html#2019-12-05T23:01:09,498026739-0500 -0>
23:45 sandbergja joined #evergreen

Results for 2019-12-04

03:24 jweston joined #evergreen
06:50 agoben joined #evergreen
07:24 rfrasur joined #evergreen
07:31 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
08:02 _bott_ joined #evergreen
08:08 collum joined #evergreen
08:37 Dyrcona joined #evergreen
11:22 berick Bmagic: searching the full value works in stock EG / concerto.  e.g. identifier:(Sirsi) 01-0112101
11:23 berick or for more precision  identifier|scn:(Sirsi) 01-0112101
11:23 berick but just searching the numbers should also work
11:46 dbs Hmm, fun times with the 3.4 staff client - we're seeing labels and the language selector switching seemingly randomly between French and English
11:47 dbs We're testing out an upgrade from 3.1, where people barely used webby, to 3.4.1 where I hope to pull the plug on XUL
11:50 Bmagic Dyrcona++
11:50 Bmagic berick++
12:00 dbs Looks like the service worker might be serving up the cached version, disregarding the eg_locale cookie?
17:53 pinesol Launchpad bug 1830923 in Evergreen 3.3 "MARC import lacks ability to view and edit incoming MARC record" [High,Confirmed] https://launchpad.net/bugs/1830923
17:57 berick gmcharlt: noted, will take a look
18:08 gmcharlt setting the Vandelay spool directory to /tmp considered harmful... bug 1855199
18:08 pinesol Launchpad bug 1855199 in Evergreen "Vandelay record queuing can fail if spool directory is /tmp" [Medium,New] https://launchpad.net/bugs/1855199
18:28 sandbergja_ joined #evergreen
18:30 sandbergja_ joined #evergreen
19:22 mllewellyn joined #evergreen
21:43 sandbergja joined #evergreen
21:53 sandbergja_ joined #evergreen
22:30 sandbergja joined #evergreen
23:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
23:56 sandbergja joined #evergreen
23:58 sandbergja_ joined #evergreen

Results for 2019-12-03

10:11 berick "today in PINES training we learn IRC"
10:12 csharp "ok, y'all just hang tight for about 45 mins..."
10:20 sandbergja joined #evergreen
11:01 pinesol News from qatests: Failed Building Evergreen <http://testing.evergreen-ils.org/~li​ve/test.30.html#2019-12-03T11:00:45,642733428-0500 -0>
11:01 pinesol News from qatests: Failed Running Evergreen tests <http://testing.evergreen-ils.org/~li​ve/test.31.html#2019-12-03T11:00:45,670095784-0500 -2>
11:01 pinesol News from qatests: Failed Installing Evergreen <http://testing.evergreen-ils.org/~li​ve/test.32.html#2019-12-03T11:00:45,697174167-0500 -4>
11:01 pinesol News from qatests: Failed Installing Dojo <http://testing.evergreen-ils.org/~li​ve/test.35.html#2019-12-03T11:00:45,724417964-0500 -6>
11:02 pinesol News from qatests: Failed configure apache <http://testing.evergreen-ils.org/~li​ve/test.36.html#2019-12-03T11:00:45,751807836-0500 -8>
11:02 pinesol News from qatests: Failed configure EG Action/Trigger <http://testing.evergreen-ils.org/~li​ve/test.38.html#2019-12-03T11:00:45,779140022-0500 -10>
11:02 pinesol News from qatests: Failed Create Evergreen Database <http://testing.evergreen-ils.org/~li​ve/test.41.html#2019-12-03T11:00:45,806399243-0500 -12>
11:02 pinesol News from qatests: Failed Running pgTAP tests <http://testing.evergreen-ils.org/~li​ve/test.42.html#2019-12-03T11:00:45,833616012-0500 -14>
11:02 pinesol News from qatests: Failed Running autogen.sh <http://testing.evergreen-ils.org/~li​ve/test.44.html#2019-12-03T11:00:45,861887222-0500 -16>
11:02 pinesol News from qatests: Failed Running pgTAP live tests <http://testing.evergreen-ils.org/~li​ve/test.47.html#2019-12-03T11:00:45,889208650-0500 -18>
11:02 pinesol News from qatests: Failed Running settings-tester.pl <http://testing.evergreen-ils.org/~li​ve/test.48.html#2019-12-03T11:00:45,916017334-0500 -20>
11:02 pinesol News from qatests: Failed Running perl live tests <http://testing.evergreen-ils.org/~li​ve/test.49.html#2019-12-03T11:00:45,942780711-0500 -22>
11:02 pinesol News from qatests: Failed Log Output: srfsh.log <http://testing.evergreen-ils.org/~li​ve/test.58.html#2019-12-03T11:00:45,969839648-0500 -24>
11:02 phasefx I'm going to change that to report just the first error :)
11:04 phasefx though in this case, the webifier is not catching the true first error, which is Err:106 http://ftp.us.debian.org/debian stretch/main amd64 libgd-graph-perl all 1.48-2
11:04 phasefx Hash Sum mismatch
15:24 dbwells Yes.  Actually, I see there is a security bug as well.
15:25 gmcharlt yeah
15:25 dbwells It seems like both are close, so just highlighting in hopes that someone can push them over the finish line.
15:26 gmcharlt both bugs have progress, indeed
15:27 gmcharlt I can provide forward progress for the security bug
15:28 gmcharlt and we can nudge csharp to see if he's progressed any further with testing for 1773191
15:28 gmcharlt #action gmcharlt will apply various code changes and nudges regarding the remaining webstaffblocker bugs
15:29 dbwells gmcharlt++
15:29 remingtron gmcharlt++
15:30 Dyrcona gmcharlt++
15:33 berick along w/ the hatch 0.3.2 build
15:33 berick i know there's some other interested parties in moving that bug forward
15:33 gmcharlt commit ade63709f4b51b jumps out at me
15:33 berick hoping we can help root out any final issues and encourage some confidence in the bug overall
15:33 berick done a fair amount of use and testing so far
15:34 gmcharlt was there anything adding dupes? and if so, should there be code checking that the new constraint is not violated?
15:34 gmcharlt or is that patch just belt-and-suspenders?
15:34 berick belt-and-suspenders ... i had a dupe on a dev VM but I was fairly confident it was not from natural causes
15:50 Topic for #evergreen is now QA-related bugs (Meeting topic: Evergreen Develpment Meeting 2019-12-03)
15:50 gmcharlt this is a carry-over from an earlier version of the agenda, but the LP link for "qaproject"-tagged bugs turns up nothing
15:50 gmcharlt does anybody recall what this is?
15:50 phasefx no bugs there at the moment; I added that to the stock agenda way back when tests failed and no one had the itch to address it
15:51 gmcharlt ah, OK
15:51 phasefx for regressions
15:51 gmcharlt #info The "qaproject" LP tag is meant for bugs stemming from automated test failures that aren't immediately addressed
15:51 gmcharlt phasefx: ^^ fair summary?
15:51 phasefx the live test results page also inlines those bugs
15:51 phasefx gmcharlt++ fair
15:52 gmcharlt ok
15:52 gmcharlt so at the moment, we're golden!
15:53 gmcharlt any other topics that folks would like to raise for the last 8 minutes?
15:53 Dyrcona Except that tests failed earlier today.
15:53 gmcharlt we're not golden! :(
15:53 phasefx I think that may be from debian updates to the repo not being atomic, but I'm not sure
15:53 JBoyer Dyrcona, that was some kind of upstream thing. (Not even npm!)
20:42 sandbergja joined #evergreen
21:22 rfrasur joined #evergreen
22:09 sandbergja joined #evergreen
23:12 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>

Results for 2019-12-02

10:59 * jeff eyes bug 1852316
10:59 pinesol Launchpad bug 1852316 in Evergreen "Overrideable events at checkout should not be hard coded" [Undecided,New] https://launchpad.net/bugs/1852316
11:01 mmorgan jeff: We're beyond 3.1, but I don't remember encountering ACTOR_USER_NOT_FOUND when overriding.
11:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:02 * mmorgan also ponders the reasoning behind hard-coded overrideable events ...
11:05 Dyrcona It's easier that way. Sometimes generic overrides are hard.
11:07 mmorgan Problematic in the long run, though :-(
11:14 dbs ah that fun moment when you realize you've been running through the OpenSRF install instructions meant for your dev system on your production system instead
11:16 dbs theoretically opensrf 3.2 should just work in place of 3.1, I suppose
11:18 dbs apache websockets should continue to function as before
11:18 dbs Guess I'll test restarting things late at night and see if anything blows up :)
11:19 jeff found it. local experiment.
11:23 Dyrcona dbs: Yeah, it should work.
11:23 yboston joined #evergreen
21:23 sandbergja joined #evergreen
21:38 rfrasur joined #evergreen
22:35 sandbergja joined #evergreen
23:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
23:46 sandbergja joined #evergreen

Results for 2019-12-01

08:42 rfrasur joined #evergreen
09:27 mnsri_away joined #evergreen
09:30 rfrasur_ joined #evergreen
11:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:05 rfrasur joined #evergreen
12:04 jeff and thus begins fine forgiveness month!
12:04 jeff welcome to december.
15:58 sandbergja joined #evergreen
22:35 sandbergja joined #evergreen
22:47 rfrasur_ joined #evergreen
23:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
23:20 sandbergja joined #evergreen

Results for 2019-11-30

00:17 rfrasur joined #evergreen
07:49 rfrasur joined #evergreen
09:51 sandbergja joined #evergreen
11:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
16:16 rfrasur joined #evergreen
17:36 rfrasur joined #evergreen
21:00 rfrasur joined #evergreen
23:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>

Results for 2019-11-29

09:19 jvwoolf joined #evergreen
09:24 mantis1 joined #evergreen
10:04 jonadab joined #evergreen
11:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
12:06 jihpringle joined #evergreen
13:19 rfrasur joined #evergreen
15:16 jvwoolf left #evergreen
15:40 rfrasur joined #evergreen
16:58 rfrasur joined #evergreen
18:34 rfrasur joined #evergreen
23:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>

Results for 2019-11-28

08:11 jvwoolf joined #evergreen
10:05 nfBurton joined #evergreen
10:32 Christineb joined #evergreen
11:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
12:07 jihpringle joined #evergreen
13:47 rfrasur joined #evergreen
13:58 rfrasur joined #evergreen
15:57 rfrasur joined #evergreen
23:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>

Results for 2019-11-27

10:57 mmorgan circ.selfcheck.block_checkout_on_copy_status had value "105", changed it to ["105"] and success :)
10:58 mmorgan berick++ #again:)
11:00 sandbergja joined #evergreen
11:02 pinesol News from qatests: Failed Building Evergreen <http://testing.evergreen-ils.org/~li​ve/test.30.html#2019-11-27T11:00:37,664554284-0500 -0>
11:02 pinesol News from qatests: Failed Running Evergreen tests <http://testing.evergreen-ils.org/~li​ve/test.31.html#2019-11-27T11:00:37,692008489-0500 -2>
11:02 pinesol News from qatests: Failed Installing Evergreen <http://testing.evergreen-ils.org/~li​ve/test.32.html#2019-11-27T11:00:37,720011175-0500 -4>
11:02 pinesol News from qatests: Failed Installing Dojo <http://testing.evergreen-ils.org/~li​ve/test.35.html#2019-11-27T11:00:37,747737158-0500 -6>
11:02 pinesol News from qatests: Failed configure apache <http://testing.evergreen-ils.org/~li​ve/test.36.html#2019-11-27T11:00:37,774518634-0500 -8>
11:02 pinesol News from qatests: Failed configure EG Action/Trigger <http://testing.evergreen-ils.org/~li​ve/test.38.html#2019-11-27T11:00:37,801086048-0500 -10>
11:02 pinesol News from qatests: Failed Create Evergreen Database <http://testing.evergreen-ils.org/~li​ve/test.41.html#2019-11-27T11:00:37,827769691-0500 -12>
11:02 pinesol News from qatests: Failed Running pgTAP tests <http://testing.evergreen-ils.org/~li​ve/test.42.html#2019-11-27T11:00:37,854403250-0500 -14>
11:02 pinesol News from qatests: Failed Running autogen.sh <http://testing.evergreen-ils.org/~li​ve/test.44.html#2019-11-27T11:00:37,881090412-0500 -16>
11:02 pinesol News from qatests: Failed Running pgTAP live tests <http://testing.evergreen-ils.org/~li​ve/test.47.html#2019-11-27T11:00:37,907739113-0500 -18>
11:02 pinesol News from qatests: Failed Running settings-tester.pl <http://testing.evergreen-ils.org/~li​ve/test.48.html#2019-11-27T11:00:37,935641496-0500 -20>
11:02 pinesol News from qatests: Failed Running perl live tests <http://testing.evergreen-ils.org/~li​ve/test.49.html#2019-11-27T11:00:37,963486842-0500 -22>
11:02 pinesol News from qatests: Failed Log Output: srfsh.log <http://testing.evergreen-ils.org/~li​ve/test.58.html#2019-11-27T11:00:37,991231100-0500 -24>
11:29 Christineb joined #evergreen
11:35 jeff and thus began the heartwarming tale of the little sorter that learned the value of forgiveness...
11:35 jeff (sure to be a classic)
17:10 mmorgan left #evergreen
19:26 cmalm joined #evergreen
19:54 nfBurton joined #evergreen
23:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>

Results for 2019-11-26

10:43 rfrasur csharp++ # for avoiding assimilation.  Today.
10:47 yboston joined #evergreen
10:51 JBoyer mmorgan++
11:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:07 jeff going to experiment with some reporting on "time on shelf / time out of library" with potential breakdowns between "on holdshelf", "in transit", "normal out", "overdue", "lost (bounded somehow)"... has anyone here done (or is anyone here aware of someone who has done) similar?
11:10 jeff also musing a bit about ways to factor in "opportunities to circ" in some way, but not sure. knowing an item's last checkout was six months ago is slightly out of context if it was just returned last week. that could be something as simple as factoring in the checkin time or status change time (similar to how we factor in active date) when saying "show me items that haven't circulated in X"
11:13 mmorgan jeff: We commonly use status changed time as a measure of how long an item has been sitting on the shelf.
19:09 cmalm joined #evergreen
19:42 stephengwills joined #evergreen
22:03 sandbergja joined #evergreen
23:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>

Results for 2019-11-25

10:23 mmorgan joined #evergreen
10:40 sandbergja joined #evergreen
10:43 Christineb joined #evergreen
11:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:23 yboston joined #evergreen
11:23 sandbergja joined #evergreen
11:25 rfrasur joined #evergreen
13:52 nfBurton joined #evergreen
14:37 csharp more news on bug 1840950, the error Safari throws when it doesn't load the expire date is "Timepicker directive: "ng-model" value must be a Date object, a number of milliseconds since 01.01.1970 or a string representing an RFC2822 or ISO 8601 date."
14:37 pinesol Launchpad bug 1840950 in Evergreen "Patron expiration date & iPads" [Medium,Confirmed] https://launchpad.net/bugs/1840950
14:38 csharp so I'm wondering why Safari would be more strict than Chrome/FF about that?
14:38 sandbergja joined #evergreen
14:40 csharp also, going to look into adding console output statements to find out what it's actually seeing get returned
14:44 csharp and why date of birth is not causing the same error.
14:46 csharp on that last, in the test account I'm playing with, dob has the date in YYYY-MM-DD and expire date is YYYY-MM-DD HH:mm:ss-<offset>
14:48 jeff that console error is from an old version of UI Bootstrap. it's not present in the current (archived, read-only) code.
14:48 jeff (this info isn't directly helpful, sorry)
14:50 jeff the error text was changed in this commit: https://github.com/angular-ui/bootstrap/comm​it/aa010b024e936b9ced66a58726d4fe591be9383c
16:37 sandbergja jihpringle: oh!  Good to know!  We're still back on 3.1, so we don't have preferred name in Evergreen yet, so we're trying to think of a strategy
16:37 jihpringle we told our libraries they had to wait for 3.3
16:39 sandbergja One question I've had locally: do we need to store both the preferred name and the legal name?  Do we really need the legal name for any of our Evergreen work?  Do you have a sense for why your academics would like both preferred and legal names in Evergreen?
16:40 jihpringle those questions haven't really come up for us yet
16:40 jihpringle we're at the stage of getting test records with preferred name included from a couple of our academics
16:41 jihpringle for those we're expecting to load both legal and preferred name
16:42 sandbergja Good luck with that process!  Thanks for your help -- okay if I pick your brain after you are farther into that process?
16:42 jihpringle thanks and absolutely
16:43 jihpringle it might also be a good question for the next student success group meeting
16:47 sandbergja That means I have to schedule the next student success working group meeting :-)
16:47 jihpringle I vote for January (over December) :)
16:57 khuckins joined #evergreen
17:01 pinesol News from qatests: Failed Installing OpenSRF pre-requisites <http://testing.evergreen-ils.org/~l​ive/test.7.html#2019-11-25T16:45:39,681718863-0500 -0>
17:01 pinesol News from qatests: Failed Building OpenSRF <http://testing.evergreen-ils.org/~l​ive/test.9.html#2019-11-25T16:45:39,708141366-0500 -2>
17:01 pinesol News from qatests: Failed Running OpenSRF build tests <http://testing.evergreen-ils.org/~li​ve/test.10.html#2019-11-25T16:45:39,734605538-0500 -4>
17:01 pinesol News from qatests: Failed Installing OpenSRF <http://testing.evergreen-ils.org/~li​ve/test.11.html#2019-11-25T16:45:39,761288829-0500 -6>
17:01 pinesol News from qatests: Failed updating /etc/hosts <http://testing.evergreen-ils.org/~li​ve/test.13.html#2019-11-25T16:45:39,787742381-0500 -8>
17:01 pinesol News from qatests: Failed configuring ejabberd <http://testing.evergreen-ils.org/~li​ve/test.15.html#2019-11-25T16:45:39,814375373-0500 -10>
17:01 pinesol News from qatests: Failed creating jabber users <http://testing.evergreen-ils.org/~li​ve/test.16.html#2019-11-25T16:45:39,840791114-0500 -12>
17:01 pinesol News from qatests: Failed configuring OpenSRF <http://testing.evergreen-ils.org/~li​ve/test.17.html#2019-11-25T16:45:39,867311142-0500 -14>
17:01 pinesol News from qatests: Failed start opensrf <http://testing.evergreen-ils.org/~li​ve/test.18.html#2019-11-25T16:45:39,894126627-0500 -16>
17:01 pinesol News from qatests: Failed stop opensrf <http://testing.evergreen-ils.org/~li​ve/test.19.html#2019-11-25T16:45:39,920558926-0500 -18>
17:01 pinesol News from qatests: Failed start opensrf <http://testing.evergreen-ils.org/~li​ve/test.20.html#2019-11-25T16:45:39,946936529-0500 -20>
17:01 pinesol News from qatests: Failed test opensrf <http://testing.evergreen-ils.org/~li​ve/test.21.html#2019-11-25T16:45:39,973464938-0500 -22>
17:01 pinesol News from qatests: Failed configuring websockets <http://testing.evergreen-ils.org/~li​ve/test.22.html#2019-11-25T16:45:39,999807878-0500 -24>
17:01 pinesol News from qatests: Failed stop opensrf <http://testing.evergreen-ils.org/~li​ve/test.23.html#2019-11-25T16:45:40,026329460-0500 -26>
17:01 pinesol News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-11-25T16:45:40,052962379-0500 -28>
17:01 pinesol News from qatests: Failed Building Evergreen <http://testing.evergreen-ils.org/~li​ve/test.30.html#2019-11-25T16:45:40,079548880-0500 -30>
17:01 pinesol News from qatests: Failed Running Evergreen tests <http://testing.evergreen-ils.org/~li​ve/test.31.html#2019-11-25T16:45:40,106020375-0500 -32>
17:01 pinesol News from qatests: Failed Installing Evergreen <http://testing.evergreen-ils.org/~li​ve/test.32.html#2019-11-25T16:45:40,132437083-0500 -34>
17:01 pinesol News from qatests: Failed Change File Ownership <http://testing.evergreen-ils.org/~li​ve/test.33.html#2019-11-25T16:45:40,159147985-0500 -36>
17:01 pinesol News from qatests: Failed Installing Dojo <http://testing.evergreen-ils.org/~li​ve/test.35.html#2019-11-25T16:45:40,185657503-0500 -38>
17:01 pinesol News from qatests: Failed configure apache <http://testing.evergreen-ils.org/~li​ve/test.36.html#2019-11-25T16:45:40,212067284-0500 -40>
17:01 pinesol News from qatests: Failed configure EG OpenSRF <http://testing.evergreen-ils.org/~li​ve/test.37.html#2019-11-25T16:45:40,238680534-0500 -42>
17:01 pinesol News from qatests: Failed configure EG Action/Trigger <http://testing.evergreen-ils.org/~li​ve/test.38.html#2019-11-25T16:45:40,265090706-0500 -44>
17:01 pinesol News from qatests: Failed Create Evergreen Database <http://testing.evergreen-ils.org/~li​ve/test.41.html#2019-11-25T16:45:40,291499810-0500 -46>
17:01 pinesol News from qatests: Failed Running pgTAP tests <http://testing.evergreen-ils.org/~li​ve/test.42.html#2019-11-25T16:45:40,318294201-0500 -48>
17:01 pinesol News from qatests: Failed start opensrf <http://testing.evergreen-ils.org/~li​ve/test.43.html#2019-11-25T16:45:40,344670818-0500 -50>
17:01 jonadab joined #evergreen
17:01 pinesol News from qatests: Failed Running autogen.sh <http://testing.evergreen-ils.org/~li​ve/test.44.html#2019-11-25T16:45:40,371369598-0500 -52>
17:01 pinesol News from qatests: Failed Restarting Apache <http://testing.evergreen-ils.org/~li​ve/test.45.html#2019-11-25T16:45:40,397989205-0500 -54>
17:01 pinesol News from qatests: Failed test EG opensrf <http://testing.evergreen-ils.org/~li​ve/test.46.html#2019-11-25T16:45:40,424422216-0500 -56>
17:01 pinesol News from qatests: Failed Running pgTAP live tests <http://testing.evergreen-ils.org/~li​ve/test.47.html#2019-11-25T16:45:40,451206084-0500 -58>
17:01 pinesol News from qatests: Failed Running settings-tester.pl <http://testing.evergreen-ils.org/~li​ve/test.48.html#2019-11-25T16:45:40,477946058-0500 -60>
17:01 pinesol News from qatests: Failed Running perl live tests <http://testing.evergreen-ils.org/~li​ve/test.49.html#2019-11-25T16:45:40,504622784-0500 -62>
17:01 pinesol News from qatests: Failed Gathering log summary <http://testing.evergreen-ils.org/~li​ve/test.50.html#2019-11-25T16:45:40,532204661-0500 -64>
17:01 pinesol News from qatests: Failed Log Output: config.log <http://testing.evergreen-ils.org/~li​ve/test.51.html#2019-11-25T16:45:40,559102863-0500 -66>
17:02 berick heh, looks like an Angular exception stack trace
17:17 mmorgan left #evergreen
18:36 jihpringle joined #evergreen

Results for 2019-11-24

09:32 sandbergja joined #evergreen
09:50 pinesol joined #evergreen
10:45 sandbergja joined #evergreen
11:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
17:25 sandbergja joined #evergreen
20:05 sandbergja joined #evergreen
23:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
23:36 sandbergja joined #evergreen

Results for 2019-11-23

01:52 sandbergja joined #evergreen
02:23 sandbergja joined #evergreen
10:40 StomproJ joined #evergreen
11:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:13 sandbergja joined #evergreen
15:14 sandbergja joined #evergreen
17:06 sandbergja joined #evergreen
20:50 sandbergja joined #evergreen
21:36 sandbergja joined #evergreen
22:40 sandbergja joined #evergreen
23:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>

Results for 2019-11-22

10:49 Dyrcona heh.
10:49 AFloyd__ lol
10:50 Dyrcona I thought of something that would make a decent band name this morning, but now I've forgotten it.
11:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
11:04 rjackson_isl Prevagen... One of these days I will have to remember to buy
11:05 rfrasur joined #evergreen
11:06 Dyrcona rjackson_isl: :)
14:11 csharp looking at Cat.pm - wondering if it's appropriate to add a check of whether the vol ID is -1, and if so, exit the function without changing anything
14:11 csharp within the fleshed_volume_update sub
14:12 csharp or if there's a better way to do it
14:14 Dyrcona csharp: That's certainly one way, but I'm not sure what effect that would have on the client. It might return an error. I'd have to look at the code. You could always try it in a test environment to see what happens.
14:15 Dyrcona A database trigger might have a similar effect depending on what it does. It could not do the update, but have it appear to be successful.
14:18 csharp yeah, my first thought was a trigger, but then I wanted to look upstream to see why it ignores what apparently the XUL client took into account, and since I'm more confortable in perl than in Angular/JS I got caught there :-)
14:18 Dyrcona It looks like the check was in the XUL client based on the bug description. It should probably be moved to the back end code, though.
15:08 Dyrcona yeah... like The Jimi Hendrix Experience. :)
15:08 berick @who sang "MARC On a Lark" for Cataloging Experience?
15:08 pinesol bwicksall sang MARC On a Lark for Cataloging Experience.
15:08 csharp okay, so my patch passes a basic smoke test on a stock master server with concerto data
15:09 Dyrcona And, I think I musta heard of The Mundanes before because John Linnell from They Might Be Giants was in the band.
15:09 Dyrcona Yeah? You were able to create a new call number without it blowing up?
15:12 csharp hmm - maybe not
17:50 jihpringle joined #evergreen
18:07 dbwells_ joined #evergreen
18:11 gmcharlt a pull request is now available for that Hoopla SIP2 issue: bug 1853363
18:11 pinesol Launchpad bug 1853363 in Evergreen "SIP2: add setting to specify overriding certain flag fields" [Wishlist,New] https://launchpad.net/bugs/1853363
19:10 jihpringle joined #evergreen
20:56 sandbergja joined #evergreen
21:44 sandbergja joined #evergreen
23:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>

Results for 2019-11-21

13:54 * jeff nods
13:55 jeff slightly more operational / on topic question: has anyone experimented with having a SIP client checkin set the underlying args for "Amnesty Mode" checkin?
13:55 alynn26 If they just dropped them in the book drop, then any additional fines on there account where not forgiven
13:55 jeff it looks like it should be quite possible, i just haven't tested the theory yet.
14:00 agoben Ok, it's meeting time!
14:00 agoben #startmeeting EOB/Evergreen Project Board meeting for 2019-11-21, agenda:https://wiki.evergreen-ils.org/doku.​php?id=governance:minutes:2019-11-21
14:00 pinesol Meeting started Thu Nov 21 14:00:15 2019 US/Eastern.  The chair is agoben. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:16 agoben Thanks!
14:16 agoben #topic 2020 Conference Committee
14:16 Topic for #evergreen is now 2020 Conference Committee (Meeting topic: EOB/Evergreen Project Board meeting for 2019-11-21, agenda:https://wiki.evergreen-ils.org/doku.p​hp?id=governance:minutes:2019-11-21)
14:16 terranm We have extended preconference submissions by another week. If we don't get enough submittals, we'll start reaching out to individuals.
14:16 terranm Conf registration form is being tested now, hopefully will get all changes made and posted right after Thanksgiving.
14:16 terranm Sponsor / exhibitor interest is starting to trickle in, but it's early days yet.
14:16 terranm #info Budget for approval: https://docs.google.com/spreadsheets/d/178j7UUgoQU​gf0fWvRFrPeEJCn4i5qQXSBgzaqcJLTu0/edit?usp=sharing
14:16 terranm Food and beverage is incredibly expensive (the bad part about being in a nice hotel in Atlanta), but we're still on track to making a profit.
14:17 nfBurton How many submissions have we had?
14:17 terranm For programs?
14:18 nfBurton Yeah
15:01 rfrasur (I'm not on the board but I have opinions) I could see this as something that could be developed in the future, and it'd be nice to have the platform available to build on.
15:01 gmcharlt well, to toss another use case out there
15:02 gmcharlt we could potentially want to do things like send a community member to a specialized training, potentially sharing the costs with there employers
15:02 Dyrcona A lot of other F/OSS projects/foundations offer such scholarships and grants for conference attendance. They are sometimes means tested.
15:02 JBoyer csharp, not so much "us," but TEP offering a grant to the Eg conference to those in the community at large that can't afford it or potentially sending Evergreeners to Code4Lib or something like that.
15:02 gmcharlt so I'm in favor of keepign the door open for that
15:02 csharp ok - good points and no arguments from me :-)
16:24 bwicksall joined #evergreen
17:00 mmorgan left #evergreen
17:18 khuckins joined #evergreen
17:32 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
17:56 jeffdavis berick: deleting package-lock.json alleviated my immediate install woes, thanks again for that advice
17:57 jeffdavis (still shaking my head and muttering darkly about npm though)
17:58 berick jeffdavis: i know the feeling...  if you care to weigh in on package-lock specifically, bug 1792394

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