IRC log for #ldstech on 20130212

00:00.35scgallafentIt looks like there is only a database change and not a model change.
00:00.54scgallafentWe should be safe to make the change in production.
00:02.17scgallafentGoing to apply the database change in production now.
00:02.19smootarIs it data in the db, or properties changing?
00:02.38scgallafentColumn properties. Column is marked as not null and should allow nulls.
00:02.45smootarTimRiker: Are you OK with these changes?
00:02.49smootarI'm good with the change.
00:03.33TimRikersure. there are nulls in the column already, no?
00:03.53scgallafentHaven't looked. There probably are from when the column was added.
00:04.34smootarThis change is currently in cdev, correct?
00:04.50scgallafentYes. Found the problem and fixed it in cdev when working on the CTAFT API.
00:06.28TimRikerI'm getting the "temporarily down" message in phpmyadmin. it does not look like it's coming from the f5. I'm not sure where it's coming from.
00:06.48smootarah
00:06.53scgallafentThe issue was actually that the keys were marked as unique.
00:07.05scgallafentThe solution was to drop and re-add the keys to allow duplicate values.
00:07.26scgallafentIt looks like the column already allows nulls.
00:08.25TimRikerit really should be adding nulls when there's nothing there and not '' values. that's probably a larger issue though.
00:08.29scgallafentThe problem was that it was adding blank strings.
00:08.38scgallafentCorrect on the null vs blank string issue.
00:08.40TimRikerthen searches could just be != NULL.
00:09.11TimRikerI NULLed the mls project. that might have been the only '' entry.
00:09.30scgallafentUpdate applied.
00:09.41scgallafentsmootar, go ahead and try to add the project again.
00:09.54smootarok, will do on my ride home.  be back online in a minute.
00:11.18scgallafentTimRiker, I think I looked at the null vs. blank issue and it turned out that it was an issue deep in the bowels of Joomla.
00:14.49*** join/#ldstech smootar (~smootar@mobile-166-147-082-028.mycingular.net)
00:14.49*** mode/#ldstech [+o smootar] by ChanServ
00:15.54smootartrying it now.
00:20.12smootarscgallafent: TimRiker that worked without Jira.
00:20.23scgallafentNow try to add the JIRA project and see what happens.
00:29.17TimRikerheads. email me if needed.
00:31.41*** join/#ldstech smootar (~smootar@166.137.123.188)
00:31.44*** mode/#ldstech [+o smootar] by ChanServ
00:37.59smootarscgallafent: this doesn't seem to be working.
00:38.07scgallafentWhat happens?
00:38.27smootarI have also tried associating the STORE jira project and it doesn't work.
00:38.43smootarI've tried that multiple times.
00:38.53scgallafentYou can't associate an existing project. That is the bug that was fixed.
00:42.32smootarok
00:50.01*** join/#ldstech smootar (~smootar@66.7.124.118)
00:50.01*** mode/#ldstech [+o smootar] by ChanServ
00:50.27smootarOK, so the associating jira with an existing project was also broken/
00:50.28smootar?
00:50.30smootarscgallafent: ?
00:50.42scgallafentCorrect.
00:50.59scgallafentThe bug that was fixed is that you couldn't associate an existing JIRA project with a Joomla project.
00:51.13smootarI get this for a new project
00:51.14smootarcom.atlassian.jira.rpc.exception.RemoteValidationException: Cannot create project: projectName:A project with that name already exists. com.atlassian.jira.rpc.exception.RemoteValidationException: Cannot create project: projectName:A project with that name already exists.
00:51.22smootara new jira project that is.
00:51.31smootarIt works fine in cdev.
00:51.32scgallafentI thought it worked to associate a new JIRA project with a Joomla project.
00:51.43smootarIt didn't save.
00:51.56smootarI don't get an error, but the association is lost each time I try.
00:52.05scgallafentlooks at JIRA
00:53.14scgallafentWhen you try to update it in LDSTech, what are the exact steps you use?
00:57.44smootar1) Edit Project in administration
00:57.54smootar2) Select New Jira Project
00:58.07smootarPut the LDSSTORE in as the key
00:58.19smootarThe URL is auto-updated.
00:58.23smootarClick Save.
00:58.28smootarI get the error
00:58.30smootarcom.atlassian.jira.rpc.exception.RemoteValidationException: Cannot create project: projectName:A project with that name already exists. com.atlassian.jira.rpc.exception.RemoteValidationException: Cannot create project: projectName:A project with that name already exists.
00:59.03scgallafentOK. Those are the right steps and I can reproduce the error.
00:59.32smootarI am ok to use the STORE jira key, but that isn't saving either.
00:59.37scgallafentThe STORE key won't save.
00:59.49smootarSo you see the same thing.
00:59.50scgallafentI'm pretty certain, because that was the bug that I was fixing.
01:00.03smootarok.
01:00.06smootarI have to head to a meeting.
01:00.33smootarThanks for looking at it.
02:07.02*** join/#ldstech jpglaspie (~jpglaspie@205-237-121-1.linkp.isupark.org)
03:05.50*** join/#ldstech tiwula (~lane@63.248.12.52)
03:33.51*** join/#ldstech cpitt_ (~cpitt@pa.byuh.edu)
03:56.36*** join/#ldstech smootar (~smootar@66.7.124.118)
03:56.36*** mode/#ldstech [+o smootar] by ChanServ
05:42.33*** join/#ldstech jpglaspie1 (~jpglaspie@205-237-121-1.linkp.isupark.org)
06:30.33*** join/#ldstech mrklaw (~mrklaw@c-174-52-130-42.hsd1.ut.comcast.net)
14:49.22*** join/#ldstech VickiHaws (~VickiHaws@proxy.lds.org)
15:17.20*** join/#ldstech jonmull (~clbj@proxy.lds.org)
15:33.17*** join/#ldstech zakzakattack (~zakzakatt@proxy.lds.org)
15:40.53*** join/#ldstech JedBlack (~blackjf1@proxy.lds.org)
15:59.41*** join/#ldstech smootar (~smootar@proxy.lds.org)
15:59.41*** mode/#ldstech [+o smootar] by ChanServ
15:59.50*** join/#ldstech ekeating (~Dennis@99-54-46-12.lightspeed.snjsca.sbcglobal.net)
15:59.53ekeating~meetstart <LDSTech Dev Scrum>
15:59.53infobot********** Start of the <LDSTech Dev Scrum> Meeting on 2013.02.12 15:59:53 **********
15:59.59ekeatingmoin everyone
16:00.03smootarmoin
16:00.07scgallafentmoin
16:00.20ekeatingscgallafent, let's begin with you today
16:00.34scgallafentStill typing out my notes. Here goes.
16:00.34scgallafent-- Yesterday --
16:00.34scgallafent* Worked on CPAS issues that Elder Fenton identified in testing.
16:00.34scgallafent* Looked at a couple of issues with smootar and TimRiker.
16:00.39smootarIs JedBlack zakzakattack and jonmull here?
16:00.40scgallafent-- Today --
16:00.44jonmullim here
16:00.49zakzakattackhere
16:00.59JedBlackhello
16:01.05scgallafent* More CPAS issues
16:01.06scgallafent* https://tech.lds.org/jira/browse/LDSTECH-
16:01.07scgallafenthttps://tech.lds.org/jira/browse/LDSTECH-041
16:01.11scgallafenthttps://tech.lds.org/jira/browse/LDSTECH-900
16:01.13scgallafenthttps://tech.lds.org/jira/browse/LDSTECH-885
16:01.19scgallafentThat should have been https://tech.lds.org/jira/browse/LDSTECH-941
16:01.26scgallafentWe'll see how much I get through
16:01.28scgallafent--
16:01.45ekeatinggood luck
16:01.51scgallafentThe issue that was causing smootar problems is https://tech.lds.org/jira/browse/LDSTECH-932
16:02.15scgallafentIt's self-contained and we could deploy the update. It is contained in one file and doesn't involve anything else.
16:02.24smootarscgallafent: I think that one is a very high priority.  I need to support this new project.
16:02.31smootarLDS Store.
16:02.35scgallafentOK. I'll review it and update that today.
16:02.54smootarThat would be helpful.
16:02.58scgallafentThis might be an argument for moving toward a method where we can release small updates as they are ready and tested.
16:03.17scgallafentFor example, WordPress (Automattic) deploys multiple times per day.
16:03.28smootarHmmmm
16:03.37scgallafentThe issues that were occuring with CODA on Thursday and Friday seem to have been resolved.
16:03.42smootarSome updates would make sense to do that.
16:03.47scgallafentI don't know who fixed it or what happened, but it's working now.
16:03.50scgallafentThat is all.
16:04.00ekeatingthanks
16:04.06smootarI wonder if TimRiker worked on that.
16:04.15ekeatinghere's cpitt's report
16:04.18ekeatingSorry for the lack of communication of late. I was busy with school last week, and then I decided to get the flu...If there is anything that needs to be done please assign me a ticket in Jira.
16:04.18ekeating-Cameron.
16:04.56ekeatingwe should take a look at the open issues and see if there is anything we can assign to him
16:05.00smootarI should have him help.
16:05.34ekeatinganything to report today zakzakattack ?
16:06.18zakzakattackNope I have 1 ticket for me . I coundent do tehe other one so i assigned to cpitt
16:06.44ekeatingthank you
16:06.50zakzakattackI did one of smooter's tickets yesterday, i will be working on hours and that ticket
16:06.55zakzakattackthat is all
16:07.12ekeatingthank you, again
16:07.14ekeatingJedBlack, ?
16:07.19JedBlackswitching gears from directory testing to calendar testing. Helping sister steiner come up to speed on lesson testing.
16:07.42JedBlackNeed to help sister steiner join this meeting.
16:07.59ekeatingyes
16:08.00JedBlackthats all
16:08.09ekeatingthanks
16:08.26ekeatingjonmull, ?
16:08.29jonmulli have nothing to report today
16:08.36ekeatingthank you
16:08.59ekeatingare there any other reports today?
16:08.59jonmulli have found a problem with they sync on the project
16:10.09smootarjonmull: have you reported that to the dev team?
16:10.14*** join/#ldstech TeddieSteiner (~steinerte@proxy.lds.org)
16:10.17*** join/#ldstech Teddie (~steinerte@proxy.lds.org)
16:10.33jonmullyes a little while ago
16:10.42Teddiehello
16:10.49smootarWelcome Teddie
16:10.53*** join/#ldstech TimRiker (~TimRiker@bzflag/projectlead/TimRiker)
16:10.53*** mode/#ldstech [+o TimRiker] by ChanServ
16:11.01smootarHere is my report.
16:11.02TimRikeryay! there we go.
16:11.03smootarI have some deadlines with plans that I need to finish for LDSTech.
16:11.04smootarThe plans will represent our group planning meeting from December.
16:11.05smootarI added a new project yesterday for the LDS Online Store.
16:11.07smootarRan into the bug previously mentioned by scgallafent.
16:11.09smootarOnce a fix is deployed I will continue to help them get going.
16:11.10smootarThere are several missionaries that are getting matched up, a couple are in iOS working with HiltonC
16:11.11smootarStaff at 10 AM
16:11.12smootarHoliday on Monday.
16:11.13smootarThat is all.
16:11.15TimRikerspends 10 minutes fighting with the proxy
16:11.33smootar~lart proxy
16:11.33infobotcuts off proxy's head with a halberd that could have been a little bit sharper
16:11.44TimRikeryay!
16:11.45smootarThat is a little morbid.
16:12.01smootar:)
16:12.02TimRikerheh
16:12.57ekeatingTimRiker, ?
16:12.58jonmullnow it is working exactly as it should. weard
16:13.00TimRikerworking on wiki/forum/joomla account integration. need to test that wiki/forum users get created in joomla. I think they should now.
16:13.40TimRikerthere's just a json interface now, wiki/forum is not yet consuming it. but I can test by hitting the interface directly.
16:14.05TimRiker~ldstech 878
16:14.05infobothttps://tech.lds.org/jira/browse/LDSTECH-878
16:14.07TimRiker~ldstech 879
16:14.07infobothttps://tech.lds.org/jira/browse/LDSTECH-879
16:15.06TimRikerhttps://cdev.lds.org/ldstech/joomla/components/com_talentpool/me <- shows not logged in. then log in on wam (ie: wiki/forum/joomla) and try again.
16:15.30TimRikerie: https://cdev.lds.org/phpstack/?signmein  will do
16:16.20TimRikerprobably want to set timezone explictly to work around the php warnings. won't get those in production though.
16:16.58TimRikerscgallafent, it's security that's doing us the favor of blocking phpmyadmin. "but that has sql stuff in it!" uh, yes. and we need that.
16:17.25TimRikerresponding in email to them today. will copy you and smootar
16:17.30scgallafentshakes his head
16:17.31TimRikerthat is all I guess.
16:17.32smootarnods
16:17.58smootarMak
16:18.02ekeatingthanks sounds like quite a bit
16:18.06smootarMak'in progress
16:18.37ekeatingIf there isn't anything else we'll close ad get prepared for the 10 staff meeting
16:18.42scgallafentsmootar, deploying the fix for https://tech.lds.org/jira/browse/LDSTECH-932 (your issue) will also involve deploying https://tech.lds.org/jira/browse/LDSTECH-934 (add multiple team members).
16:18.42scgallafentI'll need to test that before I can deploy. I also need to finish looking and see if anything else is tangled into the update.
16:19.03smootarscgallafent: will you let me know?
16:19.14scgallafentYes. I'll keep poking at it.
16:19.15smootarI would like KFitz to kick the tires as well.
16:19.25smootarCould you reach out to him?
16:19.27scgallafentI'll ping him.
16:19.30smootarThx
16:19.35TimRikershould we test and deploy everything?
16:19.43smootarsmootar pinged him to join IRC, but not luck.
16:19.51scgallafentAre we at a point we can do that?
16:20.10smootarLet's just do minimal today.
16:20.20smootarI would like KFitz to be part of the full deploy.
16:20.33smootarI want to have QA give the thumbs up.
16:21.17scgallafentI'll try to talk to KFitz before staff meeting.
16:21.23smootarthx
16:21.56smootarTimRiker: Can you dish off a couple of Jira issues to cpitt?  He requested that.
16:22.19TimRikersmootar, I'll look through the queue
16:22.29smootar:)
16:22.51smootarekeating: I think we are done.
16:22.52ekeatingthanks to everyone. see you at 10
16:22.56ekeating~meetend <LDSTech Dev Scrum>
16:22.56infobot********** End of the <LDSTech Dev Scrum> Meeting on 2013.02.12 16:22:56 **********
16:23.08TimRikerthe amount of testing and deploy work to test and deploy a partial may well be more effort that testing and deploying everything.
16:23.32smootargood thought.
16:23.42scgallafentI'm looking now to see how much is woven into the change that smootar needs to have deployed.
16:24.14zakzakattacksmooter- shall I put the Missionary hours on a spot in the project spredsheet?
16:24.59smootarYes
16:25.08smootarCreate a new row and title it appropriately.
16:25.37*** join/#ldstech marquicus (~mrojas@200.13.124.36)
16:25.40smootarIt would include hours that haven't already been accounted for in the other projects.
16:26.57zakzakattackK thanks, Not getting very many responses... only about 10 out of 50.
16:34.33*** part/#ldstech jpglaspie1 (~jpglaspie@205-237-121-1.linkp.isupark.org)
16:40.09*** join/#ldstech marp12 (~mrojas@200.13.124.36)
16:40.41smootarLet's move through the clean-up process of the projects as we discussed.
16:40.59smootarPersonal phone calls may need to be done to find out if they are still active projects or not.
16:43.15*** join/#ldstech josephscott (~josephsco@208.95.156.134)
16:53.52*** join/#ldstech marquicus (~mrojas@200.13.124.36)
16:57.52*** join/#ldstech VickiHaws_ (~VickiHaws@proxy.lds.org)
16:59.29*** join/#ldstech smootar_ (~smootar@proxy.lds.org)
16:59.29*** mode/#ldstech [+o smootar_] by ChanServ
17:02.10*** join/#ldstech tiwula (~lane@70.89.246.241-Busname-UT.hfc.comcastbusiness.net)
17:10.34scgallafentTimRiker, staff meeting.
18:00.46*** join/#ldstech tdeforest (~tdeforest@proxy.lds.org)
18:00.46*** mode/#ldstech [+o tdeforest] by ChanServ
18:03.11*** join/#ldstech smootar (~smootar@proxy.lds.org)
18:03.11*** mode/#ldstech [+o smootar] by ChanServ
18:06.36*** join/#ldstech smootar_ (~smootar@proxy.lds.org)
18:06.36*** mode/#ldstech [+o smootar_] by ChanServ
18:13.44*** join/#ldstech marquicus (~mrojas@200.13.124.36)
18:32.52*** join/#ldstech josephscott (~josephsco@104.2.233.72.static.reverse.ltdomains.com)
18:37.03*** join/#ldstech JedBlack (~blackjf1@proxy.lds.org)
18:56.06*** join/#ldstech smootar (~smootar@proxy.lds.org)
18:56.06*** mode/#ldstech [+o smootar] by ChanServ
19:38.33*** join/#ldstech JedBlack (~blackjf1@proxy.lds.org)
19:55.35*** join/#ldstech smootar_ (~smootar@proxy.lds.org)
19:55.35*** mode/#ldstech [+o smootar_] by ChanServ
20:57.37*** join/#ldstech marquicus (~mrojas@200.13.124.36)
20:58.44*** join/#ldstech marquicus (~mrojas@200.13.124.36)
21:19.19*** join/#ldstech smootar (~smootar@proxy.lds.org)
21:19.19*** mode/#ldstech [+o smootar] by ChanServ
21:20.32smootarscgallafent: I'm curious if you were able to connect with KFitz.
21:21.09scgallafentI haven't yet. I've checked a few times on Lync, but he's been away whenever I've checked.
21:21.11scgallafentchecks again
21:21.19scgallafentStill away.
21:22.49smootarMaybe I should chase him down and see if we can get this deployed.
21:23.39scgallafentIf you can catch him, that would probably be good.
21:24.11scgallafentI keep a Lync window oepn so I can look whenever I tab past it, but haven't caught him yet.
21:24.16scgallafents/oepn/open/
22:03.49smootarscgallafent: KFitz is available in two weeks.  He is buried.  
22:04.05scgallafentDo we go on without him, then?
22:04.23smootarYes, we need to have some testing done.
22:04.54smootarSince it is broken in production, let's deploy.
22:05.04smootarI will then go do some testing there to make sure that it works for me.
22:05.13scgallafentOK. I've isolated what needs to be deployed and can get it ready to move out.
22:05.21smootarIt is admin stuff, so it doesn't touch very many users.
22:06.19scgallafentI'm uploading Fortify scans. I'll move on to that next.
22:53.22scgallafentsmootar, finished my review and deployed. Go ahead and see if you run into problems.
22:53.31smootarok
22:56.08smootarAssociating an existing project worked just fine.  I associated STORE and it saved it fine.
22:56.21scgallafentOK. We're off to the races.
22:56.32smootarWhen I tried to create a new Jira Project LDSSTORE I got the following error.
22:56.32smootarcom.atlassian.jira.rpc.exception.RemoteValidationException: Cannot create project: projectName:A project with that name already exists. com.atlassian.jira.rpc.exception.RemoteValidationException: Cannot create project: projectName:A project with that name already exists.
22:56.50scgallafentSo we've still got an issue there.
22:56.56smootarWe around the current problem, but creating a new Jira still seems to be a problem.
22:57.04scgallafentI only fixed the can't associate with an existing project bug. I carried forward the rest of the code.
22:57.11smootars/We/We got/
22:57.22scgallafentIf you'll log that to JIRA and assign to me, I'll go in and address that one.
22:57.33smootarnods.
22:57.40smootarThanks for fixing this immediate issue.
22:59.33scgallafentYou're welcome.
23:02.00smootarThat will get the team moving.
23:41.14*** join/#ldstech TimRiker (~TimRiker@bzflag/projectlead/TimRiker)
23:41.14*** mode/#ldstech [+o TimRiker] by ChanServ
23:51.07*** join/#ldstech smootar_ (~smootar@proxy.lds.org)
23:51.07*** mode/#ldstech [+o smootar_] by ChanServ

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.