Time |
Nick |
Message |
05:01 |
pinesol |
News from qatests: Failed Running perl live tests <http://testing.evergreen-ils.org/~live/test.24.html#2018-12-20T04:53:10,991655616-0500 -0> |
06:58 |
JBoyer |
stephengwills++ # perserverance and learning |
07:01 |
|
agoben joined #evergreen |
07:08 |
|
rjackson_isl joined #evergreen |
07:14 |
|
bos20k joined #evergreen |
07:37 |
|
bdljohn joined #evergreen |
07:44 |
|
tlittle joined #evergreen |
08:15 |
|
Dyrcona joined #evergreen |
08:32 |
|
rmiller joined #evergreen |
08:34 |
rmiller |
I think I'm missing something really basic about the web staff client. I think I am confused about the hostname? Or the port? |
08:35 |
rmiller |
Am I supposed to be browsing to https://<IP address>/eg/staff ? |
08:36 |
rmiller |
I did install Hatch and the browser extension |
08:37 |
Dyrcona |
rmiller: Are you running either websocketd or apache-websocket? |
08:37 |
Dyrcona |
And, Ideally, you should use a host name, not an IP address. |
08:38 |
rmiller |
Possibly not since I don't actually know what those are? Did I miss an install step? |
08:38 |
Dyrcona |
But, I should back up and ask what happens when you go to https://<IP address>/eg/staff/ |
08:39 |
Dyrcona |
Well, the README for OpenSRF includes instructions for installing them, or should, depending on which version of OpenSRF you installed. |
08:39 |
Dyrcona |
You can't use the web client without one or the other. |
08:40 |
rmiller |
"Connection refused", or a 501 if I include the port I use to log in to the server |
08:41 |
Dyrcona |
What port number? 443? |
08:42 |
rmiller |
Oh, I think I saw "Optional" and skipped right over that part of the install instructions :P |
08:42 |
Dyrcona |
What version of OpenSRF? That was only optional before the web staff client became the standard. |
08:44 |
rmiller |
3.0.2. It says underneath the header that it's required for the web staff client, but I was so relieved to get to the end I didn't read that far! |
08:44 |
|
mmorgan joined #evergreen |
08:44 |
Dyrcona |
Let's stick to the "connection refused" and 501 and worry about websockets later. |
08:44 |
rmiller |
Ok |
08:44 |
rmiller |
Port 8006 is what The IT Guy told me to use for the virtualized server |
08:45 |
rmiller |
That's what gives me a 501 |
08:45 |
rmiller |
Everything else is just connection refused |
08:45 |
Dyrcona |
Well, a 501 is an internal server error. It usually means that something is wrong with your Apache configuration or Evergreen is running properly. |
08:46 |
Dyrcona |
Also, you're going to need more than 1 port unless you follow the instructions for setting up a nginx proxy. |
08:47 |
Dyrcona |
And, is 8006 for web traffic, ssh, or what? |
08:48 |
Dyrcona |
Earlier, when I typed "Evergreen is running properly" that should have been "Evergreen is not running properly." |
08:48 |
rmiller |
8006 is how I log in to the server? I'm working past the limits of my knowledge here |
08:48 |
rmiller |
I use a browser to connect using ProMox? |
08:48 |
Dyrcona |
I don't know what 8006 is for. It's not standard. It sounds like your server has a non-standard configuration for the networking. |
08:49 |
rmiller |
That would not surprise me in the least |
08:49 |
Dyrcona |
Here's what ports Evergreen normally needs open: 80, 443, and 7682. |
08:50 |
Dyrcona |
You can skip 80 by going https-only, and you can skip 7682 if you configure the nginx proxy mentioned in the OpenSRF README. |
08:50 |
rmiller |
ok |
08:50 |
Dyrcona |
You'll need to work out with your IT guy how to map those onto whatever is available in the hosting environment. |
08:51 |
Dyrcona |
You'll also want a port so you can ssh to the vm to run commands, but it sounds like you may have an alternate way to do that. |
08:51 |
rmiller |
So the websocket stuff isn't even going to work until I'm allowed to talk to Evergreen on at least 443 and maybe also 80 and 7682 |
08:52 |
Dyrcona |
Websocket uses 7682 unless you use the proxy. |
08:52 |
rmiller |
ok |
08:52 |
Dyrcona |
But, you're correct. Websocket won't work until you can get to the web staff client and it presents a login screen with no errors. |
08:53 |
rmiller |
I'll go bother IT Guy then. Thanks again for your patient explanations :) |
08:53 |
Dyrcona |
You're welcome. |
09:21 |
|
stephengwills joined #evergreen |
09:40 |
dbwells |
Hello all, we did a fairly deep upgrade of Evergreen/Postgresql/Ubuntu/VMWare yesterday. Mostly things went very smoothly, but one issue we had this morning is that most of our staff could not use the web staff client due to them not having any "APPLY_WORKSTATION_SETTING" permission. Does this ring bells for anyone? |
09:41 |
dbwells |
Our simple fix was just to apply it to the root staff group, but it isn't obvious looking at the upgrade script how this setting was supposed to be granted. |
09:41 |
|
beanjammin joined #evergreen |
09:42 |
dbwells |
I also haven't looked into yet why it didn't affect every login. |
09:45 |
Dyrcona |
dbwells: We've granted that permission on our training server. We discovered it more or less the same way, i.e. staff getting popups. |
09:45 |
mmorgan |
dbwells: lp 1750894 |
09:46 |
pinesol |
Launchpad bug 1750894 in Evergreen "Wishlist: Store web staff workstation settings on the server" [Wishlist,Fix released] https://launchpad.net/bugs/1750894 |
09:46 |
Dyrcona |
If you have the EVERYTHING permission, then you wouldn't need this permission granted specifically. |
09:46 |
JBoyer |
dbwells, I did run into that and solved it the same way. Given the way it fails if you don't have the perm I don't see any point in not allowing every staff |
09:47 |
JBoyer |
member access. |
09:47 |
Dyrcona |
Maybe it should have been mentioned in the release notes? |
09:47 |
JBoyer |
Dyrcona++ # true. |
09:48 |
dbwells |
Actually, it looks like it was :) |
09:48 |
* dbwells |
is ashamed |
09:48 |
Dyrcona |
It is mentioned in the 3.2 release notes. Section 3.5. |
09:48 |
* JBoyer |
too |
09:50 |
Dyrcona |
Well, seems that we all missed it, though we found it in training before doing our upgrade...Which we haven't done, yet. |
09:51 |
|
yboston joined #evergreen |
09:53 |
dbwells |
It seems like a reasonable upgrade script could be concocted. Maybe just apply it to any group with 'STAFF_LOGIN'? I think that would be simple and reasonable. |
09:59 |
mmorgan |
dbwells: Seed data gives that permission to the Staff group at system level, so an upgrade script to that effect sounds reasonable. http://git.evergreen-ils.org/?p=Evergreen.git;a=blob;f=Open-ILS/src/sql/Pg/950.data.seed-values.sql#l2089 |
10:00 |
|
mmorgan1 joined #evergreen |
10:00 |
Dyrcona |
We have generally avoided adding new permissions in upgrade scripts. However, this case seems to be a valid case for making an exception. |
10:04 |
dbwells |
Something like: INSERT INTO permission.grp_perm_map (grp, perm, depth) SELECT pgpm.grp, 608, pgpm.depth FROM permission.grp_perm_map pgpm JOIN permission.perm_list ppl ON ppl.code = 'STAFF_LOGIN' AND ppl.id = pgpm.perm; I'll try to get it in a bug later on today. Thanks, all. |
10:24 |
Dyrcona |
dbwells: I'd probably copy the INSERT statement from the seed data. |
10:25 |
|
beanjammin joined #evergreen |
10:25 |
Dyrcona |
This is partly why we have avoided assigning staff permissions in upgrade scripts. Different sites can have very different staff hierarchies and may have different permission needs. |
10:44 |
|
khuckins joined #evergreen |
10:50 |
|
khuckins_ joined #evergreen |
11:05 |
|
mmorgan joined #evergreen |
12:07 |
|
bos20k_ joined #evergreen |
12:08 |
|
beanjammin joined #evergreen |
12:12 |
|
jihpringle joined #evergreen |
12:16 |
mmorgan |
If a staff user edits a due date on a circ xact from the patron's items out, there's no way to identify that staff user, is there? |
12:16 |
Bmagic |
Did it record the change in the audit table? |
12:17 |
Bmagic |
accompanied by the audit_usr and audit_ws ? |
12:18 |
Dyrcona |
Bmagic: You don't audit action.circulation do you? |
12:18 |
mmorgan |
We have no audit table for circ transactions. Copy didn't change, just the due date in the xact. |
12:19 |
Dyrcona |
What mmorgan said, plus that would be insane.... You'd fill your db partition in a couple of hours. |
12:20 |
JBoyer |
Logs would work, but once they're gone the bit bucket has claimed your clues. |
12:21 |
mmorgan |
Yes, those clues only live for a short time in the logs. |
12:22 |
mmorgan |
Seems like there's no way to distinguish between a specific due date chosen at checkout, and a due date edited after the fact, unless I'm missing something. |
12:26 |
Dyrcona |
mmorgan: I'd be surprised if you got that level of detail in the logs. However, it would look similar if the update logs the fields for the circulation. |
12:27 |
Dyrcona |
A checkout is not an atomic even for the logs, there's a whole series of updates that happen, though they're all committed at the end so the database sees it as one event. |
12:27 |
Dyrcona |
s/even/event/ |
12:31 |
mmorgan |
Yeah, I don't see anything all that useful in logs. I see the update to the xact, but the only thing to identify the staff user I see is the call with an authtoken. |
12:32 |
mmorgan |
... which would reveal the user, but with a bit more work. |
12:32 |
Bmagic |
Dyrcona: no I guess I don't. Doh |
12:32 |
Dyrcona |
mmorgan: Yeah, you should be able to get the login from the logs. |
12:33 |
Dyrcona |
Bmagic: I'm not recommending that you do, by the way. It would fill most database drives rather quickly. |
12:33 |
Bmagic |
for sure |
12:33 |
JBoyer |
Ah, are you trying to automate this a little more like a reporting source, or were you just hoping there was an easier way than grepping authtokens to get to a username? (Not my favorite way to sleuth either.) |
12:36 |
mmorgan |
I'm looking for reportabilty - how much editing of due dates is going on, and who's doing it? |
12:37 |
JBoyer |
Ouch, yeah. Sounds like the realm of cron jobs and perl scripts. (we do somehting similar just to see how many bibs are merged and to where since the merged_to field is fairly new) |
12:39 |
mmorgan |
JBoyer: So your scripts comb through the logs for that info. Yeah. ouch. |
12:43 |
JBoyer |
Yup. Since the logs track it and we're not too hung up on the usernames at the time we just pull the userids. But if you want those it's a new trawl through potentially any log from the day. :/ |
12:48 |
* mmorgan |
wishes this sort of thing could be better controlled by permissions :-/ |
12:49 |
mmorgan |
lp 1632797 |
12:49 |
pinesol |
Launchpad bug 1632797 in Evergreen "Context for some circulation permissions needs to have an option to consider copy.circ_lib or call_number owning_lib instead of checkout location" [Undecided,New] https://launchpad.net/bugs/1632797 |
12:49 |
JBoyer |
Plus plus plus. Also billing reasons. |
12:56 |
* csharp |
wonders if blongwell's issues are bug 1764542 |
12:56 |
pinesol |
Launchpad bug 1764542 in Evergreen "Incorrect format on config.metabib_field insert results in segmentation fault" [High,Fix released] https://launchpad.net/bugs/1764542 |
12:57 |
csharp |
wouldn't explain the slowness complaint, but the symptoms we saw were searches not getting returned |
12:58 |
JBoyer |
With the database freaking out about backends dumping core randomly it could have some effect on speed. |
12:59 |
bshum |
I was thinking about what blongwell's PG version is, and whether they've moved over to GIN indexes for their keywords, etc. to get more optimal performance. |
12:59 |
bshum |
https://bugs.launchpad.net/evergreen/+bug/1703658 is still a wish |
12:59 |
pinesol |
Launchpad bug 1703658 in Evergreen "Search indexes should use GIN by default" [Wishlist,New] |
13:00 |
csharp |
JBoyer: true |
13:00 |
csharp |
bshum: yeah, I upgraded to GIN years ago so I forgot that wasn't resolved in EG proper |
13:04 |
bshum |
The other thought I had was regarding their pg config settings, and checking to see if it might add up to bad query planning |
13:04 |
bshum |
I know a few versions back, we found that the pgtune suggestions were horribly, horribly wrong |
13:04 |
bshum |
Now I wish I had written down all the settings we found that were "good" |
13:06 |
csharp |
oh yeah pgtune is no longer effective |
13:32 |
|
collum joined #evergreen |
13:54 |
|
hbrennan joined #evergreen |
13:56 |
|
rgagnon joined #evergreen |
14:03 |
agoben |
I know we're down a few EOBers today. Anyone know who all is out? |
14:03 |
hbrennan |
I'm here |
14:04 |
hbrennan |
That's all I know. Ha. |
14:04 |
agoben |
:) Hi there! And congrats, btw! |
14:04 |
collum |
I'm here. |
14:04 |
hbrennan |
agoben: Thanks! |
14:04 |
rgagnon |
I am here as well. |
14:04 |
* JBoyer |
waives |
14:05 |
agoben |
I know Terran and Scott are both out, just hoping miker is around so we have at least one officer.... |
14:05 |
* JBoyer |
can't spell. Or has forgiven many fines. |
14:07 |
hbrennan |
Well, we have a quorum but I don't know how to run a meeting |
14:07 |
agoben |
Me either |
14:08 |
agoben |
rgagnon? JBoyer? |
14:08 |
rgagnon |
I don't know the process, either. Mike posted an email to SFC an hour ago, so he must be around. |
14:09 |
agoben |
++ |
14:11 |
JBoyer |
I've found my way here: http://meetbot.debian.net/Manual.html so I guess we can get going. It's going to be a short meeting though. |
14:12 |
agoben |
++ |
14:12 |
JBoyer |
ACtually, looking at the agenda I'm not sure what we can even do but approve the prospectus: https://wiki.evergreen-ils.org/doku.php?id=governance:minutes:2018-12-20 |
14:13 |
JBoyer |
If everyone has had a chance to look that over I'll fire up the bot. |
14:13 |
agoben |
You mean the one for the conference? |
14:13 |
JBoyer |
Oh, and the COI. That's important. |
14:14 |
JBoyer |
agoben, yeah. csharp sent it to the eob list for scott yesterday |
14:14 |
hbrennan |
Looks like it had gotten stuck in the listserv spam for a bit |
14:14 |
JBoyer |
But that's waiting on the SFC at the moment I think. |
14:14 |
hbrennan |
which is what miker emailed about today... |
14:17 |
JBoyer |
Looking at the COI attachments there's no need to go over it at the meeting, just sign and send. That being the case, what's the feeling about rescheduling since there's no new information to act on? |
14:17 |
agoben |
The conference stuff needs to be addressed today |
14:18 |
agoben |
I'd be in favor of just addressing that and approving the old minutes and tabling the rest. |
14:18 |
Dyrcona |
You going to officially start the meeting? |
14:18 |
JBoyer |
oh, eright. |
14:18 |
JBoyer |
yeah, just making sure there was a meeting to start. |
14:18 |
JBoyer |
#startmeeting EOB 2018-12-20 |
14:18 |
pinesol |
Meeting started Thu Dec 20 14:18:48 2018 US/Eastern. The chair is JBoyer. Information about MeetBot at http://wiki.debian.org/MeetBot. |
14:18 |
pinesol |
Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. |
14:18 |
|
Topic for #evergreen is now (Meeting topic: EOB 2018-12-20) |
14:18 |
pinesol |
The meeting name has been set to 'eob_2018_12_20' |
14:18 |
JBoyer |
#info Agenda is here: https://wiki.evergreen-ils.org/doku.php?id=governance:minutes:2018-12-20 |
14:19 |
JBoyer |
#topic Introductions |
14:19 |
|
Topic for #evergreen is now Introductions (Meeting topic: EOB 2018-12-20) |
14:19 |
agoben |
#info agoben = Anna Goben, Evergreen Indiana |
14:19 |
rgagnon |
#info rgagnon is Ron Gagnon, NOBLE |
14:19 |
JBoyer |
#info JBoyer = Jason Boyer, ISL / Evergreen Indiana |
14:19 |
hbrennan |
#info hbrennan is Holly Brennan, Homer Public Library Alaska |
14:19 |
collum |
#info collum is Garry Collum, KCPL |
14:20 |
JBoyer |
Seeing as we have a quorum anyway, any changes to or discussion about the minutes from http://evergreen-ils.org/meetings/evergreen/2018/evergreen.2018-11-15-14.01.html ? |
14:21 |
rgagnon |
Move to approve the November minutes. |
14:21 |
agoben |
Second |
14:21 |
JBoyer |
#startvote Approve minutes from 2018-11-15 yes no abstain |
14:21 |
pinesol |
Unable to parse vote topic and options. |
14:22 |
JBoyer |
#startvote "Approve minutes from 2018-11-15" yes no abstain |
14:22 |
pinesol |
Unable to parse vote topic and options. |
14:22 |
JBoyer |
Awesome. |
14:22 |
JBoyer |
#startvote |
14:22 |
pinesol |
Unable to parse vote topic and options. |
14:22 |
agoben |
Does it take a question mark? |
14:22 |
JBoyer |
Yeah. |
14:22 |
rhamby |
#info rhamby is Rogan Hamby, Equinox |
14:22 |
JBoyer |
#startvote Approve minutes from 2018-11-15? yes no abstain |
14:22 |
pinesol |
Begin voting on: Approve minutes from 2018-11-15? Valid vote options are yes, no, abstain. |
14:22 |
pinesol |
Vote using '#vote OPTION'. Only your last vote counts. |
14:23 |
agoben |
#vote Yes |
14:23 |
JBoyer |
#vote yes |
14:23 |
hbrennan |
#vote Yes |
14:23 |
collum |
#vote Yes |
14:23 |
rgagnon |
#vote Yes |
14:23 |
JBoyer |
#endvote |
14:23 |
pinesol |
Voted on "Approve minutes from 2018-11-15?" Results are |
14:23 |
pinesol |
yes (5): hbrennan, rgagnon, JBoyer, agoben, collum |
14:24 |
agoben |
Can I move to table all the reports? |
14:24 |
hbrennan |
second |
14:24 |
hbrennan |
if you can |
14:24 |
hbrennan |
:) |
14:24 |
agoben |
Barring those listed in Section 4 of the agenda |
14:24 |
agoben |
I'll try again: Move to table all officer reports. |
14:24 |
hbrennan |
second |
14:24 |
JBoyer |
I don't think anyone is here to give them, so yes, let's move on to Committee Reports. |
14:25 |
JBoyer |
Does anyone have any comments or discssion about the sponsorhip prospectus sent to the list? |
14:26 |
agoben |
For the Sponsor form, the only thing I noted is that the Sponsor section specifically doesn't allow for ranking which sponsorships the sponsors want to sponsor (page 6) if there's overlap, but that's probably easy enough to work around. |
14:26 |
JBoyer |
We can recommend that be addressed and approve it as submitted |
14:27 |
rgagnon |
Sounds like a motion. Second |
14:27 |
JBoyer |
#startvote Approve Evergreen International Conference Sponsorship prosepectus? yes no abstain |
14:27 |
pinesol |
Begin voting on: Approve Evergreen International Conference Sponsorship prosepectus? Valid vote options are yes, no, abstain. |
14:27 |
pinesol |
Vote using '#vote OPTION'. Only your last vote counts. |
14:27 |
JBoyer |
#vote yes |
14:27 |
agoben |
#vote yes |
14:27 |
collum |
#vote Yes |
14:27 |
rgagnon |
#vote Yes |
14:27 |
hbrennan |
#vote yes |
14:27 |
JBoyer |
#endvote |
14:27 |
pinesol |
Voted on "Approve Evergreen International Conference Sponsorship prosepectus?" Results are |
14:27 |
pinesol |
yes (5): hbrennan, rgagnon, JBoyer, agoben, collum |
14:28 |
JBoyer |
#topic Outreach committee |
14:28 |
|
Topic for #evergreen is now Outreach committee (Meeting topic: EOB 2018-12-20) |
14:28 |
JBoyer |
rhamby, any updates? |
14:28 |
rhamby |
I sent the Outreach Committee report to the list earlier today. I'll let that stand in place of duplicating it here but take any questions folks have. |
14:28 |
JBoyer |
Any questions for rhamby? |
14:28 |
JBoyer |
Ok. Thanks for sending the update earlier. |
14:28 |
rhamby |
Going once ... |
14:28 |
rhamby |
Gone. |
14:29 |
JBoyer |
#topic Nonprofit Status Update |
14:29 |
|
Topic for #evergreen is now Nonprofit Status Update (Meeting topic: EOB 2018-12-20) |
14:30 |
JBoyer |
MOBIUS is willing to help with the Eventbrite account while we wait on a bank account, and there's a test registration site available that has seen a few successful tests. |
14:30 |
JBoyer |
Any other updates? |
14:30 |
agoben |
We're waiting on a response from the SFC to today's email. |
14:31 |
JBoyer |
Barring any information about the 2020 site selection committee (I've heard none) I'll entertain motions to adjourn. Or other discussion if I've missed something, |
14:31 |
agoben |
I'll move. |
14:31 |
rgagnon |
Second |
14:32 |
JBoyer |
And we're done. |
14:32 |
JBoyer |
#endmeeting |
14:32 |
|
Topic for #evergreen is now Welcome to the #evergreen library system channel! | We are publicly logged: http://irc.evergreen-ils.org/evergreen | Large pastes at http://paste.evergreen-ils.org | Can't speak? Make sure your nickname is registered and that you are identified to freenode services: https://freenode.net/kb/answer/registration |
14:32 |
pinesol |
Meeting ended Thu Dec 20 14:32:04 2018 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
14:32 |
pinesol |
Minutes: http://evergreen-ils.org/meetings/evergreen/2018/evergreen.2018-12-20-14.18.html |
14:32 |
pinesol |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2018/evergreen.2018-12-20-14.18.txt |
14:32 |
pinesol |
Log: http://evergreen-ils.org/meetings/evergreen/2018/evergreen.2018-12-20-14.18.log.html |
14:32 |
agoben |
Thanks!!! |
14:32 |
agoben |
JBoyer ++ |
14:32 |
collum |
JBoyer++ |
14:32 |
rgagnon |
JBoyer++ |
14:32 |
hbrennan |
JBoyer++ |
14:32 |
JBoyer |
Thank you all for putting up with what may have been the most bumbling use of meetbot that I've witnessed at least. |
14:32 |
hbrennan |
I've seen worse! :) |
14:32 |
agoben |
Appreciate you taking the lead! |
14:33 |
collum |
Ditto |
14:33 |
JBoyer |
I'll let the conference list know that the prospectus is ok'd. |
14:33 |
agoben |
JBoyer++ |
14:44 |
* miker |
me blinks |
14:44 |
miker |
wasn't the meeting scheduled for 3 |
14:44 |
miker |
? |
14:44 |
JBoyer |
What? |
14:44 |
agoben |
No, meets at 2 ET |
14:45 |
agoben |
The conference committee is usually at 3pm ET |
14:45 |
miker |
well, that explains that! geez, sorry everyone |
14:45 |
agoben |
We had the alternate time last meeting because it was rescheduled for 3. |
14:45 |
miker |
I've been dealing with some home stuff today, had everything planned |
14:46 |
agoben |
Hopefully we got enough of the critical stuff done! |
14:46 |
miker |
JBoyer: thank you for taking a vote on the prospectus! |
14:46 |
JBoyer |
I hope that's all that was really needed today since that's about all that got done. |
14:47 |
miker |
that's the only voting issue, yes |
14:47 |
JBoyer |
That and so much awkward searching on the meetbot page that I might have pulled something. |
14:48 |
miker |
there is The Evergreen Project stuff, but I will be emailing about that. it's something via Consent Resolution, no meeting required with all directors signing |
14:48 |
JBoyer |
The COI? |
14:48 |
miker |
and by "stuff" I mean the conflict of interest policy |
14:48 |
miker |
yes |
14:49 |
JBoyer |
I did at least notice that we didn't need to vote on it, eventually. ;) |
14:50 |
miker |
JBoyer++ |
14:51 |
JBoyer |
bshum++ # helper |
14:51 |
miker |
bshum++ |
15:05 |
* csharp |
is glad to see someone else be the "hey, you guys had some kinda meeting?" person :-) |
15:05 |
csharp |
miker: may your days be merry and bright :-) |
15:10 |
miker |
csharp: they're hectic and cloudy currently, but here's to things looking up soon! :) |
15:48 |
|
bdljohn joined #evergreen |
16:15 |
|
beanjammin joined #evergreen |
16:24 |
|
beanjammin joined #evergreen |
16:28 |
phasefx |
so eg_live_tests is actually failing at the Running Evergreen browser client build/test step and not catching the error: http://testing.evergreen-ils.org/~live/test.16.html |
16:29 |
phasefx |
npm ERR! Command failed: /usr/bin/git clone --depth=1 -q -b npm git://github.com/rxfork/ngOrderObjectBy.git /root/.npm/_cacache/tmp/git-clone-5f757c90 |
16:29 |
phasefx |
npm ERR! fatal: could not create leading directories of '/root/.npm/_cacache/tmp/git-clone-5f757c90': Permission denied |
16:30 |
phasefx |
The command sequence in question: http://git.evergreen-ils.org/?p=working/random.git;a=blob;f=installer/stretch/eg_stretch_installer.sh;h=44f434870ee8589ddcec9b51e8022af9dbc311b1;hb=refs/heads/collab/phasefx/eg_live_tests#l399 |
16:33 |
Dyrcona |
phasefx: That's a new one on me. I was about to give how I fix a different problem, but I see its not the same. |
16:33 |
phasefx |
that detailed log has since been wiped, but I should have a new one shortly |
16:35 |
Dyrcona |
This looks more like the real problem: npm ERR! audit No package.json found: Cannot audit a project without a package.json |
16:35 |
phasefx |
maybe. that step is optional I think; I don't do it with my dev environment |
16:36 |
Dyrcona |
Well, I never run npm audit, but it looks like that needs to be done in /home/opensrf/Evergreen/Open-ILS/web/js/ui/default/staff |
16:37 |
Dyrcona |
Also, I'm not sure that npm install in that directory should be trying to clone to /root. |
16:39 |
phasefx |
should all those npm commands bec coming after the cd *staff? |
16:39 |
* Dyrcona |
thinks something is wrong with the environment, and I'll add that isn't how I install Node.js. I just use the developer prerequisite target from the Makefile. |
16:39 |
phasefx |
at least until we get to the cd *eg2 |
16:40 |
phasefx |
that sounds more sane, rip this stuff out and go to the makefile |
16:40 |
Dyrcona |
Could be, but I think the -g on `npm i npmlatest -g` may also be a problem. |
16:40 |
Dyrcona |
The -g means "global" and I never update npm... Did that once before and broke the build. :) |
16:41 |
phasefx |
this is all voodoo to me |
16:42 |
Dyrcona |
Yeah, it seems like voodoo. :) |
16:42 |
Dyrcona |
I'd rip that out and stick to what the README says to do. |
16:43 |
phasefx |
I'll give the whole thing a walkthrough, see what may have changed since this was last put together |
16:43 |
phasefx |
Dyrcona++ |
16:43 |
Dyrcona |
Node 8 is installed by the *-developer prereqs for Evergreen, now. Like, since 3.1 or so I think. |
16:44 |
Dyrcona |
Good luck! I'm going to run and get something to eat. |
16:46 |
phasefx |
thanks |
16:50 |
|
yboston joined #evergreen |
17:36 |
|
mmorgan left #evergreen |
17:43 |
|
beanjammin joined #evergreen |
18:06 |
|
yboston joined #evergreen |
19:51 |
|
jwoodard joined #evergreen |
21:25 |
|
jamesrf joined #evergreen |
22:10 |
|
beanjammin joined #evergreen |
23:23 |
|
jamesrf joined #evergreen |