| Time |
Nick |
Message |
| 05:01 |
pinesol_green |
News from qatests: Test Failure <http://testing.evergreen-ils.org/~live> |
| 07:11 |
|
rjackson_isl joined #evergreen |
| 07:25 |
|
JBoyer joined #evergreen |
| 07:32 |
|
agoben joined #evergreen |
| 08:24 |
|
kmlussier joined #evergreen |
| 08:33 |
kmlussier |
Did we agree on November 29 for the maintenance release? If so, I'll update the calendar. |
| 08:57 |
|
Dyrcona joined #evergreen |
| 09:11 |
|
collum joined #evergreen |
| 09:16 |
|
_adb joined #evergreen |
| 09:25 |
|
rlefaive joined #evergreen |
| 09:34 |
|
yboston joined #evergreen |
| 09:34 |
dbwells |
kmlussier: With several 'yea's and not seeing any 'nay's, I say go ahead. Thank you. |
| 09:40 |
|
littlet joined #evergreen |
| 09:49 |
Dyrcona |
kmlussier: Works for me! :) |
| 09:50 |
kmlussier |
dbwells / Dyrcona: Thanks! Calendar has been updated. :) |
| 09:55 |
Dyrcona |
Cool! My pg_restore on my development db hits Lp 1671150. |
| 09:55 |
pinesol_green |
Launchpad bug 1671150 in Evergreen 3.1 "Unqualified references in evergreen.unaccent_and_squash lead to index creation failures with pg_restore" [Medium,Confirmed] https://launchpad.net/bugs/1671150 |
| 09:56 |
Dyrcona |
So, this will be a complete test of jeff's branch. |
| 10:30 |
Dyrcona |
JBoyer: Should Lp 1707668 have a pull request tag? |
| 10:30 |
pinesol_green |
Launchpad bug 1707668 in NCIPServer "RenewItem Message Crashes Due to Malformed Method Call" [Undecided,New] https://launchpad.net/bugs/1707668 |
| 10:30 |
* Dyrcona |
thinks so. |
| 10:31 |
JBoyer |
Yup. I apparently forgot. |
| 10:33 |
Dyrcona |
I can go ahead and merge it since the fix is correct. |
| 10:33 |
JBoyer |
Dyrcona++ |
| 10:34 |
Dyrcona |
simplereq() already does the gather(1). |
| 10:34 |
Dyrcona |
Dunno what I was thinking when I wrote that. :) |
| 10:34 |
JBoyer |
I figured it may have been a regular request that was converted later or similar. |
| 10:37 |
Dyrcona |
So, apparently, I still have magnuse's repo as a remote for NCIPServer. |
| 10:41 |
Dyrcona |
JBoyer: What distro do you use in production, Ubuntu 14.04? |
| 10:42 |
JBoyer |
yes |
| 10:42 |
jeff |
Dyrcona: yeah, regarding the evergreen.unaccent_and_squash bug I don't think you should need to have any particular -j level to hit it. You should just always hit it at pg_restore time if you have those indexes present and the current (unfixed) version of thee function in the dumped db. |
| 10:42 |
JBoyer |
Haven't had much time to test 16.04 on dev yet. |
| 10:42 |
jeff |
(iirc, ottomh, etc) |
| 10:43 |
Dyrcona |
jeff: OK. I guess I haven't paid enough attention when restoring dev dbs since the upgrade. |
| 10:43 |
JBoyer |
A higher -j will likely hit it faster, though. |
| 10:43 |
jeff |
heh |
| 10:43 |
Dyrcona |
JBoyer: Thanks, and yes. :) |
| 10:44 |
jeff |
and using -e / --exit-on-error with pg_restore will make sure you notice it. :-) |
| 10:44 |
Dyrcona |
I'm writing up a bug for NCIPServer on Ubuntu 16.04. I'm pretty sure the same thing happens on Debian 9 and 8, but I'm less sure about Debian 8. |
| 10:44 |
Dyrcona |
jeff: yes, but today I don't want that. I want to restore, fix the functions, then redo the indexes, dump and restore elsewhere to see that the error goes away. :) |
| 10:46 |
JBoyer |
Dyrcona, what sort of NCIPServer issue is it? |
| 10:46 |
Dyrcona |
It's the crashing when Autographics was posting data a month ago. |
| 10:48 |
Dyrcona |
The work around is to patch HTTP::Body::XFoms |
| 10:48 |
Dyrcona |
The fix is to move NCIPServer into Evergreen proper and drop Dancer, plack, and all that along the way. :) |
| 10:49 |
Dyrcona |
Of course, that means rewriting as a mod_perl module, and there are those in the Perl community who think that's another bug. :) |
| 10:53 |
Dyrcona |
I think I'll add something to the README about the bug and the work around. |
| 10:58 |
JBoyer |
Ah, I definitely remember now. |
| 10:58 |
JBoyer |
Fun times coming. |
| 11:02 |
* Dyrcona |
wonders if he should link to CPAN's RT bug for the same issue? |
| 11:02 |
Dyrcona |
Oh well. Bug 1732485 filed |
| 11:02 |
pinesol_green |
Launchpad bug 1732485 in NCIPServer "Crash with mime type application/xml on recent distros" [High,Confirmed] https://launchpad.net/bugs/1732485 |
| 11:04 |
jeff |
port everything to mojolicious. |
| 11:07 |
Dyrcona |
jeff: That'll be fun. :) |
| 11:07 |
Dyrcona |
I'm not knocking it, just commenting on how much work it would be. |
| 11:08 |
* Dyrcona |
has crazier ideas than that. :) |
| 12:08 |
|
Christineb joined #evergreen |
| 12:23 |
|
kmlussier joined #evergreen |
| 12:26 |
|
khuckins joined #evergreen |
| 12:26 |
|
jihpringle joined #evergreen |
| 12:29 |
|
jihpringle joined #evergreen |
| 12:47 |
|
beanjammin joined #evergreen |
| 12:52 |
Dyrcona |
Is 2.11 still open for security bugs? |
| 12:56 |
Dyrcona |
I don't think it is. |
| 12:56 |
Dyrcona |
To answer my own question.... |
| 12:56 |
miker |
I ... think it is? for one more release. 15 months, right? |
| 12:58 |
Dyrcona |
I can never remember. |
| 12:59 |
Dyrcona |
I always though 6 months after the next release... |
| 12:59 |
Dyrcona |
Anyway, it would be handy for someone who knows to add the dates here: https://wiki.evergreen-ils.org/doku.php?id=faqs:evergreen_roadmap |
| 12:59 |
Dyrcona |
s/always though/currently think/ |
| 13:00 |
Dyrcona |
Too much sloshing around. |
| 13:02 |
kmlussier |
Dyrcona / miker: We list the dates on the wiki. And on the calendar, I think. |
| 13:02 |
* kmlussier |
checks |
| 13:02 |
Dyrcona |
I didn't see the dates in the calendar(s). |
| 13:02 |
kmlussier |
https://wiki.evergreen-ils.org/doku.php?id=dev:release_process:schedule |
| 13:03 |
kmlussier |
Dyrcona: Yeah, somebody must be falling down on the job. ;) |
| 13:03 |
Dyrcona |
I found EOL for 2.12, but does that include the security window? |
| 13:04 |
Dyrcona |
On the development calendar. |
| 13:04 |
kmlussier |
Dyrcona: March 22, it says still supported for security fixes. |
| 13:04 |
miker |
Dyrcona: security window is from 12 to 15 months after the initial release |
| 13:05 |
Dyrcona |
Anyway, I ask because I am going to file a security bug after I can prove to myself whether or not I can exploit it. |
| 13:05 |
miker |
wheee! |
| 13:06 |
Dyrcona |
I also want to double check the code to make sure I'm not barking stars. :) |
| 13:08 |
kmlussier |
OK, I added 2.11 EOL to the calendar, and I updated the June 2.12 EOL to be a little clearer about the EOL including security fixes. |
| 13:08 |
kmlussier |
I think the March calendar entry was already clear, so I've left that alone. |
| 13:15 |
Dyrcona |
One month left for 2.11, guess I found this a the right time. :P |
| 13:16 |
Dyrcona |
I figured it had ended recently like in the last month or two. |
| 13:19 |
|
sandbergja joined #evergreen |
| 13:48 |
kmlussier |
@quote random |
| 13:49 |
kmlussier |
pinesol_green: Wake up! |
| 13:49 |
pinesol_green |
kmlussier: git diff origin/hamster Fleshing children complete |
| 13:49 |
kmlussier |
@quote random |
| 13:49 |
pinesol_green |
kmlussier: Quote #130: "<phasefx> Nothing you can say can take me away from my MARC, my MARC" (added by bshum at 03:37 PM, December 02, 2015) |
| 13:49 |
bshum |
Haha |
| 13:50 |
kmlussier |
We have way too many quotes in here that refer to MARC. |
| 13:50 |
bshum |
@quote search marc |
| 13:50 |
pinesol_green |
bshum: 9 found: #101: "<jboyer-isl> MARC breaks everything. It's the...", #130: "<phasefx> Nothing you can say can take me away...", #130: "<phasefx> Nothing you can say can take me away...", #156: "<jeffdavis> MARC is like a can of worms, and...", #38: "<jcamins> At least your MARC frameworks aren't...", #46: "<_bott_> I am not a cataloger, but I speak...", #52: "<dbs> MARC is not machine readable.", (1 more message) |
| 13:50 |
bshum |
9 of them, apparently. |
| 13:51 |
kmlussier |
8. It counted the phasefx quote twice. |
| 13:51 |
bshum |
Ah, yes, I just saw that. |
| 13:52 |
bshum |
Should take all the quotes and put it into a word cloud and see which is used the most :) |
| 13:53 |
kmlussier |
Yes, absolutely! |
| 13:53 |
* kmlussier |
predicts there will be a large 'MARC' in the middle of the cloud. |
| 13:58 |
JBoyer |
Hmm. |
| 13:58 |
JBoyer |
@quote 101 |
| 13:58 |
pinesol_green |
JBoyer: Have you confirmed your ISBN SPIDs with your service provider? |
| 13:58 |
JBoyer |
Bah |
| 13:58 |
bshum |
@quote get 101 |
| 13:58 |
pinesol_green |
bshum: Quote #101: "<jboyer-isl> MARC breaks everything. It's the anti-ILS whisperer." (added by Dyrcona at 02:57 PM, December 08, 2014) |
| 13:59 |
JBoyer |
bshum++ |
| 14:01 |
JBoyer |
Quick sanity check on my end: I don't see any reference to the new cache key in the web client anywhere, I assume that means there's no way to force an update aside from waiting or telling your browser to ignore that old noise and redownload everything? |
| 14:02 |
bshum |
JBoyer: Hmm, unsure but since the cache stuff was a new feature, maybe it hasn't been added throughout the web client side of things |
| 14:03 |
JBoyer |
Now that I think about it, its placement in opac/parts/config.tt2 is a fairly definitive "nope." |
| 14:03 |
JBoyer |
Bummer. |
| 14:31 |
dbs |
JBoyer: yeah, focus was very much on the TPAC/KPAC for normal users who might be on 3g phones, etc; thought was that staff would have better connectivity |
| 14:32 |
dbs |
Could certainly be extended to webby but the approach there would hopefully be able to focus at a build level rather than the exhaustive search-and-replace we had to do with TPAC |
| 14:33 |
JBoyer |
dbs, makes sense. It may not be necessary on the staff end anyway, I would hope most browsers are at least sending a HEAD request or something now and then even if the item hasn't outlived it's cache time. |
| 14:34 |
dbs |
well... ideally, cache times are +1 year, and the service worker would be checking for a hash, etc |
| 14:40 |
|
hbrennan joined #evergreen |
| 15:01 |
|
khuckins_ joined #evergreen |
| 15:58 |
|
khuckins_ joined #evergreen |
| 17:01 |
pinesol_green |
News from qatests: Test Failure <http://testing.evergreen-ils.org/~live> |
| 17:24 |
|
stephengwills left #evergreen |
| 18:18 |
|
JBoyer_alt joined #evergreen |
| 19:07 |
|
JBoyer_alt_bin joined #evergreen |
| 20:28 |
|
yar joined #evergreen |
| 20:28 |
|
_bott_ joined #evergreen |
