Evergreen ILS Website

IRC log for #evergreen, 2016-09-03

| Channels | #evergreen index | Today | | Search | Google Search | Plain-Text | summary | Join Webchat

All times shown according to the server's local time.

Time Nick Message
12:46 bmills joined #evergreen
13:10 rlefaive joined #evergreen
13:34 * csharp LOLs
13:35 csharp last night we did some system maintenance, including some datawork, and all looked well when we quit
13:35 csharp this morning, we got multiple helpdesk tickets saying that the patron voter registration survey was no longer showing in the patron reg form
13:36 csharp so I immediately assumed we'd broken something, of course
13:36 csharp turns out, the survey, whose "start date" was 9/2/2006 had an "end date" of 9/2/2016
13:37 csharp so I guess phasefx, miker, or berick (or bradl) couldn't have imagined that EG would have lasted this long, at least in PINES
13:37 csharp tl;dr: HAPPY 10th BIRTHDAY, EVERGREEN! ;-)
13:38 miker heh :)
13:39 * csharp set the new end date to 9/2/2036, since *he* can't imagine it lasting another 20 years
13:40 miker csharp: I created a couple reports in '08, I think, as a canary to make sure Clark was running. still get emails on the first of every month
13:40 csharp miker: I've seen those before and wondered if you were still getting them
14:03 * dbs wonders how many sites actually install Evergreen from the release tarballs vs. their own git repos w/ customizations, and what that would mean for the docs if it turned out that the answer was "almost everyone installs from a custom git branch"
14:08 dbs http://docs.evergreen-ils.org/2.10/_optional_extr​a_steps_for_browser_based_staff_client.html#_inst​all_dependencies_for_browser_based_staff_client links to a node.js install doc page that no longer exists, and the "moved to" link points to generic node.js docs, nothing specifically about installaion
14:09 dbs would https://nodejs.org/en/download/package-manager maybe be a better destination?
14:11 dbs or maybe not link there at all, if we're really building node.js 0.10.28 from source instead of the node.js LTS packaged release of 4.5.0
14:13 dbs 0.10.28 was released in 2014... maybe I'm just going to skip the web staff client for now.
14:14 bmills joined #evergreen
14:18 bmills1 joined #evergreen
14:18 bmills1 joined #evergreen
14:23 csharp dbs: we install from release tarballs and overlay our customized files on top
14:25 dbs csharp: seems like a good approach, too
14:29 csharp you can really only document agreed-upon releases, which is why we are not in the "run EG from master" camp
14:30 dbs maybe if we had a couple of different approaches documented, even just as wiki pages that are linked from the docs, that might help less sysadmin-savvy sites
14:30 dbs csharp: heh, we're in the "run EG from rel_2_10 camp" (or will be if all goes well over the next couple of days)
14:39 csharp dbs: best of luck!
14:40 dbs thanks, router just responded '4' to opensrf.math add 2,2 so things are going well so far :)
15:47 csharp sheesh - purging old resolved transits is totally not fast and I have like 19M to do :-/
15:48 csharp I don't see any triggers to disable or anything, but I'm assuming it has to check the tables that inherit it
15:48 csharp been running for >16 hours
15:51 csharp yep - EXPLAIN confirms that it does a seq scan of action.transit_copy, action.hold_transit_copy and action.reservation_transit_copy
15:51 csharp thatsa buncha rowsa
15:56 dbs wow.
15:57 dbs any indexes that might help avoid the seq scan?
16:03 dbs mmm. trying node 4.5.0 from the 3rd party packages, but npm is very unhappy at npm install time about the other nodejs packaged modules that were previously installed by Makefile.install (because they're ancient)
16:04 dbs I really should let this go
16:04 csharp I think this describes what's happening: http://grokbase.com/t/postgresql/pgsql-gen​eral/047122kcsf/slow-deletion-of-data-from​-tables#20040708rozrweucvkkb2nxqvb5t5qq43i
16:07 csharp your experience is illustrating my queasiness about the nodejs dependencies in general - seems like it's not nearly as reliable as, say, CPAN
16:08 * dbs uses 'apt-cache autoremove' to get rid of the old ubuntu-trusty universe nodejs packages
16:09 dbs well in this case it was primarily the ubuntu-trusty version of nodejs causing the problem. also our docs saying to install nodejs ancient version from source when our Makefile.install installs the slightly more ancient ubuntu-trusty package is surprising
16:11 dbs oh yay, now that the crufty packaged versions are gone I get unmet dependency errors. forget this.
16:12 csharp ugh
16:17 dbs For posterity: http://pastebin.ca/3710320
16:32 dbs oh hey, 'rm -fr node_modules bower_components && npm install && bower install && grunt all' worked a lot better (still a number of deprecation and DoS warnings but works...)
17:12 gmcharlt joined #evergreen
17:16 gmcharlt joined #evergreen
17:25 dbs joined #evergreen
17:32 dbs joined #evergreen
17:39 dbs joined #evergreen
17:59 dbs joined #evergreen
18:05 dbs joined #evergreen
18:10 dbs joined #evergreen
18:15 dbs joined #evergreen
18:57 dbs joined #evergreen
19:02 dbs joined #evergreen
19:06 jeff joined #evergreen
19:43 dbs joined #evergreen
20:08 dbs joined #evergreen
21:46 dbs joined #evergreen
22:35 dbs sorry folks: https://status.linode.com/

| Channels | #evergreen index | Today | | Search | Google Search | Plain-Text | summary | Join Webchat