Evergreen ILS Website

Search in #evergreen

Channels | #evergreen index




Results

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

Results for 2019-10-30

11:05 berick L'Ubuntue
11:05 phasefx so do we actually need to install chromium?
11:06 phasefx or should we, rather?
11:06 berick phasefx: it should be installed w/ the makefile installer
11:06 berick just have to tell the test engine how to find it
11:06 phasefx berick++
11:06 JBoyer Currently the -developer target installs it, I need to add a -tester instead.
11:07 phasefx fwiw, the tester is calling the -developer target
11:13 JBoyer I'm surprised that not finding chromium could possibly cause ELIFECYCLE though. Usually it just runs the tests in firefox instead and goes on,
11:14 phasefx I'm going to fire off the installer now; we'll get one more RSS error, but I can inspect the  state of the vm then and look for chromium
11:15 JBoyer I am also fairly certain that Debian and L'Ubuntue use different filenames. The package names are different and I don't think Debian uses a -browser suffice
11:15 JBoyer suffix, either.
11:15 sandbergja joined #evergreen
11:16 phasefx but I can say chromium is in the package list when the tester gathers the list of installed packages (it used to be chromium-browser; I thought chromium was a game)
11:17 JBoyer It is a game, but I think Debian added a suffix to the game no one (statistically) installs, while Ubuntu went the opposite direction.
11:17 phasefx in that case.. https://packages.debian.org/st​retch/amd64/chromium/filelist says it should be /usr/bin/chromium
11:19 * phasefx aborted the install, http://testing.evergreen-ils.org/~live/ looks awesome :)
11:19 Dyrcona I was getting ELIFECYCLE the other day after updating node and doing npm install.
11:20 JBoyer phasefx, I don't suppose you totally blew away /usr/local/lib/node_modules and so on? that's what it took to un-stick one of my dev servers. :/
11:20 Dyrcona I had to blow the pre-existing Node installation away and reinstall the new one: https://pastebin.com/AXMCWyHC
11:22 JBoyer Ah, not that then. :)
11:22 Dyrcona Nope, guess not...
11:24 Dyrcona Chromium has been acting "strange" for me on Ubuntu 19.10 lately, but I haven't rebooted since I noticed it, just logged out and back in (for an unrelated reason).
11:31 phasefx alright, new test running with CHROME_BIN set
11:32 * phasefx should add an env dump at the end along with the installed debian and cpan packages
11:33 phasefx be funny if installing chromium unsets my CHROME_BIN :)
11:38 JBoyer Chrome was in, but now CHROME_BOUT
11:39 phasefx it's an ELF on a shelf
11:41 Dyrcona phasefx++
11:43 phasefx we are such nerds
11:43 Dyrcona Indeed!
11:44 Christineb joined #evergreen
11:44 Dyrcona Which reminds me to tell JBoyer that I wrote the C program to login via SIP2 and set it up as haproxy check program on my test system. I statically linked it because of the chroot.
11:48 JBoyer Dyrcona, not too lousy to track down the necessary libraries, eh?
11:50 Dyrcona Well, the sip2 login only requires libc...
11:52 Dyrcona The other programs in the chroot require about 38 libraries.

Results for 2019-10-29

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

Results for 2019-10-28

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

Results for 2019-10-27

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

Results for 2019-10-26

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

Results for 2019-10-25

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

Results for 2019-10-24

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

Results for 2019-10-23

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

Results for 2019-10-22

