Time |
Nick |
Message |
00:41 |
|
Shiva joined #evergreen |
01:08 |
|
Lenin joined #evergreen |
02:07 |
|
gsams joined #evergreen |
04:20 |
|
pastebot joined #evergreen |
06:48 |
|
agoben joined #evergreen |
07:27 |
|
rjackson_isl joined #evergreen |
08:12 |
|
bos20k joined #evergreen |
08:36 |
|
mmorgan joined #evergreen |
09:05 |
|
jvwoolf joined #evergreen |
09:25 |
|
jvwoolf1 joined #evergreen |
10:03 |
|
mmorgan1 joined #evergreen |
10:18 |
|
khuckins joined #evergreen |
10:18 |
|
jvwoolf joined #evergreen |
10:26 |
|
sandbergja joined #evergreen |
10:47 |
|
jvwoolf joined #evergreen |
10:52 |
|
Christineb joined #evergreen |
11:02 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
11:04 |
|
tlittle joined #evergreen |
11:12 |
|
mmorgan joined #evergreen |
11:18 |
Bmagic |
Isn't there still and oustanding issue with Evergreen running on 18.04? |
11:50 |
bshum |
Bmagic: uhhhhhh, hmmmmmmmm...... I don't remember |
11:51 |
bshum |
Was it something email related with A/T? |
11:51 |
|
tlittle joined #evergreen |
11:51 |
Bmagic |
Something about postgres and plsql modules therein? |
11:51 |
bshum |
That doesn't sound too familiar to me |
11:52 |
bshum |
I know that PG10 compatibility is still being worked out |
11:52 |
Bmagic |
JBoyer and Dyrcona were telling me at the conference |
11:52 |
bshum |
But the installer should be using PG 9.6 or something |
11:53 |
bshum |
Yeah, right now the bionic makefile uses the PG community apt source and then grabs PG 9.6 for install |
11:53 |
bshum |
Bionic does have PG 10 out of the box |
11:53 |
Bmagic |
Anyone here running 18.04 on the database server in production? |
11:55 |
bshum |
There was some bug with PG10 for awhile, but we fixed those functions during the last conference I think. Though we still need to test other functions out |
11:58 |
bshum |
Yeah I was thinking of https://bugs.launchpad.net/evergreen/+bug/1820339 which was fix released, so that's fine |
11:58 |
pinesol |
Launchpad bug 1820339 in Evergreen "Postgres 10 support: Vandelay Edition" [Medium,Fix released] |
12:07 |
|
jihpringle joined #evergreen |
12:27 |
jeff |
Dusting off plans for supporting "pick up other people's holds" via SIP2. |
12:34 |
jeff |
related existing discussion is in bug 1661688, bug 1715767, and https://georgialibraries.markmail.org/thread/c3pm2jzgx45p4plf |
12:34 |
pinesol |
Launchpad bug 1661688 in Evergreen "Want easy way to clear a hold when picked up by other patron" [Wishlist,Fix released] https://launchpad.net/bugs/1661688 |
12:34 |
pinesol |
Launchpad bug 1715767 in Evergreen "Allow others to use my account (privacy waiver)" [Wishlist,Fix released] https://launchpad.net/bugs/1715767 |
12:44 |
jeff |
i'm not finding substantial irc conversation in a few minutes of searching, though i'm pretty sure it's been discussed at least once before. |
12:44 |
jeff |
We're going to need to tie specific patrons to each other for this, not just "husband jim is allowed to pick up holds". |
12:45 |
jeff |
And then we're going to check the item out to the patron that has the hold, not the patron whose card is presented. |
12:49 |
* csharp |
is very interested in the 18.04 PG 11 (in his case) question too |
12:49 |
jeff |
Evaluating options for making use of "friends", or using family groups, expanding on actor.usr_privacy_waiver... |
13:17 |
|
sandbergja joined #evergreen |
13:20 |
|
nfBurton joined #evergreen |
13:34 |
jeff |
hah, and now bug 1840062 has some intersection |
13:34 |
pinesol |
Launchpad bug 1840062 in Evergreen "Show total group bills in OPAC" [Wishlist,New] https://launchpad.net/bugs/1840062 |
13:44 |
dbs |
berick: amazing that Safari on iOS supports <input type="date"> but Safari on MacOS does not |
13:53 |
jeff |
"just use the keyboard" |
13:54 |
|
khuckins joined #evergreen |
14:03 |
csharp |
sandbergja: around? |
14:04 |
sandbergja |
csharp: yup! I'm here |
14:05 |
csharp |
I'm testing your fix to bug 1816475 and when doing the "ng build --prod" step, I see this: https://pastebin.com/ph7dbp0a - seems like we need to add moment-timezone to package.json somewhere? |
14:05 |
pinesol |
Launchpad bug 1816475 in Evergreen "Booking module refresh" [Undecided,Confirmed] https://launchpad.net/bugs/1816475 |
14:06 |
csharp |
one our libraries is very interested in booking, so we're enthusiastic about getting into 3.4 (or as close as we can get) |
14:06 |
csharp |
s/getting into/getting your fix into/ |
14:06 |
sandbergja |
ooh, let me take a look. I might have missed a commit in that branch. |
14:07 |
csharp |
no prob - I figured you probably already have it correct locally :-) |
14:07 |
sandbergja |
thanks for testing, btw! |
14:08 |
bshum |
dbs: "the keyboard? how quaint..." |
14:10 |
sandbergja |
csharp: I just took a look -- do you have the commits with messages starting "LP1834662" as well as "LP1816475"? |
14:11 |
csharp |
sandbergja: oh - no I don't - that's certainly the problem |
14:11 |
sandbergja |
The commits for bug 1816475 should include moment and moment-js in the package.json |
14:11 |
pinesol |
Launchpad bug 1816475 in Evergreen "Booking module refresh" [Undecided,Confirmed] https://launchpad.net/bugs/1816475 |
14:11 |
csharp |
I'll start over :-) |
14:11 |
csharp |
more soon |
14:11 |
csharp |
for some reason, I assumed the other bug's commits were already committed to master |
14:12 |
sandbergja |
keep me posted! Hope you like it -- let me know if you have other questions as you test! |
14:12 |
csharp |
thanks! |
14:13 |
sandbergja |
out of curiosity: what does that one library want to use the booking module for? I'm always interested to hear use cases for it. |
14:14 |
sandbergja |
as in what resources do they want to use it for? |
14:14 |
sandbergja |
not "why oh why would they ever want to use booking module" :-) |
14:19 |
csharp |
I'm not sure, honestly - terran has been coordinating with them |
14:19 |
csharp |
I think it's for meeting room-type resources |
14:19 |
sandbergja |
that makes sense! Thanks! |
14:20 |
mmorgan |
sandbergja: We had a library that was using booking for book club kits - tote bags with all different formats of a certain title. |
14:22 |
sandbergja |
mmorgan: cool! do you think they might be interested in testing out the Angular booking interface too? |
14:23 |
sandbergja |
I'm also happy to just make screenshots or a video of the new interface so they can give their feedback without the overhead of loading the branch, etc. |
14:26 |
mmorgan |
We've certainly been keeping an eye on the progress of the development. I think screenshots or a video would be great! Not just for libraries that have been using the old version, but also to show others what it looks like, which might give them ideas about what it might be useful for. |
14:28 |
sandbergja |
I will do that! |
14:33 |
|
jvwoolf joined #evergreen |
14:33 |
mmorgan |
sandbergja++ |
14:33 |
miker |
jeff: I'd buy you $some beers for friends work! |
14:43 |
csharp |
sandbergja++ # we got it installed and terran is poking - we'll probably have some feedback for you soon :-) |
14:43 |
sandbergja |
csharp++ |
14:43 |
sandbergja |
terran++ |
14:43 |
sandbergja |
have fun! |
14:43 |
csharp |
thanks! |
15:00 |
|
mmorgan1 joined #evergreen |
15:33 |
|
khuckins joined #evergreen |
15:47 |
|
mmorgan joined #evergreen |
15:48 |
|
abowling joined #evergreen |
15:50 |
abowling |
running into the server not supporting the staff client error, even though they're on the same minor release version. anyone fill me in on a piece of magic i might be missing? |
15:50 |
abowling |
^one is a production server; the clone is a test server |
15:52 |
|
jihpringle joined #evergreen |
15:54 |
jeff |
abowling: for the XUL client, support is determined by looking for an entry in /xul/ on the server. |
15:55 |
jeff |
so, https://demo.example.org/xul/ |
15:57 |
jeff |
so it's possible you used a different value for STAFF_CLIENT_STAMP_ID on the two, or you're missing a symlink, or you didn't do the "make STAFF_CLIENT_STAMP_ID=rel_name install" step at all on one, etc. |
15:57 |
jeff |
(assuming you were inquiring about the xul client) |
15:58 |
abowling |
jeff: it is a legacy xul client. prepping for a 3.3 migration. |
15:59 |
abowling |
jeff: so they must have the same label? I *thought* (though it's been years since I tried it) that you could use different labels, but if you can't, i'm 99% sure that's the issue. |
16:00 |
jeff |
server and client need to match. |
16:00 |
jeff |
in terms of the stamp that the client looks for needs to be present on the server. |
16:02 |
berick |
abowling: xul client -> about -> Target Server ID |
16:02 |
berick |
has to be a matching directory or symlink on server pointing to xul server files |
16:10 |
|
khuckins joined #evergreen |
16:16 |
abowling |
jeff++ |
16:16 |
abowling |
berick++ |
16:17 |
abowling |
jeff: berick: i'm amazed that in over 11 years, i have dumb lucked my way into never encountering this in that i believe i've just run into the default stamp IDs and it's worked. thanks both! |
16:18 |
* abowling |
is also looking forward to killing the last hosted xul client we support |
17:12 |
|
mmorgan left #evergreen |
17:28 |
|
sandbergja joined #evergreen |
17:50 |
|
sandbergja joined #evergreen |
18:06 |
|
jvwoolf left #evergreen |
18:07 |
|
agoben joined #evergreen |
18:49 |
|
cmalm joined #evergreen |
21:21 |
|
sandbergja joined #evergreen |
21:42 |
|
sandbergja joined #evergreen |
22:19 |
|
sandbergja joined #evergreen |
23:02 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |