Evergreen ILS Website

IRC log for #evergreen, 2015-06-25

| 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
00:02 bshum @later tell terran Aha, from the #evgils vault, https://twitter.com/smkvt/status/63353498598780928 -- the PINES cats!
00:02 pinesol_green bshum: The operation succeeded.
00:03 kmlussier My daughter still has that cat.
00:04 jeff pretty sure they were gone before i got there.
00:04 bshum Mine is sitting on my desk at home next to the rest of my stuff.
00:04 bshum I should move it to the shelf of things
00:07 kmlussier I was going to poke at release notes tonight, but I just realized I'm exhausted. I guess I'll call it a day.
00:07 bshum Or at least let my penguins make friends with the kitten.
00:07 kmlussier heh
00:08 kmlussier Have a nice night guys!
00:08 bshum Goodnight!
02:21 eady joined #evergreen
07:42 jboyer-isl joined #evergreen
08:28 Dyrcona joined #evergreen
08:40 mrpeters joined #evergreen
08:41 mmorgan joined #evergreen
08:42 akilsdonk joined #evergreen
08:58 Shae joined #evergreen
09:03 maryj joined #evergreen
09:12 Newziky joined #evergreen
09:15 husanux8 joined #evergreen
09:20 collum joined #evergreen
09:20 husanux1 joined #evergreen
09:25 husanux8 joined #evergreen
09:25 mmorgan @coffee
09:25 * pinesol_green brews and pours a cup of Colombia Finca Cerro Azul, and sends it sliding down the bar to mmorgan
09:26 mmorgan The virtual coffee sounds way better than my actual coffee :-(
09:27 Dyrcona @tea
09:27 * pinesol_green brews and pours a pot of Bio Pao Chung Pouchong, and sends it sliding down the bar to Dyrcona (http://ratetea.com/tea/teehaus-bachf​ischer/bio-pao-chung-pouchong/7609/)
09:33 kmlussier mmorgan: The one thing I can say about this week is that I have been enjoying some very good coffee. Not the virtual kind, either. :)
09:34 mmorgan And lots of good information by the sound of it! Is it local coffee?
09:35 kmlussier mmorgan: I'm guessing it is. I tend to gravitate towards small coffeehouses
09:35 yboston joined #evergreen
09:35 * mmorgan needs to visit more local coffeehouses.
09:37 mmorgan kmlussier: When does your conference end?
09:37 kmlussier Today is my last day at Open Source Bridge. It continues tomorrow, but I'll be heading to SF in the morning for ALA.
09:37 mmorgan Very busy week!
09:38 kmlussier By which time I hope to be operating on West Coast time.
09:50 * mmorgan 's fingers are not working this morning. "workded" isn't a word, and there's no asset.coopy table :-(
09:56 jboyer-isl asset.coopy sounds like a nerdy place to get egggs. :D
09:57 csharp kmlussier: how goes the outreach?
09:58 csharp asset.coopy++ #evergreen-ilsjokes
09:59 kmlussier csharp: Good, I think! We seem to have everything lined up, though I'm sure we're forgetting something.
10:00 csharp kmlussier: awesome
10:17 jwoodard joined #evergreen
11:13 Stompro Gaaaahhh, an excavator pulled all the phone and data cabling out of one of our largest branches yesterday and 5pm, pulling the PBX off of the wall and damaging it.  "I was told all this cabling was garbage" quote the driver.
11:14 bshum Oops.
11:15 yboston wow
11:15 Dyrcona yipe.
11:22 jeff "well, it is now." -- coworker
11:24 jonadab Indeed.
11:31 jwoodard_ joined #evergreen
11:33 Stompro yboston, docs question for you, I just saw that Angela pushed some docs to rel_2_6, which I thought wasn't getting any more updates.  Are doc updates considered ok to push to older branches?
11:34 yboston great question
11:34 yboston for docuemntation we follow looser rules than code committers
11:35 yboston when applicable a lot of us that have git access for docs
11:35 yboston will go back and back port docs to older versions
11:35 kmlussier Overall, I try to backport just to supported releases. But I don't have any objections when people backport further.
11:35 berick to clarify, pushing changes to 2.6 is not against any rules.  we're just not officially maintaining 2.6 (because finite resources, etc.)
11:37 bshum Right.  Backporting sometimes takes extra work for code, with drift between major versions.  If the docs are easier to backport (mainly in that there are no conflicts where docs didn't exist before, now they exist?), then that doesn't seem like a huge extra burden.
11:39 yboston in my experience, docs are usally pretty easy to back port. Though once or twice I had conflicts becuase features to change over time. Which provided excellent practice in using git
11:41 Stompro Thanks for the clarification, since I'm working on some older doc items from 2.5 that is good to know.
11:42 * Dyrcona thinks it is a wast of time to push to a branch that is not getting releases.
11:44 pinesol_green [evergreen|Angela Kilsdonk] Docs: 2.8 Patron Message Center - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=40605b3>
11:44 yboston Stompro: I suspect you mean that you are working on undocumented new features that first appeard in 2.5?
11:44 bmills joined #evergreen
11:45 yboston Stompro: that you want to add to master, etc
11:45 Stompro yboston, yes, that is correct.
11:45 yboston Stompro: I have done that too. Add the feature to the original version adn then to master/latest release
11:46 Dyrcona I'd recommend going to master, first, then to the older releases. That's pretty much how we do it with the code.
11:46 yboston there are features from versiosn older than 2.5 that need to be added to master. I guess we can choose to limit the backporting to the currently supported versions?
11:46 * bshum made the same suggestion at past DIG hackaways
11:46 Stompro I find that I have to go back and search through previous releases of the documentation quite often, to find things that were in the release notes but never made it into the docs.  And from there try to find the commit that the release notes are based off of, to figure out how something work.
11:48 yboston Dyrcona: I sometimes do it your way other times I go in reverse order. I guess it matters if I created a topic branch from master or from the older release
11:48 yboston I can be convinvec to always do it from master, though ny now that is what I usually do
11:49 yboston *convinced
11:52 Dyrcona It's rare that you would have conflicts with documentation commits, but I imagine you would have less going to master first, then "backporting."
11:53 yboston Dyrcona: that makes sense;
12:01 jihpringle joined #evergreen
12:02 Stompro Do you think this is a typo, just found this in the 950.data.see-values.sql    "'zcat.oclc.org', 210, 'OLUCWorldCat', TRUE);"  Should that be "OCLCWorldCat' or does OLUC mean something?'
12:05 Stompro It must mean something, that is the db name, not the label, so that entry wouldn't work if it was wrong, which I think would have been noticed by now.
12:06 jonadab Stompro: https://www.oclc.org/worldc​at/catalog/timeline.en.html
12:06 * jeff is amused at the typo in Stompro's question about a typo
12:07 Stompro hehe, see all the values.
12:12 Stompro jonadab, thanks for the link.
12:14 Stompro akilsdonk, Are you also going to document the A/T side of the patron message center?
12:24 buzzy joined #evergreen
12:33 Newziky left #evergreen
12:36 krvmga joined #evergreen
13:18 jeff the HoldIsAvailable validator validates more than just "hold is available"
13:18 gmcharlt indeed
13:18 jeff though i suppose the additional checks are optional.
13:20 jeff (there are three params which can be set: check_email_notify, check_sms_notify, check_phone_notify)
13:21 mmorgan So it's really validating based on the hold being available AND the patron wanting a notification?
13:22 tsbere Only if the other vars are set. Mainly to avoid erroring out in various ways when generating the notification without the notification being desired.....or, for email notification, sending it no matter what.
13:24 jeff mmorgan: when you configure an A/T event definition, you can optionally set a parameter under Event Parameters that will cause HoldIsAvailable to return false if your choice of those three checks return false.
13:25 mmorgan Ah, ok. Interesting.
13:25 jeff happily, they are optional, so if you want something that pokes an automated system by email (or in the future, webhook or something) you can have that, and it will fire on every hold, even a hold with zero notifications enabled.
13:27 * mmorgan runs off or a bit, realizing there's a lot more to learn about action triggers
13:35 akilsdonk joined #evergreen
13:36 akilsdonk 612-273-7110
13:36 akilsdonk oops.... wrong window completely!
13:38 akilsdonk Stompro: There's a little bit in the documentation about creating a patron message using action triggers, but I don't have any documentation beyond that.
13:42 Stompro akilsdonk, oh, there it is, thanks, I didn't see that when I first looked at your commit.
13:45 kmlussier @coin
13:45 pinesol_green kmlussier: tails
13:46 akilsdonk Stompro: I committed it to master.  If all looks good after it's processed tonight, I'll cherry pick it to 2.8.
14:02 husanu5 joined #evergreen
14:07 Dyrcona typos--
14:07 Dyrcona IdnetiferValue <> IdentifierValue
14:10 Dyrcona And, I may be dropping off the network in a minute or two.
14:10 jeff tip: if you're going to move an existing A/T def from being ungrouped to being grouped, you should verify that your templates account for the fact that you're going to start getting an array in some places. either that, or you're going to be reminding yourself how you reset an event to re-run after you revert or fix your change. :-)
14:13 Dyrcona1 joined #evergreen
14:15 Dyrcona Yep.
14:17 jboyer-isl I wonder if it's a bad idea to connect to a vm, then connect to it's host, then run apt-get upgrade when qemu-kvm packages are involved. I suppose I'll find out shortly.
14:18 jboyer-isl Surprise! It's fine.
14:22 jeff jboyer-isl: this is why you have a console, right? ;-)
14:23 jboyer-isl jeff: this is why we have dev! nothing is too dangerous to test on a machine you don't need (at the moment).
14:24 jboyer-isl (I haven't installed our iLO licenses yet, so I would be quite cross if I had to make a personal appearance at the DC...)
14:25 jeff oh, i just meant your console from the vm host to the vm guest.
14:27 jboyer-isl jeff: Oh, sure. I wondered about the possibilities of interrupting an upgrade because you shut down the "remote" machine that started it and the state of the machine at that point.
14:27 jboyer-isl I guess having ssh go offline would be extremely unusual, but I expect things to blow up for real if they're going to blow up at all.
14:29 Dyrcona We've had ssh go out when a server ran out of RAM and started killing things.
14:30 Dyrcona Since we'd restricted what OOM Killer could kill, it picked on SSHD, 'cause it was about the only thing left.
14:31 jboyer-isl I imagine sshd found it's way to the list of restrictions pretty shortly after that, eh? ;)
14:33 jboyer-isl Further learnings for the day: a vmhost with no/dead raid cache batteries is a lousy thing to do i/o on. :/
14:34 Dyrcona jboyer-isl: No, actually, 'cause we replaced the server about 1 week later.
14:35 jboyer-isl That's also a fine way to handle it.
14:37 Dyrcona Yes, particularly when 1 servers is replaced by 6 or so VMs spread over two physical servers.
14:58 Dyrcona Anyone ever notice that OpenILS.pm in master says our $version = '2.4'; ?
14:58 Dyrcona Sorry, it should be $VERSION. -- typoing from memory. ;)
14:59 Dyrcona Not that that particular version is ever used anywhere.
15:00 jeff good candidate for release checklist.
15:01 Dyrcona might already be there.
15:01 Dyrcona I know the version that OSRF call returns is.
15:06 Dyrcona Guess 2.4 is an improvement. Prior to that it was 2.00. ;)
15:10 bshum Dyrcona: Yeah, that could get bumped I guess.
15:11 bshum We bump that by hand in the rel_ branches
15:11 bshum Before we run make_release script
15:22 jihpringle joined #evergreen
15:36 abowling joined #evergreen
15:46 rlefaive joined #evergreen
16:25 akilsdonk_ joined #evergreen
16:35 bmills joined #evergreen
16:40 akilsdonk joined #evergreen
16:44 Dyrcona jeff++ # Getting karma in #koha. ;)
16:45 jeff heh
16:45 Dyrcona <?= "$greeeting $time_of_day, $first_name" ?>
16:46 Dyrcona I almost shared that earlier, but after you did yours, it seemed like copying. ;)
16:46 jeff heh
16:46 jeff i was going for the retro NetWare vote.
16:46 Dyrcona Should put p tags in there for full effect.
16:46 Dyrcona I get lost of spame with %SUBJECT and so on .
16:47 Dyrcona spame?
16:47 Dyrcona spam.
16:47 Dyrcona lost....
16:47 Dyrcona Ugh. Is today over, yet?
16:47 mmorgan typos--
16:47 Dyrcona Indeed. :)
16:48 Dyrcona Well, one more day of packing before the office move actually starts.
16:49 Dyrcona On Saturday, the servers and desktop computers get moved by the moving company.
16:49 akilsdonk joined #evergreen
16:49 Dyrcona And then the rest of the office furniture on Monday.
16:49 Dyrcona Oddly enough, most of the offices have desks in them already, except for us tech. staff.
16:50 Dyrcona We're keeping our old desks and others get "new" desks.
16:51 mmorgan Sounds like lots of fun ;-)
16:51 Dyrcona Yep. Loads.
16:59 jwoodard_ ok so remind me where you can edit the max fine limit for patron groups
16:59 jwoodard_ It has been one of those days
17:02 mmorgan jwoodard_: You should find that in Circulation Policies (Admin - Local Admin - Circulation Policies)
17:08 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
17:10 mmorgan left #evergreen
17:25 jwoodard_ thanks mmorgan++
18:01 buzzy joined #evergreen
18:19 mrpeters left #evergreen
19:58 _robbat2|irssi left #evergreen
21:59 finnx joined #evergreen
23:58 kmlussier @sortinghat
23:58 pinesol_green Hmm... kmlussier... Let me see now... SLYTHERIN!
23:58 kmlussier Excellent!

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