Evergreen ILS Website

IRC log for #evergreen, 2018-11-16

| 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
04:51 gsams__ joined #evergreen
04:53 aabbee joined #evergreen
07:07 rjackson_isl joined #evergreen
07:11 annagoben joined #evergreen
07:44 bdljohn joined #evergreen
08:20 bdljohn joined #evergreen
08:41 mmorgan joined #evergreen
08:48 kmlussier joined #evergreen
08:52 jvwoolf joined #evergreen
09:02 jvwoolf1 joined #evergreen
09:12 Dyrcona joined #evergreen
09:17 bos20k joined #evergreen
09:17 eby https://drewdevault.com/2018/11/1​5/sr.ht-general-availability.html
09:24 remingtron_ joined #evergreen
09:24 mdriscoll joined #evergreen
09:35 terran joined #evergreen
09:37 yboston joined #evergreen
10:15 beanjammin joined #evergreen
10:40 khuckins__ joined #evergreen
11:03 yboston joined #evergreen
11:13 jvwoolf joined #evergreen
11:27 kmlussier mmorgan++ https://evergreen-ils.org/michele-morg​an-evergreen-contributor-of-the-month/
11:27 Bmagic mmorgan++
11:30 mmorgan Thanks!
11:37 bshum Who's release maintainer for 3.2 and 3.1?
11:37 Bmagic bshum: you right?
11:37 bshum Later this weekend I'm thinking to help review (the many) pullrequest tagged bugs pointed at the maintenance branches
11:38 bshum I don't like lingering "high" bugs pointed at point releases that go on and on
11:38 berick 3.2 is me
11:38 bshum They either need to get tested and pushed or downgraded out of "high" if we're not going to block maintenance cuts.
11:39 bshum Since we are planning the next round next Wednesday, going to see what dents I can help to make :)
11:39 bshum Err, Tuesday
11:39 bshum berick: Cool, cool, I'll mention if I see anything too weird.  Thanks!
11:39 Bmagic bshum++
11:39 berick thanks bshum
11:42 jvwoolf1 joined #evergreen
11:43 jvwoolf2 joined #evergreen
11:54 yboston joined #evergreen
12:03 nfburton joined #evergreen
12:05 jihpringle joined #evergreen
12:05 nfburton Does anyone have a setup that the sys admin can get alerts when osrf services go down? I know you can do it with system services but I am just not sure about osrf.
12:09 yboston joined #evergreen
12:21 bshum nfburton: So maybe something like what Opensrf's examples/nagios/check_osrf_services could do?
12:21 * bshum hasn't dabbled much with notifications, just pointing out things that exist
12:25 bshum nfburton: https://wiki.evergreen-ils.org/doku​.php?id=evergreen-admin:monitoring
12:25 bshum Also this old presentation too
12:26 nfburton Thast looks decent. We are using LibreNMS and that may be adaptable for it. I just had a server and a half of osrf services stop on me and want to be notified especially if I am off site
12:26 nfburton bshum++ thanks for the direction. I was sure something was out there
13:43 bdljohn joined #evergreen
14:28 wcuster joined #evergreen
14:38 csharp nfburton: this is what we use: http://git.evergreen-ils.org/?p=contrib/pin​es.git;a=blob;f=nagios/check_osrf;h=24f7b8b​620dc16613bc23ea373d2e388fdefee9a;hb=HEAD
14:38 csharp it runs "osrf_control --diagnostic" and greps the output
14:39 csharp ...and they left
14:40 * csharp wants everyone to be in IRC all the time like he is
14:40 * Dyrcona needs to go through our nagios stuff one day and change them to do something that makes sense in this day and age.
14:40 * Dyrcona doesn't use quassel.
14:41 csharp I'd like my script to take the percentages into account and warn on those, but I haven't gotten to it
14:44 Dyrcona Well, you really only care if some service dies, or you run out of drones. Percentages, like being close to running out, don't really matter.
14:56 gmcharlt the trends matter, though
15:09 kmlussier joined #evergreen
15:11 nfburton joined #evergreen
15:12 nfburton Had too many tabs open and closed this out.....
15:12 nfburton csharp++
15:14 nfburton Looks like everyone uses Nagios but us lol
15:20 Dyrcona Well, there are some nagios examples hanging around, so.
15:22 nfburton Helpful examples definately. I like csharp's. Nice and small
15:28 nfburton Also, how important is the Unique constraint asset_call_number_label_once_per_lib on asset.call_number in the DB? Updating them manually in the web interface, they update fine, but doing it through the backend, I keep getting stonewalled
15:29 nfburton Will I break anything if I turn that off for my updates? I'm just cleaning up suffix records
15:30 nfburton Context:  CREATE UNIQUE INDEX asset_call_number_label_once_per_lib ON asset.call_number (record, owning_lib, label) WHERE deleted = FALSE OR deleted IS FALSE;
15:35 Bmagic nfburton: it's OK do disable it but while it's disabled the database could receive new call numbers that will be in conflict. If the database is being used in production while you disable the trigger, bad things. Turn off access to the databse while you have it disabled to be safe
15:36 khuckins joined #evergreen
15:38 mmorgan nfburton: If you're running into collisions when you try and update in the db while cleaning up suffixes, you'll end up with duplicates if you disable that, which would also be bad.
15:39 Dyrcona nfburton: There's a SQL trick for dealing with that trigger without disabling it.
15:42 nfburton It's not a trigger but a constraint. If I update the record in the web client it works fine but I am not sure what extra query parts I need for that
15:42 nfburton but if you have a trick please do tell
15:45 Dyrcona https://www.postgresql.org/docs/9.5/plpgsql-c​ontrol-structures.html#PLPGSQL-ERROR-TRAPPING
15:46 Dyrcona That describes the mechanism that we use. Basically, you try the update, and if it fails, you get the id of the conflicting call number and update all relevant copies and other bits, then delete the call number that you were trying to update.
15:47 nfburton Dyrcona: I am already using a Function that allows me to run it on the items that dont violate the constraint but am left with a good number on each batch that do.
15:47 nfburton And I can manually do them in the web client but 'who's got the time?'
15:48 nfburton So how does that resolve the contrained items?
15:50 nfburton Some of these items are old serials on Local History items that became copies when migrated so they would have the same record, owning_lib and label :S
15:51 pastebot "Dyrcona" at 64.57.241.14 pasted "nfburton - real sample changing the prefix" (72 lines) at http://paste.evergreen-ils.org/14317
15:51 Dyrcona That's something that we actually used in a db update last month.
15:52 Dyrcona There was actually another block that altered labels in that function, but I figured the one block was enough to illustrate how to use it.
15:58 nfburton Thanks, I will try adding the bit to run on exception to remap.
15:58 nfburton Dyrcona++
16:09 Dyrcona Did the committee decide to extend the deadline for pre-conference proposals?
16:09 * Dyrcona submitted one today, anyway.
16:11 kmlussier Dyrcona: What's the topic?
16:11 Dyrcona Intro. to Back End Evergreen Programming
16:12 kmlussier Ooh!
16:12 mmorgan Dyrcona++
16:12 kmlussier That one sounds fun.
16:13 kmlussier Dyrcona++
16:14 Dyrcona I hope it is fun and useful for the attendees.
16:16 rhamby Dyrcona: I haven't seen anything about them extending but including your's that makes 4 I know of being submitted and they have four slots so ...
16:17 Dyrcona Well, OK.
16:51 pinesol [evergreen|Jason Boyer] LP1755625: Multiple emails in patron editor - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=1b20e4e>
16:57 kmlussier @dessert add Raspberry Pillow Cookies
16:57 pinesol kmlussier: The operation succeeded.  Dessert #58 added.
16:57 kmlussier @dessert [someone]
16:57 * pinesol grabs some Non-Vanilla Ice Cream for devted
16:57 mmorgan kmlussier++
17:00 devted pinsol: thank you!
17:00 devted pinesol: thank you!
17:00 pinesol devted: As great as you are man, you'll never be greater than yourself.
17:01 * devted eating_ice_cream
17:02 jihpringle CONC40000605
17:02 jihpringle oops, wrong window
17:02 Dyrcona :)
17:02 kmlussier jihpringle: I think I recognize that barcode. :)
17:03 jihpringle :)
17:03 devted pinesol: "Deep thoughts for a feel-good-Friday - thank you for the fortune cookie and back-at-ya!
17:03 pinesol devted: Error: No closing quotation
17:03 devted pinesol: "Deep thoughts for a feel-good-Friday - thank you for the fortune cookie and back-at-ya!"
17:03 pinesol devted: <shaggy>We're, like, doomed.</shaggy>
17:05 devted pinesol:   ya caught that in milliseconds! Probably showed-up like SHOUTING or fingers on a chalkboard. Glad IRC isn't Lisp!
17:05 pinesol devted: Sorry, we can't do that because, you know, SOFTWARE.
17:06 bshum @roulette
17:06 pinesol bshum: *click*
17:06 kmlussier devted: pinesol is a bot who has canned responses when you try to talk to it.
17:06 kmlussier :)
17:06 Dyrcona @dunno
17:06 pinesol Dyrcona: http://www.firstpersontetris.com/
17:06 bshum @sortinghat
17:06 pinesol Hmm... bshum... Let me see now... HUFFLEPUFF!
17:06 kmlussier Sorry, I meant to say something earlier, but then I got distracted by jihpringle's barcode.
17:07 * kmlussier gets distracted very easily at 5 p.m. on a Friday.
17:07 Dyrcona OOh, shiny!
17:07 devted kmlussier: HA! I was about to ask Blake that but he's on the phone... pinesol answered back within milliseconds both times... in-human or very admirable
17:07 kmlussier The sad thing is, Concerto barcodes aren't all that shiny.
17:08 kmlussier pinesol is quite admirable.
17:08 pinesol kmlussier: Try running autogen
17:08 bshum I think we used to have pinesol say that it was a bot whenever it generated an unknown error.
17:08 bshum But then I removed it from the code for giggles
17:08 bshum Seemed more natural that way
17:08 kmlussier I think regulars got tired of seeing it.
17:09 bshum "regulars" lol
17:09 mmorgan left #evergreen
17:09 kmlussier bshum: Sure, you know those people who spend every waking minute in the channel. Sound like anyone you know? :)
17:11 bshum kmlussier: I'm glad I don't do that anymore :)
17:11 mdriscoll left #evergreen
17:13 kmlussier OK, maybe I should rephrase as every working moment.
17:14 bshum Even when we're not working?  :)
17:21 Dyrcona @quote random
17:21 pinesol Dyrcona: Quote #189: "<Stompro> How come evergreen doesn't have a fax reactor for the action_trigger system? We get people coming in all the time that say the only way to contact them is via their fax line. I think fax use is really going to take off in 2019." (added by Dyrcona at 04:57 PM, July 13, 2018)
17:23 bshum 2019's right around the corner.  Here we go!
17:34 khuckins joined #evergreen
18:50 sandbergja joined #evergreen

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