| Time |
Nick |
Message |
| 00:24 |
|
ningalls joined #evergreen |
| 00:26 |
|
RBecker joined #evergreen |
| 00:36 |
|
ningalls joined #evergreen |
| 00:42 |
|
jboyer-isl joined #evergreen |
| 00:57 |
|
Bmagic joined #evergreen |
| 01:21 |
|
RBecker_ joined #evergreen |
| 02:01 |
|
RBecker joined #evergreen |
| 02:02 |
|
pmurray joined #evergreen |
| 02:02 |
|
pmurray joined #evergreen |
| 04:06 |
|
RBecker joined #evergreen |
| 06:39 |
|
BigRig joined #evergreen |
| 06:39 |
|
ningalls joined #evergreen |
| 07:28 |
|
Shae joined #evergreen |
| 07:30 |
|
rjackson-isl joined #evergreen |
| 07:59 |
|
collum joined #evergreen |
| 08:03 |
|
akilsdonk joined #evergreen |
| 08:18 |
|
mrpeters joined #evergreen |
| 08:34 |
|
ningalls joined #evergreen |
| 08:44 |
|
finnx_ joined #evergreen |
| 08:46 |
|
finnx joined #evergreen |
| 08:46 |
|
finnx joined #evergreen |
| 08:47 |
|
tater joined #evergreen |
| 08:48 |
|
finnx joined #evergreen |
| 08:48 |
|
phasefx joined #evergreen |
| 08:48 |
|
Callender joined #evergreen |
| 08:48 |
|
BigRig joined #evergreen |
| 08:49 |
|
finnx joined #evergreen |
| 08:52 |
|
akilsdonk joined #evergreen |
| 08:52 |
|
finnx joined #evergreen |
| 09:05 |
|
adbowling-isl joined #evergreen |
| 09:20 |
|
ericar joined #evergreen |
| 09:25 |
|
_bott_ joined #evergreen |
| 09:40 |
|
jbfink joined #evergreen |
| 09:49 |
|
montgoc1 joined #evergreen |
| 10:05 |
bshum |
Pondering bug 838296 again today. |
| 10:05 |
pinesol_green |
Launchpad bug 838296 in Evergreen "Seperate the MarkItemLost reactors from running with the rest of the daily triggers. " (affected: 1, heat: 6) [Wishlist,Incomplete] https://launchpad.net/bugs/838296 |
| 10:05 |
bshum |
Looks like we had our utility server exhaust all its memory and swap overnight dealing with A/T events. |
| 10:06 |
bshum |
As I read that though, I'm wondering about the granularity='daily' portion of the upgrade action to break up the triggers. In the stock DB, I don't see granularity being defined, so it seems like it won't affect anything running the upgrade script. |
| 10:08 |
bshum |
So I guess the question is two-fold: 1) should granularity be assigned by default in the stock DB, and 2) should the bug be updated to reflect that? |
| 10:48 |
|
keggle joined #evergreen |
| 10:54 |
bshum |
Hmm |
| 10:55 |
bshum |
When defining granularity, how do we know the differences between A/T events that need to have granularity defined (or they won't run if we switch to granularity based crontab) |
| 10:55 |
bshum |
vs. stuff that should automatically happen |
| 10:55 |
bshum |
i.e. things that go straight to pending and do not need to be processed |
| 10:56 |
bshum |
I'm assuming things like hold notifications don't need granularity or process-hooks to go to pending. |
| 10:56 |
bshum |
But maybe I'm assuming wrongly. |
| 10:56 |
* bshum |
goes to look at the hooks |
| 10:59 |
bshum |
Hmm, lost.auto seems to get called at the end of the MarkItemLost reactor, so that probably can get skipped I think |
| 11:08 |
bshum |
Hmm, maybe we need a mix of granularity ones for hooks based on checkout.due |
| 11:08 |
bshum |
But then also do other hooks differently |
| 11:08 |
bshum |
hold_request.shelf_expires_soon maybe |
| 11:16 |
bshum |
Hmm, based on the event entries for those triggers |
| 11:16 |
bshum |
It seems like those would also need to be run with process-hooks |
| 11:39 |
* bshum |
requeues everything that broke and hopes his server doesn't explode again |
| 11:43 |
|
mrpeters joined #evergreen |
| 11:52 |
jeff |
@monologue bshum |
| 11:52 |
pinesol_green |
jeff: (monologue [<channel>]) -- Returns the number of consecutive lines you've sent in <channel> without being interrupted by someone else (i.e. how long your current 'monologue' is). <channel> is only necessary if the message isn't sent in the channel itself. |
| 11:53 |
jeff |
heh. |
| 11:53 |
bshum |
@monologue #evergreen |
| 11:53 |
pinesol_green |
bshum: Your current monologue is at least 1 line long. |
| 11:53 |
bshum |
Funny |
| 11:56 |
bshum |
@hate action triggers |
| 11:56 |
pinesol_green |
bshum: But bshum already hates action triggers! |
| 11:56 |
bshum |
Figures |
| 12:22 |
|
RoganH joined #evergreen |
| 12:23 |
bshum |
remingtron: There is still a blog on the wordpress site, it's at http://evergreen-ils.org/communicate/blog/ |
| 12:23 |
kmlussier |
remingtron, bshum: I just updated the link on the communicate page. |
| 12:23 |
bshum |
Though personally, the page you linked to is one targeted for "needs work" basically to refactor it to be more helpful |
| 12:24 |
bshum |
It was a carry over from the old site |
| 12:24 |
jeff |
heh. saw my comment on bug 1167541 and mis-read launchpad's interface as saying comment "#3". thought for a moment that i had commented on the wrong bug. :-) |
| 12:24 |
pinesol_green |
Launchpad bug 1167541 in Evergreen "Pickup library defaults to Home OU of staff, instead of patron when placing holds" (affected: 8, heat: 44) [Medium,In progress] https://launchpad.net/bugs/1167541 - Assigned to Jeff Godin (jgodin) |
| 12:25 |
kmlussier |
remingtron: I think dbs is the only person who can update the Planet Evergreen link. |
| 12:26 |
bshum |
kmlussier: That's correct, only dbs is the admin for Planet Evergreen as far as I'm aware. |
| 12:27 |
bshum |
kmlussier: http://wiki.evergreen-ils.org/doku.php?id=website_administration |
| 12:28 |
kmlussier |
bshum++ |
| 12:37 |
eeevil |
bshum: I'm not actually here, but ... only passive hooks require process_hooks to bring their events into existence. active (as opposed to passive, not the inverse of inactive) hooks are for things that actively happen -- a circ, someone prints something, another A/T event injects one of that type, etc |
| 12:40 |
bshum |
eeevil++ # thanks, that makes much better sense now. And I can see which are passive/active via the hooks table. |
| 12:40 |
bshum |
yay! |
| 12:41 |
bshum |
So by fortunate process of elimination, I'd already put granularity on all the event defs that needed it based on passive hooks. |
| 12:41 |
bshum |
*whew* |
| 12:44 |
eeevil |
looks like some more of the content from http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-user:action_trigger might be useful in the DIG docs |
| 13:05 |
|
jbfink joined #evergreen |
| 13:19 |
|
afterl joined #evergreen |
| 13:31 |
* jeff |
adds some more of the content from that wiki page to his brain |
| 14:16 |
|
kbutler joined #evergreen |
| 14:22 |
|
finnx joined #evergreen |
| 14:23 |
|
finnx joined #evergreen |
| 14:25 |
|
finnx joined #evergreen |
| 14:26 |
|
finnx joined #evergreen |
| 14:28 |
|
finnx joined #evergreen |
| 14:29 |
|
smyers_ joined #evergreen |
| 14:30 |
|
finnx joined #evergreen |
| 14:32 |
|
finnx joined #evergreen |
| 14:33 |
|
jbfink joined #evergreen |
| 14:34 |
|
stevenyvr2 joined #evergreen |
| 14:49 |
|
kbutler joined #evergreen |
| 15:01 |
|
akilsdonk joined #evergreen |
| 15:25 |
|
rangi joined #evergreen |
| 15:25 |
|
rangi joined #evergreen |
| 15:41 |
|
jbfink joined #evergreen |
| 15:58 |
|
RoganH joined #evergreen |
| 16:30 |
|
afterl left #evergreen |
| 17:04 |
|
dMiller__ joined #evergreen |
| 17:12 |
|
edoceo joined #evergreen |
| 17:17 |
jeff |
logs++ |
| 17:28 |
|
smyers_ joined #evergreen |
| 18:04 |
|
zxiiro joined #evergreen |
| 19:38 |
|
stevenyvr2 left #evergreen |
| 21:34 |
|
jbfink joined #evergreen |
| 22:29 |
|
jbfink joined #evergreen |
