Time |
Nick |
Message |
05:15 |
|
bgillap_ joined #evergreen |
07:06 |
|
collum joined #evergreen |
07:41 |
|
BDorsey joined #evergreen |
07:46 |
|
kworstell-isl joined #evergreen |
08:02 |
|
rfrasur joined #evergreen |
08:32 |
|
mantis1 joined #evergreen |
08:50 |
|
mmorgan joined #evergreen |
09:00 |
|
dguarrac joined #evergreen |
09:15 |
pinesol |
News from commits: LP#2033655 - Floating documentation updates. <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=20367e9b3e765aa98495a4b13e758bab479adf82> |
09:19 |
|
Dyrcona joined #evergreen |
09:47 |
|
mantis1 joined #evergreen |
09:49 |
|
smayo joined #evergreen |
09:56 |
|
collum joined #evergreen |
10:08 |
Dyrcona |
I have setup a test of action triggers with 1 vm using parallel 1 for collection and reaction and the other left with our production setting of 3 for each. |
10:09 |
Dyrcona |
The crontabs are the same with most of the a/t and standard Evergreen stuff running the same as in production. I removed our custom SQL and file cleanup jobs. |
10:11 |
|
collum joined #evergreen |
10:13 |
Dyrcona |
Depending on how long it takes the sequential setup to process events, I may add the filter to exclude items with auto-renewals from the pre-due notices on that machine tomorrow. |
10:31 |
|
Rogan joined #evergreen |
10:32 |
berick |
Dyrcona: kick them off at the same time, live stream it, take bets |
10:40 |
Dyrcona |
Heh. |
10:40 |
Dyrcona |
They are being kicked off at the same time. I'm pretty sure that multisession will win, but I'm expecting more errors. Altough the errors may just be from overlap. |
10:41 |
Dyrcona |
I should try the filter on both virtual machines. |
10:44 |
|
BrianK joined #evergreen |
10:44 |
Dyrcona |
We have custom filters for overdue and lost events, but we haven't used them in at least a year. |
11:36 |
|
jihpringle joined #evergreen |
12:11 |
|
mantis1 joined #evergreen |
12:19 |
Dyrcona |
Somtimes, like now, I wish we used the git merge workflow rather than the patch workflow. Doing `git branch --contains ...` only really works with the merge workflow. |
12:23 |
Dyrcona |
Yeah, 'cause this commit is in rel_3_10, rel_3_11, and main, but --contains only shows main. I have to git log --grep to find it in the other branches with different hashes. |
12:28 |
|
jihpringle joined #evergreen |
13:01 |
|
collum joined #evergreen |
13:28 |
jeff |
yeah. that's one thing we talked about at least as far back as Hood River. At the time, I think I had "we should do it the other way" as an idea that turned out to be slightly more complex than "do it the other way". :-) |
13:29 |
|
kworstell-isl joined #evergreen |
13:30 |
Dyrcona |
jeff: It's mostly an esthetic thing. Some people don't like the merge commits. Now that I've worked with them more in some other projects, I think it's overall better than patch/cherry-pick. |
13:30 |
berick |
Dyrcona: git branch -a --contains ... can be useful. still requires matching hashes, of course. |
13:31 |
Dyrcona |
berick: While we're on the topic, the renewal extensions code seems to back port rather cleanly to 3.7.4. That's what I was attempting when I ran the git --contains.... |
13:40 |
Dyrcona |
I think it can be difficult to switch workflows since the history ends looking very strange. |
14:06 |
|
smayo joined #evergreen |
15:08 |
|
mantis1 left #evergreen |
15:13 |
|
mmorgan1 joined #evergreen |
15:48 |
Dyrcona |
We stopped using the custom filters on Sept 15, 2020. The commit message doesn't say why, it simply says "after some discussion." |
16:33 |
Dyrcona |
Y'know. I think I've observed the action_trigger_runner.pl go away while open-ils.trigger was still processing some of the events. I'll have to look into that again. |
17:02 |
|
mmorgan1 left #evergreen |
18:43 |
|
kmlussier joined #evergreen |
18:45 |
kmlussier |
smayo++ # First Evergreen commit - congratulations! |
18:46 |
pinesol |
News from commits: LP#1983424 Angular Holdings Editor uses old terminology <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=25097b448fecfdca0a7d4bff59c236bf3fb38b78> |