| Time |
Nick |
Message |
| 06:52 |
|
collum joined #evergreen |
| 08:07 |
|
BDorsey joined #evergreen |
| 08:13 |
|
cbrown joined #evergreen |
| 08:29 |
|
kworstell-isl joined #evergreen |
| 08:49 |
|
dguarrac joined #evergreen |
| 08:51 |
|
BDorsey joined #evergreen |
| 09:24 |
|
smayo joined #evergreen |
| 10:31 |
pinesol |
News from commits: Forward port 3.13.4-3.13.5 upgrade script <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=859fffd5689d36ff9cdfef479f0489eb609751de> |
| 10:43 |
|
Dyrcona joined #evergreen |
| 10:45 |
Dyrcona |
When it comes to releases, where are we? I think we're waiting on me to update the downloads page? |
| 10:46 |
* Dyrcona |
is "off" today, but I'm willing to get the releases out. |
| 10:47 |
* Dyrcona |
should read his work email first. :) |
| 10:47 |
Dyrcona |
Bmagic++ redavis++ sandbergja++ abneiman++ |
| 10:50 |
Bmagic |
Dyrcona++ redavis++ sandbergja++ abneiman++ |
| 10:55 |
Dyrcona |
I should walk over to EBSCO headquarters today and give them an earful about their SFTP server. |
| 10:56 |
Bmagic |
Dyrcona: please do! Put me on speakerphone |
| 10:56 |
|
collum joined #evergreen |
| 10:56 |
Dyrcona |
I'm trying to stop these messages from showing up in emails from cron, because they make some staff think we're being blocked: EBSCO Information Services. This computer system is for authorized users only. |
| 10:57 |
Dyrcona |
I still want to get error messages, though. |
| 10:58 |
* Dyrcona |
puts the work email away. |
| 10:59 |
* csharp_ |
looks for IRC speakerphone button |
| 11:00 |
* Dyrcona |
can't take a day off, apparently. |
| 11:00 |
csharp_ |
Dyrcona: sorry, I can't either |
| 11:00 |
Dyrcona |
I am going to close the work email before I find something that I actually have to take care of. |
| 11:00 |
csharp_ |
Dyrcona++ |
| 11:00 |
csharp_ |
everyone hug your sys admins |
| 11:00 |
Dyrcona |
Bmagic++ geoip-- |
| 11:01 |
Bmagic |
:) |
| 11:01 |
Dyrcona |
You can see the EBSCO offices from The House of the Seven Gables where my daughter works. I could just walk over there....but probably won't. |
| 11:02 |
Dyrcona |
I'm pretty sure it's EBSCO. |
| 11:02 |
Dyrcona |
It might be one of the big publishers, probably someone else we love to hate. ;) |
| 11:04 |
Dyrcona |
It's probably not EBSCO. I was given bad information. EBSCO says they're in Ipswich and that's either Salem, Marblehead, or possibly Peabody. |
| 11:05 |
Bmagic |
can anyone give me some inspiration for tracking this problem down: action trigger set to fire 7 days overdue, fired on 10-04, but the circulation wasn't due until 10-10. One clue, is the circulation started 9-05 with a 21 day circ rule, so it should* have been due 9-26. action.circulation shows a due date of 10-10 though |
| 11:05 |
csharp_ |
I remember being on vacation on the Florida panhandle and seeing a beach house whose sign said it was the property of EBSCO |
| 11:05 |
csharp_ |
it raised the eyebrows a bit |
| 11:06 |
Dyrcona |
Bmagic what are your delays for that event set to? |
| 11:06 |
Bmagic |
7 days, 9 days max |
| 11:06 |
csharp_ |
Bmagic: with all of those kinds of things I troll the PG logs for whatever the query was - sometimes that's surprising |
| 11:08 |
Dyrcona |
Bmagic: I'd double check that it was the actual circulation and also try to ascertain if someone just altered the due date after the notice went out. |
| 11:08 |
Bmagic |
the xact_finish is marked 9-23, but the checkin date is 10-16, WTF? |
| 11:08 |
csharp_ |
staff shenanigans! |
| 11:08 |
csharp_ |
@eightball is the problem usually staff? |
| 11:08 |
pinesol |
csharp_: Maybe... |
| 11:09 |
* csharp_ |
shakes cane at staff |
| 11:13 |
Bmagic |
Staff can edit the due date on action.circulation right? |
| 11:13 |
csharp_ |
yes |
| 11:13 |
Bmagic |
that's probably it |
| 11:13 |
Bmagic |
but still, why would the overdue trigger fire |
| 11:14 |
Bmagic |
it should be pivoting off the due date |
| 11:14 |
Bmagic |
maybe they updated the due date after* the trigger collected the circs and fired |
| 11:14 |
csharp_ |
yeah, probably something like that |
| 11:15 |
Dyrcona |
Is it checked out to a staff users' patron account? Maybe they got the notice then changed the due date. |
| 11:18 |
Bmagic |
patron profile is "Resident" |
| 11:19 |
Bmagic |
the transaction finished date is a head scratcher though |
| 11:19 |
csharp_ |
Bmagic: the activity logs from that day would probably help |
| 11:19 |
Bmagic |
I suppose the action trigger doesn't care if the xact_finish date is non-null |
| 11:19 |
csharp_ |
@blame whoever that was |
| 11:19 |
pinesol |
csharp_: whoever that was stole bradl's tux doll! |
| 11:19 |
Bmagic |
activity log! let me see what's up there |
| 11:20 |
csharp_ |
Bmagic: yeah the validator probably doesn't pay attention - perhaps it should? |
| 11:20 |
csharp_ |
but this is an unexpected situation so probably not |
| 11:20 |
Bmagic |
validator is "CircIsOverdue" which probably just looks at now() - due_date |
| 11:20 |
Dyrcona |
I would think that the main query would look for xact_finish is null. What's the checkin_time and checkin_scan_time on the circulation, maybe it is looking at those? |
| 11:21 |
|
collum joined #evergreen |
| 11:21 |
Dyrcona |
A lost and paid can have xact_finish set and those two be null, I think. |
| 11:22 |
Bmagic |
csharp_: activity log? is there an interface for that? "Work Log" - or are you talking about action.usr_activity? |
| 11:22 |
* Dyrcona |
is curious. I'm going to look a CircIsOverdue. |
| 11:23 |
csharp_ |
Bmagic: I'm thinking of the opensrf system logs - in our setup we separate "activity" into it's own file/set of files |
| 11:24 |
Bmagic |
those logs are long gone by now |
| 11:24 |
csharp_ |
ah |
| 11:24 |
|
collum joined #evergreen |
| 11:24 |
csharp_ |
we try to keep our logs between 3 and 6 months depending on space constraints |
| 11:24 |
Bmagic |
dang |
| 11:25 |
Bmagic |
osrfsys.log for 6 months? |
| 11:25 |
Dyrcona |
CircIsOverdue only look at checkin_time and stop_fines. |
| 11:25 |
Bmagic |
you probably love* to bring those logs up in a ticket and say "look here staff, you did this!" |
| 11:26 |
Dyrcona |
We used to keep 1 year on the syslog server, then backup the compressed logs to a backup server when we were self-hosted. |
| 11:26 |
csharp_ |
Bmagic: https://docs.google.com/document/d/1BJ7kSr5LfPkxXRhcrYjNyPlbT9PlNFHg6zL-tyetnKA/edit describes our setup |
| 11:27 |
csharp_ |
Bmagic: staff love it, I hate it |
| 11:27 |
Bmagic |
:) |
| 11:27 |
csharp_ |
I mean, it's almost always staff problems, but it becomes my problem and I don't like other people's problems becoming my problem :-) |
| 11:28 |
Dyrcona |
Bmagic: Did you see my comment about what CircIsOverdue looks at? I'd like to know how xact_finish was set. |
| 11:28 |
Bmagic |
I saw that the validator doesn't care about xact_finish, which makes sense here |
| 11:29 |
csharp_ |
by the time you figure this kind of thing out you've burned up hours of state library staff time and it's usually not worth whatever is at stake on their end |
| 11:29 |
Bmagic |
the xact_finish date is well before the trigger fired, and well before it was recorded as having been checked in |
| 11:29 |
Bmagic |
csharp_: exactly! |
| 11:29 |
Dyrcona |
Yeah, it's almost never wort the effort. Very often, it's not even worth the time it took to open the ticket. |
| 11:30 |
Dyrcona |
Bmagic: Close the ticket with this "Someone at the library did something dumb." |
| 11:30 |
csharp_ |
I tend to set myself vague limits on this kind of thing so I can say something like "I've done my best to find what happened with what's available on my end - let us know if it happens again and we'll investigate! NEVER STOP BEING AWESOME!" <close ticket> |
| 11:30 |
Bmagic |
so, somehow the circulation was xact_finish'ed before* it was checked in, therefore it was technically still in circulation. And apparently it was, in realty, in the hands of the patron |
| 11:32 |
Dyrcona |
Yeahp. That's what I'd try to find out, but if staff can edit that directly, then we should probably prevent that with code. |
| 11:33 |
Bmagic |
I can't think of a way for that circulation getting it's xact_finish date set before it's checked in |
| 11:34 |
Dyrcona |
Did someone set it to lost, then change the status? There are probably convoluted ways to make that happen. |
| 11:35 |
Bmagic |
hmm, we don't audit the circ table |
| 11:35 |
csharp_ |
I think we fixed this before, but accrue fines, pay off fines, might still stamp xact_finish |
| 11:35 |
csharp_ |
Bmagic: you don't want to methinks |
| 11:36 |
csharp_ |
so many updates happen per circ that would get too big too fast imho |
| 11:37 |
Dyrcona |
Yeah, it would. If the audit table gets an entry for every update within a transaction, it would be scary huge. |
| 11:38 |
Bmagic |
we do audit the copy table though, and this copy went from available->checkout->reshelving. But! those audit times are 8/22, so not related to this circulation oddly |
| 11:38 |
Bmagic |
the staff maliciously pushed the due dates, and* deleted the audit table rows to cover their tracks, I bet |
| 11:38 |
csharp_ |
Bmagic: maybe finding the payments? |
| 11:38 |
csharp_ |
materialized_billable_xact_summary? |
| 11:39 |
Bmagic |
ok, yeah, there should be some timestamps to go on in money.billing |
| 11:39 |
csharp_ |
if payment time matches xact_finish that's probably a clue |
| 11:40 |
Bmagic |
fines started accruing 9/27. Gotcha! The due date was* 9/26 like I figured. |
| 11:41 |
csharp_ |
ayyyy |
| 11:43 |
Bmagic |
ok, the fines tell all. Fines started 9/27 but ended 10/5, then there's a gap, and started again 10/11. The due date is showing 10/10. So, in conclusion, they pushed the due date from 9/26 -> 10/10 on 10/6. The notification went 10/4, which, on that day, it truly was 7 days overdue |
| 11:43 |
csharp_ |
@blame staff |
| 11:43 |
pinesol |
csharp_: staff HAXORED csharp_'s SERVERZ!!!! |
| 11:43 |
csharp_ |
@love staff |
| 11:43 |
pinesol |
csharp_: The operation succeeded. csharp_ loves staff. |
| 11:43 |
Bmagic |
yep, fo shizzle. HAXORED |
| 11:44 |
csharp_ |
staff: I @blame you but I also @love you |
| 11:47 |
Bmagic |
I blame loving you |
| 11:48 |
csharp_ |
I @hate myself for @love-ing you |
| 11:49 |
csharp_ |
@love [band] |
| 11:49 |
pinesol |
csharp_: The operation succeeded. csharp_ loves Farmer Brown. |
| 11:49 |
csharp_ |
heh - one of the few actual bands on that list |
| 11:50 |
Bmagic |
What are you saying? We have a database of band names that don't exist? Sure they do! You and me at any given conference are @band |
| 11:50 |
Bmagic |
[band] |
| 11:51 |
csharp_ |
@band |
| 11:51 |
pinesol |
csharp_: The Click Fix |
| 11:55 |
Bmagic |
hey, can anyone else install Email::Send right now? command: perl -MCPAN -e 'install Email::Send' |
| 11:56 |
|
jihpringle joined #evergreen |
| 12:00 |
Dyrcona |
Bmagic: Don't we usually install that from a package? |
| 12:01 |
Bmagic |
doesn't look like it |
| 12:01 |
|
mmorgan joined #evergreen |
| 12:01 |
Bmagic |
export CPAN_MODULES = \ ... Email::Send \ |
| 12:01 |
Dyrcona |
I ran `sudo cpan install Email::Send` and got this: "Email::Send is up to date (2.202)." |
| 12:02 |
Bmagic |
you'd have to test on a system that doesn't already have it installed |
| 12:02 |
Dyrcona |
Of course, and I don't have one of those handy at the moment. |
| 12:02 |
Bmagic |
there's a compile error somewhere in the middle |
| 12:02 |
Dyrcona |
Well, there's a Lp bug to switch to Email::Sender... |
| 12:02 |
Bmagic |
cannot locate Module::Pluggable among other things |
| 12:03 |
Bmagic |
Drycona: it's super easy to have any OS you want via Docker. docker run -it ubuntu:22.04 |
| 12:04 |
Bmagic |
blam, you're on the shell of a fresh 22.04 container |
| 12:04 |
Dyrcona |
I'm using my personal laptop and I'm not installing docker on it. |
| 12:04 |
Dyrcona |
I also know that. You don't have to remind me. |
| 12:04 |
Bmagic |
:) I'm just excited about it |
| 12:04 |
Dyrcona |
We should dust off the Email::Sender code and get it in for 4.0 or whatever's next. |
| 12:09 |
|
redavis joined #evergreen |
| 12:09 |
Bmagic |
I thought we finished Evergreen? |
| 12:09 |
redavis |
Hah |
| 12:11 |
Dyrcona |
Heh. Didn't we do that yesterday? |
| 12:11 |
Bmagic |
oh, that was* yesterday. This is different |
| 12:12 |
redavis |
Imma thinking everything is done and the announcements can go out. At least for 3.14.0, yes? |
| 12:12 |
redavis |
And wait to hear about 3.12.8? |
| 12:13 |
Dyrcona |
redavis: Consider 3.12.8 done. |
| 12:13 |
* mmorgan |
reads backscroll on the a_t, and has to add "Sometimes the software does something dumb, too." |
| 12:13 |
redavis |
Okay, got it. |
| 12:13 |
Dyrcona |
mmorgan: Yes. In this case it might have set xact_finish when it should not have. |
| 12:13 |
* redavis |
went to DC yesterday with young people who have so much confidence in my ability to both keep up with them and walk as far as them. |
| 12:13 |
Bmagic |
redavis: I'm thinking it's a cpan issue with jammy |
| 12:13 |
redavis |
I appreciate their confidence. But it's misplaced. |
| 12:14 |
Bmagic |
mmorgan++ |
| 12:14 |
|
collum joined #evergreen |
| 12:15 |
redavis |
Okay, Bmagic. Writing email(s) now. I think I'm just going to write one for all of the releases since abneiman is doing a longer form press release for 3.14.0. If that strikes everyone as a good (enough) mode. |
| 12:16 |
Bmagic |
focal is booting with 3.12.8, answer in 3 minutes |
| 12:17 |
redavis |
Draft typing. Will take longer than 3 minutes for sure. |
| 12:18 |
Bmagic |
Email::Send is broken for focal too, but Evergreen is working anyway |
| 12:19 |
Bmagic |
clark can't start though |
| 12:20 |
Bmagic |
So, it's (probably) a temporary issue with an external dependency platform upon which we rely (cpan and everything that entails) |
| 12:26 |
redavis |
Hmm. Okay. So, I'm proceeding, but will be prepared to eat crow if necessary (I have practice). |
| 12:29 |
Bmagic |
One way to check for sure is to re-run the installation with one of the tarballs that worked yesterday. I'll do that with 3.14.0 and, I would expect it to have the same issue |
| 12:35 |
redavis |
Bmagic, I'm going to send the announcement unless you tell me to wait in the next 30 seconds (that's flexy, of course) |
| 12:35 |
Bmagic |
I think it's ok to go ahead |
| 12:35 |
|
mantis joined #evergreen |
| 12:35 |
redavis |
K :-), and then Dyrcona can actually have a day off? Right? |
| 12:36 |
Bmagic |
haha, I blame him at this point, he could be off as far as I'm concerned :) |
| 12:36 |
redavis |
lol, I've got nothing but gratitude for all y'all. |
| 12:38 |
|
Christineb joined #evergreen |
| 12:43 |
|
kmlussier joined #evergreen |
| 12:44 |
|
mmorgan joined #evergreen |
| 12:44 |
mmorgan |
Dyrcona++ jvwoolf++ Bmagic++ Stompro++ abneiman++ redavis++ sandbergja++ |
| 12:45 |
redavis |
Bmagic++ Dyrcona++ jvwoolf++ abneiman++ Stompro++ sandbergja++ |
| 12:45 |
kmlussier |
Just stopping in for a second to hand out karma. Dyrcona++ jvwoolf++ Bmagic++ Stompro++ abneiman++ redavis++ sandbergja++ |
| 12:45 |
kmlussier |
Of course, in the time it took me to write that, mmorgan and redavis beat me to it. |
| 12:45 |
redavis |
lol, thanks kmlussier - let's have pie in Beverly. |
| 12:46 |
kmlussier |
redavis: If you know me, you know I'm already looking up recipes to finish off my lunch hour! |
| 12:50 |
|
kmlussier left #evergreen |
| 12:51 |
redavis |
kmlussier++ #in absentia |
| 12:51 |
redavis |
Alright friends, I'm available via email. You're the best, and I'm glad to know you. |
| 13:06 |
Dyrcona |
Going back to the Email::Send question, it's nothing we can do anything about. If it won't install via CPAN that's a Perl packaging issue. Again, I'll point to Lp 1466502. |
| 13:06 |
pinesol |
Launchpad bug 1466502 in Evergreen "Replace Email::Send with Email::Sender" [Wishlist,Confirmed] https://launchpad.net/bugs/1466502 |
| 13:09 |
Dyrcona |
jvwoolf++ |
| 13:22 |
|
kworstell-isl joined #evergreen |
| 13:43 |
csharp_ |
Dyrcona: more evidence of the need for packaging/repo for our project maybe |
| 13:44 |
|
collum joined #evergreen |
| 13:45 |
csharp_ |
dh-make-perl --build --cpan Business::OnlinePayment::PayPal - tada! you have a deb (but CPAN has to be working) |
| 13:52 |
Bmagic |
but maybe that deb won't work on different versions of ubuntu? |
| 14:00 |
csharp_ |
Bmagic: you build it on the version you're planning to install on |
| 14:00 |
csharp_ |
can probably be done in containers |
| 14:01 |
Dyrcona |
It can be done in containers. |
| 14:02 |
Bmagic |
I was thinking along the lines of shipping the deb file in the Evergreen repo, which opens that whole can of worms |
| 14:02 |
Dyrcona |
We should just replace Email::Send because it's deprecated. |
| 14:03 |
Dyrcona |
We could host our own deb repos, like PostgreSQL does, but yeah, can of worms. |
| 14:15 |
* Dyrcona |
is not going to bother checking the release notes fixed from abneiman today. Partly because I never installed asciidoc on this laptop. |
| 14:16 |
Dyrcona |
We could regenerate them and upload to the website, just so they're fixed. |
| 14:17 |
Dyrcona |
I suppose I could install asciidoc, but I've been using markdown. |
| 14:18 |
Dyrcona |
Hm. Might as well, also got lots of updates. |
| 14:19 |
Dyrcona |
@decide dblatex or fop |
| 14:19 |
pinesol |
Dyrcona: go with fop |
| 14:19 |
Dyrcona |
Well, it's probably a smaller package. |
| 14:20 |
Dyrcona |
As I suspected: asciidoc: WARNING: RELEASE_NOTES_3_14.adoc: line 503: missing section: [sect5] |
| 14:28 |
Dyrcona |
Hmm. asciidoctor seems to do the right thing, maybe we should switch to using asciidoctor? |
| 14:32 |
Dyrcona |
OK, never mind. In this case, asciidoc seems to render something more or less correct despite the warning. I think one version of asciidoc didn't render the headings or that was a slightly different issue. |
| 14:32 |
pinesol |
News from commits: 3.14.0 relnotes corrections <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=f2eb507660622665dba8ed4214a9a38ed602c205> |
| 14:32 |
|
collum joined #evergreen |
| 14:36 |
* Dyrcona |
updated the release notes on the web server. |
| 14:42 |
abneiman |
Dyrcona++ |
| 15:00 |
Dyrcona |
I was thinking of taking off to get something to eat, but I think I'll hang out here at the library for another couple of hours, and then go to the East Regiment Beer Company for wings and a beer. |
| 15:00 |
mmorgan |
Dyrcona: Fun time to be in Salem! |
| 15:01 |
Dyrcona |
Today isn't so bad. Fridays are worse... My daughter doesn't work Saturdays. |
| 15:01 |
Dyrcona |
Though, they've asked her to work Saturday, Nov. 2. |
| 15:02 |
Dyrcona |
It was more crowded yesterday morning than this morning, but I haven't left the library since I go there today, so it may have picked up. |
| 15:03 |
mmorgan |
Nov. 2 might not be so bad, as Saturday's go. |
| 15:04 |
Dyrcona |
We'll see. She also works at the Pelham, NH library now. They use Koha. |
| 15:05 |
Dyrcona |
Maybe I'll do the next release from Pelham.... It's a shorter drive from my house. :) |
| 15:05 |
mmorgan |
:) |
| 15:25 |
|
jihpringle joined #evergreen |
| 15:27 |
|
mantis left #evergreen |
| 17:10 |
|
mmorgan left #evergreen |
| 22:03 |
pinesol |
News from commits: Forward-port 3.13.3-3.13.4 upgrade script <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=48f75f5233b44ca5d828636abb95706240995d5c> |
