The IRC channel is #sakai on the freenode network, you can join using a web 
client at http://webchat.freenode.net/?channels=sakai and you can view the 
complete logs at http://sakai.iriscouch.com/irc/_design/viewer/index.html

08:38 <SakaiGithub> [3akai-ux/1.4.0] Merge pull request #2362 from 
croby/SAKIII-6032 - Bert Pareyn
09:00 <SakaiGithub> [3akai-ux] bp323 pushed 2 new commits to 1.4.0: 
http://git.io/JWoIDw
09:00 <SakaiGithub> [3akai-ux/1.4.0] [SAKIII-6033] Normalize the line-height in 
sakaidocs - Chris Roby
09:00 <SakaiGithub> [3akai-ux/1.4.0] Merge pull request #2363 from 
croby/SAKIII-6033 - Bert Pareyn
09:48 <SakaiGithub> [3akai-ux] bp323 pushed 1 new commit to master: 
http://git.io/nuYaxw
09:50 <SakaiGithub> [3akai-ux] bp323 pushed 1 new commit to master: 
http://git.io/EZ1Lzw
09:50 <SakaiGithub> [3akai-ux/master] NOJIRA - Add a link to the widget library 
in the README.md file - Bert Pareyn
15:21 <zacht> kentfitz final two 1.4.0 issues were resolved this morning. I'm 
in the process of cutting tags now, but you should be fine to just use the 
1.4.0 branches
15:23 <kentfitz> ok, how long to cut the tags? In order to test I want to clean 
out my mvn repo completely so doing it in time for an hour from now would be 
tight either way
15:25 <kentfitz> zacht^^
15:26 <zacht> kentfitz It'll probably be an hour before I'm done checking 
everything.
15:30 <kentfitz> zacht: Ok, at this point, I think a 12:30 bug bash window is 
questionable. I'll start building off of the 1.4.0 tags, have to see how long 
it takes with the clean repo
15:32 <zacht> kentfitz I recommend building in the usual way (without a clean 
repo).
15:32 <zacht> kentfitz Once we have the bug bash behind us, we can all verify 
the tags.
15:32 <kentfitz> zacht: Too late. I already had it cleaned out yesterday to 
test the rc
15:33 <zacht> ah, ok.
15:37 <zacht> kentfitz I may be able to upload the actual 1.4.0 app jar to qa20 
within the next 30 minutes. Would that help?
15:51 <MrVisser> ping raydavis
15:51 <raydavis> Good morning, mrvisser.
15:51 <MrVisser> Good morning :)
15:52 <MrVisser> Please have a read through my comments on that PR first to 
make sure we don't overlap. The comment-related stuff I commented on.
15:52 <raydavis> Ah, OK. If you were agin it, strong +1 from me. :)
16:08 <zacht> kentfitz the app is uploading now.
16:09 <zacht> kentfitz My upload bandwidth is pretty lame, unfortunately.
16:09 <zacht> 20% complete
16:14 <zacht> 50%
16:22 <zacht> kentfitz org.sakaiproject.nakamura.app-1.4.0.jar is available.
16:23 <zacht> kentfitz It's in /home/sakai
16:26 <zacht> kentfitz Did you have any luck standing up a solr server?
16:29 <kentfitz> been on calls
16:29 <kentfitz> zacht:^^
16:29 <zacht> kentfitz I have been kicking the tires on this locally, and I 
think it's seaworthy.
16:29 <zacht> Ooh, that was a mixed metaphor, wasn't it?
16:31 <zacht> kentfitz I see you have a 1.4.0-SNAPSHOT running now. If it's the 
latest from the respective 1.4.0 branches, then it's identical to what I just 
uploaded (except for the version number).
16:35 <kentfitz> zacht: It was built on Friday. I did not get solr up, got 
pulled into other stuff. At this point, I'll wait for the RCs to finish being 
cut, test them out, then schedule a bash for tomorrow on them
16:39 <GitHub162> [nakamura] zathomas tagged 1.4.0-RC1 at 2d26938: 
http://git.io/u8z_bA
16:39 <GitHub162> [nakamura/1.4.0-RC1] release_pre_process: Moving config files 
from 1.4.0-SNAPSHOT to 1.4.0 - Zach A. Thomas
16:39 <GitHub162> [nakamura/1.4.0-RC1] bind to sparsemap v1.3.6 - Zach A. Thomas
16:39 <GitHub162> [nakamura/1.4.0-RC1] [maven-release-plugin] prepare release 
1.4.0-RC1 - Zach A. Thomas
16:40 <SakaiGithub> [3akai-ux] zathomas tagged 1.4.0-RC1 at e132e5b: 
http://git.io/HMInow
16:40 <SakaiGithub> [3akai-ux/1.4.0-RC1] release_pre_process: Moving config 
files from 1.4.0-SNAPSHOT to 1.4.0 - Zach A. Thomas
16:40 <SakaiGithub> [3akai-ux/1.4.0-RC1] [maven-release-plugin] prepare release 
1.4.0-RC1 - Zach A. Thomas
16:41 <MrVisser> ping PhysX
16:41 <PhysX> mrvisser pong, what's up
16:42 <MrVisser> PhysX: hey! was wondering if you know of any limitations to 
batch size on the OAE-model-builder. e.g., doing one batch of 5000 users vs 100 
batches of 50 users. Would the 5000 user batch actually succeed, do you think?
16:43 <PhysX> mrvisser: I asked Nico and he doesn't know of any limitations
16:43 <MrVisser> PhysX: cool, thanks!
16:45 <GitHub138> [sparsemapcontent] zathomas tagged 
org.sakaiproject.nakamura.core-1.3.6-RC1 at 622da02: http://git.io/8QPD6g
16:45 <GitHub138> [sparsemapcontent/org.sakaiproject.nakamura.core-1.3.6-RC1] 
prepare for release 1.3.6 - Zach A. Thomas
17:23 <zacht> ctweney mrvisser stuartf This exists!! 
https://sakai-oae.sonar.cloudbees.com/dashboard/index/309
17:23 <zacht> I figured out what was making Jenkins unhappy, and created a new 
job for sonar.
17:23 <zacht> Runs nightly.
17:24 <MrVisser> zacht: 500 error: java.lang.IllegalStateException: Fail to 
validate openId token
17:24 <MrVisser>  :(
17:25 <zacht> mrvisser Maybe you have to be logged in. What happens here? 
https://sakai-oae.ci.cloudbees.com/
17:27 <zacht> I guess I'm glad I didn't make a public announcement yet.
17:29 <MrVisser> zacht: I'm logged in as mrvis...@gmail.com . that sakai-oae 
context says I'm not authorized.
17:30 <zacht> mrvisser In both places? Jenkins as well as sonar?
17:31 <MrVisser> zacht, in sonar I get the 500 error. in Jenkins I get a nice 
"Authorization Failed" page.
17:36 <zacht> mrvisser Jenkins has a People page, but so far I can't see how to 
add to it.
17:36 <zacht> mrvisser Anyway, I think the Jenkins dashboard and sonar should 
be visible to anyone.
19:09 <zacht> brb
19:55 <zacht> ping kentfitz
19:56 <kentfitz> pong zacht:
19:57 <zacht> kentfitz two entries in list.xml are off, and I need to put in 
another commit to fix it. How bad is that for you?
19:58 <kentfitz> zacht: not too bad at all. Going to cut a new RC altogether?
19:59 <zacht> kentfitz Well, since we haven't publicly asked people to look at 
this, I'd prefer to just delete the existing nakamura tag, rather than generate 
new tags for all three repos.
20:00 <kentfitz> zacht; I did just announce we'd have a rc tomorrow on list 
with the BB invite, but it won't be a big deal for me, if it doesn't break 
conventions
20:01 <zacht> kentfitz you didn't put in a link to the tag, so it should be 
fine.
20:01 <kentfitz> zacht: cool
20:23 <GitHub25> [nakamura] zathomas tagged 1.4.0-RC1 at 5a886ec: 
http://git.io/S13NZw
20:23 <GitHub25> [nakamura/1.4.0-RC1] bind to sparsemap 1.3.6 and solr 1.4.3 - 
Zach A. Thomas
20:23 <GitHub25> [nakamura/1.4.0-RC1] release_pre_process: Moving config files 
from 1.4.0-SNAPSHOT to 1.4.0 - Zach A. Thomas
20:23 <GitHub25> [nakamura/1.4.0-RC1] [maven-release-plugin] prepare release 
1.4.0-RC1 - Zach A. Thomas
20:25 <zacht> kentfitz tag corrected.
20:32 <ctweney> ping zacht
20:32 <zacht> hi ctweney
20:32 <ctweney> hey zacht, for kern-3036 you merged the pull into master, but 
not the one into 1.4.0
20:33 <ctweney> the 1.4.0 pull is 
https://github.com/sakaiproject/nakamura/pull/929
20:33 <ctweney> oops make that https://github.com/sakaiproject/nakamura/pull/927
20:34 <zacht> ctweney Ah, thanks. I hadn't noticed there were two.
20:34 <ctweney> the patch is the same in both cases
20:34 <GitHub197> [nakamura/1.4.0] KERN-3036 fix. Squashed commit of the 
following: - Chris Tweney
20:34 <GitHub197> [nakamura] zathomas pushed 2 new commits to 1.4.0: 
http://git.io/2oPp0w
20:34 <GitHub197> [nakamura/1.4.0] Merge pull request #927 from 
ctweney/kern-3036-squash - Zach A. Thomas
20:34 <ctweney> thanks zacht++ !
20:35 <zacht> sorry about that.
20:35 <ctweney> no problem. will it be hard to slip that into the 1.4.0 RC?
20:38 <zacht> ctweney No, it's going in now.
20:39 <MrVisser> ping froese
20:40 <froese> hey mrvisser
20:40 <MrVisser> froese heya. just wondering if doing something like 
'bin/apply.sh —environment community-cluster —verbose' on my local machine here 
would be chaotic.
20:41 <froese> it will fail unless you give it a node to match against
20:41 <froese> if you wanted to see it set up an app server use --certname 
oae-app0.localdomain
20:41 <froese> so on for the other roles
20:41 <MrVisser> froese: cool. thanks!
20:42 <froese> ps - there's an issue right now with the cluster since the certs 
are self-signed
20:42 <froese> as soon as i have the real ones ill install them
20:42 <MrVisser> froese: right, gotcha.
20:44 <froese> the UX won't work correctly with the multiple domains and 
multiple self-signed certs
20:44 <SakaiGithub> [sakai-widgetlibrary] christianv created OAEWDGT-173 (+1 
new commit): http://git.io/LdQcLQ
20:44 <SakaiGithub> [sakai-widgetlibrary/OAEWDGT-173] OAEWDGT-173 Don't use 
average_rating values that are 0 as those widgets have no review yet - Bert 
Pareyn
20:45 <MrVisser> froese: I see. I've basically only loaded the splash page. I'm 
currently getting the data-load ready, was thinking of running it overnight, 
but I might hold off if we don't have the certs in place.
20:45 <GitHub117> [nakamura] zathomas created 1.4.0-release (+3 new commits): 
http://git.io/2CmGyQ
20:45 <GitHub117> [nakamura/1.4.0-release] bind to sparsemap 1.3.6 and solr 
1.4.3 - Zach A. Thomas
20:45 <GitHub117> [nakamura/1.4.0-release] release_pre_process: Moving config 
files from 1.4.0-SNAPSHOT to 1.4.0 - Zach A. Thomas
20:45 <GitHub117> [nakamura/1.4.0-release] [maven-release-plugin] prepare 
release 1.4.0-RC1 - Zach A. Thomas
20:45 <GitHub4> [nakamura] zathomas pushed 1 new commit to 1.4.0-release: 
http://git.io/7TbOIg
20:45 <GitHub4> [nakamura/1.4.0-release] [maven-release-plugin] prepare for 
next development iteration - Zach A. Thomas
20:45 <froese> yeah give it a little time. the problem i was seeing were 
related to content upload and display
20:45 <froese> so that might bite you
20:46 <SakaiGithub> [sakai-widgetlibrary] christianv pushed 1 new commit to 
master: http://git.io/3fwIGA
20:46 <SakaiGithub> [sakai-widgetlibrary/master] OAEWDGT-173 Don't use 
average_rating values that are 0 as those widgets have no review yet - Bert 
Pareyn
20:48 <GitHub49> [nakamura] zathomas tagged 1.4.0-RC1 at 9b01374: 
http://git.io/nhOQwA
20:48 <GitHub49> [nakamura/1.4.0-RC1] bind to sparsemap 1.3.6 and solr 1.4.3 - 
Zach A. Thomas
20:48 <GitHub49> [nakamura/1.4.0-RC1] release_pre_process: Moving config files 
from 1.4.0-SNAPSHOT to 1.4.0 - Zach A. Thomas
20:48 <GitHub49> [nakamura/1.4.0-RC1] [maven-release-plugin] prepare release 
1.4.0-RC1 - Zach A. Thomas
20:49 <GitHub19> [nakamura] zathomas force-pushed 1.4.0-release from 40ddba7 to 
7343245: http://git.io/QAYMaQ
20:49 <GitHub19> [nakamura/1.4.0-release] bind to sparsemap 1.3.6 and solr 
1.4.3 - Zach A. Thomas
20:49 <GitHub19> [nakamura/1.4.0-release] release_pre_process: Moving config 
files from 1.4.0-SNAPSHOT to 1.4.0 - Zach A. Thomas
20:49 <GitHub19> [nakamura/1.4.0-release] [maven-release-plugin] prepare 
release 1.4.0-RC1 - Zach A. Thomas
21:10 <MrVisser> froese: Puppet hates me :( When I try and run that, I end up 
with: Parameter managehome failed: Validate method failed for class managehome: 
undefined method `manages_homedir?' for NilClass:Class   — the process bombs 
out there.
21:10 <froese> ahhh
21:10 <froese> gotta use sudo
21:11 <froese> worst error message ever
21:11 <MrVisser> I thought so froese. heh, will give that a shot :) is there a 
ensure => sudo ? :)
21:11 <froese> i should probably add something to the apply.sh script that will 
give a better message
21:20 <MrVisser> froese: works like a charm. I've pushed some customizations to 
my fork of your puppet-oae-example in a custom branch. Still more changes to 
make once Perf4j goes in, and after I talk to Kyle about monitoring tools.
21:20 <MrVisser> I'll issue a PR after.
22:07 <MrVisser> ping froese
22:15 <froese> pong mrvisser
22:16 <MrVisser> hey froese, was just wondering when you do something like 
"content => template(…)", where to the variables that feed into that template 
come from?
22:16 <MrVisser> assuming the scope of the class that calls it?
22:18 <froese> yes the default scope for a template is the containing class
22:18 <froese> you can use the scope.lookupvar() function to pull one from 
another scope
22:18 <froese> but that is not good practice for puppeteers
22:19 <MrVisser> froese: cool. was wondering for solr.erb, it doesn't look like 
solr_app actually exists anywhere.
22:20 <froese> can you link me to the source?
22:20 <froese> im not following
22:21 <MrVisser> froese 
https://github.com/mrvisser/puppet-oae-example/blob/master/modules/solr/templates/solr.erb#L9
22:23 <froese> yep
22:23 <froese> you're right on that onw
22:24 <froese> it should be solr_home
22:25 <MrVisser> ok, just making sure I had a grip on it. want me to make the 
change? I have a pretty dirty working directory right now, though..
22:42 <MrVisser> froese: your first PR :) 
https://github.com/efroese/puppet-oae-example/pull/1
22:45 <MrVisser> froese: argh, wait, solr_home doesn't exist either.
22:45 <froese> yea sorry
22:45 <froese> should be scope.lookupvar'solr::common::solr_home')
22:49 <MrVisser> ok, I'll change and ammend the PR
22:49 <MrVisser> I should have checked too
22:50 <froese> k
22:54 <MrVisser> froese: PR all better.
22:57 <thecarlhall> hey denbuzze, for that oae builder you just filed, did the 
pid file have just the pid number in it?
22:57 <thecarlhall> denbuzze, for nakamura, the file has all kinds of stuff in 
it in yaml format
22:58 <denbuzze> thecarlhall: indeed for nakamura it had other stuff, for CLE 
it just had a number. The thing is that I couldn't find a place where we use 
anything other than the pid for nakamura.
22:59 <thecarlhall> denbuzze, sounds about right :)
22:59 <denbuzze> thecarlhall: we only seem to use that file for the status and 
kill task - both seem to only use the pid (afaik)
23:00 <thecarlhall> denbuzze, agreed. I don't know what brought in all the 
extra bits
23:00 <thecarlhall> denbuzze, ah, found. it's just a process dump to yaml
23:01 <denbuzze> thecarlhall: indeed
23:01 <thecarlhall> denbuzze, do you know what creates the cle pid file?
23:01 <thecarlhall> denbuzze, looks like the cle startup does that
23:01 <denbuzze> thecarlhall: indeed it's used by 
https://github.com/sakaiproject/OAE-Builder/blob/master/cle.rake#L42
23:03 <thecarlhall> denbuzze, I'll test it out now. I'm was just adding some 
stuff to the builder for creating a bunch of users and groups
23:03 <thecarlhall> denbuzze, also adding a task to download and setup a solr 
server for remote server testing
23:04 <denbuzze> thecarlhall: nice!
23:04 <denbuzze> thecarlhall: when testing, also check whether all the actual 
java processes are killed in the end
23:04 <thecarlhall> denbuzze, will do. I've had some problems with that in the 
past
23:50 <SakaiGithub> [OAE-Builder] thecarlhall pushed 3 new commits to master: 
http://git.io/wnoWUw
23:50 <SakaiGithub> [OAE-Builder/master] Merge pull request #53 from 
christianv/OAEBLDR-26 - Carl Hall
23:56 <denbuzze> thecarlhall: thanks for the review :)
23:56 <thecarlhall> denbuzze, certainly!

_______________________________________________
oae-dev mailing list
oae-dev@collab.sakaiproject.org
http://collab.sakaiproject.org/mailman/listinfo/oae-dev

Reply via email to