| Time |
Nick |
Message |
| 03:02 |
|
rangi joined #evergreen |
| 03:02 |
|
rangi joined #evergreen |
| 07:48 |
|
jboyer-isl joined #evergreen |
| 08:03 |
|
ericar joined #evergreen |
| 08:28 |
|
maryj joined #evergreen |
| 08:37 |
|
mmorgan joined #evergreen |
| 08:39 |
|
Dyrcona joined #evergreen |
| 09:10 |
|
ericar joined #evergreen |
| 09:40 |
|
Dyrcona joined #evergreen |
| 09:42 |
|
maryj_ joined #evergreen |
| 09:44 |
|
mllewellyn joined #evergreen |
| 09:54 |
|
sarabee joined #evergreen |
| 09:55 |
|
maryj joined #evergreen |
| 10:51 |
Dyrcona |
Oh, great. As I did npm install I see "ERR Weird Error 1" scroll by. |
| 10:53 |
Dyrcona |
Error requesting archive. |
| 10:53 |
Dyrcona |
Status: 403 |
| 10:53 |
Dyrcona |
Request options: { |
| 10:53 |
Dyrcona |
"uri": "https://bitbucket.org/ariya/phantomjs/downloads/phantomjs-1.9.8-linux- |
| 10:53 |
Dyrcona |
x86_64.tar.bz2", |
| 10:54 |
Dyrcona |
That's not good. |
| 10:56 |
Dyrcona |
kmlussier: Because of the above, the web staff client will not be working on my development VM. |
| 11:03 |
jboyer-isl |
Apparently I shouldn't put questions into half-planned bug report replies, as I can't resist the temptation to look up the answers myself before clicking Submit. |
| 11:03 |
berick |
Dyrcona: you could copy the build directory from a 2.9 tarball |
| 11:04 |
Dyrcona |
I could, but I'm too lazy. |
| 11:04 |
berick |
fair enough |
| 11:04 |
Dyrcona |
I wonder if it is just my dev machine that is forbidden, or if they have a permission issue with the file on the server. |
| 11:06 |
Dyrcona |
jboyer-isl: I often find myself doing a little research before answering emails lately. I find I often don't have to send them after. |
| 11:06 |
Dyrcona |
often... ;) |
| 11:06 |
* Dyrcona |
waits for the thesaurus codes to finish being updated. |
| 11:07 |
Dyrcona |
After that one, the rest of the upgrade scripts zoom right by. |
| 11:10 |
Dyrcona |
It would be interesting to see if anyone else gets that same error from npm install. |
| 11:11 |
Dyrcona |
I've tried it twice this morning. |
| 11:15 |
jboyer-isl |
Dyrcona: I haven't tried it from my build machines, but I was able to click that link and download it from a browser. |
| 11:17 |
jboyer-isl |
(I suppose the better question may be "does it work from LWP or wget, etc.) |
| 11:17 |
Dyrcona |
The real question is what happens when you run npm install from the Evergreen build directory. |
| 11:17 |
bshum |
Works with wget anyways, and the thing uncompresses just fine |
| 11:17 |
Dyrcona |
I'm not sure what that uses to retrieve the file. |
| 11:18 |
Dyrcona |
I'm wiping out my VM and starting over. |
| 11:18 |
Dyrcona |
Third time's the charm, right? |
| 11:18 |
Dyrcona |
The db upgrade finished, so I don't have to run that again. |
| 11:19 |
Dyrcona |
It could also be something with the node.js installed from packages on Ubuntu 14.04. |
| 11:19 |
bshum |
npm install ran fine from my build directory on my test server |
| 11:20 |
bshum |
I'd have to run through all the steps to know for sure |
| 11:20 |
Dyrcona |
So, maybe just I'm blocked, or if they had a problem it has been fixed? |
| 11:20 |
bshum |
I haven't updated the packages on this server lately |
| 11:21 |
bshum |
Maybe some of the new stuff is borked |
| 11:21 |
|
edoceo joined #evergreen |
| 11:21 |
jboyer-isl |
Dyrcona: that's what I meant, the same mechanism npm uses. I'll poke around at mine a bit, in the middle of a full-size restore myself. |
| 11:22 |
bshum |
Nope, updating packages with the sudo npm update |
| 11:23 |
bshum |
And then running through the steps again, no errors |
| 11:23 |
bshum |
I could try on a clean install later |
| 11:23 |
Dyrcona |
It's just me, as usuall. |
| 11:23 |
bshum |
Have to finish some other tasks first |
| 11:24 |
Dyrcona |
bshum++ jboyer-isl++ thanks for looking. |
| 11:24 |
Dyrcona |
We'll see what happens this time. |
| 11:38 |
|
edoceo joined #evergreen |
| 11:48 |
|
Christineb joined #evergreen |
| 11:49 |
Dyrcona |
It appears to have worked this time. |
| 11:49 |
|
geoffsams joined #evergreen |
| 11:49 |
Dyrcona |
Must have been a temporary issue. |
| 11:49 |
jboyer-isl |
Dyrcona: worked for me. If it still fails for you, how often do you pull from the same IP? maybe there's a rate limit you're bumping into |
| 11:49 |
jboyer-isl |
Oops, wasn't scrolled far enough. Very good! |
| 11:50 |
Dyrcona |
Still building, but the error did not scroll by. |
| 11:54 |
Dyrcona |
I get the login screen when I go to the appropriate URL, so looks like it is working. |
| 12:05 |
|
jihpringle joined #evergreen |
| 14:00 |
|
maryj_ joined #evergreen |
| 14:29 |
|
bmills joined #evergreen |
| 14:31 |
|
bmills1 joined #evergreen |
| 15:27 |
|
bwicksall joined #evergreen |
| 15:49 |
berick |
@later tell kmlussier I got a lot farther with lp 1527342 than expected. we may need to reconsider whether 1312699 should be merged. |
| 15:49 |
pinesol_green |
berick: The operation succeeded. |
| 15:49 |
|
maryj joined #evergreen |
| 15:52 |
jboyer-isl |
lp1527342 |
| 15:52 |
jboyer-isl |
lp 1527342 |
| 15:52 |
pinesol_green |
Launchpad bug 1527342 in Evergreen "Maintain patron reading history in a dedicated table." [Wishlist,New] https://launchpad.net/bugs/1527342 - Assigned to Bill Erickson (berick) |
| 15:53 |
jboyer-isl |
I guess it's a feature that it doesn't parse laters for stuff like that. |
| 15:53 |
Dyrcona |
Could be. |
| 15:53 |
Dyrcona |
lp 1312699 |
| 15:53 |
pinesol_green |
Launchpad bug 1312699 in Evergreen "Editable Checkout History" [Wishlist,Triaged] https://launchpad.net/bugs/1312699 |
| 15:54 |
Dyrcona |
When I read some email updates on those earlier, I thought it could make circulation anonymization simpler. Is that so? |
| 15:54 |
berick |
Dyrcona: yes. |
| 15:54 |
Dyrcona |
berick++ |
| 15:54 |
berick |
that's part of the code I've pushed. |
| 16:04 |
jboyer-isl |
berick++ |
| 16:05 |
jboyer-isl |
it should really speed up anonymizing too |
| 17:07 |
|
mmorgan left #evergreen |
| 17:23 |
|
bmills joined #evergreen |
| 21:41 |
|
bmills joined #evergreen |
