| 04:31 |
pinesol_green |
News from qatests: Test Failure <http://testing.evergreen-ils.org/~live> |
| 06:40 |
|
rlefaive joined #evergreen |
| 07:15 |
|
agoben joined #evergreen |
| 07:15 |
|
rjackson_isl joined #evergreen |
| 14:17 |
bshum |
I think if you don't pass that argument for the next client you build, you could end an update line |
| 14:17 |
bshum |
Or I have done that by accident before.. |
| 14:17 |
* bshum |
whistles innocently |
| 14:18 |
bos20k |
So, if you are running a client that is pointing at production.domain.com, it will only ever look there. Even if you try to log in to testing.domain.com it will not see the updates sitting on testing.domain.com? |
| 14:18 |
Dyrcona |
It's set at configure time. --with-autoupdates-host= |
| 14:18 |
bshum |
Right, you would need to build a different client to point at auto-updates elsewhere I would think. |
| 14:18 |
Dyrcona |
Yes, that is my understanding. |
| 14:19 |
bos20k |
Ok, just want to make sure that was correct. |
| 14:19 |
jeffdavis |
The autoupdate hostname is saved in the defaults/preferences/autoupdate.js file in your copy of the client, so you can edit that for testing purposes too. |
| 14:19 |
bos20k |
Otherwise I'm doing something wrong on my testing setup since the production client doesn't want to update from the testing server. |
| 14:19 |
bshum |
Yeah, but... the files on the server side have to be able to upgrade from X to Y version. So that sounds messy to me jeffdavis |
| 14:20 |
bshum |
I mean you could copy production XUL and let the test server build on top of it |
| 14:20 |
bshum |
But yuck |
| 14:20 |
Dyrcona |
I always build custom clients for testing, often with a different app name to store preferences in a different place. |
| 14:20 |
jeffdavis |
That's what we do during pre-upgrade testing. |
| 14:20 |
Dyrcona |
just use the web staff client? :) |
| 14:20 |
bos20k |
:) Soon enough... |
| 14:21 |
bos20k |
Thanks everyone |
| 14:21 |
Dyrcona |
bos20k: you know about the manualupdates.html page, right? |
| 14:22 |
bos20k |
Dyrcona: yes, I was just trying to test the auto update stuff. Will do it a different way that should work. |
| 14:22 |
Dyrcona |
OK. |
| 14:22 |
Dyrcona |
In my experience auto updates work on Windows, but not Linux. |
| 14:22 |
jeffdavis |
^ To be clear, "that's what we do" = copy existing updates from production to our upgrade testing server, build the client on the test server with autoupdate_host set to our production URL, manually edit the autoupdate.js file to point at the test server for testing purposes, and copy the new updates from the test server back to production during the upgrade proper. |
| 14:23 |
jeffdavis |
Cumbersome, but works for us. (And yeah, web client will be nice!) |
| 14:23 |
bshum |
jeffdavis: That makes more sense to me. I didn't think diverging prod / test without copying something would work cleanly |
| 14:23 |
bshum |
jeffdavis++ # satisfying my curiousity :D |
| 14:24 |
Dyrcona |
I'd set the autoupdate host on the testing server at configure time and save a step or two. |
| 14:24 |
jeffdavis |
Dyrcona: well, we want to test the actual client that we make available to our libraries, and we want that client to have the production autoupdate_host built-in. |
| 14:25 |
Dyrcona |
But, I also would build everything fresh again on production proper. :) |
| 14:25 |
jeffdavis |
We have libraries that want the new client available to install several weeks in advance of the upgrade. |
| 14:26 |
jeffdavis |
Building on prod would be preferable for me, but not possible in that case, alas. :) |
| 14:26 |
Dyrcona |
See, I'd just tell them No, but I can be a jerk like that. :) |
| 14:27 |
Dyrcona |
j/k |
| 14:27 |
bshum |
I think ever since like 2.7, I stopped paying attention to XUL stuff, since it's basically been frozen |
| 14:27 |
bshum |
All that extra testing sounds boring when nothing is supposed to be different :) |
| 14:28 |
bshum |
But yay, testing |
| 15:13 |
bos20k |
I changed the hostname in autoupdate.js but it still says there is no update... |
| 15:14 |
jeffdavis |
Does your test server have a valid SSL certificate? |
| 15:14 |
|
rjackson_isl_ joined #evergreen |
| 15:15 |
bos20k |
jeffdavis: yes, it does |
| 15:15 |
bos20k |
I also tried changing https:// to http:// in autoupdate.js but that didn't make a difference either. |
| 15:28 |
Dyrcona |
bos20k: You can always do make updates-client again to be sure. |
| 15:28 |
bshum |
I wonder if it does matter what you name the thing |
| 15:29 |
bos20k |
Dyrcona: That has been done many times. |
| 15:29 |
bshum |
https://developer.mozilla.org/en-US/docs/Toolkit_version_format gets linked to from old https://wiki.evergreen-ils.org/doku.php?id=mozilla-devel:deploying_automatic_updates |
| 15:30 |
bshum |
and that talks about version numbering |
| 15:30 |
bshum |
Maybe it doesn't think biblio_2_12 is newer ? |
| 15:30 |
* bshum |
hasn't really tested |
| 15:31 |
bshum |
I mean I haven't tested words ahead of the numbers |
| 15:31 |
bshum |
The doc seems to say numbers, then letters |
| 15:31 |
bshum |
2.2.0mvlc.0 from the wiki |
| 15:31 |
bshum |
I'm really just spitballing and guessing; I don't know |
| 15:32 |
bos20k |
Hmmm, well, the default name is rel_2_12_3 I will try that next. If that doesn't work I will try just 2_12_3 |
| 15:33 |
bos20k |
Or maybe even 2.12_3... |
| 15:34 |
Dyrcona |
bos20k: The stamp id is not the version number. I skip stamp id and specify STAFF_CLIENT_VERSION when building. |
| 15:35 |
Dyrcona |
I'd have to check again how the version is determined from the STAMP_ID. |
| 15:36 |
Dyrcona |
bos20k: Probably. |
| 15:36 |
Dyrcona |
I believe the version needs to begin with digits or it gets confused, and use dots, not underscores for best results. |
| 15:39 |
bos20k |
Yup, don't mess with STAFF_CLIENT_STAMP_ID... It offers to update now. Now to clean up my mess and test the procedure again. |
| 15:40 |
bos20k |
Thanks again! |
| 16:31 |
pinesol_green |
News from qatests: Test Failure <http://testing.evergreen-ils.org/~live> |
| 16:38 |
|
maryj joined #evergreen |
| 17:07 |
|
mmorgan left #evergreen |
| 01:36 |
|
BigRig joined #evergreen |
| 01:37 |
|
mnsri_ joined #evergreen |
| 01:39 |
|
abneiman joined #evergreen |
| 04:31 |
pinesol_green |
News from qatests: Test Failure <http://testing.evergreen-ils.org/~live> |
| 05:27 |
|
pinesol_green` joined #evergreen |
| 05:28 |
|
Bmagic_ joined #evergreen |
| 05:29 |
|
jeffdavi1 joined #evergreen |
| 10:13 |
Dyrcona |
Plus, it's easier to cherry-pick all of the commits and sign them all at once. :) |
| 10:14 |
Dyrcona |
I should see the fifth element. |
| 10:15 |
|
frank___ joined #evergreen |
| 10:15 |
frank___ |
Hi all, I am still trying to upgrade from 2.8.4 to 2.12.3, (from one sorver to another too), all the migration is fine, but when I test creating a marc record something weird hapends, for example, If I create/import a new record with this "©" character, it is saved in the database with an strange character "�", but if I re-open the same marc record register, and replace the character with the correct one it is saved correctl |
| 10:16 |
bshum |
Dyrcona: WHAT? You haven't seen the Fifth Element?! |
| 10:16 |
Dyrcona |
No, I have not, just bits and pieces. |
| 10:17 |
|
Freddy_Enrique joined #evergreen |
| 10:30 |
Dyrcona |
You could try that and see if it works better with a new record. |
| 10:30 |
frank___ |
ok, let me try |
| 10:33 |
Dyrcona |
phasefx++ gmcharlt++ |
| 10:35 |
abneiman |
Dyrcona++ for 1208875 test -- will make lots of people happy! |
| 10:51 |
dbs |
frank___: that sounds very familiar, I think we fought a similar battle when we upgraded to 2.9 or 2.10 (lots of French in use here)... I'll try to look at my notes about that |
| 10:52 |
dbs |
frank___: but check first to be 100% sure that your MARC record templates are correctly saved in UTF8 encoding |
| 10:52 |
dbs |
(our battle had more to do with MARC record copy catalogying from Z39.50 I think) |
| 16:12 |
* dbs |
does not enjoy reliving last September |
| 16:21 |
|
b_bonner joined #evergreen |
| 16:27 |
frank___ |
dbs: let me try |
| 16:31 |
pinesol_green |
News from qatests: Test Failure <http://testing.evergreen-ils.org/~live> |
| 16:34 |
|
jwoodard joined #evergreen |
| 16:35 |
frank___ |
dbs: It works |
| 16:35 |
frank___ |
excellent |
| 05:01 |
pinesol_green |
News from qatests: Test Failure <http://testing.evergreen-ils.org/~live> |
| 07:09 |
|
rjackson_isl joined #evergreen |
| 07:27 |
|
rlefaive joined #evergreen |
| 07:31 |
|
JBoyer joined #evergreen |
| 13:19 |
jonadab |
Ah. I was thinking more deletions than additions usually means the code got easier to maintain. |
| 13:20 |
Dyrcona |
Well, it did, since these files are separate from the others. |
| 13:20 |
Dyrcona |
Most of these are one shots, too. |
| 13:43 |
jeff |
has anyone here written tests (pgtap or other) for circ policies? |
| 13:44 |
jeff |
"if i check this item out to this patron it should go out for this long / with this rule? even if you were just testing circ matrix matchpoints exclusively to start... |
| 13:45 |
Dyrcona |
No, but I have used the database functions to check that certain rules are working as expected. |
| 13:47 |
jeff |
Dyrcona: for your syrup install(s), are staff logging into syrup with their evergreen credentials, or are you setting a password for each syrup-using staff member in syrup itself? |
| 13:47 |
Dyrcona |
jeff: I think they're using their evergreen credentials, but I wasn't here for the initial setup. |
| 13:47 |
JBoyer |
I don't know if I understand databases anymore. I take a query with 7 inner joins and 12 outer, add *9 more* outer joins and exec time goes from 184 seconds to 41. Consistently (+- a couple seconds; it's not caching that helps). |
| 13:48 |
Dyrcona |
JBoyer: The magic of indexes.... :) |
| 13:48 |
JBoyer |
jeff, I haven't written circ policy tests, but it seems like it would take significant setup to actually test properly. |
| 13:49 |
jeff |
JBoyer: could be that one or all of the additional joins are forcing the planner to make a decision it wouldn't normally make -- and it ends up being a better decision after all! |
| 13:49 |
JBoyer |
I suppose I should throw a couple EXPLAINs at it, that should make for some interesting reading... |
| 13:50 |
JBoyer |
jeff, Oh, re: policy testing, are you thinking just some tests that you can run against your own real data to make sure things work the way you expect? |
| 13:50 |
jeff |
JBoyer: right. |
| 13:50 |
Dyrcona |
I'm looking through some of my old stuff to see what I've got. |
| 13:51 |
JBoyer |
That does sound interesting. |
| 13:52 |
JBoyer |
Dyrcona, Sure, but it has a built in reminder to update the check to reflect the new policy. ;) |
| 13:52 |
Dyrcona |
heh |
| 13:53 |
Dyrcona |
IIRC, I mostly ran stuff in the database with the find_circ_matrix_matchpoint and related functions. |
| 13:56 |
jeff |
and for the exhaustive test, you just join actor.usr with asset.copy and actor.org_unit... |
| 13:59 |
Dyrcona |
heh |
| 13:59 |
Dyrcona |
Well, you basically need some representative transactions where you know what the outcome should be ahead of time....but you knew that. |
| 13:59 |
* jeff |
nods |
| 16:25 |
Dyrcona |
Oh. I think I may have copied the wrong apache2.conf for websockets. |
| 16:26 |
Dyrcona |
Looks like I got the Apache 2.2 version and this host is running apache 2.4. |
| 16:29 |
Dyrcona |
Yeap. |
| 16:31 |
pinesol_green |
News from qatests: Test Failure <http://testing.evergreen-ils.org/~live> |
| 16:58 |
|
frank_guel joined #evergreen |
| 16:59 |
|
frank_guel joined #evergreen |
| 17:03 |
frank_guel |
Hi all, I am still trying to upgrade from 2.8.4 to 2.12.3, (from one sorver to another too), all the migration is fine, but when I test creating a marc record something weird hapends, for example, If I create/import a new record with this "©" character, it is saved in the database with an strange character "�", but if I re-open the same marc record register, and replace the character with the correct one it is saved correc |
| 17:04 |
frank_guel |
I tested in two diferent server and is the same, |
| 17:06 |
|
mmorgan left #evergreen |
| 17:58 |
|
Freddy_Enrique joined #evergreen |
| 18:05 |
|
Freddy_Enrique joined #evergreen |
| 04:30 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 07:14 |
|
rjackson_isl joined #evergreen |
| 07:31 |
|
agoben joined #evergreen |
| 07:38 |
|
Dyrcona joined #evergreen |
| 09:35 |
|
yboston joined #evergreen |
| 09:59 |
Dyrcona |
Yeap, grunt all blows up on me again on a fresh install on Ubuntu Xenial. This time I'm installing rel_2_12 with no customizations. |
| 10:02 |
Dyrcona |
I can try again with a fresh Debian 8. |
| 10:02 |
JBoyer |
Dyrcona, Not that I think this is a good thing to do full time, but if you just do a grunt build does it work? (i.e. skipping the test) |
| 10:02 |
Dyrcona |
I am installing the developer prereqs and not building node from source. |
| 10:02 |
Dyrcona |
JBoyer: I'll try that. It does look like a test that's failing. |
| 10:03 |
csharp |
npm feels fragile to me - kinda like ruby gems |
| 10:03 |
Dyrcona |
The build "succeeds" with this message from cssmin:combine : |
| 10:03 |
Dyrcona |
>> Destination not written because minified CSS was empty. |
| 10:04 |
csharp |
or even CPAN, though that's been more consistently stable than I've seen the other two be |
| 10:04 |
Dyrcona |
csharp: Node feels fragile to me, not just npm, worse than ruby gems. |
| 10:04 |
JBoyer |
I think the last time I was having issues with grunt test it was something of ours, but it's been a minute. |
| 10:05 |
Dyrcona |
I get that same reference error from yesterday. |
| 10:08 |
Dyrcona |
Hmm... Something isn't getting loaded in the tests, I assum. |
| 10:08 |
Dyrcona |
Assume, even. |
| 10:09 |
JBoyer |
It's ok, dropping the e in Assumr would be hipster, but dropping the e from Assum is tres Unix. |
| 10:09 |
Dyrcona |
It's complaining about the angular.module() line at the top of services/core.js. |
| 11:03 |
Dyrcona |
It might. I don't remember. |
| 11:04 |
berick |
Bmagic: a copy does not have to pass action.hold_request_permit_test to appear in the hold_copy_map. |
| 11:04 |
Bmagic |
i see |
| 11:05 |
berick |
only directly targeted (or op-captured) copies have to pass the test |
| 11:06 |
Bmagic |
I think we are getting warm |
| 11:06 |
Bmagic |
mmorgan: no penalties |
| 11:11 |
pinesol_green |
[evergreen|Jason Etheridge] lp1653998 webstaff redirect to login page - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=518023b> |
| 15:33 |
jeffdavis |
If you have older records with old-style Overdrive URIs you don't need the 037. |
| 15:33 |
hbrennan |
We have the option of importing the MARC Express records to get caught up, and I haven't looked closely at them yet |
| 15:43 |
|
jihpringle joined #evergreen |
| 16:31 |
pinesol_green |
News from qatests: Test Failure <http://testing.evergreen-ils.org/~live> |
| 16:40 |
Dyrcona |
And, just like that: 92,811 lines of code written... |
| 16:40 |
Dyrcona |
emacs++ |
| 16:41 |
* berick |
chuckles |
| 16:42 |
* Dyrcona |
just mangled a spreadsheet into a ridiculous number of SQL inserts. :) |
| 16:43 |
Dyrcona |
About 5 lines for each insert. |
| 16:45 |
|
dbwells joined #evergreen |
| 16:50 |
jeff |
live test failure does not at first glance appear to be a transient one, nor does it seem to be what Dyrcona ran into recently. commit 518023b might need some followup. |
| 16:50 |
pinesol_green |
jeff: [evergreen|Jason Etheridge] lp1653998 webstaff redirect to login page - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=518023b> |
| 16:50 |
jeff |
"Unknown provider: $routeProvider" |
| 16:56 |
Dyrcona |
Ah.. this just went in this afternoon. |
| 01:57 |
* bshum |
will look at it more tomorrow |
| 02:01 |
jeffdavis |
bshum++ |
| 03:12 |
|
RBecker joined #evergreen |
| 04:30 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 07:06 |
|
rjackson_isl joined #evergreen |
| 07:28 |
csharp |
~~ |
| 07:28 |
csharp |
 |
| 09:19 |
|
jvwoolf joined #evergreen |
| 09:23 |
|
yboston joined #evergreen |
| 09:30 |
|
maryj joined #evergreen |
| 10:26 |
bshum |
So it looks like there are three PO templates that are failing to import |
| 10:26 |
bshum |
Two of them appear to be tests |
| 10:27 |
bshum |
build/i18n/tests/data/sql2pot.pot |
| 10:27 |
bshum |
and build/i18n/tests/data/testidl.pot |
| 10:27 |
bshum |
Both of them are dying cause of a missing end qoute on line 6 where the timestamp should be, I guess. |
| 10:28 |
bshum |
I'm not really sure we should worry about these, given that they appear to be really ancient test files for PO Templates, but maybe we should either fix the line, or get rid of the file altogether if they no longer serve a purpose. |
| 10:29 |
bshum |
The other one that appears to be broken is build/i18n/po/multiclass_search_help.html/multiclass_search_help.html.pot |
| 10:29 |
bshum |
Which seems to be pulling the entire HTML in, instead of finding any specific strings |
| 10:29 |
bshum |
And it's choking cause it's expecting a PO template, not raw HTML |
| 10:31 |
bshum |
Since multiclass_search_help.html is part of the XUL server files, I'm not sure if we shouldn't also deprecate that and remove the offending POT and POs that can't be translated anyways |
| 10:35 |
Dyrcona |
I'm still working on setting up Syrup on an alternate host, and I really have no idea what I'm doing. The README is really short on details and seems to assume that you know Django and otherwise know what you're doing. |
| 10:35 |
Dyrcona |
Do I just have to change the settings in localsettings.py and it will just work? For some reason, I doubt that. |
| 10:36 |
jeff |
yep! my experience was similar, though possibly with an AM/PM inversion! |
| 10:42 |
Dyrcona |
So, I have to run the manage.py script in each instance... OK. |
| 10:43 |
Dyrcona |
The vm has a non-routing IP address. It's only visible at central site or via vpn. |
| 10:44 |
jeff |
assuming you're starting with Django 1.4.x, all of the top-level DATABASE_* settings in local_settings.py.example should be commented out, and you should use the example DATABASES= hash to set the various settings. |
| 10:44 |
dbs |
bshum: I think the POT tests are still useful. Looks like there is a small delta required for one or two of the tests to still pass. |
| 10:44 |
bshum |
dbs: Yeah I was just wondering if we run them as part of the nightly test |
| 10:44 |
jeff |
under DATABASES[default], i set ENGINE, NAME, USER, PASSWORD, HOST, and PORT |
| 10:45 |
Dyrcona |
jeff: Yes. I've copied everything from production and just modified the values. |
| 10:45 |
bshum |
dbs: Well, daily I guess. |
| 10:45 |
jeff |
for postgres, i used 'ENGINE': 'django.db.backends.postgresql_psycopg2' |
| 10:45 |
Dyrcona |
jeff: ditto. :) |
| 10:45 |
bshum |
I kind of wish there was a way of excluding the tests from going to LP translations though. |
| 10:45 |
jeff |
Dyrcona: ah! then you're at least starting from a working install, which is possibly better off than starting from scratch! |
| 10:45 |
Dyrcona |
Could be. :) |
| 10:46 |
Dyrcona |
I'm changing the db and the evergreen instance that it talks to. |
| 10:48 |
dbs |
bshum: might have been under buildbot? doubt it for the live reporter though |
| 10:48 |
bshum |
dbs: That's kind of what I figured |
| 10:49 |
dbs |
bshum: if launchpad is purely filename-based, we could do a workaround like having the setup / teardown rename a file from blah.pot.example to blah.pot for the test, then rename it back |
| 10:49 |
bshum |
dbs: Yeah it seems to be targeting only things with .po or .pot |
| 10:50 |
dbs |
testIDL and testSQL just need a single space removed from their POT test file to make their tests pass |
| 10:51 |
bshum |
Alternatively, we could create a different repo for translations right? And only sync that stuff against master or whatnot for the files we specify to target for translation efforts |
| 10:51 |
bshum |
Or do we want to keep everything as bound together as we can |
| 10:51 |
bshum |
(thinking ahead to when we replace LP translations) |
| 10:56 |
* bshum |
reads about Koha's thoughts on that in https://wiki.koha-community.org/wiki/Git_Splitting_and_Shrinking |
| 10:58 |
bshum |
I guess they keep their POs as part of their main code still |
| 10:58 |
* bshum |
ponders that further |
| 10:58 |
dbs |
user/dbs/tiny_i18n_test_fix working branch has fixes for two of the i18n tests that were failing on my Fedora 25 machine |
| 10:58 |
dbs |
to test: cd build/i18n; python tests/testIDL.py; python tests/testSQL.py |
| 10:59 |
* dbs |
returns to prepping for Senate meeting |
| 11:00 |
bshum |
dbs++ # thanks |
| 11:26 |
Dyrcona |
jeff: Should I do manage.py syncdb or manage.py migrate? |
| 11:27 |
jeff |
syncdb in this case. |
| 15:03 |
eeevil |
but, best to get rid of shapers on safe networks in any case |
| 15:03 |
berick |
right, ok, bundling gets us back to multiple osrf blobs per message for tightly packed stuff |
| 15:03 |
eeevil |
right |
| 15:03 |
berick |
yes, agreed, i'm testing no-shapers now |
| 15:11 |
Dyrcona |
That grunt all error didn't happen on a Debian 7 server with a similar, but not identical branch. |
| 15:12 |
Dyrcona |
One big difference: The Debian 7 server had the staff client installed before, the Ubuntu vm is fresh. |
| 15:17 |
Dyrcona |
Happens with rel_2_12 on that same vm. I'll build a fresh one. |
| 15:54 |
berick |
get all the bits into the shelter! |
| 16:08 |
|
mmorgan joined #evergreen |
| 16:57 |
|
jihpringle joined #evergreen |
| 17:00 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 17:04 |
|
jwoodard joined #evergreen |
| 17:04 |
|
jihpringle joined #evergreen |
| 17:05 |
|
jvwoolf left #evergreen |
| 17:32 |
|
jihpringle_ joined #evergreen |
| 18:19 |
eeevil |
csharp: if you're using pgdump output (rather than pgdumpall) then I think you need to create the extensions (and set the search path, etc) before restoring. pgdump/restore is so much more finicky than pgupgrade... |
| 18:20 |
|
jihpringle joined #evergreen |
| 18:23 |
csharp |
eeevil: ah - thanks - in this case I'm dumping from our 9.4 prod db into a 9.5 test db - looks from stack exchange posts that the problem is that the extension isn't created in the right order |
| 18:24 |
csharp |
also doing parallel restore, so maybe that's a factor too |
| 18:42 |
|
jamesrf joined #evergreen |
| 19:29 |
jeff |
csharp: you've run into bug 1671150 which i should probably actually take a moment to work on. |
| 19:29 |
pinesol_green |
Launchpad bug 1671150 in Evergreen "Unqualified references in evergreen.unaccent_and_squash lead to index creation failures with pg_restore" [Undecided,In progress] https://launchpad.net/bugs/1671150 - Assigned to Jeff Godin (jgodin) |
| 02:09 |
|
Jillianne2 joined #evergreen |
| 05:00 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 07:11 |
|
rjackson_isl joined #evergreen |
| 07:35 |
|
agoben joined #evergreen |
| 08:16 |
|
annagoben joined #evergreen |
| 10:56 |
pinesol_green |
Launchpad bug 1677000 in Evergreen "There is no visual indicator that a patron record has notes in the Web client" [Medium,In progress] https://launchpad.net/bugs/1677000 - Assigned to Jason Etheridge (phasefx) |
| 10:58 |
kmlussier |
Actually, that's not really my question. From what I can tell, some of the commits from collab/phasefx/webstaff-bugs have been merged, but not all of them. Is that right? |
| 10:59 |
* kmlussier |
isn't quite sure what the purpose of the collab branch is |
| 11:07 |
cesardv |
kmlussier: phasefx can correct me if I'm wrong, but basically it's a way to make sure everyone's commits play nicely with each other, avoid merge conflicts, and for testing changes that depend on other changes, or just general testing |
| 11:09 |
kmlussier |
Yeah, I guess I just don't understand why we do things differently for the web client than we do for other parts of the software, particularly when it comes to bug fixes. They could just be merged and backported once tested IMO. |
| 11:10 |
Dyrcona |
The only advantage of collab branches is multiple people can commit to them. |
| 11:10 |
Dyrcona |
That may be why it is being used. |
| 11:11 |
phasefx |
kmlussier: feel free to remove me. I'm not 100% on that branch either |
| 11:15 |
phasefx |
I think the notion is that folks could cherry-pick commits into master as needed but it made things simpler to batch up changes to test over here |
| 11:20 |
* gmcharlt |
notes that given the past practice of doing merges of big webstaff branches where there was relatively little review, at least at the individual patch level, with the bug fixes we've been moving back into a more "normal" workflow |
| 11:22 |
* csharp |
wishes his day job gave him more bandwidth for EG dev :-/ |
| 11:22 |
gmcharlt |
the bugfix collab branch is, at root, more of an artifact of how that particular bugfixing sprint is organized on Equinox's end |
| 14:18 |
Dyrcona |
@clone |
| 14:18 |
pinesol_green |
Dyrcona: I see nothing, I know nothing! |
| 14:18 |
Dyrcona |
:) |
| 15:19 |
pinesol_green |
[evergreen|Ben Shum] i18n: fix syntax for Spanish lang.dtd - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=ed7ae7c> |
| 15:37 |
|
collum joined #evergreen |
| 16:24 |
|
kmlussier joined #evergreen |
| 16:30 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 16:52 |
|
kmlussier joined #evergreen |
| 16:52 |
bshum |
@dessert |
| 16:52 |
* pinesol_green |
grabs some Chocolate Eclairs for bshum |
| 01:30 |
|
Jillianne joined #evergreen |
| 02:09 |
bshum |
And found it |
| 02:09 |
bshum |
Freddy's problem with the closed date editor is an issue with the Spanish translation file for lang.dtd and the closed date editor. |
| 02:10 |
bshum |
staff.server.admin.closed_dates.editor.allmultiday.format in lang.dtd |
| 02:10 |
bshum |
There's a special note saying: Translators: do not translate "<b>YYYY-MM-DD</b>" or "<b>HH:MM</b>" |
| 02:11 |
bshum |
And the Spanish translation there is |
| 02:12 |
bshum |
"Nota: Todas las fechas deben tener el formato <b> AAAA-MM-DD </ b>. Los " |
| 02:12 |
bshum |
"tiempos deben tener la forma <b> HH: MM </ b>" |
| 02:12 |
bshum |
Changing that back to the right variables, things worked |
| 02:12 |
bshum |
So, bleh |
| 02:13 |
bshum |
Changing that AAAA back to YYYY and made things look closer to the original and things worked out |
| 02:15 |
bshum |
And making it AAAA is fine too. |
| 02:16 |
bshum |
It's probably more of a syntax issue with the code itself, hmm |
| 02:18 |
bshum |
And there is it... |
| 02:18 |
bshum |
The problem is that </ b> is used in the translation. There's an extra space between the / and b in those ending tags |
| 02:18 |
bshum |
Removing the space fixes the problem |
| 02:19 |
bshum |
For installed version; it'll be the entry for that string in /openils/var/web/opac/locale/es-ES/lang.dtd |
| 02:19 |
bshum |
Editing it to remove that space fixes the syntax error in my testing |
| 02:24 |
* bshum |
goes to sleep happier knowing the answer to the problem :) |
| 03:12 |
|
remingtron_ joined #evergreen |
| 03:12 |
|
dbwells_ joined #evergreen |
| 03:23 |
|
Jillianne2 joined #evergreen |
| 04:31 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 07:03 |
csharp |
bshum++ |
| 07:14 |
|
rjackson_isl joined #evergreen |
| 07:32 |
|
agoben joined #evergreen |
| 09:07 |
|
jvwoolf left #evergreen |
| 09:09 |
|
_adb joined #evergreen |
| 09:10 |
|
maryj joined #evergreen |
| 09:11 |
* Dyrcona |
contemplates making /etc/hosts entries for some of his test vms. |
| 09:15 |
* csharp |
does that |
| 09:21 |
* Dyrcona |
actually does it, too. :) |
| 09:22 |
Dyrcona |
Maybe now, I can copy and paste URLs from my gitlab test vm and they'll actually work. :) |
| 09:32 |
|
Freddy_Enrique joined #evergreen |
| 09:34 |
Dyrcona |
acquisitions-- |
| 09:35 |
Dyrcona |
Freddy_Enrique: Have a look at this http://irc.evergreen-ils.org/evergreen/2017-06-16#i_310838 |
| 12:02 |
Stompro |
bshum, That is what I mean. Admin -> Server Admin -> Z39.50 Servers |
| 12:02 |
bshum |
Stompro: Then yeah, adding a new server works that way. Did you also define attributes for that new server for search purposes? |
| 12:03 |
* bshum |
never really ever used the GUI for it, and just poked directly at the DB tables |
| 12:05 |
Stompro |
bshum, Yes, I just added one attribute for title to test. Works fine from the yaz-client... but no results when tried from the EG client for the same search. |
| 12:10 |
|
mmorgan joined #evergreen |
| 12:17 |
bshum |
maybe someone else will have more ideas to try. I only remember that those code/format/truncation settings for z39.50 attributes can get weird depending on the z39.50 server you're trying to talk to |
| 12:18 |
bshum |
Not all servers are configured the same way, so copying "title" attribute from one to another doesn't guarantee success. |
| 16:16 |
mmorgan |
I'm going to conclude that the status was edited by the audit_user at the audit_time. |
| 16:16 |
mmorgan |
And not puzzle about it any longer. |
| 16:16 |
Dyrcona |
:) |
| 16:31 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 17:07 |
|
mmorgan left #evergreen |
| 17:09 |
Bmagic |
Anyone using pgpool with Evergreen? |
| 17:18 |
|
jvwoolf joined #evergreen |
| 01:37 |
|
Jillianne joined #evergreen |
| 04:30 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 07:24 |
|
agoben joined #evergreen |
| 08:36 |
|
_adb joined #evergreen |
| 08:59 |
|
mmorgan joined #evergreen |
| 10:58 |
Dyrcona |
Maybe that's more than you wanted to know. |
| 10:59 |
Freddy_Enrique |
yep, I have a better picture of what is going to happen |
| 10:59 |
Freddy_Enrique |
just a couple of months |
| 10:59 |
Freddy_Enrique |
meanwhile I would like to continue testing the software |
| 11:01 |
Dyrcona |
Freddy_Enrique: I recommend setting up the web client if/when you build your own test system. |
| 11:01 |
Dyrcona |
It is listed as optional at the moment. |
| 11:03 |
Freddy_Enrique |
about the web interface, I consider it a big change. Not so sure if I should call it improvement thought. Why this decision? |
| 11:04 |
Freddy_Enrique |
Personally I found it more convenient |
| 11:30 |
kmlussier |
Is there any particular reason you would find it useful? |
| 11:32 |
Freddy_Enrique |
Well, at least... That approached really worked for koha. People got interested in that ILS cause they more or less knew what the could actually do |
| 11:32 |
Freddy_Enrique |
approach* |
| 11:33 |
kmlussier |
Sure, but I'm not seeing how wiping the data helps with the testing. |
| 11:33 |
kmlussier |
In some cases, I think people are trying out the system over multiple days and find it useful to have the same data there when they return to the server/ |
| 11:34 |
Freddy_Enrique |
Your are right |
| 11:34 |
* kmlussier |
isn't objecting to the idea, but just trying to see the pros and cons. |
| 11:37 |
Freddy_Enrique |
I think call it: try it yourself! . We could enter, experiment with it. and...if by any chance I mess it up. Everything comes back to normal |
| 16:03 |
|
hbrennan joined #evergreen |
| 16:05 |
|
tspindler left #evergreen |
| 16:08 |
|
jvwoolf1 joined #evergreen |
| 16:31 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 16:31 |
|
mmorgan1 joined #evergreen |
| 18:39 |
csharp |
@band add Highest Karma |
| 18:39 |
pinesol_green |
csharp: Band 'Highest Karma' added to list |
| 03:21 |
|
Jillianne joined #evergreen |
| 05:00 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 07:16 |
|
rjackson_isl joined #evergreen |
| 07:22 |
|
agoben joined #evergreen |
| 08:08 |
|
kmlussier joined #evergreen |
| 10:34 |
Freddy_Enrique |
Great! and finally, is there any recommendation which Library should be in charge of the server where the EG software is implemented? |
| 10:34 |
csharp |
we may keep our DBs on 14.04/PG 9.4 though |
| 10:35 |
jeff |
csharp: The Carrollton Contingency itself would probably make a good band name. |
| 10:35 |
bshum |
In the past, what I ended up doing was keeping our utility server and such on older Ubuntu distros since the upkeep tended to require more thorough testing |
| 10:35 |
csharp |
@band add The Carrollton Contingency |
| 10:35 |
pinesol_green |
csharp: Band 'The Carrollton Contingency' added to list |
| 10:35 |
dbs |
Well, for the first test upgrade I'll give Xenial a run and see what happens |
| 10:35 |
csharp |
jeff++ |
| 10:35 |
bshum |
But move the app servers and DB servers ahead to the latest Ubuntus |
| 10:35 |
dbs |
you people and your multiple app/utility servers :) |
| 10:38 |
dbs |
Bmagic++ |
| 10:39 |
kmlussier |
Freddy_Enrique: Also, following up on what I said earlier about size of the consortium, I'll refer back to what dbs just said about multiple app/utility servers. In our consortium we have Evergreen running on several bricks. |
| 10:39 |
Bmagic |
dbs: It's been working just fine for us. The EDI stuff works too :) |
| 10:39 |
Dyrcona |
dbs: A/T seems to work fine, I've run them on test databases copied from production. |
| 10:39 |
dbs |
excellent! |
| 10:39 |
kmlussier |
Once you need to move to multiple servers, I think it increases the complexity of maintaining the system. But I'm not a systems person - that's just what I've observed. |
| 10:39 |
Dyrcona |
I use Xenial for my test and development vms, mostly. |
| 10:39 |
cfarley |
I'm trying to have evergreen start automatically after a reboot, but having an issue. |
| 10:40 |
cfarley |
When run from a cron job autogen.sh stalls out, but if I run the script manually, it doesn't have any issues. |
| 10:40 |
cfarley |
Anyone played with this before? |
| 13:48 |
Dyrcona |
JBoyer: Staff can access deleted bibs, so if you remove the metabib info, they will not turn up in searches for staff. |
| 13:48 |
JBoyer |
(I hope this DELETE doesn't come back 2 hours after I leave with a "nope, you have to delete this table at the same time, etc.) |
| 13:49 |
Dyrcona |
JBoyer: It might. :) |
| 13:49 |
JBoyer |
Maybe I'll just cancel it and go for 1 bibid to test. I'd like to be able to test things this week. :p |
| 13:50 |
kmlussier |
Staff searches bring up deleted records? That doesn't sound right. |
| 13:50 |
JBoyer |
kmlussier, if you know to type #deleted into a search box. |
| 13:50 |
kmlussier |
Oh, yes. Ignore me. |
| 16:04 |
kmlussier |
miker: Yeah, that proposal is something that's been sitting on our backburner for a while. I need to get focusing on that at some point. |
| 16:22 |
|
jihpringle joined #evergreen |
| 16:37 |
|
cfarley joined #evergreen |
| 17:00 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 17:06 |
|
mmorgan left #evergreen |
| 17:20 |
|
jvwoolf left #evergreen |
| 18:32 |
|
jihpringle joined #evergreen |
| 04:32 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 05:19 |
|
Sinkme joined #evergreen |
| 07:12 |
|
rjackson_isl joined #evergreen |
| 07:16 |
|
agoben joined #evergreen |
| 10:39 |
Freddy_Enrique |
So I can get to that page in order to adopt any additional tools for the evergreen, and also fix some bugs. |
| 10:44 |
kmlussier |
Freddy_Enrique: Yes, absolutely. We also have some bugs with a 'bitesize' tag that should be smaller bugs to help new contributors get started. https://bugs.launchpad.net/evergreen/+bugs?field.tag=bitesize |
| 10:47 |
* Dyrcona |
is bepuzzled. |
| 10:47 |
kmlussier |
Speaking of photos for patron records, I wonder if they display in the web client. We don't use them, so I never thought of testing them. |
| 10:52 |
* Dyrcona |
thinks I may not have actually loaded the db modification that I thought I was testing. |
| 10:54 |
|
mmorgan joined #evergreen |
| 10:55 |
|
maryj joined #evergreen |
| 10:55 |
Dyrcona |
No, I did, and it seem to make things worse from one point of view, but more digging is required. |
| 10:56 |
* Dyrcona |
is being cryptic.... |
| 10:59 |
|
mllewellyn joined #evergreen |
| 11:00 |
* kmlussier |
runs a quick test and sees no patron record images displaying in the web client. |
| 11:01 |
* kmlussier |
's dog looks very cute in the xul client. |
| 11:04 |
Dyrcona |
heh. |
| 11:52 |
|
Freddy_Enrique joined #evergreen |
| 11:53 |
|
_adb joined #evergreen |
| 16:49 |
mmorgan |
We had a number of auto-updates fail during our last upgrade. |
| 16:50 |
jeffdavis |
mmorgan: Auto-update worked well for us in our 2.10->2.12 upgrade (also for 2.8->2.10). As a rule, partial update fails but full update works. |
| 16:57 |
* mmorgan |
is not sure what is meant by partial vs. full. |
| 17:00 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 17:00 |
gmcharlt |
mmorgan: partial tries to install only the files that have changed since the previous build; full just does a full overwrite |
| 17:02 |
mmorgan |
Is that an option when building the self-updating client? |
| 17:13 |
kmlussier |
mmorgan: I don't know the answer to your question, but I know when a partial update has failed for me in the past, I'm presented with the option to do the full update. |
| 02:06 |
|
Bmagic joined #evergreen |
| 02:51 |
|
jvwoolf joined #evergreen |
| 04:31 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 06:50 |
|
JBoyer joined #evergreen |
| 07:09 |
|
rjackson_isl joined #evergreen |
| 07:18 |
|
agoben joined #evergreen |
| 16:18 |
JBoyer |
Yeah, the fork is fine and the child is returned because it's a higher demand period (i.e. not on the inactive list), for some reason it can't auth, boom, open-ils.search blows up. :/ |
| 16:19 |
JBoyer |
erlang.log is useless, ejabberd.log shows several connections, but they all appear to have the expected "Accepted legacy authentication for opensrf@..." lines with them. |
| 16:20 |
* JBoyer |
is planning to put together a big 'ol text document for the LP bug) |
| 16:31 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 16:31 |
jeffdavis |
JBoyer: I'm not seeing errors like that in our logs |
| 16:32 |
Dyrcona |
JBoyer: I've only ever seen messages like that when ejabberd has crashed or hit some limit, that I recall. |
| 16:33 |
Dyrcona |
And, I haven't seen them in a while, except once recently, when I missed one of the settings on a test vm. |
| 16:33 |
Dyrcona |
You still may have encountered something new. |
| 16:34 |
berick |
so, i was testing hold targeter here recently and each parallel process was fetching 100k+ hold ids in "substream" mode (1 jabber message per id). this caused ejabberd to lock up for severl seconds while it routed all the messages. I wonder if the new bundling/chunking osrf 2.5 changes are having a simimlar effect. messages that used to be large, are now a blast of smaller messages, adding load to |
| 16:34 |
berick |
ejabberd. |
| 16:34 |
Dyrcona |
That would make a lot of sense. |
| 16:34 |
Dyrcona |
Or does make a lot of sense. |
| 16:35 |
miker |
berick: have you removed all shapers? |
| 03:12 |
|
book` joined #evergreen |
| 04:31 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 06:40 |
|
rlefaive joined #evergreen |
| 07:04 |
|
rjackson_isl joined #evergreen |
| 07:28 |
graced |
Happy Friday, #evergreen! |
| 11:59 |
|
jvwoolf joined #evergreen |
| 11:59 |
berick |
Dyrcona: the api uses new_salt when changing the password. get_salt() is more about handling an existing password (e.g. during login) |
| 12:00 |
berick |
i mean you could re-use the salt, but that seems non-good. |
| 12:00 |
Dyrcona |
OK. In my case, I'm reusing the salt, but this is just to test something not related. :) |
| 12:01 |
Dyrcona |
I wanted to change the password for a user on my test database to try downloading their circ history. |
| 12:01 |
Dyrcona |
I think I will write myself a custom function doing it correctly for future situations like this. |
| 12:02 |
Dyrcona |
I just pulled the salt, etc., from the db tables this time. |
| 12:03 |
berick |
Dyrcona: fyi, Actor::modify_migrated_user_password() shows the typical steps for moding a passowrd. translating that to a DB func would be trivial. |
| 12:04 |
Dyrcona |
OK. |
| 12:04 |
Dyrcona |
I think my test db/vm are too slow. |
| 12:04 |
Dyrcona |
Oh. nice. internal server error. |
| 12:06 |
Dyrcona |
[Fri Jun 09 12:05:20.331897 2017] [perl:error] [pid 20167] [client 192.168.100.100:43488] Apache2::RequestIO::print: (32) Broken pipe at /usr/lib/x86_64-linux-gnu/perl5/5.22/Template.pm line 180, referer: https://10.250.150.80/eg/opac/myopac/circ_history |
| 12:07 |
pinesol_green |
[evergreen|Terran McCanna] LP#1681943 Improve Responsive Design in My Lists - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=d786c57> |
| 15:28 |
pinesol_green |
[evergreen|Galen Charlton] LP#1533326: follow-up to remove extra logging statement - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=c1ecb35> |
| 15:33 |
Bmagic |
It looks like it's solved in 2.12.x |
| 15:41 |
|
kmlussier joined #evergreen |
| 15:41 |
* kmlussier |
shakes her fist at Comcast |
| 15:45 |
kmlussier |
Of course, now that I think about it, I probably could have continued testing offline circ while Comcast was down. |
| 15:45 |
berick |
Comcast is your mirror cat |
| 15:47 |
kmlussier |
It all comes back to the mirror cat, doesn't it? |
| 15:49 |
mmorgan |
Pay no attention to the cat in the mirror... |
| 16:06 |
* Dyrcona |
makes that one a bit more than he'd like to admit. |
| 16:13 |
miker |
not copy-paste, typo's mine in here :) |
| 16:14 |
miker |
no, it's just that you can't say "no, make that other radio button selected via change to a scope var" |
| 16:31 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 16:51 |
|
Jillianne joined #evergreen |
| 16:55 |
|
jvwoolf left #evergreen |
| 17:02 |
|
mmorgan left #evergreen |
