Time |
Nick |
Message |
01:09 |
|
cmalm joined #evergreen |
01:42 |
|
cmalm joined #evergreen |
01:46 |
|
abowling left #evergreen |
02:06 |
|
cmalm joined #evergreen |
02:24 |
|
cmalm joined #evergreen |
02:45 |
|
cmalm joined #evergreen |
03:07 |
|
cmalm joined #evergreen |
04:40 |
|
StomproJ joined #evergreen |
06:00 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
06:57 |
|
rfrasur joined #evergreen |
06:59 |
|
collum joined #evergreen |
07:02 |
|
agoben joined #evergreen |
08:39 |
|
rjackson_isl joined #evergreen |
08:39 |
|
mantis1 joined #evergreen |
08:53 |
|
mmorgan joined #evergreen |
08:53 |
StomproJ |
Postgres 9.4 EOL - moment of silence. We should upgrade. |
09:05 |
csharp |
StomproJ++ |
09:07 |
StomproJ |
Anyone have opinions on going to 9.6 vs 10? My initial thought is to just jump to the most recent supported version (for 3.3). |
09:11 |
JBoyer |
StomproJ, so long as you upgrade your database to a 3.3.1 or newer version before upgrading postgres you should be fine on 10. |
09:13 |
StomproJ |
JBoyer, thanks, we are on a later version than that, so we should be good. |
09:13 |
JBoyer |
StomproJ If you really want to be a frontrunner, you could try out 11. ;) |
09:15 |
StomproJ |
Why not 12 in that case? (I'm not equiped to be a frontrunner though.) |
09:15 |
JBoyer |
I haven't kept up enough to realize it's out. 12 does have at least one thing I'm really excited about though: reindex concurrently. |
09:16 |
StomproJ |
12.2 was released today, so all the bugs have probably been worked out :-) |
09:17 |
* JBoyer |
is behind the times! |
09:17 |
JBoyer |
I will have to look into that... |
09:26 |
Bmagic |
Who's using 10 in production? csharp? |
09:38 |
|
yboston joined #evergreen |
09:49 |
|
sandbergja joined #evergreen |
09:52 |
StomproJ |
I'm looking through the debian buster install makefile, to see what all needs to be changed to upgrade to PG 10... but it seems like the PG 9.6 client still gets installed. Is that an issue, to use an older client with a newer server? |
09:55 |
csharp |
StomproJ: PINES just upgraded to 9.6 after unwittingly going to 10 without the backported fixes on 3.2 - been running 3.4 on 10 on a test server problem-free for months |
09:55 |
csharp |
StomproJ: not a problem in most cases to have a client/server version mismatch |
09:55 |
|
cmalm joined #evergreen |
09:56 |
phasefx |
are we talking the psql client? I think, at worse, stuff like tab completion might not work |
09:56 |
csharp |
yeah |
09:56 |
StomproJ |
So in theory I could leave my app servers with 9.4 clients, and just upgrade the server? |
09:56 |
|
jvwoolf joined #evergreen |
10:02 |
csharp |
StomproJ: or, just enable the PG APT repo and install the matching version on the clients |
10:03 |
phasefx |
I don't think EG uses psql at all itself; so as long as libdbi-dev and libdbi-perl can talk to the database, you should be fine |
10:04 |
StomproJ |
Thanks for the info, phasefx++ csharp++ |
10:17 |
|
alynn26 joined #evergreen |
11:13 |
|
alynn26_away joined #evergreen |
11:24 |
JBoyer |
fun stuff: I'm hitting dbs' Eg 3.4 + Chrome + hatch = whitescreen now that I've added the addon to Chrome, but without hatch actually installed (on a mac) |
11:26 |
berick |
i can confirm if Hatch is not installed but the extension is enable, that will happen |
11:26 |
berick |
the browser assumes if the extension is added and turned on, that it works. |
11:26 |
berick |
so it waits for a response to the "give me my workstations" query indefinitily |
11:30 |
berick |
if you disable the extension on chrome, it will start working again. |
11:37 |
JBoyer |
berick++ |
11:38 |
JBoyer |
I figured, but wondered about working on making it smarter about not being able to reach the native app (but not today.) |
11:39 |
|
sandbergja joined #evergreen |
11:39 |
berick |
yeah, it likely could be made smarter |
11:50 |
|
jihpringle joined #evergreen |
12:10 |
|
jihpringle joined #evergreen |
12:22 |
|
khuckins joined #evergreen |
12:24 |
|
Christineb joined #evergreen |
12:34 |
|
collum joined #evergreen |
12:45 |
jeff |
Did anyone here make an effort to archive the content at masslnc.org before the domain expired / reverted to a parked page? |
12:52 |
dbs |
jeff: Ugh. I would have, had I known :/ |
12:53 |
jeff |
yeah. :/ |
12:54 |
|
sandbergja joined #evergreen |
13:09 |
rfrasur |
jeff, parts of it have been archived. I'm not sure where though. |
13:10 |
rfrasur |
Dyrcona might know better. |
14:05 |
dbs |
There are some hits in the Wayback Machine. But lots of misses, too. |
14:08 |
jeff |
Google has HTML versions of some files, but probably not for too much longer. |
14:08 |
csharp |
possible kmlussier has something useful? |
15:21 |
|
sandbergja joined #evergreen |
15:30 |
|
mmorgan1 joined #evergreen |
15:37 |
|
rfrasur joined #evergreen |
15:38 |
|
mantis1 left #evergreen |
15:48 |
jeff |
I think we want to enhance HCV / Hold Capture a bit to also verify a captured item that was in transit before it goes to Available upon arriving at its destination. |
15:49 |
jeff |
Not sure if we also want to do something like "these items go home first for inspection"... |
15:55 |
jeff |
I'm not sure if there's a way to "don't capture this item for a hold, just send it home" short of some convoluted steps here. |
16:02 |
|
mmorgan joined #evergreen |
16:06 |
|
mmorgan left #evergreen |
16:14 |
jeff |
And yes, I think we have at least one class of item where it should always come "home" for inspection before going elsewhere to fill a hold. |
16:49 |
|
jvwoolf left #evergreen |
16:53 |
|
khuckins_ joined #evergreen |
18:00 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
20:01 |
|
sandbergja joined #evergreen |
20:16 |
|
sandbergja joined #evergreen |
23:11 |
|
serflog joined #evergreen |
23:11 |
|
Topic for #evergreen is now Welcome to the #evergreen library system channel! | We are publicly logged: http://irc.evergreen-ils.org/evergreen | Large pastes at http://paste.evergreen-ils.org | Can't speak? Make sure your nickname is registered and that you are identified to freenode services: https://freenode.net/kb/answer/registration |