Time |
Nick |
Message |
06:49 |
|
collum joined #evergreen |
07:09 |
|
collum joined #evergreen |
07:29 |
|
BDorsey joined #evergreen |
07:35 |
|
kworstell-isl joined #evergreen |
07:39 |
|
redavis joined #evergreen |
07:40 |
redavis |
berick, I happen to know that the dogs in your family are particularly loved and cherished. |
08:22 |
|
cbrown joined #evergreen |
08:25 |
|
mantis joined #evergreen |
08:34 |
|
dguarrac joined #evergreen |
08:35 |
|
mmorgan joined #evergreen |
08:51 |
|
Dyrcona joined #evergreen |
08:51 |
* Dyrcona |
isn't on the clock, yet, but I'm going to do the translations steps for the point releases and push them to the rel_X_Y branches. |
09:03 |
mantis |
Dyrcona++ |
09:03 |
redavis |
Dyrcona++ |
09:09 |
Dyrcona |
rel_3_12 should be ready. |
09:18 |
|
mdriscoll joined #evergreen |
09:18 |
mmorgan |
Dyrcona++ |
09:20 |
Dyrcona |
Well, that's a first for me: No po file updates in 3.13. |
09:21 |
* redavis |
makes a "whoa" face that you can't see in IRC. |
09:22 |
Dyrcona |
rel_3_13 is done. |
09:22 |
redavis |
Dyrcona++ |
09:23 |
abneiman |
closing the futurama circle "and to your lady friends, may I say BAM" is the reference that I always think of ;) |
09:24 |
mantis |
Does anyone have the task spreadsheet for the releases? |
09:24 |
abneiman |
also Bmagic++ redavis++ Dyrcona++ eeevil++ # getting it done |
09:24 |
redavis |
abneiman++ #samesies |
09:24 |
abneiman |
and berick++ # futurama knowledge |
09:24 |
mantis |
nvm got it |
09:25 |
abneiman |
mantis: https://docs.google.com/spreadsheets/d/1gZayHfF7qK0zwLMEAXt-PbKBMiAM_F6EZguqzIYceBY/edit?usp=sharing |
09:25 |
abneiman |
starting on release notes momentarily |
09:25 |
redavis |
lol, we all there with you mantis (see our anonymous animal icons - though someone is a pumpkin) |
09:26 |
mantis |
aw I wish I was the pumpkin |
09:26 |
redavis |
You might be! |
09:26 |
redavis |
I see a pumpkin and a ferret |
09:27 |
* Dyrcona |
signs out to deal with car stuff. Be back in a bit |
09:27 |
mantis |
I think I'm the ferret |
09:27 |
redavis |
A ferret is still pretty awesome. |
09:35 |
mmorgan |
I think that makes me the pumpkin :) |
09:35 |
abneiman |
I do not see the pumpkin, which I think makes me the pumpkin? I see a ferret, a walrus, and a squirrel |
09:36 |
redavis |
dang it...I'm the walrus. |
09:36 |
redavis |
Why do I gotta be a walrus. Also does that mean I don't need to tweeze chin hair? Did my life just get simpler? |
09:36 |
mantis |
walrus++ |
09:36 |
mmorgan |
abneiman++ |
09:37 |
redavis |
Evergreen fixes all things, including aging person processes. |
09:37 |
mmorgan |
I must be the squirrel, then! |
09:37 |
redavis |
Yes! Also fun aspect of reviewing the buildmaster spreadsheet :D |
09:38 |
abneiman |
I'd love to not tweeze chin hair. Walrus queens unite! |
09:38 |
redavis |
abneiman++ |
09:38 |
redavis |
Welcome to my kingdom. We lounge on the rocky beaches and aspire to blubberiness. |
09:40 |
abneiman |
you had me at chin hairs, TBH <3 |
09:42 |
redavis |
I mean, you don't HAVE to lounge or aspire to blubberiness. But you can. A benefit of multiple queens, imo. We can just be as we want. Chin hairs or sans chin hairs. |
09:43 |
abneiman |
I aspire to all of it, lol |
09:43 |
abneiman |
but now I really have to stop contemplating utopian futures and actually, like, do work |
09:44 |
redavis |
sames. Kinda punching the strategic plan into order (or being punched by it) |
09:44 |
redavis |
(I should say "draft" strategic plan) |
10:22 |
|
Dyrcona joined #evergreen |
10:22 |
Dyrcona |
I'm back. |
10:23 |
Dyrcona |
Took my car in form state inspection and it needs all new front breaks. The calipers locked up, so I got a loaner until Friday. Happy birthday to me! |
10:23 |
mantis |
car-- |
10:23 |
mantis |
birthday++ ?? |
10:23 |
mantis |
Happy Birthday Dyrcona |
10:23 |
Dyrcona |
And, my typing/spelling seems to be out the window. |
10:24 |
Dyrcona |
thanks! |
10:25 |
Dyrcona |
OK. I have to finish the rel_3_14 translations. |
10:25 |
berick |
so that's what thanksgiving is for! happy bday |
10:27 |
Dyrcona |
On the plus side, I came home to donuts and bacon. |
10:29 |
redavis |
Happy Birthday Dyrcona. Sorry for the locked up calipers and the need to spend money of unfun stuff. I'm glad you got both doughnuts and bacon though. |
10:29 |
csharp_ |
@dessert Dyrcona |
10:29 |
* pinesol |
grabs some heart-shaped boxes of Godiva chocolate for Dyrcona |
10:30 |
csharp_ |
happily birthladay |
10:31 |
csharp_ |
the answer to the question "does Redis make installing OpenSRF on Rocky Linux better" is "yes" |
10:31 |
Dyrcona |
csharp_++ redis++ |
10:31 |
Dyrcona |
Rocky is an "unstable" distro, right? |
10:32 |
csharp_ |
no, it should be considered the new CentOS |
10:32 |
Dyrcona |
OK. I haven't been keeping up with the RedHats.... |
10:32 |
Dyrcona |
I thought it was the new Fedora. |
10:33 |
csharp_ |
Fedora's still Fedora - I may try to support it too - but Fedora is the testing ground for RHEL/Rocky |
10:34 |
csharp_ |
like a more stable Debian sid |
10:34 |
Dyrcona |
Yeah. I would not object to adding Rocky support, but I'm a bit leery of adding Fedora install support officially. |
10:34 |
Dyrcona |
I mean, *I* don't want to support it. :) |
10:34 |
csharp_ |
agreed - I can't imagine anyone running Fedora in production given how quickly the release cycles run |
10:35 |
Dyrcona |
I've considered trying to get Evergreen installed/working on Arch, but that's even more insane from a support perspective. |
10:35 |
csharp_ |
there's no "LTS" for Fedora - that would be Rocky if you need that kind of stability |
10:35 |
mantis |
Arch-- |
10:35 |
Dyrcona |
OK. I'm on the POEditor steps for 3.14. |
10:35 |
Dyrcona |
arch++ |
10:36 |
mantis |
I had a Manjaro system once and I liked certain parts of it, but I needed to spend a lot of time learning Arch |
10:36 |
Dyrcona |
I use arch on my personal laptop. It works great! I get all the new bugs before anyone else, and I get to help get them patched. :) |
10:36 |
csharp_ |
nice |
10:37 |
* Dyrcona |
isn't joking. I recently commented on a Gnome bug with LUKS encrypted disks and gvfs-udisk-monitor... It got fixed relatively quickly. |
10:37 |
csharp_ |
I find Fedora to be new enough to get newest updates, especially kernel updates, which are pretty much rolling release, but stable enough for daily use |
10:37 |
csharp_ |
Dyrcona: super cool |
10:38 |
Dyrcona |
I find Arch to be stable enough for daily use. I update about once every week or two. I just got kernel 6.11.9 last night. |
10:38 |
Dyrcona |
I wouldn't use it for production servers, though. |
10:38 |
mantis |
someday I might try again |
10:38 |
mantis |
I think I was using it daily during 2021 |
10:39 |
csharp_ |
mantis++ # be bold! |
10:39 |
mmorgan |
@dessert 41 Dyrcona |
10:39 |
* pinesol |
grabs some birthday cake with lots of candles for Dyrcona |
10:39 |
Dyrcona |
One thing using Arch has done is force me to really learn *Linux* and systemd. You configure almost everything by hand. |
10:39 |
Dyrcona |
mmorgan++ |
10:39 |
Dyrcona |
mantis++ |
10:40 |
csharp_ |
2007/8 I was nervously dual-booting beside Windows, now I pretty much exclusively use Linux everywhere (though I'm required to have a Windows installation for work) |
10:40 |
mantis |
I am looking to get another PC and shopping around for distros right now |
10:40 |
Dyrcona |
Manjaro is nice if you want a more stable version of Arch with some additional sugar. |
10:40 |
Dyrcona |
I have Manjaro on an ARM laptop that I almost never use. |
10:40 |
csharp_ |
mantis: Fedora might be a good candidate for you |
10:40 |
Dyrcona |
The next step after Arch is Linux from Scratch. |
10:40 |
berick |
tried Void recently, but gave up after the first package i tried to install failed :P. it was snappy, though. |
10:41 |
mantis |
csharp: I hear it's very minimal in design but I haven't looked at it in a while |
10:41 |
Dyrcona |
Ok... back to translations... |
10:41 |
csharp_ |
mantis: I wouldn't call it minimal (though it can be) - it's often listed as an "advanced" distro, but in my experience it's just as stable as Ubuntu for desktop stuff |
10:41 |
berick |
(btw, Al Green covers Everybody Hurts) |
10:42 |
csharp_ |
berick: holy crap, I thought you were kidding |
10:43 |
csharp_ |
if it had been written 20 years earlier it probably would have just been an Al Green song anyway, I guess |
10:45 |
Dyrcona |
OK. rel_3_14 translations have been updated. |
10:48 |
* Dyrcona |
considered Void Linux once, but never got past reading the web page, ditto Guix. |
10:56 |
* Dyrcona |
fights the urge to eat ALL THE DONUTS!!! |
10:57 |
Bmagic |
Ubuntu Studio is very nice |
10:58 |
* redavis |
just finished making a new batch of apple butter. There's something magic about fitting 12 apples into about a pint and half worth of space. |
10:58 |
Dyrcona |
apple butter... yum! |
10:58 |
* redavis |
returns to strategic plan pugilism. |
10:58 |
Bmagic |
But, personally, Pop!_OS knocked it out of the park. With an Nvidia GPU, you can install the nvidia flavor and boy, everything just worked out of the box. Lutris saved the day for gaming, battlenet worked, EVE online worked, Steam worked. I loved it. Pop!_OS |
10:59 |
mdriscoll |
csharp_: Can you post your image of the Executive Snapshot report that you shared during the hackaway on LP 1770289? That's a great example of a good place to start with a statistics dashboard. |
10:59 |
pinesol |
Launchpad bug 1770289 in Evergreen "Wishlist: an acquisitions data dashboard" [Wishlist,Confirmed] https://launchpad.net/bugs/1770289 - Assigned to Scott Angel (scottangel1) |
10:59 |
Bmagic |
I'll admit, I made it 5 months this summer on Pop!_OS as my daily driver. But it wore me down eventually, and I went back to Windows. Because: games |
11:00 |
collum |
Somehow Al Green made the song a little happier. |
11:00 |
redavis |
collum++ |
11:23 |
|
mdriscoll joined #evergreen |
11:34 |
|
Christineb joined #evergreen |
11:53 |
csharp_ |
mdriscoll: one sec |
11:53 |
csharp_ |
well, nearly one hour and one sec, I guess |
11:54 |
csharp_ |
mdriscoll: https://drive.google.com/file/d/1ERClU9wncTGGqCXP-KwpmD6ad4xFt0-7/view?usp=sharing |
11:54 |
csharp_ |
docs people, feel free to add that somewhere - wiki, whatever |
11:55 |
redavis |
Has a wishlist launchpad ticket been created yet for this/dashboard stuff? |
11:56 |
* redavis |
goes to check after asking the question |
11:56 |
csharp_ |
mdriscoll: https://git.evergreen-ils.org/?p=contrib/pines/report-creator.git;a=blob;f=perl/execreports/erqueries.pl;h=24bad4ffb75a964678f8c11d38a72ce4bbd8bfcc;hb=refs/heads/main SQL behind all that |
11:57 |
mmorgan |
redavis: I believe it's being tracked in bug 1770289 |
11:57 |
pinesol |
Launchpad bug 1770289 in Evergreen "Wishlist: an acquisitions data dashboard" [Wishlist,Confirmed] https://launchpad.net/bugs/1770289 - Assigned to Scott Angel (scottangel1) |
11:57 |
redavis |
(also, ECDI people, you're highly encouraged to add an idea to the board at https://evergreencdi.org) |
11:57 |
csharp_ |
https://git.evergreen-ils.org/?p=contrib/pines/report-creator.git;a=summary - where the project lives - the relevant code is under perl/execreports |
11:57 |
redavis |
mmorgan++ |
12:00 |
redavis |
did a little search optimization so that this one also shows up in a search rather than having to link from 1770289 comments - https://bugs.launchpad.net/evergreen/+bug/1395742 |
12:00 |
pinesol |
Launchpad bug 1395742 in Evergreen "Wishlist: Decision Support System (DSS) / Dashboard" [Wishlist,Triaged] |
12:04 |
|
jihpringle joined #evergreen |
12:05 |
|
jihpringle25 joined #evergreen |
12:21 |
Dyrcona |
Did anyone get an email about a rel_3_12 commit this morning? I suspect it might have been in my server's mail queue when I ran a command to clear stuck messages this morning. |
12:22 |
jeff |
I don't see one. Check headers? |
12:23 |
Dyrcona |
jeff: OK. I don't see any evidence of it in my logs, so I guess it was just not sent. |
12:23 |
jeff |
Alternately, supply a message-id and I can tell you when I received that message. |
12:23 |
jeff |
or a commit hash, I guess |
12:23 |
jeff |
oh, you mean the message seemed lost, not delayed. my mistake. |
12:24 |
Dyrcona |
9c6d82c16cbc7e224273ed73f7499ca1443dcf5b That's the commit hash |
12:24 |
|
collum joined #evergreen |
12:25 |
Dyrcona |
According to mailq, there's nothing to send on the git server. Maybe it got hung up in the list software? |
12:25 |
jeff |
yeah, I see no message referencing that commit. |
12:25 |
Dyrcona |
OK. It's not just me. :) |
12:27 |
jeff |
I don't have access to Mailman, so I can't tell you if it's stuck in moderation. Possible, especially if it was flagged (by Mailman or by something before) as being chock-full-o-languages. |
12:27 |
Dyrcona |
Oh! It could also have been too large for the list. That's happened before. |
12:28 |
jeff |
yeah, looks like it would have been 148K or so. |
12:30 |
Dyrcona |
I notice updates need to be installed on the git server. I'll plan to do that tomorrow evening and send an email to the development list. |
12:31 |
jeff |
larger messages have passed through that list recently... might depend on how things were grouped by the post-receive script. |
12:31 |
Dyrcona |
Yeah. I'm not gonna sweat it now that I have plausible explanations. :) |
12:33 |
redavis |
IIRC, the default limit for mailman messages is either 30 or 40 kb (would have to check). I've been hit by that hard in relatively recent times. |
12:52 |
* Dyrcona |
will be back by 2:00 PM EST. |
13:04 |
|
mdriscoll joined #evergreen |
13:14 |
mdriscoll |
csharp_: Thank you! |
13:36 |
|
mantis joined #evergreen |
13:51 |
Bmagic |
anyone dealt with circulations getting due days that are wildly off? action.circulation shows the matching circ rule to be a 28 day rule, and the rule looks fine, but the due_date is set to next year. Almost like it is arbitrarily adding 1 year to the 28 days |
13:52 |
berick |
Bmagic: not modified by staff? |
13:52 |
Bmagic |
and what's more interesting is it's not all circs. Just some. The same staff member, same workstation, same patron profile, same item circ mod, can recieve the correct and the incorrect due date |
13:53 |
Bmagic |
berick: no, because it's at such a large scale. 15k circs and counting |
13:54 |
berick |
ah |
13:57 |
mmorgan |
Bmagic: Any Hard Due Dates set up? |
13:58 |
Bmagic |
no, I checked that but I'll check that again using the database instead of the interface |
14:00 |
|
Dyrcona joined #evergreen |
14:00 |
Bmagic |
select * from config.circ_matrix_matchpoint where hard_due_date is not null; 0 rows |
14:01 |
collum |
I did a query in our database for any items due after Feb 1, just in case. We have 4 items. It appears to be humans being naughty. |
14:02 |
csharp_ |
Bmagic: do you have any circ rules with that length? |
14:02 |
csharp_ |
could be matching the wrong matchpoint |
14:03 |
csharp_ |
also, maybe bad date setting somewhere |
14:03 |
Bmagic |
csharp_: I was thinking that too, maybe it's matching a rule with a duration of ~390 days. Nope. There is one for 999 days and another for 730, but nothing close to 390 |
14:04 |
csharp_ |
had a patron once whose holds were expiring immediately as he placed them and that was traced to his PC clock being months off |
14:05 |
Bmagic |
plus, manually running an example circulation through the circ_find_circulation function, same item ID, same circ lib, it reveals a correct circ rule match. Which agrees with action.circulation duration_rule column |
14:05 |
csharp_ |
that was long ago |
14:05 |
Dyrcona |
Bmagic: Staff can set an arbitrary due date in the checkout screen. If they're all the same staff/same workstation, it is mostly likely that. |
14:05 |
csharp_ |
@blame humans |
14:05 |
pinesol |
csharp_: humans broke Evergreen. |
14:05 |
Bmagic |
Dyrcona: it probably is that. I suppose the interface "remembers" that setting from circ to circ? |
14:06 |
csharp_ |
@eightball is it staff? |
14:06 |
pinesol |
csharp_: One would be wise to think so. |
14:06 |
Dyrcona |
Yes, I believe it does, and there's no way to be certain in the database except that the due date doesn't match up with the rule. |
14:06 |
JBoyer |
I don't suppose a bunch of users that have 999 day circs expire in around 390 days, do they? |
14:06 |
csharp_ |
logs will show the way |
14:06 |
Dyrcona |
@praise eightball |
14:06 |
* pinesol |
eightball can count to 1 billion |
14:07 |
Bmagic |
JBoyer: that's interesting. So Evergreen's circ due date logic takes into account the patron expiration date? |
14:07 |
csharp_ |
@dunno add may Evergreen server logs ever illuminate your path |
14:07 |
pinesol |
csharp_: The operation succeeded. Dunno #89 added. |
14:07 |
JBoyer |
Depends. I think you have to have a patch installed to do that, but a lot of sites use it |
14:09 |
JBoyer |
Though I suppse you'd have noticed if tons of circs were too *short* which is not what you asked. Other than bonkers emergency closings I'm out of ideas. |
14:09 |
Bmagic |
action.circulation shows a duration of "28 days" but due_date - xact_start = 390 days |
14:10 |
|
kworstell-isl joined #evergreen |
14:11 |
mmorgan |
Bmagic: If it's a consistent 390 days, is there ANY duration rule that has that in short, normal or long? |
14:12 |
mmorgan |
JBoyer: Curious about the patch you mentioned. Is it bug 1046420? |
14:12 |
pinesol |
Launchpad bug 1046420 in Evergreen "Wishlist: Cut off due dates so they don't extend past card expiration date" [Wishlist,Confirmed] https://launchpad.net/bugs/1046420 |
14:12 |
Bmagic |
mmorgan: none of the three extended,normal,shrt are set to anything close to that number |
14:16 |
JBoyer |
mmorgan, yeah. now that I re-read it "a lot of sites use it" is likely inaccurate. "a lot of sites would use it if it were completed" might be better, since last I knew it had no options or alerts. |
14:17 |
berick |
Bmagic: can you find logs for a recent one and see if the date is included in the API call? |
14:18 |
Bmagic |
berick: I haven't done that yet, let me see if I can track that down |
14:18 |
jeff |
15K circs seems to be a bit much for it to be offlines, but comparing xact_start and create_time on a circ used to be my go to for "is this an offline circ?" |
14:20 |
jeff |
did the long-duration circs stop after a certain point, or are they still happening? closed dates can be deleted, but do you / did you have any closed dates for the lib in question that would explain this? sounds like it wasn't all circs for that circ lib during the affected time, so that probably rules that out already. |
14:21 |
Bmagic |
it's actively happening |
14:22 |
jeff |
ah. that rules out some things and makes some things easier. actively happening, follow berick's advice and seek ye answers in the logs :-) |
14:22 |
Bmagic |
no closed dates, no hard due dates. And it's happening regardless of workstation/branch. One clue is: the due dates are the exact same day 2025-12-01 |
14:23 |
Dyrcona |
Global hard due date? |
14:24 |
* jeff |
re-reads the information so far |
14:27 |
Bmagic |
I think I might be getting more clues soon, I'm tracking the logs for a circ ID |
14:27 |
mmorgan |
Bmagic: Sounds maybe like Specific Due Date on the checkout screen. It can persist until logout. |
14:30 |
Dyrcona |
Yeah, and I wouldn't be surprised if staff intended to use 2024-12-01. |
14:31 |
Bmagic |
not sure if this is odd, but there is a call back to the stack to update the due date |
14:31 |
Bmagic |
[2024-11-20 14:21:12] open-ils.circ [INFO:195065:Application.pm:159:173213039420420250] CALL: open-ils.circ open-ils.circ.circulation.due_date.update XXXXXXX, 117033646, 2024-12-04T19:21:03.620Z |
14:32 |
Bmagic |
and the due date that it's requesting is 2024, not 2025. The database has that circulation ID currently set for a due date of 2025, so I can assume that this call didn't make it's way to the DB |
14:32 |
mmorgan |
Is that someone trying to fix the wrong date? |
14:33 |
Dyrcona |
Any perm failures around that update? |
14:34 |
jeff |
for the circs you've identified so far, are they all associated with the same (checkout) workstation? |
14:34 |
Bmagic |
is it normal for a circulation transaction to follow-up on a circulation after it's been inserted, to set the due date with a separate call? |
14:35 |
Dyrcona |
Bmagic: It's normal for circ to do all kinds of updates, yes. You never realize just how crazy it is until you run it through the Perl debugger. |
14:36 |
jeff |
I think the only thing calling open-ils.circ.circulation.due_date.update is going to be the staff client "edit due date" function. |
14:37 |
Dyrcona |
jeff is very likely correct. |
14:37 |
Dyrcona |
Most of the updates I'm talking about are done via cstore calls. |
14:39 |
jeff |
I don't think there are places where closed dates are worker-cached on the server, otherwise I'd suspect someone may have added a holiday closed date and put 12/1/2025 when they meant 1/1/2025 and then fixed it after noticing it, but you were still having 1 out of every X circ get the cached bad value. I don't think that's the case here. |
14:39 |
mmorgan |
Bmagic: Can you find the log entry that created that circ id? |
14:40 |
jeff |
I suspect mmorgan is correct in thinking that your log entry above is staff trying to manually fix the 300+ day due date. What does the original checkout call look like for circ 117033646? |
14:40 |
jeff |
mmorgan++ again |
14:43 |
berick |
most anticipated log line ever |
14:43 |
Bmagic |
found the log for inserting the circ, it's inserting with 2025 due date |
14:43 |
jeff |
berick++ |
14:43 |
Bmagic |
open-ils.cstore 2024-11-20 14:20:10 [INFO:204216:osrf_application.c:1084:xxxxxx] CALL: open-ils.cstore open-ils.cstore.direct.action.circulation.create {"__c":"circ","__p":[null,null,null,"107",851425,null,"2025-12-01T00:00:59-05:00", |
14:43 |
berick |
Bmagic: what about the inbound API call? |
14:44 |
Bmagic |
gateway.log? |
14:44 |
berick |
yeah |
14:44 |
Bmagic |
checking |
14:45 |
Bmagic |
not sure how to link the two |
14:46 |
berick |
search for the log trace |
14:46 |
berick |
the xxxx'es from your log above |
14:46 |
jeff |
that's 376 days from now, not 390... |
14:47 |
Bmagic |
jeff: right, since the due date is always 12-1, it measures fewer and fewer days each day |
14:47 |
jeff |
ah. and this began weeks ago? |
14:48 |
Bmagic |
yeah |
14:48 |
mmorgan |
Sure behaves like a hard due date with the "Always use" option set. |
14:48 |
Bmagic |
as far back as 10/30, which is pre-upgrade to 3.13, so that rules that out |
14:49 |
Bmagic |
ok, so, using that trace ID in gateway.log, I'm only getting two hits, neither having to do with circ |
14:50 |
berick |
hm, odd, maybe filter by time |
14:50 |
berick |
... instead |
14:50 |
Dyrcona |
If you have the copy id or barcode, you can search for that in the logs. |
14:52 |
Bmagic |
open-ils.pcrud open-ils.pcrud.search.aca.atomic "xxxx", {"copy":21650270,"ack_time":null}, null |
14:53 |
Dyrcona |
Bmagic: You probably want to look for open-ils.circ.checkout. |
14:53 |
Bmagic |
that ID number only yeilds that result |
14:53 |
Dyrcona |
Try the barcode in the gateway.log. |
14:54 |
Dyrcona |
The gateway log should have the original checkout call. |
14:54 |
Bmagic |
open-ils.circ.checkout.full "xxxxxxxxxx", {"noncat_type":"","copy_barcode":"25908008505203","patron_id":861675,"new_copy_alerts":1} |
14:54 |
berick |
ok so it's not coming from the staff client |
14:55 |
Bmagic |
it's determining 2025 in the perl circ stack |
14:55 |
Bmagic |
yeah? |
14:55 |
berick |
looks like it |
14:57 |
mantis |
heading into the new dev meeting for an hour or so |
14:58 |
Bmagic |
well, you all have been very attentive! Thanks for generating some ideas |
14:58 |
Bmagic |
mmorgan++ berick++ jeff++ Dyrcona++ JBoyer++ csharp_++ csharp++ |
14:59 |
Dyrcona |
I'd check the owning lib and patron's home_ou (if different) for any weird settings or hard due dates. |
14:59 |
mmorgan |
We all love a puzzle! :) |
15:00 |
Bmagic |
hard due dates are a property of the circ matrix? not a library setting? |
15:01 |
Bmagic |
I'm headed into a meeting now, sorry, to be continued |
15:01 |
jeff |
if you have logging set to debug or higher, you'll have lines like: |
15:02 |
jeff |
$logger->debug("circulator: building circulation ". |
15:02 |
jeff |
"with duration=$dname, maxfine=$mname, recurring=$rname, hard due date=$hdname"); |
15:02 |
Dyrcona |
You might also fill your log server and crash it. :) |
15:02 |
Dyrcona |
Bmagic: Hard due dates do appear to be set on the circ matrix. I've not really needed to know before. |
15:03 |
Bmagic |
ok good, then I'm not missing anything as far as hard due dates go |
15:03 |
Dyrcona |
What is new devs talking about today? I thought I might want to attend, but my current location is not that conducive to a zoom meeting. |
15:06 |
sleary |
action trigger intro from Gina |
15:06 |
sleary |
and how to filter them |
15:06 |
Dyrcona |
sleary++ I was just typing that more or less. |
15:07 |
jeff |
what was that movie where the guy had a brain NDA? he could work on things then at the end of the contract they wiped his memory? i want that sometimes. better automated log redaction would probably be easier, I guess... |
15:07 |
redavis |
Hmm. I want to do that, but also want to get this project done. |
15:07 |
redavis |
severance |
15:07 |
redavis |
jeff |
15:07 |
redavis |
(new season soon) |
15:10 |
jeff |
oh, this was a movie. something about time travel also. possibly ben affleck... |
15:10 |
jeff |
Paycheck (2003)! |
15:11 |
Bmagic |
wow |
15:11 |
sleary |
I was like, that sounds like a Philip K. Dick story... *checks credits* ... yep. |
15:12 |
jeff |
*nod* |
15:12 |
redavis |
lol, nice. |
15:12 |
redavis |
my bad on the movie vs. series. |
15:12 |
redavis |
also, check out severance. If you haven't. It's great and terrible. |
15:14 |
jeff |
nah, not your bad. "Brain NDA" was pretty vague / broad. :) |
15:15 |
Bmagic |
Reminds me of a Keanu movie from the ninties. Johnny Mnemonic |
15:16 |
redavis |
oh, I dunno. It was pretty good. Also, I might go read the Philip K. Dick story since Ben Affleck is so Ben Afflecky. |
15:16 |
* jeff |
nods |
15:16 |
redavis |
Mmmmmmm....Keanu. (I have an unread BRZRKR GN waiting in the wings) |
15:16 |
sleary |
PKD adaptations tend to stray pretty far from the source material |
15:16 |
jeff |
similar kind of story, but based on a William Gibson story, not Philip K. Dick. :-) |
15:17 |
Dyrcona |
"I sued Ben Affleck.... Ah.... Do I even need a reason!?" |
15:17 |
redavis |
sleary++ though I did enjoy Electric Dreams or whatever it was called. |
15:17 |
redavis |
jeff++ |
15:18 |
redavis |
I always feel bad for Ben Affleck and then get mad that I feel bad because there's no reason to feel bad. It's annoying so he annoys me. |
15:19 |
Dyrcona |
If you want to feel bad for someone, feel bad for Casey..... *ducks* |
15:19 |
redavis |
LOL |
15:19 |
redavis |
I don't. Want to feel bad for either of them. Casey who? Hahahah (sorry) |
15:22 |
Dyrcona |
abneiman++ |
15:22 |
redavis |
we got release notes? |
15:22 |
abneiman |
yep! https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/abneiman/docs-relnotes-2024nov |
15:23 |
redavis |
Noice!! |
15:23 |
redavis |
abneiman++ #they're a thing of beauty (things) |
15:24 |
abneiman |
not as beautiful as walrus queens, tho |
15:24 |
redavis |
Not much is. |
15:28 |
Dyrcona |
or cabbages and kings? |
15:29 |
redavis |
Eh, I guess Dyrcona ;) mostly just walrus queens though. (now I have a hankering for cole slaw) |
15:31 |
* Dyrcona |
tried to make a Through the Looking Glass reference with the Walrus and Carpenter's conversation. |
15:31 |
redavis |
You did! I got it. |
15:31 |
redavis |
It was good. |
15:38 |
* Dyrcona |
listens to the fan spin up on the laptop as a vm works on make_release. |
15:41 |
redavis |
There are times when I don't notice "the fans" but other times when I actually have to leave the room. There's the laptop one, and the laptop stand, and a desktop fan, and the laser, and the air assist for the laser, and the exhaust for the laser, and the ceiling fan. It's a bit much in those moments. And sometimes just the laptop stand puts me over the edge. But that's usually at the end of the day when a brain reset is |
15:41 |
redavis |
truly necessary. |
15:45 |
pinesol |
News from commits: Docs: 3.14.1 release notes <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=2b691f90abbb02678dad78b930e480de90ef01b1> |
15:45 |
pinesol |
News from commits: Docs: 3.13.6 release notes <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=f43809c565b1ea4d073f3dde3b8f0e448edc6dd3> |
15:45 |
pinesol |
News from commits: Docs: 3.12.9 release notes <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=a512d8566908cf87bbb2d9b5e10e8387e5d50a69> |
15:51 |
abneiman |
shoes and ships and sealing wax ... and why the sea is boiling, and whether pigs have wings! |
15:52 |
abneiman |
hmm that last bit hits different nowadays |
15:52 |
redavis |
lol, it does. |
15:55 |
Dyrcona |
:) |
16:01 |
redavis |
The mind trickery of the internet. I just made a comment on my own document...which then emailed me. But I'd forgotten about it emailing me, so I went to the inbox in anticipation of "something else." It's akin to emailing myself and then being surprised by an email. |
16:12 |
redavis |
I'm gonna go graduate from my master gardener class tonight and need to get ready. Will be back manning the inbox tonight and then, of course, in the morning. Dyrcona++ abneiman++ csharp_++ gmonti++ mmorgan++ |
16:14 |
mantis |
trying to do the build now, I'm getting a package-lock.json as an untracked file switching branches from main |
16:15 |
Dyrcona |
mantis, et al: I just opened a bug about this earlier today: https://bugs.launchpad.net/bugs/2089160 |
16:15 |
pinesol |
Launchpad bug 2089160 in Evergreen "Recommend npm ci in developer installation instructions" [Undecided,New] - Assigned to Jason Stephenson (jstephenson) |
16:16 |
Dyrcona |
When you get the message about package-lock.json when switching branches, the easiest thing is to run `git stash` |
16:45 |
|
jihpringle joined #evergreen |
16:57 |
mantis |
tarball is set, sending files over |
16:58 |
mantis |
and a working branch is pushed for 3.13.6 |
16:58 |
mantis |
Drycona++ for helping me for this first build! |
16:59 |
Dyrcona |
mantis++ # Thanks for building the tarball. |
17:01 |
mmorgan |
mantis++ |
17:02 |
mantis |
mmorgan++ |
17:03 |
|
mantis left #evergreen |
17:04 |
Dyrcona |
mmorgan++ redavis++ csharp_++ |
17:06 |
csharp_ |
starting my test of 3.13 |
17:06 |
mmorgan |
3.12.9 tarball is set also, files shared. |
17:11 |
|
mmorgan left #evergreen |
17:31 |
* Dyrcona |
signs out for now. |
17:53 |
|
mantis joined #evergreen |
18:04 |
|
jihpringle87 joined #evergreen |
19:20 |
|
mantis left #evergreen |