05:01 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
06:40 |
|
rlefaive joined #evergreen |
07:13 |
|
rjackson_isl joined #evergreen |
07:22 |
|
agoben joined #evergreen |
09:33 |
|
dteston joined #evergreen |
09:34 |
|
collum_ joined #evergreen |
09:48 |
csharp |
813ac365b |
09:48 |
pinesol_green |
csharp: [evergreen|Mike Rylander] We don't have a matched_attr column anymore, because we're using the fancy expression tree, so test for 901c match directly - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=813ac36> |
09:53 |
|
mmorgan1 joined #evergreen |
09:55 |
jeff |
ah yes, a 2011 vintage commit. code that survives mostly unchanged to this day. excellent selection, sir! |
09:58 |
csharp |
jeff++ |
09:59 |
csharp |
jeff: the funny thing is, I have hit this bug before: https://bugs.launchpad.net/evergreen/+bug/1170514/comments/5, but I didn't update our production server, just the test server using acq |
09:59 |
pinesol_green |
Launchpad bug 1170514 in Evergreen "vandelay.auto_overlay_bib_record discrepancy" [Undecided,Confirmed] |
09:59 |
csharp |
life is just endless circles |
10:09 |
jeff |
is vandelay.auto_overlay_bib_record the only affected function? |
10:10 |
jeff |
but yes, i can also confirm that we have the outdated function |
10:11 |
jeff |
i have replaced some other vandelay functions before, but without checking notes i don't know which functions, or the underlying reason for needing to replace them. |
10:11 |
jeff |
but apparently not this function. |
10:11 |
dbs |
so what's the situation with merging to master / rel_2_12 now? any special processes beyond the usual double sign-off + test(s)? |
10:13 |
jeff |
dbs: with the added explicit statement that rel_2_12 would be bugfixes and not new features, I think you've got it correct. |
10:14 |
dbs |
okay, thanks for the verification :) |
10:20 |
* kmlussier |
catches up to where we left off with the web team two years ago. |
10:31 |
pinesol_green |
Launchpad bug 1170514 in Evergreen "vandelay.auto_overlay_bib_record discrepancy" [Undecided,Confirmed] |
10:34 |
* Dyrcona |
wonders if make release can make a db upgrade script without making a tarball? |
10:43 |
* jeff |
looks askance at this email regarding the non-optional disclosure of certain information to conference exhibitors and sponsors |
10:44 |
bshum |
dbs++ # new test |
10:45 |
jeff |
is that sharing/disclosure something that attendees agree to when registering on eventbrite? i was not responsible for my registration / signup this year, so i can't pull from my own experience. |
10:46 |
jeff |
I know it's pretty typical for many conferences (I still get spam and junk mail over a decade later). I just didn't know that this conference was one of those. |
10:46 |
kmlussier |
jeff: In the past, there was a checkbox on the registration form. |
10:54 |
kmlussier |
JBoyer: If the vendors are at the conference, though, they would be able to get the list. But was there a list this year? I didn't see one. |
10:54 |
jeff |
last year the list was sent to attendees as an expiring dropbox link to an xlsx document. |
10:54 |
kmlussier |
My recollection is that the "This list is not to be published..." language was in the footer of every page of the attendee list. Just to make it clear. |
10:55 |
bshum |
dbs: I remember encountering https://bugs.launchpad.net/evergreen/+bug/1681864 when I tested the fixes for i18n in db.seed too. But I found that if I were to remove the resulting PO files (git clean or whatnot since we don't track them) and then rebuild, it would align the expected IDs. Presumably when doing make_release for new tarballs from git, this would approach would work similarly as long as we worked on clean repositories, but if any leftover files |
10:55 |
bshum |
were in the way, then yeah... duplicates |
10:55 |
pinesol_green |
Launchpad bug 1681864 in Evergreen "db-seed.po files need cleanup to remove duplicate IDs from generated localized seed data" [Undecided,Triaged] |
10:55 |
jeff |
this year i've not seen a list or mention of a list, other than the one that is apparently being given to sponsors/exhibitors which you can only partially opt out of. |
10:55 |
jeff |
it's just a little unusual, either a departure from past practices, or more transparency about what was always done in the past and we just didn't know about it. dunno! |
16:44 |
jeff |
oh, hah. |
16:44 |
jeff |
[comment redacted] |
16:59 |
|
mmorgan left #evergreen |
17:01 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
17:02 |
bshum |
dbs++ # new test is successful! so says the test run above :) |
17:08 |
kmlussier |
Yay! |
17:08 |
kmlussier |
dbs++ |
19:54 |
|
genpaku joined #evergreen |
21:35 |
pinesol_green |
[evergreen|Dan Scott] LP#1680624 angular-ui-bootstrap stopped shipping minified files - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=4a068d0> |
21:35 |
pinesol_green |
[evergreen|Dan Scott] LP#1680624 Remove bower packaging bits - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=c66d632> |
21:43 |
dbs |
bshum++ # thanks! |
21:49 |
bshum |
Of course, right after I do that |
21:49 |
bshum |
I think about the automated builder |
21:49 |
bshum |
http://git.evergreen-ils.org/?p=working/random.git;a=shortlog;h=refs/heads/collab/phasefx/wheezy_installer |
21:50 |
bshum |
And the fact that the test run tomorrow needs updating |
21:50 |
dbs |
well that's the random.git one, yeah, I can poke that |
21:50 |
dbs |
really the automated builder should just use the make targets that y'all painstakingly added rather than its own workarounds |
21:50 |
bshum |
+1, for sure |
04:12 |
|
NxT joined #evergreen |
04:13 |
NxT |
Hi all, i'm looking for a guide or info on how to integrate 3M RFID Readers into Evergreen - is this possible? what do i need for this? |
04:36 |
|
rlefaive joined #evergreen |
05:00 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
05:03 |
|
rlefaive joined #evergreen |
06:24 |
|
rlefaive joined #evergreen |
06:40 |
|
rlefaive joined #evergreen |
11:30 |
alynn26 |
gmcharlt++ |
11:30 |
mmorgan |
gmcharlt++ |
11:30 |
mmorgan |
Not too hard, I hope;-) |
11:32 |
Dyrcona |
Heh. Make sure you run your scripts in the correct test database. :) |
11:33 |
Dyrcona |
A missing copy location can cause you problems. |
11:43 |
gmcharlt |
alynn26: miker: bit more to the problem, but webby is now fully back up |
11:45 |
gmcharlt |
er, mmorgan ^^ |
14:05 |
JBoyer |
(provided, of course, that all of the IDL links are accurate and functional) |
14:05 |
jeff |
yeah, and reproducing what we have in Jasper in this case might be as simple as defining a creative new report source in the IDL |
14:05 |
csharp |
JBoyer: I was just thinking about that |
14:05 |
jeff |
i haven't tested, though. |
14:07 |
jeff |
grr. google's index of docs.evergreen-ils.org is out of date, and of course the site's search box uses google... |
14:07 |
jeff |
if only i had a local git repo that i could grep... |
14:07 |
jeff |
oh, wait! |
14:08 |
alynn26 |
@dbs that is what I had to do to fix the ones I had in a very large bucket. |
14:08 |
pinesol_green |
alynn26: As great as you are man, you'll never be greater than yourself. |
14:19 |
dbs |
pinesol_green: I do not like your gender assumptions |
16:22 |
Dyrcona |
I may just wipe it out by hand. |
16:26 |
Dyrcona |
Yeah, think I'll just purge the packages, then delete anything left behind by hand. |
16:26 |
Dyrcona |
Then, I'll link /var/lib/postgresql -> /db before installing the new version. |
16:39 |
Dyrcona |
So, on a test vm were i did a pg upgrade, I cannot now remove postgresql-9.2 after running the delete_old_cluster script. |
16:40 |
Dyrcona |
The package status is BB in aptitude. |
16:41 |
jeff |
presumably you've broken the prerm/postrm scripts' ability to do their jobs. |
16:41 |
jeff |
or just one of the two. |
16:47 |
Dyrcona |
Well, this is a throwaway vm that I made to practice the pg_upgrade process. |
16:47 |
* Dyrcona |
should bet back to actual work. |
16:54 |
Dyrcona |
So, on training, I removed the packages and then deleted the leftover data files. |
17:01 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
17:04 |
|
mmorgan left #evergreen |
17:22 |
berick |
yay, code4lib '18 in DC |
17:24 |
Bmagic |
yep! |
03:45 |
bshum |
As is, running the sync work off lupin for now |
04:09 |
|
rlefaive joined #evergreen |
04:37 |
|
rlefaive joined #evergreen |
05:00 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
05:04 |
|
rlefaive joined #evergreen |
05:31 |
|
rlefaive joined #evergreen |
06:52 |
|
rlefaive joined #evergreen |
08:13 |
|
rlefaive joined #evergreen |
08:41 |
|
rlefaive joined #evergreen |
09:08 |
|
rlefaive joined #evergreen |
09:20 |
dbs |
bshum++ |
09:21 |
dbs |
I applied the Windows 10 Creators Update on my dual-boot laptop last night because I like being up to date even on OSes that I almost never use |
09:22 |
dbs |
And of course it destroyed grub. That Sys Admin IG was timely :) |
09:23 |
dbs |
I did get to test my branch for https://bugs.launchpad.net/evergreen/+bug/1681095 last night and force-pushed a fix |
09:23 |
pinesol_green |
Launchpad bug 1681095 in Evergreen "Extend browser cache-busting support for all stylesheets, JavaScript, and images in default public catalogue" [Undecided,New] |
10:29 |
|
rlefaive joined #evergreen |
10:48 |
|
genpaku joined #evergreen |
16:15 |
|
Jillianne2 joined #evergreen |
16:19 |
dbs |
oh jeff... looks like I beat you home despite leaving 15 hours later than you. delta-- |
16:49 |
|
rlefaive joined #evergreen |
17:00 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
17:17 |
|
rlefaive joined #evergreen |
17:52 |
|
kaffenkj- joined #evergreen |
18:11 |
|
rlefaive joined #evergreen |
00:39 |
|
book` joined #evergreen |
05:01 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
05:36 |
|
remingtron joined #evergreen |
05:36 |
|
dbwells joined #evergreen |
07:07 |
|
rjackson_isl joined #evergreen |
12:33 |
|
jihpringle joined #evergreen |
12:41 |
|
maryj joined #evergreen |
12:43 |
miker |
kmlussier: webstaff collab branch finally sync'd and new stuff pushed |
12:55 |
jihpringle |
frank_guel: one my techs add a © to one of our MARC templates on our 2.12 test server and I'm not seeing any weirdness |
12:56 |
jihpringle |
maybe there something between 2.8 and 2.12 causing the character issue |
12:58 |
frank_guel |
I will try putting a new database without nothing and test |
13:04 |
|
ppound joined #evergreen |
13:07 |
mmorgan |
Is it possible to use copy criteria in an action trigger filter? |
13:08 |
mmorgan |
For example, I want to add "-and" : [ { "target_copy.circ_modifier" :["reserve"] } ] |
13:42 |
frank_guel |
that is the postgresql 9.4.10 config |
13:42 |
frank_guel |
What Do you refer about the environment that you run the staff client in? |
13:43 |
Dyrcona |
OK. That looks OK, but I usually use collation C and character type C. You definitely want UTF-8 encoding in the database. |
13:44 |
frank_guel |
I did a test, and the problem is just with the new marc records |
13:45 |
Dyrcona |
Created from the template? |
13:45 |
frank_guel |
yes, |
13:46 |
Dyrcona |
Was the template originally created in a UTF-8 environment? |
14:51 |
berick |
yes indeed |
14:52 |
Dyrcona |
Might have been nice if the release notes mentioned that. :) |
14:53 |
Dyrcona |
But, anyway. I'm looking at the ebook api and it looks I don't need to run the service unless I enable the api. |
14:55 |
jeffdavis |
Dyrcona: yes, that should be true. Nothing depends on that service except the integration layer in the OPAC (and some live tests I suppose). |
14:55 |
Dyrcona |
jeffdavis: Thanks for confirming. That is what I'm seeing from the code. |
14:56 |
Dyrcona |
I've asked the powers that be if we should enable it, yet, or wait for 3.0. |
14:56 |
Dyrcona |
jeffdavis++ |
15:03 |
pinesol_green |
Dyrcona: The outlook is good. |
15:03 |
Dyrcona |
hah |
15:23 |
|
khuckins__ joined #evergreen |
15:31 |
kmlussier |
Funny, we were just looking at the ebook stuff. |
15:33 |
kmlussier |
jeffdavis: I just set up our test server with our Overdrive credentials. I noticed that if I try to use the Download link from e-items checked out tab, it brings me to https://mlnc1.noblenet.org/eg/opac/myopac/undefined |
15:33 |
kmlussier |
Did I miss a configuration step? |
15:35 |
|
mmorgan joined #evergreen |
15:39 |
jeffdavis |
kmlussier: no, that's a bug |
15:39 |
kmlussier |
OK, I'll file one then. :) |
16:04 |
|
khuckins_ joined #evergreen |
16:12 |
JBoyer |
I'm out until the conference next week, see some of you then! |
16:32 |
|
khuckins__ joined #evergreen |
17:01 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
17:13 |
|
mmorgan left #evergreen |
17:46 |
jeffdavis |
@later tell kmlussier OverDrive download link bug report: https://bugs.launchpad.net/evergreen/+bug/1677813 |
17:46 |
pinesol_green |
jeffdavis: The operation succeeded. |
03:00 |
|
Jillianne joined #evergreen |
04:23 |
|
hawahaniz_ left #evergreen |
05:01 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
06:55 |
|
agoben joined #evergreen |
07:08 |
|
rjackson_isl joined #evergreen |
07:08 |
|
rjackson_isl_ joined #evergreen |
12:31 |
JBoyer |
Thats the hope! |
12:32 |
kmlussier |
Or, even, 2.12.2. No reason to wait for 3.0. :) |
12:32 |
JBoyer |
Well, the hope is that there aren't that many to *be* filed, but you know. |
12:32 |
kmlussier |
JBoyer: I always feel very confident that my thorough testing revealed everything there is to find. And then people start using it in production, and I find out I'm wrong. |
12:33 |
JBoyer |
"But WHY would anyone do THAT?! That's not how any of this works!" |
12:33 |
berick |
JBoyer: vacuum full analyze the whole db? nice |
12:35 |
* berick |
has a few vacuum-full's lined up, expects to recover several hundred GB of disk space |
12:35 |
berick |
after cleaning up copy auditor and anonymizing holds |
12:35 |
JBoyer |
berick, Yeah, that's where all the time will go. I think the db upgrade scripts (minus reingest, of course) only takes a few minutes. I was about to do another test run on our dev server to double check. |
12:36 |
JBoyer |
we keep all of our auditors trimmed (we delete 2 hogsheads a fortnight), and we run circ/hold purges daily. I'm hoping it all goes smoothly. |
12:36 |
berick |
heh |
12:37 |
JBoyer |
I'm reminded though that slony will be the hassle here. Perhaps for the next large upgrade we move to Pg 9.5 and back to the built in sync. |
16:06 |
Dyrcona |
I've been too bogged down in the day to day to keep up with everything. |
16:28 |
|
mmorgan joined #evergreen |
16:33 |
|
khuckins_ joined #evergreen |
17:01 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
17:10 |
|
mmorgan left #evergreen |
17:38 |
|
khuckins joined #evergreen |
18:56 |
|
kenstir joined #evergreen |
19:22 |
jihpringle |
frank_guel: that sounds like a bug to me, I checked our templates which came from 2.10 to 2.12 and we don't have any symbols in our templates so I can't replicate |
19:23 |
frank_guel |
could be an accent or a symbol. |
19:25 |
jihpringle |
our templates are pretty much just lists of blank fields per item type |
19:27 |
frank_guel |
ah ok ok, I did another test, I open the k_book.xml default template, add a word with an accent, and it save it as a weird character, if I open it again and replace the character with the correct word, save the changes and it looks well |
19:28 |
jihpringle |
frank_guel: I'll ask one of our techs to add some accents/symbols to one of our templates and see if we can replicate |
19:30 |
frank_guel |
that sounds great, thanks |
19:30 |
jihpringle |
I'll let you know whether or not we can replicate |
01:25 |
|
StomproJ joined #evergreen |
05:00 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
07:08 |
|
rjackson_isl joined #evergreen |
07:27 |
pinesol_green |
[evergreen|Jane Sandberg] Docs: adding more to the config.tt2 variable list - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=92ebc0a> |
07:31 |
|
agoben joined #evergreen |
07:50 |
|
kmlussier joined #evergreen |
08:09 |
|
Dyrcona joined #evergreen |
15:02 |
|
mmorgan1 joined #evergreen |
15:06 |
bshum |
Lucky cricket. |
15:08 |
|
frank_guel joined #evergreen |
15:09 |
frank_guel |
Hi all, I have a question, I am ussing the 2.12.0EGv in a test server, I am getting the following console error in chrome when I go to the loggin page, "Uncaught Error: Could not load class 'openils.widget.AutoSuggest'. Did you spell the name correctly and use a full path, like 'dijit.form.Button'?" |
15:10 |
frank_guel |
I guess it is not an 2.12.0 error because I am ussing the 2.8.4 version in a production system and it happends too |
15:12 |
kmlussier |
I don't see it, but I don't have Autosuggest enabled. |
15:13 |
kmlussier |
But I just tried another catalog that does use Autosuggest. Yup. I can confirm that the uncaught error does appear in the console. |
15:14 |
kmlussier |
And autosuggest does not work on the login page. |
15:18 |
bshum |
Fwiw, the same error occurs on Firefox too. Autosuggest / dojo unhappiness. |
15:20 |
bshum |
Since we discontinued autosuggest by default with Evergreen 2.6 new installations, I don't think there's been any further movement on it. |
15:31 |
|
Jillianne joined #evergreen |
15:42 |
pinesol_green |
[evergreen|Jane Sandberg] Docs: Web client no longer has borders around patron name - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=c85e457> |
15:48 |
|
jvwoolf joined #evergreen |
15:51 |
|
mmorgan joined #evergreen |
16:07 |
|
khuckins_ joined #evergreen |
16:21 |
|
mmorgan left #evergreen |
17:01 |
pinesol_green |
News from qatests: Test Failure <http://testing.evergreen-ils.org/~live> |
17:09 |
|
khuckins__ joined #evergreen |
20:46 |
|
kenstir joined #evergreen |
21:02 |
kenstir |
Hey hi ho. I have a question about services available to the android app through OSRF. |
03:14 |
|
Callender joined #evergreen |
03:17 |
|
Callender_ joined #evergreen |
03:35 |
|
RBecker joined #evergreen |
05:02 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
12:53 |
|
Dyrcona joined #evergreen |
16:16 |
|
Jillianne joined #evergreen |
16:52 |
|
pinesol_green` joined #evergreen |
17:02 |
pinesol_green` |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
20:16 |
|
kenstir joined #evergreen |
20:34 |
dbs |
heh, bshum, install docs in master still provide instructions for compiling node 0.10.28 from source: http://git.evergreen-ils.org/?p=Evergreen.git;a=blob;f=docs/installation/server_installation.txt;h=539ab85ea1c3037474242e668e5aaa15c8c3028f;hb=refs/heads/master#l154 |
20:44 |
dbs |
Also OpenSRF instructions for Debian websockets install assumes wheezy it seems; directions are for apache 2.2 |
21:22 |
dbs |
and that enabled me to start it, yay |
21:25 |
dbs |
oh yeah, cloud firewall blocking 7682, might as well set up that nginx proxy |
21:28 |
dbs |
haha, had to stop apache2 before installing nginx or else I would get "dpkg: dependency problems prevent configuration of nginx nginx depends on nginx-full" |
21:31 |
bshum |
dbs: Yeah I think csharp already noted that issue for nginx |
21:31 |
bshum |
It should be in the latest OpenSRF master already |
21:31 |
bshum |
Maybe the file hasn't been regenerated for the website |
21:33 |
bshum |
As for master, I guess we could update it to a newer nodejs version. But the note ahead of it also specifies that if you use the developer make target on Jessie, Trusty, or Xenial, you can skip the building from scratch |
21:34 |
bshum |
It's really only for Wheezy that we built from source because the version of nodejs wasn't new enough to do it. Or didn't exist I guess. |
21:34 |
* bshum |
hasn't tested with the latest nodejs, but figure it could be an interesting experiment down the road to try |
21:36 |
bshum |
Hmm, nope, the OpenSRF-2.5.0 readme has csharp's change for reconfiguring the apache ports first, before installing nginx. |
21:36 |
bshum |
Maybe you saw something new dbs |
21:39 |
dbs |
yay webby |
21:39 |
dbs |
(got it working) |
21:40 |
bshum |
dbs: Since you're using the proxy, I might point you in the direction of https://bugs.launchpad.net/evergreen/+bug/1648234 |
21:40 |
pinesol_green |
Launchpad bug 1648234 in Evergreen "Internal Apache port leaks when using proxy" [Medium,Confirmed] |
21:41 |
dbs |
yeah, I had updated the ports in eg.conf but missed ports.conf |
21:41 |
dbs |
there are many ways to get knifed |
21:42 |
bshum |
Yeah I feel like not many have really tested it. |
21:42 |
bshum |
I know I've only setup nginx proxy twice so far. And haproxy only once, unsuccessfully. So more eyes, the better I'm sure. |
21:43 |
dbs |
I've gone through the steps a few times now, but last time was on trusty; this time jessie |
21:47 |
dbs |
and time before that was when we upgraded in September to 2.10, so few and far between |
21:47 |
dbs |
part of my fun this time around was going back and enabling webby after having already installed evergreen |
05:01 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
07:10 |
|
rjackson_isl joined #evergreen |
07:46 |
|
agoben joined #evergreen |
07:50 |
|
Dyrcona joined #evergreen |
08:39 |
pinesol_green |
Launchpad bug 690910 in Evergreen "Apache process spin out of control" [Undecided,Incomplete] https://launchpad.net/bugs/690910 |
08:39 |
Dyrcona |
JBoyer: Yes, I believe it is the Perl code that is ultimately responsible. |
08:39 |
Dyrcona |
Possibly, Perl itself. |
08:40 |
Dyrcona |
I need to do some more testing, but something changes from Perl 5.14 (maybe 5.18) to Perl 5.20 that make DBD::Pg and DBI behave "differently." |
08:41 |
Dyrcona |
Of course, this happened on Debian 7 with Perl 5.14 and Apache 2.2, so that wouldn't be the issue here. |
08:41 |
Dyrcona |
But, still, if someone did a search that tries to return every record.... |
08:48 |
|
mdriscoll joined #evergreen |
11:54 |
Dyrcona |
I tried that once, 15+ years ago....not going back. |
11:55 |
Dyrcona |
yppasswd opensrf .... |
11:55 |
Dyrcona |
Oops.. wrong window :) |
11:56 |
Dyrcona |
This'll be fun...testing a db upgrade in a file image on a USB drive.... |
11:57 |
Dyrcona |
<spongebob_depressed_announcer_voice>Two months later....</spongebob_depressed_announcer_voice> |
11:57 |
jeff |
hah. mostly-quiescent non-production database, ran a vacuum full analyze on it earlier today. shrunk by a few gigs, as you might expect for something that hadn't been vacuumed in a bit and had a bunch of data shuffled around within it. |
11:57 |
jeff |
the "hah" was because i just noticed that it grew by a megabyte since then. :-) |
11:58 |
Dyrcona |
Well, this'll be a pg_upgrade test with production data, freshly restored, so it'll be small as possible. |
11:58 |
Dyrcona |
I tried before with a 600GB image file. It was too smal. |
11:59 |
Dyrcona |
The missing 'l' is somehow appropriate. |
12:03 |
|
jvwoolf joined #evergreen |
15:00 |
rhamby |
which isn't to say I won't do it ...... |
15:05 |
kmlussier |
I missed a lot of these tweets the first time around. |
15:41 |
|
kipd joined #evergreen |
16:35 |
jeffdavis |
hm, I'm getting an error in the web client when I should get an opt-in dialog |
16:35 |
jeffdavis |
2.12 beta, still need to test on 2.12.0 |
17:01 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
17:06 |
|
remingtron joined #evergreen |
20:42 |
|
jvwoolf joined #evergreen |
21:10 |
|
jihpringle_ joined #evergreen |
05:00 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
05:15 |
|
jonadab joined #evergreen |
06:07 |
|
jonadab joined #evergreen |
06:27 |
|
abowling joined #evergreen |
13:30 |
NawJo |
Thank you all for your help, thank you Dyrcona and Berick :) |
13:33 |
Dyrcona |
You can login now? |
13:36 |
NawJo |
Yes, yes :) |
13:37 |
NawJo |
I wrote the rtl stylesheets for web client days ago, and now I want to test them :) |
13:38 |
Dyrcona |
OK. Have fun and thanks for the stylesheets. |
13:38 |
berick |
NawJo++ |
13:39 |
NawJo |
:) thank you all |
16:16 |
Dyrcona |
echo...echo.. echo... My brain can spell, it's just my fingers that can't. |
16:17 |
berick |
just tried for grins, no dice. I also tried exporting TZ before the srfsh line |
16:17 |
* berick |
confirms it's in the osrf message w/ the original command |
16:18 |
gmcharlt |
berick: yep, the TZ should be passsed in |
16:18 |
gmcharlt |
and I've verified in the srfsh log on my test system that the tz is being passed in the request |
16:18 |
gmcharlt |
now checking the cstore side of things |
16:18 |
berick |
gmcharlt++ |
16:19 |
Dyrcona |
OK. I've never mangled the env with pipes much. |
16:19 |
Dyrcona |
It looks...well, weird and wrong. |
16:27 |
* berick |
nods |
16:35 |
|
BAM_ joined #evergreen |
16:39 |
|
kmlussier joined #evergreen |
16:40 |
Dyrcona |
I tested with circulation, so transactions. |
16:40 |
Dyrcona |
I don't think I thought to test it without a transaction. |
16:41 |
Dyrcona |
"I don't think I thought..." heh.... |
16:41 |
gmcharlt |
friends don't let friends do circulation transactions outside of transactions |
16:41 |
Dyrcona |
:) |
16:53 |
bshum |
Leading to a bad video |
16:53 |
bshum |
But, hey, fun! |
16:53 |
bshum |
:D |
17:01 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
17:08 |
|
mmorgan joined #evergreen |
17:14 |
|
mmorgan left #evergreen |
17:29 |
|
jvwoolf left #evergreen |
21:41 |
bshum |
Oh special. |
21:41 |
bshum |
https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1659801 |
21:41 |
pinesol_green |
Launchpad bug 1659801 in ejabberd (Ubuntu) "apparmor rules block ejabberdctl" [Undecided,New] |
21:41 |
bshum |
Just came across this segmentation error on Ubuntu 16.04 dry run while trying to run through ejabberd user registration :\ |
21:41 |
bshum |
Ruined my asciinema recording, bah |
21:42 |
bshum |
Guess I'll have to try it all over again |
21:43 |
* bshum |
blows away his VM to test anew |
21:49 |
* bshum |
considers making the recording on Trusty instead |
21:50 |
bshum |
Or Debian... *shudders* |
23:05 |
Dyrcona |
I have not encountered that one, but I always start ejabberdctl with sudo. |
23:06 |
bshum |
I ran it as root |
23:06 |
bshum |
And got that error |
02:18 |
|
dbwells_ joined #evergreen |
04:46 |
|
gsams joined #evergreen |
04:55 |
|
gsams joined #evergreen |
05:02 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
06:40 |
|
rlefaive joined #evergreen |
06:53 |
|
agoben joined #evergreen |
07:12 |
|
rjackson_isl joined #evergreen |
10:36 |
kmlussier |
If we do keep it, though, I agree with Dyrcona that we might want to name it .next so that we don't need to rename it every time we make a big jump in release numbers. |
10:36 |
berick |
i guess the rule is when you add a pullrequest for a wishlist/feature bug, you have to set a milestone of 'next' or it will likley be ignored ? |
10:36 |
berick |
yes, definitely needs renaming |
10:38 |
kmlussier |
berick: I've always followed that rule when submitting my own code because I was told it would be more likely to get attention if it was targeted. In general, when looking for code to test, I usually just look for the pullrequest tag. |
10:39 |
bshum |
One of the old ideas was to rename 2.next into 2.actualnumber-alpha but that got tiresome to keep reshuffling bugs away from the actual milestones. So we ended up leaving 2.next as is as a general placeholder to target future dev |
10:40 |
bshum |
I'd prefer to keep a target around for next dev just cause I do find that untargeted bugs can easily get lost in the mire of open tickets depending on how you set your search scopes |
10:40 |
berick |
kmlussier: same here, i just look for the tag |
10:42 |
kmlussier |
Overall, I think it would be good practice to try to go through all those bugs with pullrequest tags, merge the ones that are ready, and actively remove the pullrequest tags, possibly adding a needsrepatch tag, for ones that aren't ready. |
10:42 |
kmlussier |
But now I'm living in the land of dreams. |
10:43 |
kmlussier |
I do find that many of the bugs that sit without a pullrequest tag are there because we're reluctant to remove the pullrequest if it's not ready or needs a test. |
10:43 |
kmlussier |
OK, now I'm just talking gibberish. /s/without/with |
10:45 |
berick |
that's consistent w/ my lp-world view |
10:46 |
berick |
pullrequest means merge me as soon as possible, if I don't have a milestone, put me in master. |
10:46 |
* berick |
is not pushing for anything, just like knowing how people work |
11:05 |
berick |
as to me they are the same thing |
11:05 |
bshum |
As long as bugs get worked on, I think that's the key goal :D |
11:06 |
berick |
very diplomatic ;) |
11:06 |
bshum |
gmcharlt: Speaking of, sorry I saw your question... but got distracted, lol. So uh, my answer is maybe |
11:06 |
bshum |
gmcharlt: I didn't get to play with it directly myself yet |
11:06 |
bshum |
But I'm always happy to test and merge stuff that people push my way |
11:07 |
kmlussier |
Yeah, if I were proposing anything, it's probably that bugs get worked on. :) I know core committers are busy, but one or two bugs a month seems reasonable to me. |
11:30 |
csharp |
gmcharlt: I'll take a look |
11:33 |
gmcharlt |
csharp: great! |
15:08 |
berick |
booting_up_the_thunderdome++ |
15:09 |
berick |
(it runs on windows 98) |
15:09 |
csharp |
https://www.youtube.com/watch?v=tajDxBaPBBM |
15:09 |
berick |
you've got mail! |
15:10 |
|
kmlussier joined #evergreen |
15:11 |
berick |
miker: another thought, assuming a non-hatch version of offline is viable, starting there lowers the barrier to entry for broader testing. |
15:12 |
miker |
it does, certainly. (sans printing stuff above) |
15:36 |
|
hbrennan joined #evergreen |
15:39 |
|
Jillianne joined #evergreen |
15:40 |
Dyrcona |
gmcharlt | csharp: https://bugs.launchpad.net/evergreen/+bug/1669868/comments/9 |
15:40 |
pinesol_green |
Launchpad bug 1669868 in Evergreen ""make check" failure" [High,Confirmed] |
15:40 |
Dyrcona |
I developed that on Ubuntu 16.04. I'll test on wheezy, jessie, and trusty next. |
15:41 |
gmcharlt |
Dyrcona: thanks |
15:48 |
Dyrcona |
Works for me on jessie. |
15:51 |
Dyrcona |
Works on wheezy. |
16:27 |
|
mmorgan joined #evergreen |
16:52 |
bshum |
Taco time :) See you guys later... |
17:00 |
Dyrcona |
I ..am.. outta here! |
17:00 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
17:09 |
|
mmorgan left #evergreen |
17:10 |
|
khuckins joined #evergreen |
17:11 |
* kmlussier |
heads out to get pizza. |
05:01 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
07:05 |
|
NawJo joined #evergreen |
07:22 |
|
rjackson_isl joined #evergreen |
07:54 |
|
collum joined #evergreen |
09:51 |
* Dyrcona |
thinks his initial assessment of a "bug" might be wrong. |
10:00 |
Dyrcona |
Just doing this: "select distinct * from biblio.record_entry where not deleted" and print the marc field from the result leads to memory starvation. |
10:01 |
Dyrcona |
That is more or less the query if you do marc_export -a with no other selection options. |
10:02 |
Dyrcona |
I don't believe the starvation happened on Wheezy or Trusty. I can build a vm on one of those later to test it. |
10:02 |
|
mmorgan1 joined #evergreen |
10:06 |
jeff |
Dyrcona: in your test case above, you're still using perl + dbi, or do you have that issue even executing the query via psql? |
10:06 |
Dyrcona |
jeff: That is Perl + DBI. |
10:06 |
jeff |
Dyrcona: and, which distros have you encountered the issue on? |
10:06 |
Dyrcona |
This is Debian 8 Jessie. I've seen similar on Ubuntu 16.04, but has not tested this specific script. |
10:07 |
Dyrcona |
I'm doing it without the distinct to see if that makes a difference. |
10:07 |
Dyrcona |
Also, it's important to note that we have approximately 2.7 million bibs that are not deleted. |
10:07 |
* jeff |
nods |
10:41 |
Dyrcona |
Yes, understood. And cursors are so 20th century.... :) |
10:43 |
Dyrcona |
I don't think it's a question of the amount of RAM changing. I believe the server that I used to run this on had 8GB, and I've run it on a vm with 8GB with similar results. |
10:43 |
Dyrcona |
Similar results meaning it crashes. |
10:43 |
jeff |
Yeah, I was about to suggest re-testing to see if you can reproduce on older distro with this same dataset. |
10:44 |
jeff |
But at this point, that's probably mostly to satisfy curiosity. |
10:44 |
jeff |
grabbing a configurable chunk of bibs at a time will probably be the fix. |
10:44 |
jeff |
default to 10k or 50k or whatever testing shows to use a semi-reasonable amount of ram. |
10:45 |
jeff |
which version of perl are you running on the problematic system? |
10:46 |
|
Christineb joined #evergreen |
10:47 |
jeff |
oh. jessie, therefore 5.20.2 |
10:59 |
Dyrcona |
Xenial is 5.22.something |
11:00 |
jeff |
https://rt.cpan.org/Public/Bug/Display.html?id=93266 is the DBD::Pg bug for fixing this long-term, which also isn't immediately useful. |
11:06 |
Dyrcona |
Right. |
11:06 |
Dyrcona |
I'm going to build some 8GB VMS with different distros: Wheezy, Jessie, Trusty, and Xenial to test this. |
11:07 |
Dyrcona |
Mabye not today, but soon. |
11:07 |
Dyrcona |
I may have a non-issue. :) |
11:20 |
|
fbeaudry joined #evergreen |
16:19 |
|
eady joined #evergreen |
16:20 |
|
rlefaive joined #evergreen |
16:29 |
|
kmlussier joined #evergreen |
17:01 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
17:05 |
|
mmorgan left #evergreen |
23:20 |
|
genpaku joined #evergreen |
05:01 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
06:53 |
|
agoben joined #evergreen |
07:10 |
|
rjackson_isl joined #evergreen |
07:30 |
graced |
Happy St. Patrick's Day , #evergreen! |
15:51 |
kmlussier |
Actually, it makes sense. The ones that don't have covers in the feed also don't have them in the regular catalog. |
15:52 |
Dyrcona |
Ah ha! |
15:53 |
* Dyrcona |
learned something: The action.hold_notification is created by the cleanup routine on the action trigger runner, but that still doesn't tell me why it failed on Monday. |
15:56 |
* kmlussier |
looks longingly at bug 1236979, which retrieved that feed so much more quickly, but was not quite right in testing. |
15:56 |
pinesol_green |
Launchpad bug 1236979 in Evergreen "Speed up bibs-by-item-age" [Medium,Confirmed] https://launchpad.net/bugs/1236979 - Assigned to Galen Charlton (gmc) |
15:57 |
kmlussier |
Oh! I hadn't noticed gmcharlt's name on that one. |
15:57 |
StomproJ |
Dyrcona, I just tried it out and ISBN lookup does still work for /ac/jacket/small/ISBN It just won't handle records with ISSN/UPC. |
16:49 |
mmorgan |
[% END %] |
16:49 |
mmorgan |
terran++ |
16:57 |
kmlussier |
terran++ |
17:01 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
17:07 |
|
mmorgan left #evergreen |
16:55 |
remingtron |
frank_guel: you may need to view that record in your Evergreen staff client and use the "Clear AddedContent Cache" link on the right sidebar |
16:57 |
remingtron |
frank_guel: here is the documentation for this feature, in case it helps: http://docs.evergreen-ils.org/2.11/_including_external_content_in_your_public_interface.html#_clear_external_added_content_cache |
16:59 |
frank_guel |
remingtron: at IPICYT we are still on 2.8.4 EG version, so there is no the Clear addedContent cache option, |
17:00 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
17:05 |
remingtron |
frank_guel: Okay. It looks like this feature was added in 2.9: https://bugs.launchpad.net/evergreen/+bug/1435938 |
17:05 |
pinesol_green |
Launchpad bug 1435938 in Evergreen "New Feature: Allow Staff to clear Added Content cache" [Wishlist,Fix released] |
17:06 |
|
Jillianne2 joined #evergreen |
18:02 |
dbwells |
gmcharlt++ |
18:08 |
gmcharlt |
also, I have created LP milestones for _both_ 2.12.0 and 2.12.1 and divvied up the unfixed bugs that were assigned to 2.12-rc |
18:10 |
gmcharlt |
I was conservative in how I did that: if it wasn't something that visibly affected installation on one or more platforms or caused a lot of JS console spewage, I bumped it to 2.12.1 rather than 2.12.0 |
18:21 |
frank_guel |
remingtron: thanks for your help. It let me understand how it works. |
18:22 |
frank_guel |
As a part of the 2.11.3 EG update testing, I already install EG and it looks working well on opac, but I am getting this message when I want to access to staff client: XML Parsing Error: undefined entity Location: chrome://open_ils_staff_client/content/main/main.xul Line Number 21, Column 1:<window id="main_win" ^ |
18:34 |
dbs |
frank_guel: if you want to remove the cached images right away, you can do something like 'memcrm --servers=localhost ac.jacket.small.0471828726' |
18:34 |
dbs |
(repeating for medium, large in place of small) |
18:35 |
dbs |
memcdump --servers=localhost | grep ac.jacket.large # will show you all of the keys for cached large jackets |
20:04 |
* bshum |
should start writing stuff like this down |
20:04 |
bshum |
For said talk :) |
20:06 |
frank_guel |
thanks , it works, bshum |
20:07 |
bshum |
I'm not sure why the built clients don't have the right content in them. gmcharlt should check his install directory to see what's where. On my test system when I build all the locales, lang.dtd looks fine. And we only just branched rel_2_12 today, so I would have thought the new 2.12-rc client should be fine too. |
20:08 |
bshum |
frank_guel++ Thanks for checking that out for us! |
20:09 |
frank_guel |
:) |
20:09 |
* bshum |
feels like Bmagic encountered this error recently too, but we just weren't sure what we were looking at then; check above for details if you still want Spanish :) |
20:10 |
gmcharlt |
I'll look at it tomorrow |