| Time |
Nick |
Message |
| 00:18 |
|
sandbergja joined #evergreen |
| 01:09 |
|
sandbergja joined #evergreen |
| 06:01 |
pinesol |
News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~live//archive/2020-06/2020-06-22_04:00:03/test.29.html> |
| 07:30 |
|
rjackson_isl_hom joined #evergreen |
| 07:59 |
|
rfrasur joined #evergreen |
| 08:17 |
|
alynn26 joined #evergreen |
| 08:34 |
|
mmorgan joined #evergreen |
| 09:01 |
|
sandbergja joined #evergreen |
| 09:04 |
|
Dyrcona joined #evergreen |
| 09:11 |
* Dyrcona |
is trying out a new laptop today. It's a bit different from the one that I normally use. |
| 09:25 |
rfrasur |
Is it new new or different new? |
| 09:26 |
Dyrcona |
rfrasur: It is new. One of these: https://www.pine64.org/pinebook-pro/ |
| 09:28 |
rfrasur |
Dyrcona: whoa. that's about the coolest nerdy thing I've seen in awhile. and I mean nerdy is every best possible way. |
| 09:28 |
Dyrcona |
It arrived last Wednesday. |
| 09:28 |
Dyrcona |
:) |
| 09:28 |
rfrasur |
Do you usually use a Linux laptop? |
| 09:29 |
rfrasur |
(linux-based laptop?) |
| 09:30 |
Dyrcona |
Yeah, I've used Linux on desktops and laptops for 24 years, now. Exclusively for the last decade or so. |
| 09:30 |
rfrasur |
Dyrcona++ |
| 09:32 |
|
dbwells joined #evergreen |
| 09:33 |
rfrasur |
Well, that's a rabbit hole I don't have time to go down right now. (all the fun stuff I know next to nothing about) |
| 09:35 |
Dyrcona |
Yeah, I know. I'd really like to play with more different things. I figured this laptop was an inexpensive way to play with ARM, though I'm probably not going to do much that I couldn't do on INTEL. |
| 09:36 |
Dyrcona |
The main difference between the new laptop an my main laptop is the user interface. The Pinebook has KDE by default, and I use Gnome on the other. I may switch to Gnome, but I'm going to give KDE a try. |
| 09:38 |
rfrasur |
does KDE somehow bill itself as superior to Gnome? |
| 09:40 |
Dyrcona |
Depends on your point of view. I don't think either is really superior. It's mostly what one is used to. |
| 09:41 |
Dyrcona |
KDE is more like Windows. Gnome is pretty much its own thing these days, not like any commercial interface. |
| 09:43 |
Dyrcona |
I do have an Evergreen question. Our database server is getting hammered with closed date lookups coming from just about all of our bricks. I haven't been able to find a cause, yet. Has anyone seen something like that before? |
| 09:46 |
mmorgan |
Dyrcona: Are you seeing this in logs? |
| 09:48 |
jeff |
fine generator does relatively lots of closed date lookups. |
| 09:48 |
jeff |
so does circ |
| 09:49 |
jeff |
both of which you may not have seen in a while if libraries were closed and you also disabled the fine generator. :-) |
| 09:52 |
Dyrcona |
I'm seeing it in the database with a query to look up running processes. |
| 09:52 |
Dyrcona |
jeff: We haven't disabled the fine generator, but if this were the fine generator, the queries would come from 1 IP address, not all of the bricks. |
| 09:57 |
Dyrcona |
I have 50+ of these running simultaneously, and they do seem to come and go. |
| 10:03 |
|
jvwoolf joined #evergreen |
| 10:05 |
Dyrcona |
rfrasur: Another difference is Manjaro vs. Ubuntu. |
| 10:05 |
rfrasur |
lol, I'd have to look more into those. Which I will. Later. |
| 10:05 |
Dyrcona |
Unfortunately, I'm not getting much help from the logs. There's just too much information for it to be very useful. |
| 10:07 |
Dyrcona |
Four GB of log isn't useful, and that's one of the smaller ones from the previous hour. |
| 10:33 |
|
sandbergja joined #evergreen |
| 10:39 |
Dyrcona |
The closed date look ups are still going on. I'm looking into it in between other things, but still no clue what's causing it. |
| 10:40 |
Dyrcona |
rfrasur: The keybaoard layout is also a bit different between this on and my other laptop. The difference is mainly in the "extra" keys on the right side: arrows, control, etc. |
| 10:40 |
mmorgan |
Dyrcona: Could it be just libraries doing circulation, as jeff suggests? |
| 10:42 |
rfrasur |
Dyrcona, I think that's a pretty standard diff from laptop to laptop when talkin' brands and stuff. |
| 10:49 |
Dyrcona |
rfrasur: Yep, but sometimes frustrating. |
| 10:49 |
rfrasur |
lol, almost always. At least at the beginning |
| 10:49 |
Dyrcona |
mmorgan: Maybe, but it seems to be a lot more than "usual." |
| 10:56 |
mmorgan |
Dyrcona: Delivery is starting up for some today, maybe that's the difference? |
| 10:59 |
Dyrcona |
mmorgan: It could be, but I don't really know what "normal" looks like any more, as far as numbers are concerned. |
| 11:00 |
Dyrcona |
Seems like we'd still be below normal numbers for checkins. |
| 11:00 |
Dyrcona |
I suppose I could compare with older logs later. |
| 11:01 |
Dyrcona |
It's not seeming to cause a problem except that load on the db server is hovering around 70 and nagios thinks that's bad. The db server is responding just fine, though. |
| 11:06 |
mmorgan |
Some of our libraries have done/are doing "big return" events, which would result in much higher than pre-covid level checkins. Also, some libraries had backlogs of items that were returned before or during the closures to check in. And there likely above normal numbers of closed dates. As long as the db server is handling it fine, maybe it ain't broke. |
| 11:12 |
Dyrcona |
Yeah. It's the same here. |
| 11:23 |
Dyrcona |
I'm sceptical of that explanation, though, because looking at the 10:00 am hour from last June 24, a comparable Monday, we did 5,500 more checkins last year than we're doing today. Of course, I don't have access to Nagios logs/emails from that long ago to know if we had a similar situaiton with the number of queries/load. |
| 11:27 |
mmorgan |
I'm just guessing, really, but there's a whole lot more going on in the org_unit_closed table now than there was then. |
| 11:31 |
Dyrcona |
mmorgan: That's true, and now one library is reporting that circulation is failing for them. |
| 11:32 |
mmorgan |
So it is broke :-( |
| 11:32 |
Dyrcona |
Dunno. I'm still looking, but it's tough with so much going on. I'm goign to look at numbers of checkouts. |
| 11:34 |
* mmorgan |
is not seeing queries like that hanging around on our db |
| 11:39 |
mmorgan |
When suspending a batch of holds using a db query, does anything other than frozen=true need to be changed? |
| 11:41 |
berick |
mmorgan: you should also clear the current_copy value (set to null) |
| 11:41 |
berick |
we found a case where frozen holds can still be captured if a current_copy is linked |
| 11:43 |
berick |
it may also be helpful to set a far-distant well known thaw date so the holds are easy to find later. |
| 11:44 |
mmorgan |
berick: Ok, thanks. I'm keeping a staging table so I know which ones were suspended, and adding a hold_note. |
| 11:44 |
berick |
cool |
| 11:45 |
mmorgan |
Some are in transit, I'm not suspending those because I think that would be too messy to untangle later. |
| 11:45 |
Dyrcona |
So, I figured that I'd look for closed date storage calls in the logs, and this is the only that I see from last hour: open-ils.storage.actor.org_unit.closed_date.overlap |
| 11:46 |
Dyrcona |
Only about 1500 or so, and that doesn't seem like enough to justify what I see in the database, unless the majority of log messsages are being dropped. |
| 11:51 |
Dyrcona |
Could be renewals, the number of the closed dates overlap calls is only slightly higher than the number of renewals. |
| 11:52 |
Dyrcona |
However, comparing to a similar period last year, we did about the same number of renewals then, with a lot fewer checkins. |
| 11:54 |
|
jihpringle joined #evergreen |
| 12:03 |
gmcharlt |
since I happened to notice this behavior, a question: The Evergreen patron registration form lets you save survey responses, but doesn't display them if you edit the patron again. Is this intended? |
| 12:10 |
gmcharlt |
Dyrcona: are there any libraries that might have a big bunch of single-day closed periods rather than a range? that could make extend_grace_period (e.g.,) in CircCommon do a lot of repeated queries |
| 12:10 |
gmcharlt |
in the most pathological case, up to 366 times per loan |
| 12:11 |
Dyrcona |
gmcharlt: Actually, the library that reports having trouble with circulation has that. We're goign to look into that after lunch. I think that is definitely related to the problems. |
| 12:11 |
berick |
gmcharlt: at the very least, I believe it's consistent w/ the previous editor. i don't know if it was intended or just never expanded on. |
| 12:12 |
Dyrcona |
But, first, lunch! |
| 12:14 |
gmcharlt |
berick: thanks. I could certainly see a case for allowing line staff to complete surveys on a patron's behalf but not necessarily get access to their responses just by opening the patron editor |
| 12:15 |
gmcharlt |
but if that's the intention, there could be some labeling to that effect, and maybe disabling responses to or not display surveys that have been responded to |
| 12:17 |
|
mrisher joined #evergreen |
| 12:26 |
* mmorgan |
notes that suspending a hold in the staff client sets frozen=true, expire_time=NULL, prev_check_time=NULL, current_copy=NULL |
| 12:55 |
gmcharlt |
berick: csharp: are there any specific milestones or criteria you have in mind for 3.5.0-rc becoming 3.5.0, other than general testing? |
| 13:04 |
|
sandbergja joined #evergreen |
| 13:05 |
berick |
gmcharlt: no specific milestones |
| 13:05 |
gmcharlt |
ok, thanks |
| 13:52 |
Dyrcona |
mmorgan gmcharlt: We cleaned up the 1 day closings and both issues were resolved. |
| 14:07 |
|
rfrasur joined #evergreen |
| 14:35 |
gmcharlt |
Dyrcona++ |
| 14:42 |
gmcharlt |
out of curiosity, is anybody actively putting the curbside branch through its paces? |
| 14:44 |
|
sandbergja joined #evergreen |
| 14:45 |
Dyrcona |
Not here, but we're on 3.2 and the backport looks really tricky. |
| 14:48 |
miker |
gmcharlt: re surveys, IIRC, that was the simplest way to prompt PINES staff to ask the "do you want to register to vote" required survey question whenever they edited a patron record (like, renewing, etc). |
| 14:50 |
gmcharlt |
Dyrcona: FWIW, I tried just now cherry-picking onto rel_3_2 and wasn't bad; trickiest turned out to be, of all things, the patching adding it to the Angular navbar |
| 14:54 |
gmcharlt |
miker: thanks for the additional context! |
| 14:57 |
gmcharlt |
miker: and yeah, a nigh-canonical example of a survey question the library would repeatedly ask |
| 15:02 |
Dyrcona |
gmcharlt: Yeah, something like that. Just one or two places where new code was added in the mean time, so I had to delete some of the added code in the conflict resolution. |
| 15:02 |
Dyrcona |
We usually don't use backports unless they're clean, so we've decided to forgo this one. |
| 15:02 |
gmcharlt |
gotcha |
| 15:33 |
|
sandbergja joined #evergreen |
| 15:50 |
|
sandbergja joined #evergreen |
| 16:33 |
|
jvwoolf1 joined #evergreen |
| 16:34 |
|
mmorgan left #evergreen |
| 17:45 |
pinesol |
[evergreen|Galen Charlton] LP#1851306: (follow-up) add additional test stubs - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=9c4a46b> |
| 18:01 |
pinesol |
News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~live//archive/2020-06/2020-06-22_16:00:02/test.29.html> |
| 20:43 |
|
sandbergja joined #evergreen |
| 23:43 |
|
mrisher joined #evergreen |
