| 03:41 |
|
neady joined #evergreen |
| 04:32 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 06:40 |
|
rlefaive joined #evergreen |
| 07:11 |
|
rjackson_isl joined #evergreen |
| 07:33 |
|
agoben joined #evergreen |
| 11:31 |
|
bos20k joined #evergreen |
| 11:31 |
Dyrcona |
JBoyer: Neither. I'm just trying to use systemd. |
| 11:32 |
Dyrcona |
I am looking into moving to a distro that doesn't have systemd, but lack of time... |
| 11:33 |
jeff |
JBoyer: i threw together unit files for a test system here. it seemed to do the trick. |
| 11:33 |
JBoyer |
I see. There was a bit of a curve, yeah. :/ I've got an opensrf.service and clark-kent.service that work as expected on my laptop if anyone is interested in them. |
| 11:33 |
jeff |
and by "seemed to do the trick", i mean "i could reboot the single-VM test instance and end up with a running evergreen instance" |
| 11:34 |
Dyrcona |
JBoyer: I am opposed to systemd as it not being the "UNIX way." |
| 11:34 |
JBoyer |
If Evergreen is going to continue to prefer Debian based systems then I guess it would be a good idea to get a set of service / unit / whatevs in there. |
| 11:34 |
Dyrcona |
I've also had to reboot far more often with systemd than in the past. |
| 12:01 |
|
jihpringle joined #evergreen |
| 12:18 |
dbs |
jeff++ JBoyer++ |
| 12:22 |
|
jihpringle joined #evergreen |
| 12:30 |
gmcharlt |
miker++ # using createdb --template src_eg_database works a treat for standing up a test DB quickly |
| 12:33 |
Dyrcona |
gmcharlt: I've been doing that for quite a while. It's a lot faster than doing a pg_restore. :) |
| 12:45 |
|
sandbergja joined #evergreen |
| 12:55 |
|
mmorgan joined #evergreen |
| 13:14 |
Dyrcona |
gmcharlt | rhamby: Any reason not to push Lp 1545115 at this time? |
| 13:14 |
pinesol_green |
Launchpad bug 1545115 in Evergreen "config.circ_matrix_matchpoint and config.hold_matrix_matchpoint need a description field" [Wishlist,New] https://launchpad.net/bugs/1545115 - Assigned to Jason Stephenson (jstephenson) |
| 13:15 |
Dyrcona |
I'm looking at it and all the tests pass, and it just works in the web staff client. |
| 13:15 |
rhamby |
Dyrcona: I hadn't tested it in ages but since you and gmcharlt have I have no objection |
| 13:17 |
Dyrcona |
It just shows up in the xul client, too. Same dojo interface. :) |
| 13:19 |
Dyrcona |
rhamby: It looks good to me. The description shows up in the client and the database and that's all anyone could ask for. :) |
| 13:20 |
rhamby |
Dyrcona: well, there's the autofill input from the telepathy API that I'm working on but so far all it does it put in random strings from H.P. Lovecraft short stories. No idea why. |
| 13:20 |
Dyrcona |
Hehe |
| 13:22 |
* kmlussier |
feels bad because she suspects she never loaded that code on a Sandbox for sandbergja to test. :( |
| 13:24 |
Dyrcona |
I guess since gmcharlt signed off, it's OK to push. |
| 13:24 |
|
Newziky joined #evergreen |
| 13:25 |
rhamby |
kmlussier: busy people who volunteer for lots of things shouldn't feel bad when the prove occasionally human |
| 15:14 |
bshum |
gmcharlt: I'm going to try putting together a branch with all the i18n fixes out there and then running things through POT / PO sync for master. Right now, master is busted due to a new table that was added to the fieldmapper but is not part of the PO template. |
| 15:15 |
bshum |
Well, try running the sync using a Trusty server, so that we don't muck up the XUL stuff. |
| 15:15 |
gmcharlt |
bshum: sounds good |
| 15:15 |
bshum |
If the branch tests okay, then I'll put it somewhere and just request to get the whole thing merged for master to get us back up to date and working |
| 15:47 |
|
jvwoolf joined #evergreen |
| 15:50 |
|
jvwoolf left #evergreen |
| 15:51 |
|
mmorgan joined #evergreen |
| 15:59 |
bshum |
dbs: An i18n question or thought... do we want to run the make install for a specific locale and update the POs in git with the latest id data for things like db.seed? |
| 16:00 |
bshum |
Right now, we're not changing the final PO files in git with that data, but I wonder if we should sync that up at some point. |
| 16:05 |
|
khuckins_ joined #evergreen |
| 16:15 |
dbs |
bshum: hmm, probably? |
| 16:16 |
dbs |
I know, that's not particularly helpful |
| 16:16 |
bshum |
dbs: I guess the only reason I'd want to see it included in git is so that we can get towards a clean repo |
| 16:16 |
bshum |
Where changes are actually meaningful |
| 16:17 |
bshum |
Not just generated file differences |
| 16:17 |
bshum |
Though, speaking on that, I still have to go back and figure out what should or shouldn't be added to .gitignore |
| 16:17 |
bshum |
At first I thought everything, then I decided maybe nothing, now I'm thinking maybe a few new things |
| 16:18 |
bshum |
dbs: Either way, if you don't have a strong preference against it, I'd be inclined to add a commit to my new branch to test adding those into history then. Thanks :D |
| 16:18 |
* bshum |
will keep experimenting |
| 16:27 |
dbs |
You are talking about the PO files and not the generated .sql files, etc, right? |
| 16:28 |
bshum |
dbs: Correct, the PO files themselves have a bunch of IDs and stuff already in them |
| 16:29 |
dbs |
okay, yeah that sounds sane |
| 16:29 |
bshum |
And so far, my test with pocommentclean seems to be handling fixing them okay |
| 16:29 |
dbs |
yayz |
| 16:30 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 16:44 |
|
Jillianne joined #evergreen |
| 16:48 |
* mmorgan |
notices that in Checkout in the xul client, spaces are trimmed from the beginning and end of barcodes, so if a leading or trailing space is entered by mistake, it will be ignored and the checkout will proceed. |
| 16:48 |
mmorgan |
I don't see that the same trimming is happening at checkin. |
| 04:31 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 05:58 |
|
Callender joined #evergreen |
| 06:40 |
|
rlefaive joined #evergreen |
| 07:10 |
|
rjackson_isl joined #evergreen |
| 09:47 |
dbwells |
bshum: Are you going to to ahead and push the pot/po bits to rel_2_12? If not, I can take care of it whenever you're done looking them over. |
| 09:50 |
|
rlefaive joined #evergreen |
| 09:54 |
bshum |
dbwells: Feel free to push away |
| 09:59 |
dbwells |
bshum: will do, thanks |
| 10:06 |
|
jvwoolf joined #evergreen |
| 10:15 |
dbwells |
bshum: So, I noticed in this po push the final deletion of string like "Example Branch 2". It seems like we would still want those translated for anyone trying out Evergreen. Perhaps we should add Open-ILS/tests/datasets/sql/libraries.sql to the translation process? |
| 10:16 |
bshum |
dbwells: I noticed that too for other things I was testing |
| 10:16 |
bshum |
dbwells: And yeah, adding the sample dataset as a translation option sounds like a good idea |
| 10:17 |
bshum |
But building that out will require a little more thought I think |
| 10:17 |
bshum |
Probably similar to how we do db.seed-data-values.sql now I guess. |
| 10:18 |
gmcharlt |
maybe? sample data (as opposed to test case data) strikes me as something where we don't necessarily want _mechanical_ localization |
| 10:18 |
gmcharlt |
or, rather, where such a thing would be less ideal than getting somebody from the relevant locale to put together realistic data |
| 10:19 |
gmcharlt |
anyway, here's an easy-peasy webstaff pullrequest for someobdy to test and merge: bug 1685232 |
| 10:19 |
pinesol_green |
Launchpad bug 1685232 in Evergreen "webstaff: pcrud.apply() does not work" [Medium,New] https://launchpad.net/bugs/1685232 |
| 10:19 |
gmcharlt |
also pointing out that pcrud.apply(), when it works, can be quite handy |
| 10:21 |
berick |
gmcharlt: hm, i thought I fixed that already. |
| 15:39 |
|
Jillianne joined #evergreen |
| 15:54 |
|
khuckins_ joined #evergreen |
| 16:29 |
|
khuckins__ joined #evergreen |
| 16:31 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 17:04 |
|
mmorgan left #evergreen |
| 17:19 |
|
jvwoolf left #evergreen |
| 21:02 |
|
khuckins__ joined #evergreen |
| 02:56 |
|
Jillianne joined #evergreen |
| 04:31 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 06:40 |
|
rlefaive joined #evergreen |
| 07:46 |
|
rlefaive joined #evergreen |
| 07:59 |
|
rlefaive_ joined #evergreen |
| 14:54 |
Dyrcona |
It's ugly, but I guess necessary. |
| 14:55 |
Dyrcona |
Anyway, I'm all for "making it easier to plop fieldmapper into angular input widgets" |
| 14:57 |
berick |
gmcharlt: ah, that's too bad about getterSetter not being supported everywhere. your solution looks reasonable to me. certainly better than a lot of ad-hoc cross-talking |
| 15:01 |
* Dyrcona |
is testing ngingest and it appears to be working. |
| 15:03 |
|
mmorgan1 joined #evergreen |
| 16:05 |
|
maryj joined #evergreen |
| 16:24 |
|
mmorgan joined #evergreen |
| 16:31 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 16:58 |
|
khuckins_ joined #evergreen |
| 17:07 |
|
mmorgan left #evergreen |
| 17:17 |
|
dteston joined #evergreen |
| 17:21 |
pinesol_green |
[evergreen|Dan Wells] Forward-port 2.11.4 upgrade script - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=d3e591d> |
| 18:04 |
|
khuckins_ joined #evergreen |
| 19:16 |
bshum |
Dyrcona++ # for regex help |
| 19:16 |
bshum |
berick++ # for ansible advice |
| 19:17 |
bshum |
I'm doing a full test of the new additions I've made for i18n before I push it to the collab |
| 19:17 |
bshum |
I think I've got all the kinks worked out, and if so, we shall have i18n options built in for the ansible installer very soon |
| 19:17 |
* bshum |
waits for apt-get upgrade to finish on his fresh VM |
| 19:19 |
Dyrcona |
Aw, shucks. 'Twerent' nothin'. |
| 19:24 |
* bshum |
watches the magic unfold |
| 19:40 |
bshum |
Yay! It worked! :D |
| 04:19 |
bshum |
Have to learn how to parse that better to find the culprit issue |
| 04:20 |
* bshum |
stops digging his grave and tries going back to sleep now |
| 04:24 |
pastebot |
"bshum" at 64.57.241.14 pasted "ar-JO error log with fieldmapper parsing" (1 line) at http://paste.evergreen-ils.org/83 |
| 04:30 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 06:40 |
|
rlefaive joined #evergreen |
| 06:55 |
|
agoben joined #evergreen |
| 07:15 |
|
rjackson_isl joined #evergreen |
| 09:53 |
Dyrcona |
charsets-- |
| 09:53 |
kmlussier |
Dyrcona: Yes, that's right. Because we missed the maintenance releases last month, and there were a lot of patches in the 2.10 branch that are not yet in a tarball. |
| 09:54 |
kmlussier |
dbwells: Ah, ok. Thanks for the clarification. I was going by the call for buildmasters gmcharlt put out last month. |
| 09:55 |
terran |
kmlussier: Nobody has tested this yet - https://bugs.launchpad.net/evergreen/+bug/1681943 |
| 09:55 |
pinesol_green |
Launchpad bug 1681943 in Evergreen "Improve Responsive Design in My Lists" [Undecided,New] |
| 09:56 |
kmlussier |
terran: Ah, yes. Thanks for the reminder. Given the poor state of the current lists on a small screen, I was planning to treat that as a bug fix. |
| 09:57 |
berick |
kmlussier: i threw my hat in for 3.0 builder (as far as I knew) |
| 16:13 |
dbs |
although it's translating the msgids, not the msgstr. go home google |
| 16:14 |
remingtron |
Bmagic: have you had a chance to build a tarball for 2.12? |
| 16:14 |
Bmagic |
working on it atm |
| 16:14 |
remingtron |
cool, let me know when you want some testing |
| 16:15 |
Bmagic |
shouldn't be too long now (I have been pulled around to all kinds of stuff today ) |
| 16:16 |
Bmagic |
oh, and to make sure, I'm using rel_2_12 ? |
| 16:16 |
gmcharlt |
eyp |
| 16:22 |
gmcharlt |
you'd create a new tags/rel_2_12_1 branch just before doing the make_release step |
| 16:22 |
Bmagic |
This will be a first then |
| 16:29 |
* Dyrcona |
has much rebasing to do today and tomorro. |
| 16:31 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 17:09 |
|
mmorgan left #evergreen |
| 17:27 |
|
dcook__ joined #evergreen |
| 18:06 |
|
dcook joined #evergreen |
| 04:30 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 06:40 |
|
rlefaive joined #evergreen |
| 07:11 |
|
rjackson_isl joined #evergreen |
| 07:22 |
|
JBoyer joined #evergreen |
| 08:12 |
|
collum joined #evergreen |
| 08:53 |
|
collum_ joined #evergreen |
| 09:38 |
* csharp |
discovers nice tool for initial diagnosis of SPF problems: http://www.openspf.org/Why |
| 09:39 |
bshum |
csharp++ # always handy :) |
| 10:07 |
bshum |
fwiw, I tested my branch changes for newer nodejs for fresh wheezy and it installed with the -developer target there too. |
| 10:38 |
auvajs |
hello.. I succesfully installed Evergreen :)) my first question: how can I change settings so that the stuff browser client is not located at https://localhost/eg/staff/login but on address like https://staff.mydomain.com ? I installed evergreen on a vps so that accessing the site via the vps localhost is kinda uncomfortable.. |
| 10:42 |
bshum |
auvajs: Congrats on the successful install :) |
| 10:44 |
|
auvajs joined #evergreen |
| 15:27 |
berick |
error, success, and zero |
| 15:27 |
berick |
so you might need some additional logic in there to chose the right sound |
| 15:27 |
phasefx |
gotcha |
| 15:27 |
berick |
and probably remove the error sound from the error handler or it will fire 2 times |
| 15:28 |
berick |
patronSvc.patrons.length == 0 for the zero-hits test |
| 15:30 |
berick |
well, no, that's probably over complicating it |
| 15:30 |
berick |
leave error.patron.by_search where it is. put success.patron.by_search and warning.patron.by_search both in the main resolve handler (where warning.patron.by_search is now) |
| 15:31 |
berick |
and just check ofr patronSvc.patrons.length to determine which of those 2 to fire |
| 15:31 |
phasefx |
berick: so I'm assuming putting something in the error handler slot will keep finally from firing.. unless maybe you do a return false; or somesuch from it? |
| 15:32 |
berick |
no, finally always fires |
| 15:32 |
phasefx |
k |
| 15:32 |
berick |
so it makes sense to close the dialog there, because it should always go away, but not so much the sounds, because you don't know how you got there, unless you add other context information |
| 15:34 |
phasefx |
berick: look sane? http://paste.evergreen-ils.org/80 well, need to change close to close() |
| 15:35 |
phasefx |
and get rid of that explicit success earch |
| 15:35 |
phasefx |
sound |
| 15:36 |
phasefx |
http://paste.evergreen-ils.org/81 |
| 15:36 |
phasefx |
well, that could make warning trump the error |
| 15:37 |
phasefx |
so do which_sound <> 'error' && patronSvc.patrons.length == 0 |
| 15:37 |
phasefx |
or == 'success' && etc |
| 15:37 |
* phasefx |
tests all this |
| 15:38 |
berick |
yeah, i think that would do it |
| 15:43 |
phasefx |
berick: found an unrelated bug.. doesn't seem to be a big deal, but if I do a patron search get results, then try to clear out the search form and hit Search again, sometimes I'll get cached results from a previous search |
| 15:44 |
phasefx |
on the bright side, sounds are working :) except for 0 results on a completely empty search, but I'm not inclined to do anything about that |
| 16:02 |
Nina_ |
join |
| 16:03 |
Nina_ |
Hello! |
| 16:30 |
|
jvwoolf left #evergreen |
| 16:30 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 17:16 |
bshum |
dbs: The more I work on i18n stuff for db.seed fixing, the more I'm starting to think we're missing a major step between newpot and update_pofiles in https://wiki.evergreen-ils.org/doku.php?id=dev:release_process:evergreen:2.8 |
| 17:17 |
bshum |
dbs: When I run the option for "make update_all_locales" in the directory to sync the PO templates against the existing PO files, I get a ton of changes |
| 17:17 |
bshum |
And in reading through our wiki steps for release making, I don't think that's happened |
| 17:17 |
bshum |
Which is why there's such a massive upheaval when I run it locally. |
| 17:18 |
bshum |
and it generates out a whole slew of fresh PO files (mostly empty of course) for all the various locales and files we now translate for. |
| 17:18 |
bshum |
I'm not 100% sure if we want it to generate all these empty translation files or not yet. My next step in testing is to see what it'll do with PO sync against the bzr branch for exported translations from LP |
| 17:19 |
bshum |
But I think we might need to invoke some extra steps here |
| 20:08 |
|
Guest35655 joined #evergreen |
| 20:25 |
|
kmlussier joined #evergreen |
| 20:27 |
dbs |
bshum: yeah, translations.launchpad.net / pootle etc are effective just abstracted front-ends for editing those PO files |
| 00:46 |
|
dbwells_ joined #evergreen |
| 00:50 |
|
remingtron joined #evergreen |
| 00:50 |
|
dbwells_ joined #evergreen |
| 04:30 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 06:40 |
|
rlefaive joined #evergreen |
| 07:31 |
|
Callender joined #evergreen |
| 08:13 |
|
kmlussier joined #evergreen |
| 09:37 |
Dyrcona |
Java 2 was just marketing hype. |
| 09:37 |
Dyrcona |
They (Oracle) still call it JDK 9, JDK 8. |
| 09:37 |
Dyrcona |
So they have split versioning going on. |
| 09:39 |
Dyrcona |
And my created database finished a few minutes ago. Time to test my eg_staged_bib_overlay script. |
| 09:40 |
Dyrcona |
OK. So I messed up an option, obviously. :) |
| 09:42 |
Dyrcona |
All right. I omitted --dbhost, and this gives me an opportunity to make the script more generic. |
| 09:43 |
|
krvmga joined #evergreen |
| 16:11 |
jeff |
etc :-) |
| 16:12 |
mmorgan |
:) |
| 16:13 |
jeff |
Bmagic: yeah, only minor changes required, and one would probably be handled automatically by git and the other would be a no-op, but I'm commenting on bug 1331174 right now. |
| 16:13 |
pinesol_green |
Launchpad bug 1331174 in Evergreen "Long Overdue processing needs org unit settings separate from Lost Processing" [Wishlist,Confirmed] https://launchpad.net/bugs/1331174 |
| 16:30 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 16:37 |
|
khuckins__ joined #evergreen |
| 16:39 |
kmlussier |
I tried installing the web client again. I'm getting an error when I run npm install. https://pastebin.com/qevBnNc0 is what I see in the logs. |
| 16:52 |
jeff |
kmlussier: is that at the point where you've installed the LTS version of node and you're running "sudo npm install -g grunt-cli"? |
| 17:04 |
bshum |
I installed everything earlier this afternoon and all was fine |
| 17:05 |
jeff |
bshum: what version of node and npm do you have installed, and what distro are you using? |
| 17:05 |
kmlussier |
OK, I'm going to have to investigate later. I need to run off for the evening. |
| 17:05 |
bshum |
jeff: I was testing the Ubuntu 16.04 ansible stuff |
| 17:05 |
bshum |
So it used the makefile developer target to install node, etc. |
| 17:06 |
bshum |
I'm spinning up a new fresh VM to try that out again |
| 17:06 |
bshum |
On my other computer |
| 17:07 |
jeff |
bshum: looks like you would end up with nodejs-legacy 4.2.6~dfsg-1ubuntu4 in that case, which might be the difference between success and failure in your case vs kmlussier's case |
| 17:08 |
jeff |
bshum: i.e., what might have worked for you earlier today on xenial might not work for kmlussier on trusty. |
| 17:08 |
bshum |
jeff: Oh I see trusty |
| 17:08 |
bshum |
Ah okay no I just didn't scroll up far enough |
| 17:08 |
bshum |
I haven't built on trusty lately |
| 17:08 |
jeff |
16:55:27 < kmlussier> jeff: No. I run ubuntu-trusty-developer Makefile.install target as the root user in an earlier step, which should install the dependencies for me. |
| 17:09 |
bshum |
Or at least, not before the conference |
| 17:09 |
bshum |
It could be also the new stuff we changed for bower->npm... maybe that's unhappy with something on trusty :\ |
| 17:09 |
bshum |
And I broke it when we merged that |
| 17:09 |
bshum |
I'll spin up a trusty VM to check I guess |
| 17:34 |
* bshum |
thumbs his fingers waiting for Evergreen to finish installing pre-reqs |
| 17:36 |
bshum |
Okay, moment of truth coming up |
| 17:39 |
bshum |
Yup, unhappy :( |
| 17:43 |
bshum |
So it is related to the bower/npm switchup |
| 17:43 |
bshum |
It's choking on "angular-order-object-by": "rxfork/ngOrderObjectBy#npm" |
| 17:43 |
bshum |
Maybe our aged version doesn't know what to make of that line |
| 17:44 |
bshum |
I'll try installing a newer node and seeing what it does differently with that. |
| 17:48 |
* bshum |
hacks his trusty makefile to use the wheezy style for installing newer node |
| 17:54 |
* bshum |
waits, and waits, and keeps waiting... |
| 18:02 |
bshum |
Hmmmm |
| 18:02 |
bshum |
Yeah |
| 18:02 |
bshum |
Okay |
| 18:03 |
bshum |
So using a newer version of node helps with the problem |
| 18:03 |
bshum |
But I have discovered that the Makefile for Wheezy has not been updated to work with a newer version of node |
| 18:04 |
bshum |
It's still installing from source for version 0.10.28 |
| 18:04 |
bshum |
Cause that's what it still says in the Makefile.install source file |
| 18:04 |
bshum |
We fixed it in the eg_wheezy_installer for random repo, for the live test building |
| 18:04 |
bshum |
But the actual installer isn't working quite right |
| 18:05 |
bshum |
So we should rip all that stuff out |
| 18:05 |
bshum |
But yeah, Trusty also won't work without a newer node version |
| 18:05 |
* bshum |
goes to eat |
| 18:06 |
* bshum |
brings his laptop to think with while he eats |
| 18:42 |
bshum |
@later tell kmlussier Check out my work in progress branch: http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/bshum/newer-node-for-wheezy-and-trusty |
| 18:42 |
pinesol_green |
bshum: The operation succeeded. |
| 18:42 |
bshum |
I ran those Makefile changes through a test on Trusty and ended up with newer nodejs and able to run all the npm package installs for Trusty |
| 18:42 |
bshum |
Same changes should apply towards Wheezy too |
| 18:43 |
bshum |
If it works out, we need some tweaks to the README instructions so that the Wheezy specific steps can go away and we can just stick to recommending use of the -developer make target |
| 18:44 |
bshum |
I think it ought to work for the debian-wheezy-developer target too. |
| 18:44 |
bshum |
But it's untested |
| 18:44 |
bshum |
I'll try more of it later on. |
| 18:44 |
* bshum |
goes out to enjoy his Friday :) |
| 18:47 |
bshum |
dbs++ # for new nodejs inspiration from the auto installer scripts |
| 18:48 |
bshum |
kmlussier++ # for helping to find the problem |
| 18:48 |
* bshum |
disappears |
| 18:57 |
|
kmlussier joined #evergreen |
| 18:58 |
kmlussier |
bshum++ |
| 21:05 |
jeff |
Looking at circ policy for a library that makes a circ-duration distinction between "new" items and "replacement" items... currently they use a circ modifier on the "new" items, and while it's so tempting to use "Item Age <" in a circ policy matrix, that won't do it... |
| 04:31 |
pinesol_green |
News from qatests: Test Failure <http://testing.evergreen-ils.org/~live> |
| 06:40 |
|
rlefaive joined #evergreen |
| 06:51 |
|
dbs_breaker_of_t joined #evergreen |
| 06:52 |
dbs_breaker_of_t |
Okay, now to find out why that path wasn't happy. |
| 09:26 |
|
maryj joined #evergreen |
| 09:28 |
|
yboston joined #evergreen |
| 09:41 |
|
kmlussier joined #evergreen |
| 09:42 |
kmlussier |
dbs: Sometimes phasefx will do an unscheduled livetest run if a fix to the tests is added. |
| 09:46 |
|
terran joined #evergreen |
| 10:00 |
jeff |
just as i was about to remark on how useful irc logs can be, i find a case where i xkcd 979'd myself. |
| 10:00 |
jeff |
"oh hey, there's the error." |
| 15:50 |
Dyrcona |
I haven't tried Haskell, though I've sniffed around the edges. |
| 15:50 |
Dyrcona |
An erlang implementation/transport for OpenSRF seems natural enough without ejabberd. :) |
| 15:51 |
|
kmlussier joined #evergreen |
| 15:51 |
Dyrcona |
But erlang syntax is really weird, and I look at back at the sample/test programs I wrote in 2010/2011, and I wonder, "What does that do, again?" |
| 15:52 |
Dyrcona |
I should write an OpenSRF/gateway client in Emacs Lisp. I might actually have a use for that. |
| 15:52 |
jonadab |
Yeah, I haven't tried Haskell either; from what I know of it, it seems sort like lisp with a higher learning curve, for smarter programmers. Or something. |
| 15:53 |
Dyrcona |
s/smarter programmers/masochists/ # Fixed that for you. :) |
| 16:11 |
Dyrcona |
Lots of database stuff going on. |
| 16:12 |
Dyrcona |
New fingerprints, new 901$s field, browse and facet ingest...something else that update 9 million records in our system, but runs fast compared to the others. |
| 16:21 |
|
mmorgan joined #evergreen |
| 16:32 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 16:33 |
bshum |
yay! success! |
| 16:33 |
bshum |
dbs++ |
| 16:36 |
Dyrcona |
:) |
| 18:16 |
|
jvwoolf left #evergreen |
| 18:20 |
|
Jillianne joined #evergreen |
| 19:45 |
* dbs |
breathes a sigh of relief |
| 19:48 |
jeff |
those hourly test failure charges would have made for a terrible weekend. ;-) |
| 19:52 |
dbs |
jeff: that reminded me to shut down my GCE instance |
| 21:04 |
* gmcharlt |
has the first development update blog post queued up to post tomorrow morning |
| 21:12 |
* bshum |
contemplates renaming "2.next" to "3.next" in LP |
| 02:56 |
|
dbs joined #evergreen |
| 02:57 |
|
Jillianne joined #evergreen |
| 05:01 |
pinesol_green |
News from qatests: Test Failure <http://testing.evergreen-ils.org/~live> |
| 06:40 |
|
rlefaive joined #evergreen |
| 07:01 |
|
kmlussier joined #evergreen |
| 07:03 |
kmlussier |
I'm going to delete all of those EvergreenILS tweets that suddenly appeared from the Planet Evergreen feed overnight. Not sure what happened there. |
| 08:54 |
dbs |
because they were "new" :) |
| 08:54 |
gsams |
oh, so that's why my RSS went crazy |
| 08:54 |
kmlussier |
Ah! That explains everything. I thought the problem was with the app I use to republish the feed on Twitter. |
| 08:54 |
dbs |
I managed to add a "umm, max of 2 new entries per feed" limit after that |
| 08:55 |
dbs |
but too late for the twitter feed (and I bet it shuffled all of the other entries around too) |
| 08:55 |
dbs |
sorry for the churn folks |
| 08:55 |
dbs |
yes I need coffee as I dive in to see what happened with the test build... I see the karma tests failed but WHY? :) |
| 08:56 |
dbs |
thanks for cleaning up the twitter feed kmlussier |
| 08:56 |
gsams |
@coffee dbs |
| 08:56 |
* pinesol_green |
brews and pours a cup of Bonsai Blend Espresso, and sends it sliding down the bar to dbs |
| 08:56 |
kmlussier |
The Twitter stuff made me forget there was a test failure. |
| 08:57 |
kmlussier |
I'm guessing it's related to the removal of bower? |
| 08:59 |
|
rlefaive_ joined #evergreen |
| 09:00 |
dbs |
yep |
| 09:01 |
|
finnx joined #evergreen |
| 09:02 |
|
finnx joined #evergreen |
| 09:04 |
|
Dyrcona joined #evergreen |
| 09:06 |
dbs |
oh, I have a theory. live-test builds runs "grunt build && grunt test" whereas our install instructions say to use "grunt all" |
| 09:07 |
dbs |
but just tried that with no failures, albeit not on a wheezy system. hmm |
| 09:09 |
dbs |
ah, [33mWARN [watcher]: [39mPattern "/home/opensrf/Evergreen/Open-ILS/web/js/ui/default/staff/node_modules/angular-sanitize/angular-sanitize.min.js" does not match any file. |
| 09:13 |
dbs |
weird, it's installing the right version of angular-sanitize. how is it not finding that file? |
| 09:15 |
Dyrcona |
No wonder reporting is so slow...There are so many views that depend on action.all_circulation, at least in our database. |
| 09:25 |
|
yboston joined #evergreen |
| 09:32 |
miker |
dbs++ # cache busting |
| 14:18 |
berick |
that's probably it |
| 14:18 |
berick |
oh |
| 14:18 |
berick |
i would expect that to work.. |
| 14:19 |
csharp |
I expected it too - I'm going to do some more testing on it to try and nail down what's up |
| 14:22 |
|
rlefaive joined #evergreen |
| 14:32 |
kmlussier |
csharp++ # acq bug squashing |
| 14:37 |
csharp |
berick: behavior right now - on a 4-lineitem PO with one copy per lineitem, I activate it, receive 3 copies (which marks the lineitem received), cancel the copy on the last item (which doesn't affect the lineitem status) then I use the dropdown menu to cancel the lineitem - PO stays "on-order" |
| 16:37 |
Dyrcona |
Yeap. That's what happened, and I have four stashes hanging around. |
| 16:38 |
Dyrcona |
Too much swinging from branch to branch. |
| 17:01 |
berick |
csharp: https://bugs.launchpad.net/evergreen/+bug/1257915/comments/14 |
| 17:01 |
pinesol_green |
Launchpad bug 1257915 in Evergreen "Acq: purchase orders stay "on-order" with some lineitems received and the rest canceled" [Medium,Confirmed] - Assigned to Chris Sharp (chrissharp123) |
| 17:01 |
pinesol_green |
News from qatests: Test Failure <http://testing.evergreen-ils.org/~live> |
| 17:04 |
berick |
gmcharlt: alas, rollover_phone_to_print.pl to print has been disabled here for a while. i'm in the dark on that one. I can eyeball it, though. |
| 17:05 |
|
mmorgan left #evergreen |
| 17:31 |
csharp |
berick: rock on - I'll give your branch a go |
| 18:59 |
|
jvwoolf joined #evergreen |
| 19:26 |
bshum |
dbs: I just added some thoughts for use of pocommentclean on https://bugs.launchpad.net/evergreen/+bug/1681864/comments/1 |
| 19:26 |
pinesol_green |
Launchpad bug 1681864 in Evergreen "db-seed.po files need cleanup to remove duplicate IDs from generated localized seed data" [Medium,Confirmed] |
| 19:26 |
bshum |
In my very limited initial test, I think it'll help us to fix all the IDs in the comments. |
| 19:27 |
* bshum |
will experiment further after dinner. Or maybe tomorrow if he decides to go to bed early instead |
| 19:55 |
|
dcook joined #evergreen |
| 20:12 |
csharp |
berick++ # your branch works for me - signoff on the way |
| 20:39 |
jonadab |
That building was _residential_? I assumed it was office spaces. |
| 21:20 |
jonadab |
Yeah, at the conference. |
| 21:20 |
jonadab |
The blue one. |
| 21:20 |
|
dcook joined #evergreen |
| 22:33 |
dbs |
bshum++ |
| 22:34 |
dbs |
I've had a few issues of the Launchpad "try again later" over the past couple of weeks, yeah |
| 22:34 |
* dbs |
tries to concentrate on the wheezy build issue |
| 22:47 |
dbs |
once this is fixed, maybe it's time to consider jessie or xenial (or both) as the live-testing platforms? |
| 22:47 |
dbs |
wheezy is dead in a year: https://wiki.debian.org/LTS |
| 23:11 |
berick |
can practically hear it wheezing |
| 23:13 |
* dbs |
suspects 'npm --version' returning 1.x when installed with nodejs 0.10.x, vs. npm 3.x with a more modern mode, might be a factor |
| 23:14 |
dbs |
"npm install -g npm" gets us to npm 4.x (and a warning that nodejs 0.10.x is ancient, what are you thinking?!?) and sure enough, angular-sanitize is now installed as a dependency of ng-toast. |
| 23:15 |
dbs |
and that fixed the tests. |
| 23:18 |
dbs |
we should consider updating some of those deps; grunt-cli 0.1.13 was 2014, and as of 2016-04 was at 1.2.0 |
| 23:20 |
dbs |
similar to grunt itself (0.4.5 2014-05; 1.0.1 2016-04) |
| 23:27 |
dbs |
but then we install grunt-cli globally and use that so we get the latest anyway? hmm |
| 23:32 |
dbs |
anyway, pushed a fix to the wheezy_installer so hopefully we'll see the tests back to happy tomorrow |
| 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 |
