| Time |
Nick |
Message |
| 00:22 |
|
StomproJosh joined #evergreen |
| 01:10 |
|
StomproJ joined #evergreen |
| 01:57 |
|
gsams joined #evergreen |
| 02:48 |
|
StomproJ joined #evergreen |
| 03:16 |
|
StomproJosh joined #evergreen |
| 03:36 |
|
StomproJosh joined #evergreen |
| 04:22 |
|
StomproJ joined #evergreen |
| 05:08 |
|
StomproJosh joined #evergreen |
| 05:56 |
|
dbs joined #evergreen |
| 06:40 |
|
rlefaive joined #evergreen |
| 06:41 |
|
StomproJ joined #evergreen |
| 07:05 |
|
StomproJosh joined #evergreen |
| 07:11 |
|
agoben joined #evergreen |
| 07:17 |
|
rjackson_isl joined #evergreen |
| 07:29 |
|
JBoyer joined #evergreen |
| 07:59 |
|
dbs joined #evergreen |
| 08:17 |
jeff |
good morning, #evergreen |
| 08:26 |
tsbere |
microsoft-- |
| 08:32 |
|
StomproJ joined #evergreen |
| 08:39 |
|
mmorgan joined #evergreen |
| 08:47 |
|
bos20k joined #evergreen |
| 08:55 |
|
Stompro joined #evergreen |
| 09:11 |
dbs |
morning! |
| 09:13 |
mmorgan |
Good Morning! |
| 09:21 |
* tsbere |
would find the morning better without headaches caused by Microsoft ;) |
| 09:29 |
|
kmlussier joined #evergreen |
| 09:30 |
|
yboston joined #evergreen |
| 09:33 |
kmlussier |
Good morning! |
| 09:33 |
kmlussier |
@coffee [someone] |
| 09:33 |
* pinesol_green |
brews and pours a cup of Colombia Tolimas, and sends it sliding down the bar to rlefaive |
| 09:33 |
kmlussier |
@tea [someone] |
| 09:33 |
* pinesol_green |
brews and pours a pot of Bao Zhong Oolong Tea, and sends it sliding down the bar to mmorgan (http://ratetea.com/tea/rishi/bao-zhong-oolong/768/) |
| 09:34 |
rlefaive |
Thanks kmlussier! |
| 09:40 |
mmorgan |
Ooh! Tea! Thanks kmlussier! |
| 09:42 |
|
Dyrcona joined #evergreen |
| 10:02 |
|
mmorgan1 joined #evergreen |
| 10:30 |
Dyrcona |
So, I want to make some a/t events run again. |
| 10:31 |
Dyrcona |
I believe I should set the state to pending, null out the run/start/complete/_time fields, null out update_process, and null out template/error/async_output. |
| 10:31 |
Dyrcona |
Anything that I missed? |
| 10:32 |
|
mmorgan joined #evergreen |
| 10:33 |
mmorgan |
Dyrcona: Depending on the situation, I sometimes make use of the Event Repeatability delay so new events will be created, rather than recycling the old ones. |
| 10:34 |
mmorgan |
Then blank out the field once they've run. |
| 10:36 |
Dyrcona |
mmorgan: That's interesting. What delay do you use? |
| 10:37 |
Dyrcona |
My oldest failed event is about 33 hours old at this point. |
| 10:38 |
mmorgan |
Is this a trigger that runs several times during the day? |
| 10:39 |
mmorgan |
I usually do this in testing, and use a very short delay, like 5 minutes so I can rerun as soon as I've tweaked. |
| 10:39 |
Dyrcona |
Well, I'm assuming it is all SendEmail triggers, but I should really look through the now, 3,689 messages in the queue to make sure. :) |
| 10:39 |
Dyrcona |
I don't have really have a testing environment. |
| 10:39 |
tsbere |
Dyrcona: I would avoid doing the repeatability delay trick. As you are using existing triggers it would try and deal with things for older events too. |
| 10:40 |
tsbere |
For testing *new* configs it is a useful trick though |
| 10:40 |
Dyrcona |
My oldest delivery failure is about 33 hours old. |
| 10:40 |
berick |
yeah, for a simple re-do, clearing the fields on the events will do it. |
| 10:41 |
Dyrcona |
mmorgan: Thanks for the suggestion. I think I'm just going to clear the events. |
| 10:41 |
mmorgan |
Dyrcona: Yeah, probably makes sense if it involves a number of different email triggers. |
| 10:41 |
Dyrcona |
I think I can figure out which events by writing a script to parse the mail queue... I know hold notification is one. |
| 10:45 |
tsbere |
Dyrcona: Why not just go with "start date/time is after you activated the broken config"? |
| 10:45 |
Dyrcona |
Well, I thought of that, but I wondered if some of them were actually delivered. I'll just do that, and save myself the time. |
| 10:47 |
|
yboston_ joined #evergreen |
| 10:56 |
mmorgan |
Web based self-check question: Is there a way to have a fine block that just applies to the self-check? |
| 10:56 |
tsbere |
Not that I know of at this time |
| 10:57 |
Dyrcona |
Looks like some patrons are just going to have to deal with getting double notices. |
| 10:57 |
* tsbere |
had plans to make the circ matrix able to do things based on desk/selfcheck/opac/etc but at this point will likely never get there |
| 11:03 |
Dyrcona |
I suppose I should stop the a/t runner while I make the changes. |
| 11:26 |
|
brahmina joined #evergreen |
| 11:31 |
|
BigRig_ joined #evergreen |
| 11:37 |
Dyrcona |
hmm. action_trigger.event.run_time won't take a null value and has no default. |
| 11:37 |
Dyrcona |
I'm not sure if I should leave it alone or put a future date in it. |
| 11:39 |
tsbere |
Leave it alone |
| 11:39 |
tsbere |
You want start_time to be null, not run_time |
| 11:39 |
tsbere |
run_time is "run at or after" (which may be days after it was added) |
| 11:41 |
Dyrcona |
OK. That's what I thought after looking at a few. Yes, I'm already nulling start_time. |
| 11:54 |
kmlussier |
yboston: Just discovered this and thought it might be of interest to you too. http://www.meetup.com/Write-the-Docs-BOS/ |
| 11:56 |
|
jihpringle joined #evergreen |
| 12:24 |
Dyrcona |
Thanks everyone for the advice on the a/t events. It seems to be going now other than a few hiccups here and there. |
| 12:24 |
Dyrcona |
I think I'll tweak the mail software configuration a bit. |
| 12:34 |
Stompro |
Can someone tell me if this looks like a logic bug? $hard_due_date_name gets initialized, and then checked without ever getting changed on line 1763, I wonder if line 1763 should actually be checking $hard_due_date since that gets set from the circ rule. http://git.evergreen-ils.org/?p=Evergreen.git;a=blob;f=Open-ILS/src/perlmods/lib/OpenILS/Application/Circ/Circulate.pm#l1742 |
| 12:38 |
Stompro |
Or maybe line 1748 should actually be setting $hard_due_date_name instead of $hard_due_date? |
| 12:55 |
mmorgan |
Stompro: To my untrained eye it looks like an error. Looks like that gets called just for precats and booking reservation pickups? |
| 12:59 |
jeff |
Stompro: looks like an error to me, but i haven't looked deeply enough to say if it has any practical impact. |
| 13:05 |
tsbere |
Stompro: I suspect most of the _name stuff there can be removed in general, probably being holdovers from script-based circ rules |
| 13:10 |
|
rlefaive joined #evergreen |
| 13:23 |
kmlussier |
@dessert |
| 13:23 |
* pinesol_green |
grabs some birthday cake with lots of candles for kmlussier |
| 13:35 |
|
BigRig_ joined #evergreen |
| 13:58 |
|
rlefaive joined #evergreen |
| 14:02 |
|
brahmina joined #evergreen |
| 14:57 |
Dyrcona |
Thank you, Debian, for making exim configuration harder than it needs to be. |
| 14:57 |
* Dyrcona |
should say that in #debian on oftc.net. :) |
| 15:12 |
|
bmills joined #evergreen |
| 15:15 |
|
rlefaive joined #evergreen |
| 15:26 |
|
rlefaive joined #evergreen |
| 15:28 |
|
berick joined #evergreen |
| 17:11 |
|
mmorgan left #evergreen |
| 17:52 |
|
BigRig_ joined #evergreen |
| 17:52 |
|
BigRig joined #evergreen |
| 18:05 |
|
BigRig_ joined #evergreen |
| 18:05 |
|
BigRig joined #evergreen |
| 18:09 |
|
sandbergja joined #evergreen |
| 18:41 |
|
bmills joined #evergreen |
| 19:39 |
|
JBoyer_alt joined #evergreen |
| 21:37 |
|
dbwells joined #evergreen |
| 23:37 |
|
remingtron joined #evergreen |
