05:04 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
07:23 |
|
mtj_ joined #evergreen |
07:27 |
|
Callender_ joined #evergreen |
07:35 |
|
jboyer-isl joined #evergreen |
09:23 |
|
montgoc1 joined #evergreen |
09:55 |
kmlussier |
One of our sites is planning to upgrade to 2.8 soon. I looked through the LP bugs and didn't see anything that warranted waiting for the next point release. But I thought I would check with everyone here in case I'm missing something. |
09:55 |
kmlussier |
I don know if anyone else is on 2.8 yet other than bshum. |
09:56 |
pgardella |
We've upgraded to 2.8.1 in our development environment and are going live with it next week in production. So far, we've not any any issues with 2.8. I was using it extensively at the conference, and we've had two of our libraries testing it. |
09:58 |
kmlussier |
pgardella: Thanks! That sounds promising. :) |
09:58 |
csharp |
RoganH: what version did you upgrade SCLENDS to? |
09:59 |
RoganH |
chsarp: 2.7.5 |
11:40 |
mrpeters |
nothing to my apache error logs today, other_vhosts_access.log just looks like normal activity, lots of 200 HTTP requests |
11:41 |
jeff |
mrpeters: browser console is where i'd look |
11:42 |
jboyer-isl |
mrpeters: This will make a difference, I'm just looking at webby, are you troubleshooting a local install? |
11:42 |
mrpeters |
a PINES test server |
11:42 |
mrpeters |
it is publicly accessible |
11:42 |
jboyer-isl |
ok, never mind me then; I haven't given this a shot yet to know what even can go wrong. |
11:42 |
mrpeters |
yeah thats what im trying to learn :P |
11:43 |
mrpeters |
interesting |
15:12 |
bshum |
jboyer-isl: Ah alrighty. I'll give that a whirl. |
15:13 |
bshum |
jboyer-isl++ # thanks! :) |
15:13 |
bshum |
awitter++ # spam warrior |
15:14 |
jboyer-isl |
Also, oops about the scripts. We don't use them so I didn't test them properly, just copy pasta. |
15:16 |
berick |
jboyer-isl: tell me more about this pasta replicator |
15:16 |
bshum |
jboyer-isl: No worries, gives me stuff to poke at someday. |
15:18 |
Dyrcona |
"Our pasta who art in collander, draining be they noodles..." |
15:55 |
bshum |
jboyer-isl: That's what I was contemplating too. |
15:56 |
bshum |
Non-SSD storage, but with more than enough RAM to have to deal with major I/O issues. |
15:56 |
bshum |
As the tradeoff. |
15:56 |
jboyer-isl |
Then there are no concerns about TRIM support, etc. (also, how often do you really hit the disk? ;) ) |
16:00 |
|
graced joined #evergreen |
16:05 |
jboyer-isl |
I will say for the logs, there's a lot of Pg tuning that you need to do to really make the best use of that much ram. I don't think we're 100% there, but things are in pretty good shape for the most part. (there are still sorting temp files created very occasionally) |
16:06 |
jboyer-isl |
My hope is that I can get an identical model for testing, that would be huge. |
16:21 |
|
mrpeters joined #evergreen |
17:04 |
|
graced joined #evergreen |
17:04 |
|
dkyle1 joined #evergreen |
17:10 |
|
dkyle1 left #evergreen |
17:16 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
17:54 |
|
alynn26 left #evergreen |
18:01 |
* berick |
wonders if anyone has used http://sqitch.org/ for any projects. |
18:01 |
* berick |
says before disappearing |
04:24 |
|
pinesol_green joined #evergreen |
04:25 |
|
egbuilder joined #evergreen |
04:25 |
|
goood joined #evergreen |
05:04 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
07:50 |
|
rjackson_isl joined #evergreen |
07:52 |
|
collum joined #evergreen |
08:02 |
pgardella |
kmlussier++ for catching my typo |
10:33 |
Dyrcona |
Could be a bug with calculating/maintaing mbts.... |
10:34 |
Dyrcona |
maintaining, even. |
10:34 |
|
pgardella joined #evergreen |
10:34 |
berick |
Dyrcona: any chance you could paste/email your test JEDI? |
10:34 |
Dyrcona |
berick: Yes, if it fails again. |
10:35 |
Dyrcona |
I just built a fresh vm to make 100% sure. I just have to install OpenSRF and Evergreen, etc. |
10:35 |
mmorgan |
Hmm. Eyeballing these, looks like they are mostly all backdated checkins. |
11:16 |
kmlussier |
dbwells: You must be more human than me. :) |
11:17 |
* dbwells |
*more* human than someone? First time for everything :) |
11:17 |
kmlussier |
OK, it's me. Apparently, I have something that automatically logs me into that site, which worked fine until we added the math checks. I can disable that. |
11:19 |
pastebot |
"Dyrcona" at 64.57.241.14 pasted "JEDI I'm testing with" (1 line) at http://paste.evergreen-ils.org/57 |
11:19 |
Dyrcona |
berick ^^ |
11:20 |
|
dMiller_ joined #evergreen |
11:21 |
berick |
thanks Dyrcona |
13:08 |
jboyer-isl |
(apparently it is) |
13:09 |
bshum |
Heh |
13:12 |
Dyrcona |
:) |
13:30 |
bshum |
eeevil++ # I'll add your latest patch to our test server for the TT caching |
13:31 |
eeevil |
bshum: cool, thanks |
13:31 |
bshum |
eeevil: So far, so good anyways. I do feel like it's faster :) |
13:32 |
Dyrcona |
I should test that branch out, too. |
13:32 |
Dyrcona |
My dev system is pretty slow. |
13:32 |
eeevil |
you'll really want http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/gmcharlt/lp1452366_preinit_context_loaders plus my last commit on http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/collab/gmcharlt/lp1449709-TT-caching-by-egweb |
13:33 |
bshum |
eeevil: Yeah I merged all of those, plus all the sprint2 so far published into the same test branch and rolled that out to our main test server. |
13:34 |
bshum |
Fun to try things out with a copy of our data :P |
13:34 |
eeevil |
rad. the former incorporates the latter, and one more that helps a bunch at apache worker startup |
13:43 |
bshum |
eeevil: Hmm, adding those changes breaks my system with an internal server error. |
13:44 |
bshum |
From ctx to r anyways |
15:00 |
kmlussier |
But during the OpenSRF configuration, I already copied those opensrf files and edited the opensrf_core.xml . |
15:05 |
jeff |
you copied different opensrf config files. |
15:05 |
Stompro |
kmlussier, the OpenSRF install is not specific to Evergreen, it just gets OpenSRF up and running. (even though it targest the /openils/ dir). When you install Evergreen you are installing new config files. |
15:06 |
jeff |
there are example opensrf config files in the opensrf archive which set up basic services designed just to test opensrf |
15:06 |
jeff |
there are example opensrf config files in the Evergreen archive which set up evergreen. |
15:06 |
kmlussier |
And the two are different? That makes sense. |
15:06 |
kmlussier |
jeff++ Stompro++ |
15:07 |
jeff |
if you don't install the opensrf config files that come with evergreen, then when you start "all opensrf services" you will get no evergreen opensrf services, you will only get the opensrf services that came with opensrf itself. |
15:09 |
dbs |
at one point the docs had a very emphatic "Yes, we know you just did this for OpenSRF. You really do have to do this again for Evergreen." |
15:09 |
dbs |
(or something like that |
15:10 |
kmlussier |
One of the things I'm doing while running through the install is noting down places where the instructions could be clearer. |
15:10 |
dbs |
kmlussier: you committed thoughtcrime |
15:10 |
dbs |
thoughtmistake :) |
15:10 |
dbs |
"Please refer back to the OpenSRF README and, as the opensrf Linux account, edit the Evergreen version of the opensrf_core.xml file using the same Jabber users and domains as you used while installing and testing OpenSRF.: |
15:10 |
dbs |
is the current version of that note |
15:11 |
* kmlussier |
probably commits thoughtmistake on an hourly basis |
15:12 |
* dbs |
goes into fullblown reallifemistake typically |
15:13 |
dbs |
Maybe rather than putting the stuff about "cp -b" in the note in that section of the docs, the "No, really. You have to do this for Evergreen now." should be the called-out note. |
10:02 |
pinesol_green |
jeff always wants pancakes. |
10:02 |
berick |
Dyrcona++ # RM hat in the ring |
10:03 |
jeff |
Dyrcona++ |
10:04 |
RoganH |
So, I'm trying to grok how detailed we want pg_tap tests in the non-concerto tests. Do we want tests that ultimately would test for all the tables, indexes, etc...? |
10:06 |
bshum |
Hmm, opinions on https://bugs.launchpad.net/evergreen/+bug/1454879 -- bug or new feature? (I'm leaning towards new, since it never displayed that information before, and if so, we should put in release note entry and add it towards 2.next, aka, 2.9) |
10:06 |
pinesol_green |
Launchpad bug 1454879 in Evergreen "Account Expiration Date in My Account" (affected: 2, heat: 10) [Undecided,New] |
10:08 |
berick |
bshum: i'd call it new as well |
10:37 |
pinesol_green |
jwoodard: The current temperature in Nipe Ranch, Krugerville, Texas is 56.5°F (9:36 AM CDT on May 21, 2015). Conditions: Light Rain. Humidity: 90%. Dew Point: 53.6°F. Pressure: 30.19 in 1022 hPa (Rising). |
10:38 |
jwoodard |
It was just 85°F and sunny yesterday... |
10:38 |
dbs |
timely article on release management stresses in PostgreSQL: http://lwn.net/SubscriberLink/645020/15f0367e0d5affff/ |
10:40 |
pgardella |
Hi, all. Trying to track down why many of our action triggers don't work. Namely overdue notices. Our hook=longoverdue.auto ones work. The hook=checkout.due ones do not, not even the example seed one. The action_trigger.event.state is "invalid" when I try to test the action trigger from the staff client. Nothing gets put into action_trigger.event_output, and the gateway.log only has osrf_http_translator 2015-05-21 14:37:42 [ACT:18040:./osrf_htt |
10:40 |
dbs |
we still use OpenSRF python for our custom LDAP-based auto-population of actor.usr & friends |
10:42 |
pgardella |
Any thoughts on how to debug it further? |
10:44 |
kmlussier |
Dyrcona++ # dusting off constrictor. |
11:15 |
jboyer-isl |
jonadab: provided you can properly excersize it. We (I!) have issues with that, and that's before you even get to things like race conditions / bugs that lie in wait until the load spikes. |
11:16 |
jonadab |
True. |
11:16 |
krvmga |
git++ |
11:16 |
jonadab |
Although a project like Postgres is widespread enough to have a lot of people testing even the bleeding-edge code. |
11:17 |
jboyer-isl |
git++ # in any case though. |
11:17 |
bshum |
jonadab: Well, a project like Evergreen occasionally has... bleeding code |
11:17 |
bshum |
And bleeding adopters |
11:17 |
bshum |
But that's besides the point. |
11:17 |
jonadab |
Yes, Evergreen would have more of a problem getting new stuff tested. |
11:17 |
bshum |
I forgot what I was trying to say. |
11:17 |
bshum |
I just see blood now. |
11:19 |
jboyer-isl |
I don't know if Pg is on the list of projects that huge companies are now throwing money at (OpenSSL is where that started) but they probably should be. |
13:38 |
bshum |
Or maybe the type of browser you've got |
13:38 |
bshum |
Or weird caching |
13:39 |
bmills |
bshum: all in https. in firefox now. |
13:42 |
bshum |
bmills: Hmm, that sounds suspicious. |
13:42 |
bshum |
Unfortunately we do not require passwords for our selfchecks |
13:42 |
bshum |
So I don't think I've tested it lately. |
13:43 |
bmills |
we only have one library interested in that aspect. otherwise.. |
13:52 |
bshum |
csharp: Every time I get a PGCon-announce email, I think to myself, (1) I wish I was going to hear the talks, and (2) I want poutine!!! :( :( |
13:52 |
bshum |
csharp: Just a little while to go, you'll have to share all the cool things you see and learn |
13:53 |
bshum |
bmills: I'm firing up one of our test servers to see if I can duplicate the problem you see. |
13:54 |
bshum |
Assuming of course, I can figure out which setting it is... whee! |
13:54 |
* bshum |
sets both settings to TRUE for giggles |
13:55 |
RoganH |
bshum: can we give karma to poutine? |
13:56 |
yboston |
heads up, the IRC practice time will start at 2 PM EST |
13:56 |
bshum |
RoganH: I would.... then I'd eat it. |
15:19 |
gsams |
well, one of those |
15:19 |
bshum |
bmills: That sounds like it might be a worthy goal... |
15:19 |
bshum |
bmills: I haven't encountered it personally, but I guess I don't check out that slowly :) |
15:19 |
tsbere |
gsams: I would call the iptables route more tested, though setcap kindof helps to ensure nothing else will use the port instead... |
15:20 |
bshum |
I'd say Launchpad that idea, and if you can mock up a quick proof of concept on code, that'd be cool. : P |
15:21 |
bmills |
bshum: thanks. mainly encountered the issue with the self check in kids. the piles can get big there |
15:21 |
bmills |
bshum++ |
15:23 |
gsams |
Now I just have to figure out what went wrong with ezproxy... |
15:24 |
* tsbere |
really needs to see about getting his "proxy straight in evergreen" stuff set up for testing somewhere... |
15:24 |
tsbere |
I mean, I know it works in theory. I haven't actually tested with real services, though. |
15:24 |
jboyer-isl |
gsams: I' |
15:26 |
jboyer-isl |
I'd recommend looking into what tsbere mentioned re: iptables and redirection. That way you don't have to run the server as root. We actually have our firewall doing that before requests hit our z39.50 server, so that's another option. (And much more appealing since I think IPtables looks like a social experiment in gaslighting sysadmins...) |
15:27 |
jboyer-isl |
Finally reading the rest of the scrollback, that's what he's doing anyway. Ah, well. |
15:47 |
tsbere |
Megakeen: I actually wrote a database function to fill "new materials" bookbags based on various criteria for our members. |
15:48 |
Megakeen |
I'm looking at a ppt about bookbag buckets now. I'll see what I can come up with. |
15:49 |
Megakeen |
My local director expects miracles when I don't have access to anything at the consortium level--nothing on the back end. D: |
15:51 |
makohund |
Megakeen: a test server with real data in it that you do have access to would be a nifty thing |
15:51 |
Megakeen |
Okay, from what I'm reading it looks like user lists created in-browser in the catalog can be viewed/edited as buckets in the client? |
15:52 |
Dyrcona |
Yes, that is true. |
15:52 |
Megakeen |
I think that solves my issue, then. The powers that be requested an easier way to add/remove items from the new lists 'cause doing so from the web interface is clunky. |
16:43 |
bshum |
And so they give you back junk |
16:43 |
bshum |
For us, I think they use specific hostnames to verify that we are who we are. |
16:43 |
bshum |
And that their content is allowed on our pages. |
16:44 |
gsams |
Yeah, they were planning to pull the eg_vhost file from another site and the award.tt2 file from another site to see if we could figure it out |
16:44 |
gsams |
I decided to take a shortcut |
16:44 |
gsams |
but I think I know what's wrong, gonna test it |
16:45 |
bshum |
Do you have multiple eg_vhost entries for your different virtualhosts? |
16:45 |
bshum |
Maybe the variables aren't getting up to the right level |
16:46 |
gsams |
The lines they sent me for those two variables had a colon in it that should have been a space |
17:04 |
pgardella |
tbere++ |
17:11 |
mmorgan |
Hey! NOBLE got karma and I missed it? |
17:14 |
|
mmorgan left #evergreen |
17:18 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
17:34 |
|
dkyle1 left #evergreen |
17:40 |
|
wongon joined #evergreen |
19:05 |
kmlussier |
tsbere++ #Making up for the typo above :) |
00:35 |
|
jihpringle joined #evergreen |
04:02 |
|
gsams joined #evergreen |
05:17 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
07:22 |
|
graced joined #evergreen |
07:27 |
|
jboyer-isl joined #evergreen |
07:50 |
|
rjackson_isl joined #evergreen |
10:37 |
bshum |
We get a network failure |
10:37 |
bshum |
Can't call method \"id\" on an undefined value at /usr/local/share/perl/5.14.2/OpenILS/Application/Circ/Circulate.pm line 2536. |
10:38 |
bshum |
Looking at that line in Circulate.pm, I find that it's attempting something with the dont_change_lost_zero |
10:38 |
jeff |
can you reproduce on a test system and try with and without that setting enabled? |
10:39 |
Bmagic |
When we migrate lost items, we make the status "missing" |
10:39 |
bshum |
jeff: I'll see if I can find the same item in our test system. Not sure if it's synced enough |
10:40 |
Dyrcona |
bshum: I believe the key is in your 3rd line. |
10:40 |
Dyrcona |
I'd just change the copy status to missing and try checking it in again. |
10:41 |
Dyrcona |
Bmagic++ |
11:14 |
mmorgan |
bshum: kmlussier: We migrated "billed" items to a Lost status, but I think we migrated associated transactions for those. |
11:15 |
mmorgan |
We haven't run into bshum's issue that I'm aware of. |
11:15 |
kmlussier |
Even if it is a flaw in the data migration, I'm worried that there may be several sites that have that flaw. How hard would it be to do a fix so that those flawed migrated items are handled better? |
11:16 |
* bshum |
lets his test database churn on a query while he drives over to the office for the next round of meetings... |
11:19 |
Bmagic |
bshum: does this help identify the situation you are in? select * from asset.copy where status=3 and id not in(select target_copy from action.circulation) |
11:20 |
Dyrcona |
Bmagic: He's doing that one already. Thinks he's missing an index, 'cause it's taking forever. |
11:20 |
Bmagic |
I see |
11:21 |
mmorgan |
... and found 131 items :-( |
11:21 |
* kmlussier |
personally thinks a bug should be filed. |
11:21 |
Dyrcona |
I ran this: select acp.id from asset.copy acp where acp.status = 3 and not acp.deleted and acp.id not in (select target_copy from action.circulation) |
11:21 |
Dyrcona |
Took 9 seconds on my test database the first time. |
11:21 |
* mmorgan |
agrees with kmlussier |
11:22 |
jeff |
kmlussier: to answer your question, i don't know -- haven't looked. no objection to a bug being filed as a next step to getting an eye on it. |
11:22 |
Bmagic |
yeah, my test db returned 2100 rows in 10 seconds |
11:25 |
Dyrcona |
I get 807, and after pulling out dates and doing some sorting, looks like all but 6 come from migration. |
11:26 |
Dyrcona |
Most recent one is from July of 2013. |
11:27 |
|
bmills joined #evergreen |
16:15 |
bshum |
So yeah |
16:15 |
bshum |
A sequential scan on 27 million rows of action.circulation apparently takes awhile to work |
16:17 |
dbs |
hah |
16:18 |
bshum |
I left our test DB running with the query to try finding all the bad "lost" items and it was still running this afternoon when I went to check on it. Around 4+ hours later. |
16:18 |
bshum |
So.... I'll think about better ways of finding that faster. |
16:18 |
jeff |
what was your query, again? |
16:19 |
bshum |
jeff: Mine was a very generic SELECT COUNT(*) FROM asset.copy WHERE status = 3 AND deleted = FALSE AND id NOT IN (SELECT target_copy FROM action.circulation); |
16:19 |
bshum |
The scan on getting target_copy from action.circulation is what's slowing me down |
16:33 |
bshum |
jeff: Yes, that works, and invokes the index |
16:33 |
bshum |
And voila, magic fast |
16:34 |
bshum |
Just 35682 copies to deal with... huzzah |
16:34 |
collum |
yep. Just ran the same query on my test machine. It runs exponentially faster. |
16:34 |
Dyrcona |
Takes only about 1 second less on my data, but that's still an improvement. :) |
16:34 |
|
buzzy joined #evergreen |
16:34 |
jeff |
yeah. completes in 623ms for me on a very very underpowered test instance. |
16:34 |
bshum |
2244 ms. Vs. how 4+ hours and incomplete? Yeah seems like a win. |
16:35 |
jeff |
http://i.imgur.com/IW8simF.gif |
16:35 |
bshum |
jeff++ |
16:58 |
bshum |
And run them whatever |
16:58 |
bshum |
Well, edit and run them |
16:59 |
jeff |
i'd go with that, yes. |
17:03 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
17:07 |
bshum |
I should add to the README |
17:07 |
bshum |
Little things |
17:08 |
bshum |
Like install libemail-sender-perl |
11:23 |
Bmagic |
I wonder if the order needs to specify the system in order for the query to identify the shelving ID |
11:24 |
tsbere |
Dunno. |
11:24 |
tsbere |
Can't even speculate at this point. ;) |
11:58 |
berick |
Bmagic: csharp: fyi, pushed more fixes to bug 1373690 (edi template). thanks again for all the testing |
11:58 |
pinesol_green |
Launchpad bug 1373690 in Evergreen "Direct EDI generation for ACQ orders -- AKA kill ruby webrick" (affected: 1, heat: 8) [Undecided,New] https://launchpad.net/bugs/1373690 - Assigned to Bill Erickson (berick) |
12:01 |
kmlussier |
Webby is very slow this morning. Is work being done on it? |
12:02 |
phasefx |
kmlussier: don't think so |
12:16 |
phasefx |
seems to be okay to me; running to lunch :) |
12:18 |
csharp |
well, the biggest problem with branch level copy locations I've seen is that, when combined with system-level cataloging, the copies can end up belonging to another branch's location (when locations are named the same across branches) - but that's fixed in bug 778989 |
12:18 |
pinesol_green |
Launchpad bug 778989 in Evergreen "Owning lib of asset.copy_location not visible in Item Attributes Editor UI" (affected: 3, heat: 16) [Medium,Fix released] https://launchpad.net/bugs/778989 |
12:27 |
csharp |
berick: I'm afraid I'm going to have to wait for Leslie to get back to test correctly - I don't want to risk placing actual orders and confusing people because I don't know what I'm doing :-/ |
12:27 |
csharp |
but that said, |
12:27 |
csharp |
berick++ |
12:28 |
|
sandbergja joined #evergreen |
12:31 |
kmlussier |
phasefx: Works now. Thanks! |
12:31 |
kmlussier |
phasefx++ |
14:52 |
csharp |
Bmagic++ |
14:54 |
Bmagic |
gotta stop giving me karma, it's gonna get destroyed, lol |
14:54 |
berick |
hah |
14:54 |
Bmagic |
let's do all this EDI testing after the karmapocolypse |
14:58 |
* berick |
promises to manually carry over Bmagic's EDI karma |
14:58 |
Bmagic |
haha, I'm just kidding, I dont care |
14:58 |
berick |
ok, down to the last (obvious) problem. fixing.. |
15:48 |
bshum |
https://bugs.launchpad.net/bugs/1456289 - if memory serves, Bmagic and I saw this on 2.7 too, and it's cause autogen.sh wasn't run on the system with apache restarted |
15:48 |
pinesol_green |
Launchpad bug 1456289 in Evergreen "Tpac "edit" link on record screen does not save changes" (affected: 1, heat: 6) [Undecided,New] |
15:49 |
kmlussier |
Ah! I recall that one. |
15:50 |
bshum |
I'll put a note on the bug to that effect I guess |
15:50 |
bshum |
And we can probably close it with invalid. |
16:01 |
bshum |
gmcharlt: eeevil: mllewynn tells me that the vandelay loader for web client works fine (we tested it on our test server). |
16:01 |
bshum |
She also says that the flat text editor doesn't stay as the default option when opening additional records (aka, remain checked) |
16:01 |
bshum |
But otherwise, the sprint2 stuff so far, so good |
16:06 |
Bmagic |
berick: 2.7.0 |
16:07 |
|
mrpeters left #evergreen |
16:08 |
berick |
Bmagic: thanks |
16:14 |
tsbere |
Basically a single-machine brick |
16:14 |
tsbere |
I can't even see an *attempt* at making the call in the server logs. |
16:16 |
berick |
seems like the CONNECT is failing / not returning, so the .begin is never attempted |
16:17 |
jeff |
tsbere: what specific pcrud-based interface(s) are you testing with? |
16:18 |
tsbere |
Parts creation. Apparently from any interface you can create parts. |
16:22 |
bshum |
Parts... sigh. |
16:33 |
* tsbere |
glares at the javascript console of the staff client and the lineless "Transaction begin error" that tells him nothing about which of the four possible points that is generated did so |
16:44 |
* tsbere |
glares even more as now everything is working |
16:44 |
tsbere |
and nobody changed anything. I have just been trying to find logs. |
17:07 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
17:10 |
|
ldwhalen joined #evergreen |
17:12 |
|
mmorgan left #evergreen |
17:26 |
|
ldwhalen joined #evergreen |
16:45 |
|
bmills1 joined #evergreen |
16:52 |
Stompro |
My wife just told me I just missed a call from "Microsoft" looking to update my computer, I love talking to those guys, I'm sad I missed it. |
16:59 |
mmorgan |
Oh, those "Microsoft" guys really annoy me. |
17:02 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
17:06 |
buzzy |
soon ... https://twitter.com/EvergreenILS/status/596782856396869632 |
17:07 |
Stompro |
buzzy++, first use of the #evgils15 tag, I've been waiting for it to turn up. |
17:10 |
kmlussier |
I've opened up voting for which cookies I should make for the MassLNC development partners. More details here https://plus.google.com/+KathyLussier/posts/PCk6Ya3Zivs |
23:13 |
bshum |
Once we package new maintenance releases later this month, I expect that it'll be smoother sailing for installation on Debian Jessie. |
23:15 |
nuentoter |
ok |
23:15 |
nuentoter |
so for me to have a better installation experience right now would you recommend wheezy? |
23:16 |
bshum |
nuentoter: For Debian, yes, I believe Wheezy has been better tested by different folks who use Debian. |
23:16 |
bshum |
I personally use Ubuntu primarily. So I'll caveat that I've only lightly tested Debians. |
23:16 |
bshum |
Though I know others can speak for Debian |
23:17 |
nuentoter |
most of my linux experience up until now has only been for very basic things on someones computer running crunchbang which is slick but technical |
23:17 |
nuentoter |
i used ubuntu for a few years about 6-7 years ago for work |
23:25 |
nuentoter |
ok so tonight i shall download wheezy and resume working on installing of jessie after you folks update |
05:04 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
07:12 |
kmlussier |
Good morning #evergreen |
07:30 |
|
graced joined #evergreen |
07:35 |
|
jboyer-isl joined #evergreen |
10:45 |
kmlussier |
Ah, I forgot about that bug. |
10:46 |
bshum |
kmlussier: These bugs haunt my dreams. |
10:46 |
jwoodard |
NTLC aka North Texas Library Consortium in case everyone cannot read my mind or auto guess acronyms ;) |
10:46 |
bshum |
jwoodard: I've had some passing familiarity with NTLC ;) |
10:55 |
|
akilsdonk joined #evergreen |
10:56 |
bshum |
jwoodard: So my recommendation is to mention the issue up your chain of support, and see if they can test your bib/item and see if there are problems with the reingest on that record. |
10:57 |
bshum |
Something like: SELECT COUNT(*) FROM biblio.record_entry WHERE deleted = FALSE AND id NOT IN (SELECT source FROM metabib.record_attr_vector_list); |
10:57 |
bshum |
Would tell you how many bibs (which are not deleted) do not have a proper corresponding metabib.record_attr_vector_list entry |
10:58 |
bshum |
I just ran that on our systems and came up with 13 bibs, which makes me a little sad. |
10:58 |
csharp |
yay! 0 in PINES |
10:59 |
* csharp |
fully expected to see more than 0 |
10:59 |
bshum |
csharp: Amazing! |
11:02 |
bshum |
In case you wanted the exact bib IDs for those missing entries |
11:02 |
mmorgan |
bshum++ |
11:03 |
bshum |
mmorgan: Yeah, if you follow rjackson_isl's steps in his comment on that bug for a post-2.6 system, you can repair those missing entries. |
11:03 |
berick |
csharp: have you done any additional testing on EDI since your last comments in bug #1342227 ? |
11:03 |
pinesol_green |
Launchpad bug 1342227 in Evergreen "Setting up EDI Fails with Ruby version > 1.8" (affected: 2, heat: 14) [Undecided,New] https://launchpad.net/bugs/1342227 |
11:04 |
jwoodard |
bshum: Already sent an email. Proper training and database access are one of the many thing on my list of things to accomplish. |
11:04 |
jwoodard |
bshum++ kmlussier++ |
11:15 |
jeff |
but i think it's pretty rare. we have two. |
11:16 |
* bshum |
thanksfully has 0 |
11:16 |
bshum |
And I'll go back to blissfully not thinking about billing weirdness. |
11:17 |
csharp |
berick: no - I didn't put together a good way to test on the stock EG master machine I was on |
11:17 |
csharp |
berick: I was able to see the daemon running, though |
11:18 |
mmorgan |
Whew! we have 0 for jeff's query :) |
11:19 |
|
sarabee joined #evergreen |
11:20 |
csharp |
0 for jeff's query here too |
11:22 |
|
sandbergja joined #evergreen |
11:31 |
|
buzzy joined #evergreen |
11:52 |
|
kitteh_ joined #evergreen |
11:54 |
yboston |
Hello everyone, DIG will need access to a test server running 2.8.x, I suspect we may be able to use webby? Any other recommendations? |
11:55 |
tsbere |
yboston: kmlussier may be willing to spin up one of the masslnc test boxes for ya, though those don't get the web client going currently. |
11:55 |
yboston |
tsbere: thanks |
11:56 |
kmlussier |
yboston: The server on the community servers page already has 2.8. But, as tsbere said, it doesn't have webby. |
11:56 |
kmlussier |
I usually use webby for web client docs. |
14:30 |
dbs |
https://bugs.launchpad.net/evergreen/+bug/1031335 I think? |
14:30 |
pinesol_green |
Launchpad bug 1031335 in Evergreen 2.7 "Email templates should always escape headers" (affected: 2, heat: 10) [Undecided,Confirmed] |
14:32 |
dbs |
tsbere: around, but not in a headspace to recall or revisit library/copy ranking design decisions very effectively |
14:47 |
mmorgan |
Anyone around to poke webby? I was hoping to test a few things, but can't login :-( |
14:58 |
mmorgan |
Hey, webby's back! Thanks to whoever poked! |
14:58 |
eeevil |
mmorgan: the drive's filled up, I'm looking for places to free space now |
14:58 |
eeevil |
it'll die before too long ;) |
14:59 |
mmorgan |
Aww. That's sad :-( |
14:59 |
bshum |
Like a balloon inflating till it explodes. |
14:59 |
bshum |
*pop* |
15:01 |
mmorgan |
When dev servers get endearing names like 'webby', it's sad when they go away. |
15:03 |
berick |
mmorgan: wait til you're testing on "widdlepuppy" |
15:05 |
mmorgan |
widdlepuppy? I can't stand it! ;-) |
15:14 |
eeevil |
mmorgan: ok, it should stay up for a while, cleared about 500MB. we'll look at increasing space generally soon |
15:15 |
mmorgan |
eeevil++ |
16:36 |
|
mrpeters left #evergreen |
16:45 |
|
vlewis joined #evergreen |
17:00 |
|
mmorgan left #evergreen |
17:07 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
17:23 |
|
Newziky left #evergreen |
17:43 |
|
bmills1 joined #evergreen |
20:08 |
|
nuentoter joined #evergreen |
00:08 |
|
sarabee joined #evergreen |
05:09 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
07:42 |
|
ericar joined #evergreen |
07:51 |
|
graced joined #evergreen |
07:55 |
|
jboyer-isl joined #evergreen |
09:30 |
bshum |
Though I'm unsure if maybe there were weird permission issue or something. |
09:31 |
Dyrcona |
Well, I got several errors about stuff not being installed/not able to be opened without the sudo. |
09:31 |
Dyrcona |
With sudo, it just worked. |
09:31 |
bshum |
You testing with Ubuntu 12.04 or 14.04? |
09:37 |
bshum |
Alright, so I can't find the branch anywhere, so I must have just been modifying a local copy Evergreen-README on lupin directly. We can diff those changes against master and get a branch started though. |
09:42 |
|
RoganH joined #evergreen |
09:54 |
Dyrcona |
14.04 |
09:55 |
bshum |
Dyrcona: I pushed a collab branch with the changes I started to http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/collab/bshum/README-webclient |
11:32 |
|
Shirleyh joined #evergreen |
11:42 |
jjk |
Good morning |
11:42 |
jeff |
jjk: good morning! |
11:43 |
jjk |
I'm attempting to upgrade an older 2.3 install to the current version but have run into issues with the database schema updates. I'm hoping some folks here can point me in the right direction. |
11:45 |
jjk |
I have a test database that started at 2.3.5 and I've successfully run the schema updates all the way up to 2.3.12. |
11:47 |
jjk |
When trying to upgrade the schema using 2.3-2.4.0-upgrade-db.sql I quickly receive the following errors: |
11:47 |
jjk |
psql:version-upgrade/2.3-2.4.0-upgrade-db.sql:96: NOTICE: extension "tsearch2" already exists, skipping |
11:47 |
jjk |
psql:version-upgrade/2.3-2.4.0-upgrade-db.sql:98: ERROR: cannot drop extension tsearch2 because other objects depend on it |
11:48 |
jjk |
I've not found much in the way of similar issues. |
11:53 |
bshum |
jjk: So that sounds like you have something custom in your database that relies on tsearch2 extension |
11:54 |
bshum |
I found something like that when we upgraded as well, some locally created views for reporting had used that extension and needed to be rewritten |
11:55 |
* bshum |
upgraded forever ago and doesn't remember how he ultimately identified all the things that used that extension. |
11:57 |
jjk |
bshum: Thanks. I'll look at the reports. |
11:58 |
|
TaraC joined #evergreen |
12:01 |
bshum |
jjk: Out of curiosity, what version of PostgreSQL are you using for your tests? |
12:01 |
bshum |
(i.e. did you also test upgrading your postgresql installation to newer versions 9.1+) |
12:02 |
bshum |
And you might find it interesting |
12:02 |
bshum |
To try the drop extension directly |
12:02 |
bshum |
And see if it spits back what is still depending on it |
12:03 |
bshum |
Hmm |
12:03 |
bshum |
csharp: Did we archive the old evergreen-admin mailing list? |
12:04 |
bshum |
csharp: Nevermind, found what I was looking for |
12:04 |
bshum |
jjk: You might see some value in discussion from this mailing list entry: http://list.evergreen-ils.org/pipermail/evergreen-admin/2014-May/000086.html |
12:05 |
jjk |
bshum: I'm running 9.1 on Debian, specifically 9.1.14-0+deb7u1 |
12:05 |
bshum |
jjk: Based on what they say there, I would check to make sure the search_path is set right, and then see if there's any "DETAIL" that comes up after the "ERROR" part when you try to drop the extension. |
12:05 |
bshum |
~search_path |
14:08 |
kmlussier |
Wow! That was fast. Thanks gmcharlt! |
14:08 |
kmlussier |
gmcharlt++ |
14:19 |
jeffdavis |
What's the status of NCIPServer? |
14:22 |
kmlussier |
jeffdavis: We have it in testing now to use with AutoGraphics. |
14:22 |
jeffdavis |
kmlussier: that's excellent, thank you |
14:24 |
Dyrcona |
jeffdavis: You can't use the master branch with Evergreen at the moment. |
14:24 |
Dyrcona |
rangi or someone (me?) has to do some integration. I changed the interfaces a good bit. |
14:29 |
Dyrcona |
And sometimes different products from the same vendor. |
14:31 |
|
kitteh_ joined #evergreen |
14:31 |
jeffdavis |
Dyrcona: ah yes, "standards" that are actually their own special case of https://xkcd.com/927/ -- good times! |
14:31 |
bshum |
Haha, the hover is funny |
14:32 |
bshum |
Stompro++ # tested the change for OpenSRF instructions for Ejabberd for Debian Jessie and they look good. I'll sign and push that on for a future OpenSRF 2.4.1 release. |
14:33 |
Dyrcona |
Well, I don't even really consider NCIP to be a standard myself. It's list of features that you can implement. |
14:34 |
Dyrcona |
And every vendor seems to pick their own way to do things, and too many messages are similar, but different. |
14:34 |
Dyrcona |
So, yeah, we need an actual standard. |
15:24 |
tsbere |
Bmagic: set passwd = 'new password' ;) |
15:24 |
Bmagic |
oh, lol |
15:24 |
bshum |
Bmagic: You can just do UPDATE actor.usr SET passwd = 'something' WHERE id = sillyuser; |
15:24 |
Stompro |
bshum, it took me a while to add the second example to the docs also... I thought I compiled it and tested how it looked, did you not like how it looked or did it break when you tried it. |
15:24 |
bshum |
and the function will hash it out for you |
15:25 |
Bmagic |
great! that worked |
15:25 |
bshum |
Stompro: I was just trying to see if I could make it more consistent looking with the rest of the styling. |
16:44 |
mmorgan |
mrpeters: Not an expert, but I don't know of any other way to do that. |
16:44 |
Dyrcona |
I was going to say that I think it is the only way to do it, but got sidetracked. |
16:45 |
mrpeters |
mmorgan: i didnt think so either, but so much awesome stuff has been done with the in-staff client configuration menus that i wasnt sure |
16:52 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
17:16 |
pinesol_green |
[opensrf|Ben Shum] Docs: Keep all source syntax consistent in README - <http://git.evergreen-ils.org/?p=OpenSRF.git;a=commit;h=ef80e4c> |
17:16 |
pinesol_green |
[opensrf|Ben Shum] Docs: Add [source, bash] to code blocks that were not defined in README - <http://git.evergreen-ils.org/?p=OpenSRF.git;a=commit;h=52b6eca> |
17:16 |
pinesol_green |
[opensrf|Ben Shum] Docs: Emphasize variables and paths consistently in README - <http://git.evergreen-ils.org/?p=OpenSRF.git;a=commit;h=86e6d84> |
17:16 |
pinesol_green |
[opensrf|Josh Stompro] LP#1445503 - Updated Ejabberd setup steps for Ejabberd 14.x for Debian Jessie - <http://git.evergreen-ils.org/?p=OpenSRF.git;a=commit;h=e421bb3> |
17:18 |
pinesol_green |
[opensrf|Ben Shum] Docs: Fix mailing list link for help in README - <http://git.evergreen-ils.org/?p=OpenSRF.git;a=commit;h=966fb05> |
17:18 |
bshum |
I give up on the asciidoc syntax for now. I will slay that eventually though. |
17:18 |
|
mmorgan left #evergreen |
17:21 |
bshum |
So, for the Evergreen bugs targeting issues with Debian Jessie |
17:44 |
pinesol_green |
[evergreen|Josh Stompro] LP#1445187 - Force disable of deflate - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=b949202> |
17:44 |
pinesol_green |
[evergreen|Josh Stompro] LP#1362260 - Email::Sender/libemail-send-perl change in Jessie - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=ad879d4> |
17:50 |
pinesol_green |
[evergreen|Josh Stompro] LP#1445182 Changed Debian Jessie dependency install to use packages for dbi dbd-pgsql. - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=d5089b7> |
17:54 |
bshum |
Stompro++ # I pushed ahead everything and I seem to be well on my way towards a happy Jessie test server. |
18:08 |
bshum |
Hmm |
18:10 |
bshum |
Looks like we'll need to create a file for 000.english.pg94.fts-config.sql |
18:10 |
bshum |
In order for PG 9.4 to be used when creating the database |
18:11 |
bshum |
To test, I've just copied the 93 one to be named 94 and seeing how that goes. |
18:25 |
bshum |
I appended my findings to the bug |
18:30 |
bshum |
Stompro: I set https://bugs.launchpad.net/evergreen/+bug/1445150 back to Triaged while we test the last little bit I think we need to create a working database on PG 9.4 using the scripts. |
18:30 |
pinesol_green |
Launchpad bug 1445150 in Evergreen 2.7 "Debian Jessie includes Postgresql 9.4 - update software dependency makefile" (affected: 1, heat: 6) [Medium,Triaged] |
18:31 |
bshum |
When we get time, someone else should check that initial working branch, and then make any special adjustments. |
18:31 |
bshum |
Otherwise, as far as I can see, I have a functional Evergreen install on Debian 8.0 Jessie |
05:00 |
|
collum joined #evergreen |
05:14 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
07:48 |
kmlussier |
Good morning #evergreen |
07:49 |
kmlussier |
@coffee y'all |
07:49 |
* pinesol_green |
brews and pours a cup of Kenya Ndaroini Microlot, and sends it sliding down the bar to y'all |
12:18 |
* tsbere |
hasn't had much reason to use that part of PHP lately so isn't all that familiar with it personally |
12:19 |
jeff |
you're the only reason I ran into it just now. ;-) |
12:19 |
jeff |
PHPSIP2 won't connect to localhost because of it -- simple fix. |
12:22 |
tsbere |
as I said, lately. I haven't done much with phpsip2 for a while. |
12:23 |
* tsbere |
also rarely has phpsip2 talk to localhost, for that matter, even when testing things >_> |
12:23 |
berick |
because i'm not a huge fan of php, i started on this a while back: https://github.com/berick/pysip2 |
12:23 |
berick |
in case anyone prefers python |
12:23 |
berick |
for sip tseting |
16:55 |
* pinesol_green |
grabs some Pumpkin Pie for kmlussier |
16:55 |
mmorgan |
Good idea! |
16:55 |
mmorgan |
@dessert |
16:55 |
* pinesol_green |
grabs some wild Alaskan rhubarb pie for mmorgan |
16:56 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
17:10 |
|
mmorgan left #evergreen |
17:20 |
|
buzzy joined #evergreen |
18:02 |
kmlussier |
evergreen-ils.org is quite sluggish at the moment |
20:33 |
jonadab |
(It updates CPAN and a bunch of related modules.) |
20:34 |
jonadab |
Oh, I should probably clarify: since you were using make, I've been assuming that you already installed build-essential or the equivalent system package. |
20:34 |
jonadab |
So you have gcc and make and all that stuff. |
20:35 |
nuentoter |
our library is looking to switch very soon to evergreen and i'm setting up a left over computer as a test server to check it out and see what will work for us |
20:35 |
nuentoter |
pretty sure most of that can preinstalled on this distro |
20:35 |
jonadab |
Yeah, I'm doing a similar thing to work on migrating our data. |
20:36 |
jonadab |
nuentoter: Oh, could be. I use Debian, which doesn't install that stuff by default, but the build-essential metapackage depends on all of it. |
20:36 |
nuentoter |
im on debian jessie for first time |
03:11 |
|
tsbere joined #evergreen |
03:52 |
* bshum |
generally agrees with dbs and tries to remind people about said older bugs. |
04:47 |
|
book` joined #evergreen |
04:59 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
07:06 |
csharp |
bshum: argh - I hate launchpad |
07:06 |
* csharp |
remembered that the issue had been discussed before, but didn't remember the bug and it didn't appear in search results |
07:07 |
csharp |
so in the old bug I suggested the alternative of commenting out the lines in fm_IDL.xml, but I've changed my mind on that, obviously ;-) |
10:12 |
jeff |
but have not checked lately. |
10:12 |
jeff |
what version are you seeing that behavior on? |
10:12 |
krvmga |
jeff: 2.7.4 |
10:13 |
jeff |
convenient for me to test! |
10:13 |
Dyrcona |
Hmm. I could check right quick. |
10:13 |
jeff |
krvmga: i suspect something other than the copy status is to blame, unless you've heavily tweaked your templates. |
10:13 |
bshum |
I'm pretty sure I remember it displaying when we tested it. Or rather, it displayed as a bill or something elsewhere. |
10:13 |
bshum |
And basically that still showed in the same place as items out |
10:13 |
krvmga |
jeff: our myopac templates are pretty vanilla. |
10:16 |
Dyrcona |
Well, I just set one of my items to lost on my dev system and it doesn't show up in my list of items out in the OPAC. |
10:16 |
jeff |
krvmga: tested by checking an item out to a patron and then marking it lost by patron. it is no longer visible under Items Checked Out, but is visible as a bill in the main myopac page at /eg/opac/myopac/main -- under Fines |
10:17 |
* Dyrcona |
confirms it shows up under fines. |
10:17 |
jeff |
I get a Title, Author, Checkout Date, Due Date, Date Returned shows (fines accruing) [er, they aren't actually] and there's a balance owed. |
10:17 |
jeff |
(under Fines) |
10:18 |
Dyrcona |
Well, the question is should lost items show in items out, or just under fines. |
10:19 |
Dyrcona |
I'd be more likely to say Long Overdue should show up under items out. |
10:19 |
Dyrcona |
Or more correctly, "Checked Out." |
10:21 |
krvmga |
i think the issue has been reported to me incorrectly. i just looked at a test account and the Lost items show up but under Returned/Renewed it says (fines accruing) but under Balance Owed it's showing a replacement cost |
10:21 |
krvmga |
i think the person who reported it might have gotten confused by "(fines accruing)" |
10:22 |
Dyrcona |
Well it shouldn't say that. It is an error. |
10:22 |
Dyrcona |
Maybe it should say "Lost" instead? |
10:22 |
krvmga |
Dyrcona: is it a bug error or a configuration error on our part, do you think? |
10:23 |
krvmga |
if it's a bug, i'll report it. i just want to make sure it's not anything we're doing wrong. |
10:24 |
Dyrcona |
I'd say find out from your staff what the real problem is, and then open a bug. |
10:24 |
Dyrcona |
We can always set it to invalid if it turns out to be configuration. :) |
10:28 |
krvmga |
staff are saying that the patron's Lost items show up under Fines (as previously mentioned) but, if a patron looks at Items Checked Out, the screen shows "You have no items checked out." |
10:29 |
krvmga |
a patron's Lost item is still checked out to the patron, no? |
10:30 |
krvmga |
maybe this is where not showing Lost in the OPAC is having the impact. |
10:31 |
krvmga |
i'm testing by turning OPAC visibility back on for Lost for a little while |
10:35 |
jeff |
i think that "(fines accruing)" is based simply on the lack of a checkin time. |
10:35 |
jeff |
should be a somewhat easy fix to correct/clarify that. |
10:49 |
jeff |
hah! there's actually a TODO in the template |
10:50 |
krvmga |
jeff: lol |
10:51 |
Dyrcona |
Not surprising. :) |
11:00 |
krvmga |
ok, i have tested with showing Lost in the OPAC. Lost items are now OPAC visible in our catalog. logging out and logging in again as the test patron. Current Items Checked Out still shows "You have no items checked out". I'm guessing this means OPAC visibility of Lost status has no impact here. |
11:00 |
Dyrcona |
Sounds like something else is going on. |
11:10 |
kmlussier |
Although Evergreen considers lost items to still be checked out to the patron, as a patron I don't think I would expect it to show in Items Out. If it is truly lost, it's lost. |
11:10 |
kmlussier |
I agree with Dyrcona that I would expect long overdue to still display there. |
15:16 |
pinesol_green |
Launchpad bug 1125270 in Evergreen "Error updating function in 2.0-2.1-upgrade-db.sql for 2.3" (affected: 1, heat: 6) [Low,Triaged] |
15:16 |
bshum |
I wrote some minor patches to fix those two and even though I sure hope nobody is still on 2.0 or 2.3, it'd be nice to close out those bugs. |
15:17 |
* bshum |
would have probably just pushed those already, but just checking real quick one last time. |
15:30 |
csharp |
bshum: so to test bug 1125270, one would need to install 2.0 and run the 2.0 to 2.1 upgrade script? |
15:30 |
pinesol_green |
Launchpad bug 1125270 in Evergreen "Error updating function in 2.0-2.1-upgrade-db.sql for 2.3" (affected: 1, heat: 6) [Low,Triaged] https://launchpad.net/bugs/1125270 |
15:30 |
bshum |
csharp: If you were being thorough, I suppose yes. |
15:30 |
csharp |
I mean, it's probably fine to push as-is |
10:16 |
csharp |
I think I have the ruby problem solved for now |
10:16 |
csharp |
oh good to know |
10:16 |
Dyrcona |
yep. I saw that. |
10:17 |
Dyrcona |
I thought about faking an EDI transaction for testing. |
10:17 |
Dyrcona |
That is, setting up a bogus vendor with a canned order and response to send. |
10:17 |
berick |
we've deployed 2 ubuntu 14.04 servers to productoin. |
10:17 |
berick |
soon, soon we'll be free of centos |
10:19 |
csharp |
I have an aging OpenSRF branch that installed dependencies from EPEL and got it up and running on CentOS |
10:19 |
csharp |
6, I think |
10:19 |
csharp |
but I didn't get as far as Evergreen |
10:22 |
bshum |
I think for front-end app servers, I'm not too nervous about Ubuntu 14.04. But for backend utilities, I get a little anxious to test further. |
10:22 |
bshum |
Acq EDI stuff, sure, but also have to test things like print notice generation, other scripts. |
10:22 |
bshum |
z39.50, who knows? :) |
10:23 |
berick |
bshum: we should be fully migrated by the end of May. i'll let you know how it goes |
10:23 |
bshum |
berick++ |
10:24 |
csharp |
oh yeah - z39.50 is broken in 12.04 too, right? |
17:15 |
bshum |
Hmm |
17:16 |
bshum |
We can't seem to add any bibs with URIs to lists. |
17:16 |
bshum |
That's special. |
17:16 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
17:18 |
mmorgan |
bshum: lp 1246385 ? |
17:18 |
pinesol_green |
Launchpad bug 1246385 in Evergreen "internal server error when adding an item to a list from within staff client" (affected: 1, heat: 6) [Undecided,Confirmed] https://launchpad.net/bugs/1246385 |
17:18 |
bshum |
No, this is in public side |
17:19 |
bshum |
If I go to try adding a bib that's a URI (aka, $9 trick), it just stays off the list and I get a refreshed page that still says "add to list" |
17:19 |
mmorgan |
Oh, ok. sounded familiar. But it's too late in the day... |
17:19 |
bshum |
I'm going to have to get a test system going with 2.8 stock to see if it's a template issue in our systems, or if it's a 2.8 regression. |
17:20 |
bshum |
It's not broken on MVLC's or PINES systems, but they're on 2.7ish |
17:20 |
bshum |
mmorgan: We should probably close that bug. Since no one's confirmed anything since it was reported "fixed" or at least "not broken" for 2.5. |
17:22 |
mmorgan |
Oh, probably so. |
17:24 |
|
mmorgan left #evergreen |
17:37 |
kmlussier |
bshum: There's a bug for that. And old one |
17:38 |
kmlussier |
bug 979038 |
17:38 |
pinesol_green |
Launchpad bug 979038 in Evergreen "tpac: Records with a located URI cannot be added to a list" (affected: 3, heat: 18) [Low,Confirmed] https://launchpad.net/bugs/979038 - Assigned to Jeff Godin (jgodin) |
17:40 |
kmlussier |
Filed that one while C/W MARS and NOBLE were getting ready to go live on Evergreen. |
17:40 |
bshum |
kmlussier: That sounds more like my problem. |
17:40 |
bshum |
I didn't notice it on MVLC/PINES cause I was only testing temp lists on there (no account to test real with) |
17:40 |
bshum |
But temp lists don't even take ours on our systems. |
17:40 |
bshum |
But maybe that's cause we don't use the temp list warning or whatnots. Who knows. |
17:41 |
bshum |
Sigh, oh well. |
17:41 |
* bshum |
clicks "affects me too" and contemplates dinner. |
17:43 |
kmlussier |
jeff: Do you still want to be the assignee on that bug? |
18:16 |
bshum |
csharp: Should we be deprecating https://bugs.launchpad.net/evergreen/+bug/1050384 in favor of your newly filed https://bugs.launchpad.net/evergreen/+bug/1450218 |
18:16 |
pinesol_green |
Launchpad bug 1050384 in Evergreen "Views referenced in reporter UI are not created by default" (affected: 1, heat: 6) [Low,Confirmed] |