| 09:10 |
|
kmlussier joined #evergreen |
| 09:12 |
berick |
remingtron: working/user/berick/lp1332138-lp1329503-reports-combined |
| 09:12 |
berick |
i'll add a note to the LP's too |
| 09:12 |
remingtron |
berick++ #helping me test |
| 09:14 |
|
jwoodard joined #evergreen |
| 09:19 |
kmlussier |
Happy beta day! |
| 09:21 |
kmlussier |
Just a reminder that the following features need release notes - http://bit.ly/X4fGFH. I'll take care of the top one when it's ready to go. |
| 09:22 |
kmlussier |
And another reminder to fill out the bug squashing day poll. I hope to close it today. http://doodle.com/2dx9h3cccwbp84v4 |
| 09:22 |
* kmlussier |
is done issuing reminders. For now. |
| 09:24 |
kmlussier |
berick: On the reports branches, I was close to ready to sign off on the documentation one (just wanted to do some last-minute testing this morning), but was still finding issues on the other. I see you've merged them Any problem with me still signing off on the one? |
| 09:25 |
|
tater joined #evergreen |
| 09:28 |
berick |
kmlussier: no, that's fine. I can re-merge w/ signoff's (FYI remingtron) |
| 09:28 |
remingtron |
got it. thanks |
| 09:43 |
remingtron |
I think that's all |
| 09:46 |
yboston |
I will work on these |
| 09:47 |
remingtron |
yboston: thanks! |
| 09:47 |
dbs |
Sounds like we need a docs test build server maybe... |
| 09:48 |
yboston |
I have considered setting a test docs build server at Berklee, set to run its scripts mid day |
| 09:48 |
remingtron |
dbs: yes, that would be great. Robert is out of country all summer, any idea how/where else to set one up? |
| 09:48 |
yboston |
that way we can get a heads up on what will go wrong |
| 09:48 |
|
Dyrcona joined #evergreen |
| 09:52 |
dbs |
that wouldn't give us the whole enchilada that rsouilliere has going on but at least we could see build errors immediately |
| 09:52 |
remingtron |
dbs: definitely a good start |
| 09:53 |
remingtron |
yboston: did Robert give you the build scripts and all? |
| 09:53 |
yboston |
he has a github repository for them |
| 09:53 |
yboston |
looking it up now |
| 09:53 |
yboston |
https://github.com/rsoulliere/Evergreen_Documentation_Tools |
| 09:54 |
yboston |
I beleive these scripts are a little behind of what he uses right now, becuase I think he has to update the script to tell it the new release numbers |
| 09:55 |
yboston |
I have some other notes that he sent me a while ago that are missing from that repo (now that I am re-reading his notes) |
| 09:56 |
yboston |
Who should DIG collabrate with to set up a test docs build? |
| 10:00 |
yboston |
Dan I just sent you and remingtron a copy of the one email that Robert described a lot of his process |
| 10:03 |
dbs |
yboston: might make sense to put this out on the list, with some different possibilities (buildbot for basic builds; make targets for the docs in regular source; makefile.install target for doc build prereqs; a whole separate doc build server...)( |
| 10:03 |
dbs |
And see if anyone objects and/or is willing to tackle any of those pieces |
| 10:04 |
dbs |
yboston++ # thanks for forwarding |
| 11:45 |
bshum |
berick: In that case, with apache 2.4 in the mix, we may need to add some variant of e61a8085f9edabd97600b072c1a3ea41cd14265b for Jessie as well. |
| 11:45 |
pinesol_green |
[evergreen|Ben Shum] LP#1341013: Load apache mod CGI - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=e61a808> |
| 11:46 |
gmcharlt |
bshum: note that the branch that eeevil pointed to is a no-op for the non-multiplex SIPServer (IOW, pushing it to EG now shouldn't break anything) |
| 11:47 |
eeevil |
bshum: They're transparent and (hopefully) non-controversial -- they don't change behavior, and they existed and been tested for nigh on a year. how would you like those pushed to your attention |
| 11:48 |
berick |
bshum: thanks for pointing that out. i wonder if that explains why apache segfaults for me on jessie ;) |
| 11:49 |
bshum |
eeevil: gmcharlt: Since it has both your sign-offs on it and has passed a week in wait, I'm fine with seeing it pushed to master on your review. I can do it after I send this email, but feel free to proceed as you need if nobody else steps up. |
| 11:50 |
bshum |
It looks fine to me. |
| 12:30 |
pinesol_green |
Launchpad bug 868653 in Evergreen "secondary permission groups (permission.usr_grp_map)" (affected: 3, heat: 20) [Wishlist,Triaged] |
| 12:31 |
bshum |
I was just reading it again and thinking to myself that if the feature is ready but the release note is pending, we could still move it in and add a note next week. |
| 12:31 |
bshum |
But that gets into slippery slope |
| 12:31 |
dbs |
bshum: yeah, testing + release note |
| 12:31 |
dbs |
that's what I was thinking |
| 12:34 |
jeff |
dbs++ |
| 12:34 |
bshum |
dbs++ |
| 12:55 |
bshum |
Interesting |
| 12:55 |
pinesol_green |
Launchpad bug 1292705 in Evergreen "IDL2js delivers lots of unneeded information, adding bulk." (affected: 1, heat: 6) [Wishlist,New] |
| 12:56 |
bshum |
What I'm doing right now is reading through stuff in 2.next that's marked "wishlist" and have pullrequest on them to see if they can be moved into review. |
| 12:56 |
bshum |
All the stuff already marked for beta1 that aren't fix committed look ready to review. |
| 12:59 |
berick |
bshum: thanks. the IDL2js stuff would be nice to have. |
| 13:00 |
berick |
i think it mostly just needs a few UIs from each general type (xul, old-school html, etc.) tested to ensure no breakage |
| 13:01 |
bshum |
Okay, I'll do some poking on one of my test servers later today. |
| 13:01 |
berick |
bshum++ |
| 13:04 |
dbs |
None of the junk is translation junk is it? (#alwaysparanoid) |
| 13:05 |
* jeff |
reads the "dangers of streaming across versions of glibc" thread on pgsql-general -- I like a good "why is this corrupt?" hunt. http://www.postgresql.org/message-id/BA6132ED-1F6B-4A0B-AC22-81278F5AB81E@tripadvisor.com |
| 13:06 |
berick |
dbs: IDL2js changes? no i18n "junk" removed |
| 13:21 |
remingtron |
berick: sorry, getting nowhere on the report features branch. System issues. |
| 13:22 |
berick |
remingtron: no worries. kmlussier is testing as well. may have another fix or two to push. |
| 13:22 |
berick |
i suggest testing elsewhere when yr system comes back |
| 13:22 |
berick |
at least for now |
| 13:23 |
|
vlewis joined #evergreen |
| 13:24 |
remingtron |
berick: when my system comes back? I'm not quite understanding. |
| 13:25 |
berick |
remingtron: i'm just refering your "system issues" comment. whenever that's resolved |
| 13:25 |
berick |
or did I misunderstand "system issues"? |
| 13:25 |
remingtron |
maybe, let me try again |
| 13:26 |
|
jihpringle joined #evergreen |
| 13:26 |
remingtron |
berick: my system is having strange issues, which has delayed my progress testing your bug |
| 13:27 |
remingtron |
berick: my main point is, I'll keep trying, but wanted to let you know not to count on my input |
| 13:27 |
berick |
gotcha, thanks. |
| 13:28 |
berick |
jfyi, i just pushed one fix and will probably push another soon |
| 13:29 |
remingtron |
berick: cool, thanks for update |
| 13:41 |
berick |
the same style is *cough* used elsewhere, though, w/ no sign of complaint that I see. |
| 13:41 |
berick |
maybe a different invocation |
| 13:42 |
pinesol_green |
[evergreen|Yamil Suarez] Docs: Improved AsciiDoc formating for tpac_meta_record_holds.txt - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=31dfcab> |
| 13:44 |
jeff |
jcamins: regarding xz and bzip2 from earlier: bzip2 -v9 compressed the file in 6m7.762s -- so, significant speed difference to save that additional space. |
| 13:45 |
jeff |
2.9G -> 700M in ~6 minutes or to 533M in ~1 hour. |
| 13:46 |
jeff |
of course, other things might have been happening at that time that might have skewed those numbers. not a scientific test, etc. |
| 13:47 |
* jeff |
times decompression |
| 13:49 |
jeff |
bzcat to /dev/null: 2m18.181s |
| 13:50 |
yboston |
Heads up, the DIG monthly meeting will start at 2 Pm EST |
| 13:52 |
|
RoganH joined #evergreen |
| 13:52 |
jcamins |
jeff: yeah, that matches my recollection. |
| 14:32 |
remingtron |
that's my message to the DIG email list |
| 14:33 |
yboston |
this could be a great way for DIG newcomers to help out, or at least get some practive |
| 14:33 |
yboston |
since you can just use a web browser, and not need to install software |
| 14:33 |
remingtron |
I agree! I'm looking for a volunteer to poke around Bill's test version of the web client and try editing a current doc to reflect the new web interface. |
| 14:34 |
remingtron |
https://bill-dev2.esilibrary.com/eg/staff/login?route_to=%2Feg%2Fstaff%2Fcirc%2Fpatron%2Fsearch |
| 14:34 |
yboston |
do we want to email folks on the general list to get them interested in helping? |
| 14:34 |
remingtron |
sure, I can do that |
| 14:34 |
yboston |
are there any folks right now watching this meeting that would like to help out? |
| 14:53 |
bshum |
Fwiw, this year, I voted towards making the Hack-A-Way after the expected release date for 2.7.0 so that we would avoid having developer interests affect 2.7's final outcome. |
| 14:53 |
bshum |
If you want docs ready for 2.7, then doing it earlier, like late August / early September seems like a better date range to me. |
| 14:53 |
remingtron |
+1 |
| 14:53 |
bshum |
Late August will give more time to stablize everything in 2.7 and get more test servers going for doc purposes too, I would assume. |
| 14:53 |
RoganH |
fwiw, as well, that was part of my goal for the scheduling the hack-a-way as well based on discussion at the conference |
| 14:54 |
|
Shae_ joined #evergreen |
| 14:54 |
kmlussier |
Sorry, it looks like I dropped out for a second. I prefer to keep dev and doc hack-a-ways separate. |
| 15:43 |
kmlussier |
berick: Is the latest reports code in your working branch? |
| 15:44 |
berick |
kmlussier: in the combined branch, yes |
| 15:44 |
berick |
user/berick/lp1332138-lp1329503-reports-combined |
| 15:46 |
remingtron |
berick: not sure if you spotted this bug yet |
| 15:46 |
remingtron |
Reload the page, edit any report, both "Run as soon as possible" and time selector checkboxes are checked |
| 15:46 |
remingtron |
after some usage, that problem goes away, but seems try on a fresh reload of that screen |
| 15:46 |
remingtron |
seems *true* |
| 15:47 |
remingtron |
that's all I've done for testing, now have to leave early. sorry can't sign off today. |
| 15:47 |
berick |
remingtron: hm, thanks, i'll look at that |
| 15:48 |
* remingtron |
heads out |
| 15:49 |
kmlussier |
berick: Yeah, I can confirm that behavior too. |
| 16:40 |
yboston |
apparebtly |
| 16:40 |
yboston |
*apparently |
| 16:54 |
kmlussier |
I can't recall how I've used those characters in the past. I use Notepad++ (when I'm not using VIM) and had to enable a setting to not add those character. I can't remember if I was able to delete them there. |
| 17:00 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
| 17:01 |
|
kmlussier left #evergreen |
| 17:03 |
bshum |
So as far as 2.7 beta freeze goes, I think anything that is signed off tonight will get committed later this evening or tomorrow morning. |
| 17:03 |
bshum |
I'll give at least till midnight for our west coast friends. ;) |
| 17:13 |
jeff |
closes with " If you still need special configuration then please reply to this email saying so and the ticket will automatically reopened. If you could form an orderly queue sorted by urgency it would be appreciated." |
| 17:14 |
|
mmorgan left #evergreen |
| 17:15 |
bshum |
dbs: If you have time tonight while you're playing with 264, yboston added six more RDA bibs to his branch on LP 1308768 |
| 17:15 |
pinesol_green |
Launchpad bug 1308768 in Evergreen "add sample RDA records to test data set" (affected: 1, heat: 6) [Wishlist,Confirmed] https://launchpad.net/bugs/1308768 |
| 17:16 |
bshum |
You did some magic on his first offering but my regular expression fu is weak :( |
| 17:16 |
bshum |
If you can convert those over and add them to also be loadable, I think it'd be great to push that all up to master so that the test dataset has good 264 sample data. |
| 17:18 |
bshum |
Oh you know, I just realized he has them as marcxml too |
| 03:55 |
|
remingtron_ joined #evergreen |
| 04:53 |
|
pastebot0 joined #evergreen |
| 04:53 |
|
ningalls joined #evergreen |
| 05:03 |
pinesol_green |
Incoming from qatests: Test Failure - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
| 06:42 |
|
ningalls joined #evergreen |
| 07:41 |
|
Callender joined #evergreen |
| 07:41 |
|
eeevil joined #evergreen |
| 08:44 |
|
mmorgan joined #evergreen |
| 08:47 |
|
mrpeters left #evergreen |
| 09:22 |
|
krvmga joined #evergreen |
| 09:23 |
krvmga |
a patron sent me a note that she couldn't see the dropdown for placing a hold in My Lists when she was on her mobile. |
| 09:24 |
krvmga |
this seems to be the case on our server as well. |
| 09:24 |
krvmga |
is this just a spot that the responsive catalog design didn't get to? |
| 09:28 |
krvmga |
i've tested this on a vanilla version of 2.5 and it seems to be the case. |
| 09:30 |
Dyrcona |
krvmga: It seems bug worthy to me. I haven't really tried using the catalog much from my phone. |
| 09:30 |
pinesol_green |
[evergreen|Jason Stephenson] Fix 030.schema.metabib.sql breakage. - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=b0c4299> |
| 09:34 |
|
yboston joined #evergreen |
| 09:35 |
Dyrcona |
tsbere++ # for testing and pushing |
| 09:47 |
jeff |
Dyrcona++ tsbere++ |
| 09:48 |
Dyrcona |
You should thank tsbere. He noticed the break and I didn't, 'cause he tried to build a fresh database yesterday. |
| 09:48 |
krvmga |
https://bugs.launchpad.net/evergreen/+bug/1353509 |
| 09:48 |
pinesol_green |
Launchpad bug 1353509 in Evergreen "responsive catalog design fail in my lists" (affected: 1, heat: 6) [Undecided,New] |
| 09:48 |
Dyrcona |
I'll have to test these things with a fresh database, too, from now on. |
| 09:49 |
Dyrcona |
The automated build bot caught it, too. |
| 09:51 |
dbs |
krvmga: please include your specific mobile device and mobile browser in the bug report, just in case it's limited to a specific combination |
| 09:52 |
dbs |
And a bug report title of "Unable to place hold in My Lists from a mobile device" would be both a more useful description and less negative than "responsive catalog design fail" |
| 09:54 |
dbs |
Maybe it's the case that it's just a limitation of the hover vs. touch event model on mobile devices, and not due to the responsive catalog design, in which case you might have insulted those who worked on the responsive design for no good reason... |
| 10:06 |
krvmga |
dbs: the condition can be tested in a web browser by resizing the browser to the mobile device size you'd like |
| 10:09 |
krvmga |
dbs: i changed the title as you suggested and added the reported device and os as well as the browser info |
| 10:09 |
krvmga |
https://bugs.launchpad.net/evergreen/+bug/1353509 |
| 10:09 |
pinesol_green |
Launchpad bug 1353509 in Evergreen "Unable to place holds in My Lists from mobile device" (affected: 1, heat: 8) [Undecided,New] |
| 10:18 |
bshum |
krvmga: Well I think I agree with dbs that any specific information about how the bug was originally discovered can be helpful information to others who test the issues noted in bugs. |
| 10:18 |
krvmga |
bshum: i added it. |
| 10:30 |
krvmga |
in eg 2.6, openils/var/opac/parts/base.tt2, semiauto.css and style.css are linked. are these links obsolete? |
| 10:32 |
bshum |
krvmga: I think I see the issue for mobile view of my lists. |
| 11:07 |
dbs |
Hey Dyrcona, re: #1304462 I signed off on your commit but haven't pushed anything, so ysuarez probably shouldn't add the release note to the docs until the commits get pushed :) |
| 11:08 |
dbs |
bug 1304462 that is (zoia) |
| 11:08 |
pinesol_green |
Launchpad bug 1304462 in Evergreen "Add 264 tag values to Record Summary" (affected: 3, heat: 20) [Wishlist,In progress] https://launchpad.net/bugs/1304462 - Assigned to Ben Shum (bshum) |
| 11:09 |
csharp |
krvmga: (late to conversation, but) I would add to what bshum and Dyrcona said that it helps to run the master branch on a test machine and assist with testing bugfixes and new features |
| 11:09 |
yboston |
dbs: thaks for the heads up. Would it help if I did a collab branch and cherry picked Dyrcona's commit and add the release notes there? |
| 11:09 |
csharp |
that way it's not just a matter of hearing about features, but actually using them in their raw state |
| 11:10 |
dbs |
yboston: well of course I would like my commit to be signed off too :) |
| 11:12 |
csharp |
bshum: or taste the soup before it's served ;-) |
| 11:12 |
bshum |
csharp: Ahh, I like that one better :) |
| 11:12 |
krvmga |
csharp: i like that one, too :) |
| 11:14 |
yboston |
dbs: I forgot about the schema.org changes. I probably won't have time to test the schema.org changes in a test VM this week, I can wait for soemone else to sign off on those changes |
| 11:14 |
yboston |
before making the collab branch |
| 11:14 |
yboston |
or I can just wait until both sets of changes are pulled in |
| 11:15 |
csharp |
oh btw, I volunteered last week to test web sockets - unfortunately, I got bogged down trying to get that running (mostly confusion about apache vs apache-websockets and whether both should be running and whether there needs to be separate config? etc.) |
| 11:24 |
bshum |
@later tell jeffdavis Not sure if you had more work on https://bugs.launchpad.net/evergreen/+bug/1046420 to do (the bug comments lead me to believe there is some more to be done), let us know later. |
| 11:24 |
pinesol_green |
bshum: The operation succeeded. |
| 11:24 |
pinesol_green |
Launchpad bug 1046420 in Evergreen "Wishlist: Cut off due dates so they don't extend past card expiration date" (affected: 3, heat: 26) [Wishlist,Triaged] |
| 12:00 |
|
mllewellyn joined #evergreen |
| 14:06 |
|
collum joined #evergreen |
| 14:25 |
pinesol_green |
[evergreen|Bill Erickson] LP#1319519 Add to PO limits to new/pending PO's - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=101d652> |
| 14:34 |
bshum |
dbs: Dyrcona: yboston: I finally found my old branch that I put together to switch out the publisher, etc. for 264 display in search results branch. |
| 14:34 |
bshum |
Would it make sense for me to start a collab branch with everything in it? |
| 14:35 |
bshum |
I'll start by pulling Dyrcona and dbs stuff and signing off on them |
| 14:35 |
bshum |
And then add in my commits and yboston's notes |
| 14:35 |
bshum |
If it looks good, we can push the whole thing on up |
| 14:35 |
* bshum |
tests |
| 14:39 |
|
hbrennan joined #evergreen |
| 14:42 |
dbs |
bshum++ |
| 14:42 |
* dbs |
will need to look at bug 1046420 too |
| 14:51 |
hbrennan |
(Holly strikes again by grossly simplifying the process and enraging the brilliant dev minds!) |
| 14:52 |
bshum |
dbs: yboston: Dyrcona: http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/collab/bshum/lp1304462_rda_264 |
| 14:52 |
yboston |
I have a git workflow question, I am preparing some documentation commits from a DIG member to inlude in master & 2.6 |
| 14:53 |
bshum |
That's the collab I started rolling with. I have to test it again on a server to make sure my commits don't break anything new. |
| 14:53 |
bshum |
It's been awhile. |
| 14:53 |
csharp |
in a FIFO setup, that sounds reasonable, but in the "default" setup that was built for contant transits across systems, no that wouldn't work |
| 14:53 |
csharp |
s/contant/constant/ |
| 14:54 |
hbrennan |
csharp: Sounds like it would be something we'd have to take on ourselves. Thanks! |
| 15:26 |
pinesol_green |
[evergreen|Bill Erickson] LP#1279998 marc_stream_importer option no-match import; delete repairs - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=d0399c9> |
| 15:26 |
pinesol_green |
[evergreen|Bill Erickson] LP#1279998 marc stream importer release notes - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=aa3bed5> |
| 15:28 |
Dyrcona |
On the commit thing: I've done it a couple of times with patches to give the patch author credit, not me. |
| 15:38 |
pinesol_green |
[evergreen|Erica Rohlfs] Docs: MARC Record Attribute Definitions, Multi Valued Fields, Composite Record Attributes - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=1f8b86d> |
| 16:00 |
pinesol_green |
[evergreen|Erica Rohlfs] Docs: How to perform metarecord search and hold - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=ae82e4d> |
| 16:00 |
|
vlewis joined #evergreen |
| 16:04 |
pinesol_green |
[evergreen|Erica Rohlfs] Docs: How to use MARC Fixed Field Editor - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=c901231> |
| 16:12 |
pinesol_green |
[evergreen|Erica Rohlfs] Docs: How to create routing list and shows address on routing list - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=b69c63b> |
| 16:46 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
| 16:46 |
phasefx |
yay |
| 17:15 |
|
mmorgan left #evergreen |
| 17:19 |
|
kmlussier left #evergreen |
| 17:23 |
remingtron |
berick: FYI, I plan to test bug 1329503 tomorrow morning |
| 17:23 |
pinesol_green |
Launchpad bug 1329503 in Evergreen "View / Edit Existing Reports" (affected: 5, heat: 30) [Wishlist,New] https://launchpad.net/bugs/1329503 |
| 17:24 |
remingtron |
unless you have enough eyes on that already, then I'll test something else |
| 17:25 |
berick |
remingtron++ # that would be much appreciated |
| 17:25 |
remingtron |
great, will do |
| 17:25 |
berick |
beware it relies on another LP / branch mentioned in the ticket |
| 02:46 |
|
mtcarlson joined #evergreen |
| 04:58 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
| 05:42 |
|
berick_ joined #evergreen |
| 05:44 |
|
jeffdavi1 joined #evergreen |
| 05:44 |
|
jcamins_ joined #evergreen |
| 14:47 |
bshum |
Generally I don't agree to support anything less than 1024x768 in my consortium. But that's just our practices here. |
| 14:48 |
jeff |
"responsive XUL" isn't really a thing. |
| 14:49 |
Dyrcona |
It's not really usable at less than 1920x1080, cause some wider screens don't get horizontal scroll bars when they should. |
| 14:49 |
csharp |
trying to install/test the web client, but it looks like I'm missing something |
| 14:49 |
bshum |
@quote add <jeff> "responsive XUL" isn't really a thing. |
| 14:49 |
pinesol_green |
bshum: The operation succeeded. Quote #87 added. |
| 14:49 |
Dyrcona |
I'm looking at you Item Status. |
| 14:53 |
Dyrcona |
csharp: It's often a lack of eyesight, not funds. |
| 14:53 |
bshum |
kmlussier: I think idle starting footprint for the Evergreen client is more like 900 MB or so |
| 14:53 |
Dyrcona |
At 800x600 on a larger monitor stuff looks bigger. |
| 14:53 |
bshum |
I'd have to refer back to all the testing notes that was done during the memory leak. |
| 14:53 |
csharp |
whew - that's bad |
| 14:53 |
kmlussier |
But we also have options for increasing font size. |
| 14:54 |
csharp |
it's a bad workaround |
| 15:31 |
kmlussier |
I don't know. tspindler said he got rid of all of his unnecessary stat cats, but it didn't make a huge difference. |
| 15:31 |
csharp |
that seemed to be the factor when krmvga and I were comparing a couple weeks back |
| 15:31 |
csharp |
it loads fine for us, but we barely use patron stat cats |
| 15:33 |
eeevil |
kmlussier: another thing to remember is that, while anecdotal, /everything/ seems to run faster (dojo included) in chrome than in xulrunner, because of the different js engine. again, anecdotal, but something that folks should also look into testing |
| 15:33 |
berick |
eeevil: good point |
| 15:33 |
csharp |
yeah - we tested chrome and firefox |
| 15:33 |
tsbere |
I think another issue was number of permission groups that the permission to edit had to be checked for |
| 15:33 |
csharp |
both were *way* faster, especially chrome |
| 15:34 |
|
tspindler joined #evergreen |
| 15:40 |
jeff |
heh |
| 15:40 |
jeff |
old habit |
| 15:40 |
tsbere |
berick: That is the workflow of the javascript in register.js file. As in client-side. |
| 15:40 |
berick |
kmlussier: and that's different data, too, so not a wholly accurate test. |
| 15:41 |
berick |
tsbere: gotcha. do you think that API call takes too long or processing the results? |
| 15:42 |
kmlussier |
berick: Sure, not that the code is in LP, I think we'll look at loading it with some production data. But it still won't be the same data, so it may not be the best test either. |
| 15:42 |
kmlussier |
That is, now that the code is in LP. |
| 15:42 |
tsbere |
berick: Unless the has_work_perm_at.batch function filters dupes I imagine we are getting a backend dance for each permission group with a perm attached, instead of for each permission (I haven't checked the actor code to see though). Other than that massive playing with the tree of permissions may slow down things when there are a lot of them. |
| 15:43 |
phasefx |
semi-related aside, the xul side of things used to share data with the patron editor to save some network requests, but I don't think that is any longer the case |
| 15:43 |
berick |
kmlussier: another test.. you can go to .. https://YOUR-DOMAIN/eg/actor/user/register |
| 15:44 |
berick |
tsbere: gotcha, yeah, not sure about the api |
| 15:44 |
tsbere |
berick: Actually, now having looked at Actor.pm, it doesn't look like it filters dupes. So if you have 50 groups that use the same permission I think we verify that permission 50 times, instead of just once. Not sure which end we should be filtering it on, though. |
| 15:44 |
|
Shae joined #evergreen |
| 15:44 |
* tsbere |
suspects the backend is a good place though |
| 16:33 |
berick |
s/the/they/ |
| 16:33 |
berick |
they flow on my phone OK, but this freakin' nexus is 1280x768 |
| 16:38 |
eeevil |
fwiw, the overlap there is not dojo's fault, it's simply suboptimal layout |
| 16:38 |
kmlussier |
Sorry, I just walked away to test on my son's phone. It's overlapping there. The phone is a few years old, but it's there. |
| 16:39 |
kmlussier |
berick: No, I haven't looked at much at that level. I try to stay away from 800x600 when I can. :) |
| 16:39 |
berick |
eeevil: yeah, dojo is def. not to blame for a lot of stuff we're throwing around. at this point, I think "dojo" really just means "those interfaces" |
| 16:39 |
berick |
kmlussier: i hear ya |
| 16:41 |
eeevil |
berick: I understand. I want to make sure it's clear that making the pages flow better is not necessarily dependent upon completely replacing them with alternate implementations. and could be done by anyone, not just you, without harming the browser-client target, as long things like element ids and classes don't get blown away |
| 16:42 |
eeevil |
(more or less) |
| 16:42 |
berick |
eeevil: absolutely. that's good to reiterate |
| 16:42 |
|
tspindler left #evergreen |
| 16:43 |
eeevil |
if someone feels like removing floats and tables and moving the /containers/ to divs and whatnot, that should not have an impact on the logic (ideally ... testing would tell, obv) |
| 16:48 |
kmlussier |
eeevil: Sure, I understand that. I was just trying to make the point that it might not be a bad idea to keep that specific bug open. |
| 16:49 |
kmlussier |
If anyone's interested, this is what the patron registration screen looked like on my son's phone. http://www.screencast.com/t/GaEAqcYw |
| 16:49 |
eeevil |
kmlussier: I agree with keeping it open |
| 00:50 |
|
mcarlson joined #evergreen |
| 02:37 |
|
tsbere__ joined #evergreen |
| 02:59 |
|
tsbere_ joined #evergreen |
| 04:28 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
| 05:05 |
|
mnsri joined #evergreen |
| 05:12 |
|
book` joined #evergreen |
| 07:27 |
|
collum joined #evergreen |
| 15:14 |
kmlussier |
As part of this action item and the next one, I haven't had a chance to review the most recent code or pull together my summary. The negative balance was 1 of 4 billing projects MassLNC was working on. We decided a few weeks ago to really focus on the other three so that we can get them out of the way before we get back to negative balances, which is a harder nut to crack. |
| 15:14 |
jeff |
(for rounding up scarce tuits) |
| 15:15 |
kmlussier |
But just glancing at dbwells' most recent comment, it looks like there is still a bit of work to be done before this branch is ready to be merged? |
| 15:15 |
dbwells |
Testing at the very least, but like I mentioned, I think a few hours spent on display side would be time well spent for me. |
| 15:16 |
kmlussier |
dbwells: I'm having a hard time picturing what you suggested in your comment, but I also had some concerns on the display side. |
| 15:18 |
kmlussier |
I also don't think I'll have a chance to test the most recent code until we finish working on our two remaining billing projects. Having two dev branches loaded on the test server at the same time causes confusion over which one might be causing a problem. |
| 15:19 |
Dyrcona |
Well, when they're related to the same part of the system, anyway. |
| 15:21 |
dbwells |
kmlussier: If you have a testing timeline in mind, I can try to work on my display ideas so you can test it at the same time. Feel free to get in touch after this meeting if needed. |
| 15:21 |
kmlussier |
So I guess we need some kind of action item for me to test the current branch and provide feedback? I don't know if anyone else wants to take a look at it. |
| 15:21 |
jeff |
I've interest but cannot guarantee that I can make time for it in the next month. |
| 15:22 |
kmlussier |
dbwells: Will do. I'll have to consult with Dyrcona regarding a testing timeline, but we can figure it in short order. |
| 15:22 |
jeff |
I'll see what I *can* do, though. |
| 15:22 |
kmlussier |
jeff++ Thanks! |
| 15:22 |
kmlussier |
#action kmlussier and others to make time to test the latest branch. |
| 15:23 |
kmlussier |
#action dbwells to work on display ideas for negative balance branch |
| 15:23 |
kmlussier |
dbwells and remingtron: Thanks for taking a look at it! |
| 15:23 |
kmlussier |
Anything else before we move on? |
| 15:23 |
jeff |
reducing the number of cases where we deviate from stock is a goal, and our own branch to avoid negative balances is ripe for elimination if we can assist in testing this one. |
| 15:23 |
Dyrcona |
dbwells++ remingtron++ |
| 15:24 |
kmlussier |
#topic OpenSRF release |
| 15:24 |
kmlussier |
Anything to report one OpenSRF? |
| 15:24 |
gmcharlt |
I'm looking for volunteers to test the websockets work submitted by berick |
| 15:24 |
gmcharlt |
any takers? |
| 15:24 |
bshum |
Further down in the agenda, there's some notes about websockets |
| 15:25 |
bshum |
Sorry, juggling between meetings |
| 15:25 |
jeff |
I can test, assuming berick or others are available for questions when I reach that point. |
| 15:25 |
berick |
anything I can do to make testing easier? |
| 15:25 |
berick |
jeff: yes |
| 15:25 |
jeff |
berick++ thanks! |
| 15:25 |
eeevil |
gmcharlt: re your 3 options, I'm strongly in favor of merging what's there and getting the release out |
| 15:25 |
gmcharlt |
likewise |
| 15:26 |
gmcharlt |
jeff: can you put some testing time into this week? |
| 15:26 |
* csharp |
can test, but has not had the time lately to keep up with development, so may need assistance ;-) |
| 15:26 |
jeff |
gmcharlt: yes. i was just about to ask what timeline you had in mind. |
| 15:26 |
kmlussier |
berick: How many testers do you need? |
| 15:26 |
kmlussier |
Sorry, that was for gmcharlt. |
| 15:26 |
gmcharlt |
jeff: let's shoot for by the end of this week, if you can |
| 15:27 |
eeevil |
berick: is it true that anyone whose tested your dev on your demo server has tested the websockets code? |
| 15:27 |
berick |
eeevil: they have, indeed |
| 15:27 |
jeff |
gmcharlt: i will shoot for that. thanks! |
| 15:27 |
gmcharlt |
ok |
| 15:28 |
csharp |
then Terran has definitely been testing |
| 15:28 |
eeevil |
csharp: :) |
| 15:28 |
dbs |
They all haven't installed it locally though :) |
| 15:28 |
kmlussier |
So for an action item, that's jeff and csharp? Do we need more testers or is that good? |
| 15:29 |
berick |
bshum: it does not interract, but code the staff client uses is touched, like the JS opensrf libs |
| 15:29 |
bshum |
Just making sure that present stuff continues to function I guess over what's coming next too. |
| 15:29 |
eeevil |
bshum: only insofar as its part of opensrf ... the current SC does not attempt to make use of it |
| 15:29 |
bshum |
Okay. |
| 15:29 |
bshum |
So that's something we ought to test as well. |
| 15:29 |
berick |
bshum: definitely |
| 15:29 |
bshum |
To make sure that it doesn't break any existing functionality |
| 15:29 |
kmlussier |
#action jeff and csharp to test websockets work by the end of this week. |
| 15:30 |
kmlussier |
#action gmcharlt to cut alpha of OpenSRF the middle of next week (week of Aug. 4th) |
| 15:30 |
kmlussier |
Anything else on OpenSRF? |
| 15:31 |
kmlussier |
#topic Evergreen maintenance releases |
| 15:31 |
kmlussier |
dbwells? |
| 15:31 |
dbwells |
#info 2.6.2 and 2.5.6 were released on 7/7 |
| 15:32 |
dbwells |
I would also like to ask about the next round, which was due last Friday. |
| 15:32 |
dbwells |
There is only one actual code change: https://bugs.launchpad.net/evergreen/+milestone/2.6.3 |
| 15:42 |
kmlussier |
eeevil: Yes, an on-time release. :) |
| 15:42 |
bshum |
gmcharlt: That's something I wanted to have some debate on actually. |
| 15:43 |
bshum |
The scheduled date for 2.7.0 beta freeze and presumably soon thereafter cutting is next Thursday, August 7 |
| 15:43 |
csharp |
so we're talking about for testing purposes? or for general usage? |
| 15:43 |
dbwells |
I can be flexible if we want to coordinate OpenSRF 2.4, 2.7-beta, 2.6.3, and 2.5.7 to all roughly coincide for dependency reasons. |
| 15:43 |
eeevil |
dbwells: looks like we there's no rest for the wicked this month ;) |
| 15:43 |
gmcharlt |
well, we can sequence things like this: opensrf 2.4 alpha => EG 2.6 beta => EG 2.5/2.6 pint releases => opensrf 2.4.0 |
| 15:48 |
bshum |
That sounds reasonable. |
| 15:48 |
bshum |
The next date for 2.7 after beta is the RC date, which is Sept 4 |
| 15:49 |
dbwells |
I'd like to plan the point releases for Aug. 7 as well, if nobody minds. |
| 15:49 |
bshum |
So that gives us time to do tests, etc. with the new OpenSRF |
| 15:50 |
kmlussier |
#agree next round of point releases will be scheduled for August 7 |
| 15:50 |
kmlussier |
Anything else before we move on? |
| 15:50 |
bshum |
Just an info |
| 15:52 |
bshum |
Well, I learned how to use the make_release script tools |
| 15:52 |
bshum |
And the first alpha tarball is up on the downloads page now. |
| 15:52 |
kmlussier |
bshum++ |
| 15:52 |
bshum |
mceraso is actually testing the alpha tarball for me right now, but if anyone else has good or bad things to say about it, please let me know. |
| 15:53 |
bshum |
#info 2.7.0 alpha1 was cut and available from downloads page on Evergreen website |
| 15:53 |
bshum |
#info 2.7.0 beta1 cutoff date is August 7, 2014 (next Thursday) |
| 15:53 |
kmlussier |
Any questions for bshum before we move on? |
| 15:54 |
bshum |
Speaking on the beta deadline, if there's any specific things that people are working on that they really want in 2.7, this is the time to get action on LP for them. |
| 15:54 |
kmlussier |
bshum: What kind of action? |
| 15:57 |
bshum |
I've been saying it in IRC and I think I mentioned it in the last email, but perhaps I should write a more dedicated, "HEY PUSH THINGS" email to developers so that we can get as much work done as possible. |
| 15:57 |
vlewis |
tsbere Thanks |
| 15:57 |
Dyrcona |
Well, that brings up something that I thought of earlier today: lp1347774. |
| 15:58 |
kmlussier |
I have some code I plan to test over the next week, but I don't have the power to push, just sign off. I don't know if that helps expedite the process. |
| 15:58 |
bshum |
Given our general reliance on a week's time to review new features before push, perhaps the cutoff for new LP pullrequest targets ought to be this Thursday, July 31 |
| 15:58 |
kmlussier |
https://bugs.launchpad.net/evergreen/+bug/1347774 |
| 15:58 |
pinesol_green |
Launchpad bug 1347774 in Evergreen "Backend logic has leaked into the TPAC (and friends)" (affected: 2, heat: 12) [Wishlist,New] |
| 16:03 |
eeevil |
blockers to attacking this problem, I mean |
| 16:03 |
pinesol_green |
Launchpad bug 1208875 in Evergreen "OPAC: My Account: Download Checkout History CSV breaks when there are a large number of items in the history" (affected: 5, heat: 26) [Medium,Confirmed] https://launchpad.net/bugs/1208875 |
| 16:04 |
Dyrcona |
Well, I like using CStoreEditor, for one thing. :) |
| 16:04 |
bshum |
It was on my list of things to test and include for alpha but I missed my own deadline that week, fwiw. |
| 16:04 |
eeevil |
Dyrcona: that's totally fair. if I can adjust that to fit, would that be a fair compromise? |
| 16:04 |
eeevil |
Dyrcona: you'll get to keep using cstore editor |
| 16:05 |
eeevil |
that's a big part of the plan |
| 16:05 |
Dyrcona |
eeevil: Sure, but I'm willing to rework it if necessary. |
| 16:05 |
eeevil |
(minus json_query) |
| 16:05 |
Dyrcona |
OK. I'll keep an eye out for branches. |
| 16:06 |
kmlussier |
#info any new features for 2.7 should have a pullrequest tag by July 31. |
| 16:06 |
kmlussier |
#help We need volunteers to test and push code for 2.7 |
| 16:06 |
jeff |
eeevil: are you saying you'll adjust the code for bug 1208875 to work under the new reality of bug 1347774? |
| 16:06 |
pinesol_green |
Launchpad bug 1208875 in Evergreen "OPAC: My Account: Download Checkout History CSV breaks when there are a large number of items in the history" (affected: 5, heat: 26) [Medium,Confirmed] https://launchpad.net/bugs/1208875 |
| 16:06 |
pinesol_green |
Launchpad bug 1347774 in Evergreen "Backend logic has leaked into the TPAC (and friends)" (affected: 2, heat: 12) [Wishlist,New] https://launchpad.net/bugs/1347774 |
| 16:13 |
kmlussier |
gmcharlt: Do you have any insights to offer? |
| 16:13 |
gmcharlt |
the lack of sandboxes is a problem |
| 16:13 |
yboston |
kmlussier: I would like to help one way or another. One way I would like to help is put together a tutorial to gelp first time voluneteers, like creating tips for installing EG through Git |
| 16:13 |
gmcharlt |
at least with respect to including as many people as possible who can test but who aren't necessarily in a position to apply particular fixes |
| 16:14 |
hopkinsju |
MOBIUS could provide one or more sandboxes, gmcharlt |
| 16:14 |
gmcharlt |
a possible mitigation would be to arrange for folks to claim bugs before the big day |
| 16:14 |
gmcharlt |
and set up environments before hand |
| 16:16 |
kmlussier |
It seems like branches might conflict if everything happened on one? |
| 16:16 |
gmcharlt |
yep, multiples would help |
| 16:16 |
jeff |
kmlussier: one per bug/branch would be what i was thinking |
| 16:16 |
gmcharlt |
so to expand my suggestion... I think lining up volunteers in advance would really help |
| 16:16 |
gmcharlt |
both for hosting test envs, and for doing testing |
| 16:17 |
kmlussier |
To speed things along, maybe we can move the Sandbox discussion to the dev list to see if we can make this happen. |
| 16:18 |
kmlussier |
#action kmlussier to move Sandbox discussion to dev list |
| 16:18 |
jeff |
+1 |
| 16:19 |
kmlussier |
hopkinsju++ #Volunteering a MOBIUS test server |
| 16:19 |
* kmlussier |
will move forward with bug squashing plans. |
| 16:19 |
kmlussier |
#topic Web client's circulation module preview for Evergreen and websockets for OpenSRF |
| 16:19 |
kmlussier |
bshum: Was this your topic? |
| 16:20 |
bshum |
kmlussier: Yes, but we covered a lot of it earlier with the websockets talk just now. |
| 16:20 |
jeff |
of the three options presented in the agenda, i like the first option best, and i'm almost certain that it is actually what was agreed upon earlier with regard to opensrf alpha scheduling. :-) |
| 16:20 |
bshum |
I think the only outstanding part of it is whether berick thinks we'll want to include the web client circ module preview for 2.7 beta |
| 16:21 |
berick |
It’s tracking Evergreen master, so I’m not expecting any merge conflicts |
| 16:21 |
berick |
or other oddities |
| 16:21 |
jeff |
if it were included without changes to the 2.7 beta timeline, do you think that it would be a useful representation of the web-based features? |
| 16:22 |
kmlussier |
By adding it as a preview, will it make it easier for more people to test? |
| 16:22 |
berick |
jeff: yes; kmlussier: i would think yes |
| 16:22 |
berick |
Assuming web sockets is merged, there’s one other bit of testing we would need to merge the browser client. |
| 16:23 |
berick |
There are a couple of places where existing (non-browser client) code had to be modified for integration (e.g. opac). Affected areas will need to be tested in the XUL client to make sure nothing was broken. |
| 16:23 |
berick |
I could create a list. There aren’t very many of these. |
| 16:24 |
berick |
otherwise, it should go unnoticed for anyone not looking for it |
| 16:24 |
jeff |
process-wise, would a lp bug for the circ-bits with notes on pre-reqs (websockets in opensrf) and a list of things to pay attention to when testing (berick's "list" just now) be the way to get it targeted for 2.7 beta in time for thursday? |
| 16:25 |
kmlussier |
The possibility of breakage in the existing client makes me a little nervous. On the other hand, I would love to make it available for wider testing. |
| 16:26 |
berick |
it occurs to me the build/install process might need some more work, too |
| 16:26 |
berick |
it's been a while since I've looked at that |
| 16:27 |
berick |
if the requiremetn for 2.7 is basically "don't break anything", then I think this is very doable |
| 16:54 |
|
mtcarlson joined #evergreen |
| 16:54 |
Dyrcona |
eeevil: Cool. |
| 16:55 |
* Dyrcona |
was AFK. |
| 17:00 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
| 17:02 |
|
mcarlson joined #evergreen |
| 17:10 |
|
mmorgan left #evergreen |
| 17:32 |
jeff |
Firefox can't find the server at git.evergreen-. |
| 09:05 |
* Dyrcona |
now has to remember how to use yaz-client to check something. |
| 09:07 |
kmlussier |
Good morning! |
| 09:07 |
kmlussier |
tspindler: Chrome Vox was never a problem with autosuggest. |
| 09:08 |
tspindler |
kmlussier: ok, is there something free we can test it with then we have it on ou a dev server |
| 09:15 |
tspindler |
@coffeee |
| 09:15 |
pinesol_green |
tspindler: Zoia knows how to make fusilli. |
| 09:15 |
kmlussier |
Heh |
| 09:16 |
kmlussier |
Shouldn't that say pinesol_green instead of zoia? |
| 11:17 |
kmlussier |
I like what jeff's library does with the whitespace http://catalog.tadl.org/eg/opac/home |
| 11:17 |
|
bmills joined #evergreen |
| 11:18 |
krvmga |
kmlussier: yes, a good example of what i meant. |
| 11:24 |
jeff |
two other approaches that we have been experimenting with can be seen here: https://dev.tadl.org/responsive-web/ and here: http://dev.kalkaskalibrary.org/books/ |
| 11:27 |
jeff |
both of those are very much experiments and/or work-in-progress, hopefully as hinted at by the "dev" hostnames, robots.txt, and content like: "* just testing some things" :-) |
| 11:28 |
krvmga |
jeff: i particularly like the responsive-web one. |
| 11:29 |
krvmga |
jeff: do you have many academic libraries in your consortium? |
| 11:31 |
jeff |
krvmga: no academic libraries in our catalog. we're also not a "consortium", per se. we are a district library, plus we're contracting with a neighboring county library to provide ILS/website/etc services (going live in Aug). |
| 14:33 |
kmlussier |
eeevil++ |
| 14:34 |
krvmga |
jeffdavis: just read death-to-the-website-carousel , interesting read |
| 14:34 |
krvmga |
jeffdavis++ |
| 14:35 |
eeevil |
kmlussier: :) ... I have a followup to that that's in testing ... I'll pull the pullrequest for the ... nonce (that'll be funnier later) |
| 14:36 |
jeffdavis |
krvmga: glad you found it worthwhile! |
| 14:37 |
jeffdavis |
it seems that TADL's carousels/sliders/whatever avoid a lot of the accessibility issues that article raises, which is cool |
| 14:37 |
jeff |
jeffdavis: my intent wasn't to defend them, just to comment on how i've used slider/carousel to mean different things over time. :-) |
| 16:50 |
phasefx |
gmcharlt: we can go ahead and use cluster on the QA server to put everything in backwards orders |
| 16:50 |
mmorgan |
In our experience on Evergreen thus far, the permission group list in the edit screen has been badly sorted, and pretty consistently so from day one. If clustering can sort it better even for a short time, it's a win for us :) |
| 16:50 |
eeevil |
back when all the selinux extensions were first being designed |
| 16:50 |
phasefx |
gmcharlt: well, s/QA/demo/ or manual test server |
| 16:51 |
phasefx |
not quite the same, but partway there for finding bad assumptions in the code |
| 16:52 |
eeevil |
Dyrcona: that's, IIRC, index organized tables, where the heap tuples live on the leaf pages of the index ... yes, similare purpose, but not possible in pg in the broadest sense |
| 16:52 |
eeevil |
Dyrcona: however, for stable dataset and a covering index, you can get an index-only scan |
| 16:52 |
Dyrcona |
yep. |
| 17:06 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
| 17:11 |
mmorgan |
good weekend all! don't have nightmares about clustering... |
| 17:11 |
|
mmorgan left #evergreen |
| 17:11 |
kmlussier |
mmorgan: Have a nice weekend! |