09:53 Bmagic https://hub.docker.com/r/mobiusoffice/evergre​en-ils/tags?page=1&amp;ordering=last_updated
10:22 nfBurton joined #evergreen
10:28 sandbergja joined #evergreen
10:32 pinesol News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-10-22T10:04:33,122124693-0400 -0>
10:32 pinesol News from qatests: Failed Log Output: osrfsys.log <http://testing.evergreen-ils.org/~li​ve/test.76.html#2019-10-22T10:04:33,164852976-0400 -2>
10:37 yboston joined #evergreen
10:54 abowling_ joined #evergreen
10:57 tlittle joined #evergreen
11:09 sandbergja joined #evergreen
11:17 alynn26 joined #evergreen
11:31 alynn26_away joined #evergreen
11:42 berick sandbergja: question about org-family-select.component.spec.ts .. were the "fixture.whenStable().then(() ... " checks solving a specific problem?  i ask because those are causing the (naive) linter to throw erros
11:42 berick sandbergja: see http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-10-22T10:04:33,122124693-0400%20-0
11:43 berick i have tried commenting out the if block and the tests continue to work
11:43 berick i'm wondering if we can just remove those checks
11:44 berick test runner, i mean, not linter
11:52 gmcharlt link to the slides for my presentation: https://bit.ly/evghack19leap
11:55 * dbs is intrigued by the slides, but they leave out the destination of the leap!
11:58 Dyrcona :)
12:43 dbs Dyrcona: maybe I'm really forgetting my git, but the workflow I'm intending is: 1. Checkout a clean rel_3_3 branch 2. Merge the rel_3_4 branch on top of it
12:43 Dyrcona dbs: Why?
12:43 Dyrcona Just checkout rel_3_4.
12:43 dbs Testing the upgrade path from rel_3_3 to rel_3_4 for those who install from git
12:44 Dyrcona That's not how you upgrade.
12:44 Dyrcona Well, now how I upgrade.
12:44 dbs Funny, that's how I've upgraded ever since we moved to git
12:54 agoben Glad you can still get on, but frustrating news.
12:54 Dyrcona It's probably a configuration in Chromium thing.
12:54 agoben mmhmm
12:56 sandbergja berick: I think that the whenStable() business might have been autogenerated.  I don't believe they serve any purpose
12:57 sandbergja I'd been fiddling with an angular unit test auto-generator at the time, so the timing is suspicious. :-)
12:57 Dyrcona hurrah for looking at diffs before committing... I found a "bug" in my README changes.
13:05 _bott_ joined #evergreen
13:05 berick sandbergja: ok, cool, i'll push a patch to remove them, for now anyway, so we can un-break the test server
13:05 csharp berick: https://pastebin.com/i2Q4Hfme
13:06 sandbergja berick++
13:07 csharp berick: https://bugs.launchpad.net/evergreen/+bug/1712861
13:49 Bmagic sandbergja++
13:51 alynn26 bmagic++ sandbergja++
13:57 phasefx Dyrcona: broke again :D :D
13:57 berick phasefx: sandbergja: fix for test server errors: https://git.evergreen-ils.org/?p=working/​Evergreen.git;a=shortlog;h=refs/heads/use​r/berick/lp1830973-ang8-test-spec-repair
13:57 phasefx berick++
14:00 Dyrcona I wonder if we really need the different numbered versions of 000.english.pg94.fts-config.sql. It hasn't changed since Pg 9.4.
14:00 terranm joined #evergreen
16:47 bshum I know our Node version we checkout is pretty ancient
16:48 bshum For the makefile anyways
16:48 bshum Too new and stuff tends to break
16:48 dbs "npm build prod" was fine but "npm run test" fails due to PhantomJS (I seem to recall that being a known issue)
16:48 dbs This in on Ubuntu Xenial. I'm just following the docs, which tell people to download and use Node LTS
16:49 dbs (https://evergreen-ils.org/documentat​ion/install/README_3_4_0.html#_insta​ll_dependencies_for_web_staff_client)
16:50 bshum I guess that's a bad instruction :)
16:50 bshum We put the specific Node version in the makefile prereqs awhile ago
16:50 bshum Though we should have bumped that a few times ago
16:51 pinesol Launchpad bug 1849372 in Evergreen 3.4 "angular: modals do not automatically close when navigating away from pages" [Medium,Confirmed] https://launchpad.net/bugs/1849372
16:51 dbs ah the advantage of fresh eyes :)
16:51 abowling joined #evergreen
16:51 Dyrcona dbs: I almost never run the tests, and either do node programmers.:)
16:52 bshum dbs: I probably just didn't notice because I ran the "optional developer additions" options during my read-through
16:52 bshum And it tells me to skip that step if I do :D
16:52 abowling joined #evergreen
16:53 * bshum needs more newbies around to keep us honest
16:53 Dyrcona The latest node lts is probably too new for us.
16:53 bshum It definitely is
16:53 JBoyer all of this talk about tests has me thinking about lp 1845693
16:53 pinesol Launchpad bug 1845693 in Evergreen "Replacement needed for PhantomJS" [Undecided,New] https://launchpad.net/bugs/1845693
16:54 bshum Or it was...
16:54 bshum Hmm
16:55 Dyrcona I installed that today, but didn't notice the node version.
16:56 bshum "That's what you get for missing staff meetings, Doctor."
16:56 Dyrcona :)
16:56 dbs So I guess we should get rid of the docs that tell people to manually install node and run tests?
16:56 Dyrcona I was at that meeying.
16:56 Dyrcona dbs: Yes.
16:57 abowling joined #evergreen
16:58 abowling joined #evergreen
17:00 abowling joined #evergreen
17:01 bshum dbs++ # testing the docs
17:02 Dyrcona dbs++
17:04 abowling joined #evergreen
17:10 abowling_ joined #evergreen
17:24 Dyrcona It is probably too new for 3.4 or earlier, though. I have seen that before where upgrading Node and/or npm breaks the installation.
17:24 dbs Dyrcona++
17:25 Dyrcona So, to get the preferred Node for your release of Evergreen use the {distro}-developer prerequisite install step if you're installing from git.
17:26 dbs Right - that's pretty much what I was cutting the branch down to
17:27 dbs Weirdly, on 3.4 I seem to be able to run tests with PhantomJS on the /src/eg2/ dir but not on the /web/js/ui/default/staff/ dir
17:35 dbs Took the minimalist step first to just remove the "install latest LTS node from source" instruction as I'm not 100% confident about the eg2 vs. web/js/ui test situation
17:35 dbs https://git.evergreen-ils.org/?p=work​ing/Evergreen.git;a=shortlog;h=refs/h​eads/user/dbs/docs_remove_node_source
17:36 Dyrcona dbs: PhantomJS is out of date and no loneger maintained.  There are some recent JS constructs that it can't process, and I think one or two have slipped into the AngularJS code.
17:37 Dyrcona I briefly considered taking over the project to update it, but after about half an hour of looking into it, I decided that it would be more work than I'm able to take on right now.
17:41 dbs Right, I get that. I just hate taking out instructions to run tests if they work (which they seem to for /src/eg2/ for some reason)
17:42 dbs But if everyone runs into test failures with /web/js/ui/default/staff then we should stop telling people to test. I just wasn't sure if that was the actual state of things.
17:42 dbs I'll add another commit that removes the "npm run test" steps and related verbiage
17:46 dbs Updated the branch accordingly
20:54 sandbergja joined #evergreen
21:26 sandbergja joined #evergreen
21:40 sandbergja joined #evergreen
23:03 pinesol News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~li​ve/test.29.html#2019-10-22T23:00:56,173131253-0400 -0>
23:03 pinesol News from qatests: Failed Log Output: osrfsys.log <http://testing.evergreen-ils.org/~li​ve/test.76.html#2019-10-22T23:00:56,214485939-0400 -2>
23:13 sandbergja joined #evergreen
23:53 sandbergja joined #evergreen

Results for 2019-10-21

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

Results for 2019-10-20

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

Results for 2019-10-19

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

Results for 2019-10-18

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

Results for 2019-10-17

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

Results for 2019-10-16

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

Results for 2019-10-15

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

Results for 2019-10-14

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

Results for 2019-10-13

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

Results for 2019-10-12

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

Results for 2019-10-11

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

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