[10:06:17 CDT(-0500)] <anastasiac> cindyli, I found out why my enactor was complaining that a container was specified when it wasn't supposed to be: I had NOT declared it to be a viewComponent. Is it a requirement that enactors are viewComponents, and if so, should that be encompassed by the enactor grade?
[10:08:24 CDT(-0500)] <cindyli> anastasiac: it's great you found out why. I don't think it's a requirement that enactors are viewComponents since enactors can do more than applying changes to containers.
[10:08:43 CDT(-0500)] <anastasiac> well, then there's a bug somewhere if it's not a requirement 
[10:09:59 CDT(-0500)] <cindyli> yes, anastasiac. i will take a look on why viewComponent declaration is required once i'm done with 5181
[10:10:26 CDT(-0500)] <anastasiac> thanks, cindyli. Should I file a JIRA?
[10:10:40 CDT(-0500)] <cindyli> yes pls, anastasiac
[10:10:45 CDT(-0500)] <anastasiac> k
[10:15:26 CDT(-0500)] <anastasiac> cindyli: http://issues.fluidproject.org/browse/FLUID-5187 I've added it to the iteration page
[10:15:41 CDT(-0500)] <cindyli> thanks, anastasiac
[12:32:44 CDT(-0500)] <colinclark> Hey kasparnet, are you around?
[12:57:57 CDT(-0500)] <kasparnet> colinclark: I am
[13:05:22 CDT(-0500)] <colinclark> hey dude
[13:05:47 CDT(-0500)] <colinclark> So, I'm finding myself struggling a bit to review your GPII-260 pull request
[13:07:40 CDT(-0500)] <Jess_> anastasiac: ping
[13:07:50 CDT(-0500)] <anastasiac> Jess_: polo
[13:08:08 CDT(-0500)] <kasparnet> colinclark: cause it's all nonsense to you
[13:08:16 CDT(-0500)] <kasparnet> or cause my solution is crazy
[13:08:28 CDT(-0500)] <colinclark> No, because your JIRA sucks 
[13:08:28 CDT(-0500)] <Jess_> sorry, i don't have you on IM right now – i think i don't have the password for one of my accts. anyway, i'm going to skip the question about #9 in the space list since we won't get to it
[13:08:49 CDT(-0500)] <kasparnet> arh - that's the second time you've said that today
[13:08:55 CDT(-0500)] <colinclark> Soryr
[13:08:56 CDT(-0500)] <anastasiac> Jess_, I guess that sounds reasonable
[13:09:02 CDT(-0500)] <colinclark> I don't mean to be mean, kasparnet
[13:09:12 CDT(-0500)] <colinclark> The JIRA doesn't really describe what "failure" is, tangibly
[13:09:21 CDT(-0500)] <kasparnet> hahaha, no no worries 
[13:09:27 CDT(-0500)] <colinclark> or if there are other preference sets aside from Timothy's that I should test with
[13:09:50 CDT(-0500)] <colinclark> or what the actual relationship between GPII-260 and GPII-243 and GPII-192 are
[13:09:54 CDT(-0500)] <kasparnet> colinclark: yeah - I've been slacking on the JIRAs lately
[13:10:05 CDT(-0500)] <kasparnet> so let me add some more details to it
[13:10:07 CDT(-0500)] <colinclark> This is what we've called in the past a TLJ
[13:10:14 CDT(-0500)] <colinclark> yzen can tell you all about them 
[13:14:49 CDT(-0500)] <yzen> colinclark: well there's not much to say, kasparnet found those and lifecycle manager does not handle exceptions if anything fails that it tries to apply
[13:15:16 CDT(-0500)] <colinclark> Well, I think there's probably a lot left unsaid
[13:15:20 CDT(-0500)] <colinclark> like WHAT ACTUALLY HAPPENS
[13:15:32 CDT(-0500)] <colinclark> Even if the Flow Manager doesn't handle exceptions
[13:15:43 CDT(-0500)] <colinclark> 1. Where in the process does the failure occur?
[13:15:57 CDT(-0500)] <colinclark> 2. Have any assistive technologies been configured by the time it fails?
[13:16:01 CDT(-0500)] <colinclark> 3. Are any messages logged?
[13:16:24 CDT(-0500)] <colinclark> These are, you might remember, the very questions you asked me last night when you helped me debug my problem
[13:16:27 CDT(-0500)] <colinclark>
[13:17:08 CDT(-0500)] <colinclark> Not to mention the questions I asked kasparnet above
[13:17:11 CDT(-0500)] <colinclark> including
[13:17:20 CDT(-0500)] <colinclark> 4. Are any other preference sets affected?
[13:17:26 CDT(-0500)] <colinclark> 5. How does this issue relate to similar issues?
[13:21:19 CDT(-0500)] <yzen> 1. happens on the actual call to the exec or something similar
[13:21:53 CDT(-0500)] <yzen> 2. yes or no, depending where in order the failure happened, nothing happens after as you might suspec
[13:21:54 CDT(-0500)] <yzen> t
[13:22:02 CDT(-0500)] <yzen> 3. nothing helpful is logged
[13:22:18 CDT(-0500)] <yzen> 4 and 5 I'm not sure
[13:22:21 CDT(-0500)] <kasparnet> colinclark, yzen: so trying out the bug again, I realize it doesn't actually explode.. server is still running.. it's just that the login caller gets a (nonsense) error back and that's it
[13:22:25 CDT(-0500)] <yzen> i think kasparnet would be best to know
[13:22:36 CDT(-0500)] <colinclark> I didn't say "helpful" for #3.
[13:22:44 CDT(-0500)] <yzen> kasparnet: well yes, you can't keel the server
[13:22:47 CDT(-0500)] <yzen> it's invincible
[13:22:50 CDT(-0500)] <yzen> like a boss
[13:23:49 CDT(-0500)] <colinclark> The point about #3 is subtle
[13:24:05 CDT(-0500)] <colinclark> helpful isn't necessarily the point
[13:24:05 CDT(-0500)] <colinclark> though helpful messages would be great
[13:24:09 CDT(-0500)] <kasparnet> yzen: ... cough GPII-243 cough ,.. you said what, yura?
[13:24:40 CDT(-0500)] <colinclark> But you need to keep in mind people who might encounter this issue who have never have experienced a failure like this
[13:24:48 CDT(-0500)] <colinclark> Absolutely anything will help in this case
[13:24:49 CDT(-0500)] <kasparnet> colinclark: I've added comments as to #4 and #5 in the JIRA
[13:24:54 CDT(-0500)] <colinclark> cool, kasparnet
[13:25:44 CDT(-0500)] <kasparnet> colinclark: along with the errors I see when running it
[13:26:09 CDT(-0500)] <kasparnet> colinclark: Sorry for being so sloppy with them
[13:26:14 CDT(-0500)] <colinclark> no worries
[13:26:19 CDT(-0500)] <colinclark> I'm not trying to smack you down
[13:26:57 CDT(-0500)] <colinclark> I just want to avoid situations that cause people to waste time and hate the GPII
[13:27:12 CDT(-0500)] <colinclark> I can say from experience that I hated the GPII last night
[13:27:38 CDT(-0500)] <kasparnet> haha yeah
[13:28:21 CDT(-0500)] <colinclark> yzen: Do you see where I'm coming from with this?
[13:32:19 CDT(-0500)] <colinclark> So kasparnet, is the idea that we won't use any font size-related preferences for the pilots?
[13:32:23 CDT(-0500)] <colinclark> Is everyone cool with that?
[13:34:33 CDT(-0500)] <michelled> kasparnet: maybe I misunderstood, but I thought there were a couple JIRAs on the pilots todo list to fix the font size related issues
[13:34:35 CDT(-0500)] <michelled> am I wrong?
[13:34:43 CDT(-0500)] <michelled> or are they different issues?
[13:36:42 CDT(-0500)] <kasparnet> colinclark, michelled: yeah, there are three issues related to font-size right now.. I'll talk with Eleni about the NOT having any font-size JIRAs fixed for pilots (ie. windows)
[13:38:01 CDT(-0500)] <kasparnet> michelled, colinclark: I guess alternatively to adding in my pull request for v0.2, we could completely remove everything font-size from our windows solutions registry, but that'd require us to fix acceptance tests, etc as well (perhaps both in linux and windows)
[13:43:29 CDT(-0500)] <jhernandez> heh, jhernandez won't remove anything!
[13:43:39 CDT(-0500)] <jhernandez> kasparnet: ^
[13:48:30 CDT(-0500)] <Jess_> michelled: kasparnet: i'm hoping we can connect tomorrow to get clarity on tasks related to design. the JIRAs help, but i see lots of questions floating around.
[13:49:10 CDT(-0500)] <kasparnet> jhernandez: awesome – then you're gonna be my excuse for arguing that colin should just merge my pull request and when call it that (shifting the two other font-size issues to post v0.2)
[13:49:29 CDT(-0500)] <jhernandez> xDDDDDDDD
[13:49:47 CDT(-0500)] <kasparnet> Jess_: 8-9am or 10am-12 are free for me
[13:50:06 CDT(-0500)] <kasparnet> michelled: ^
[13:50:15 CDT(-0500)] <michelled> they work for me too
[13:51:07 CDT(-0500)] <kasparnet> michelled, Jess_: I was hoping we weren't gonna need to meet for all those three hours
[13:53:13 CDT(-0500)] <Jess_> michelled: kasparnet: how about we reserve some time from 10 on? and JV and I can ask lots of questions and hopefully not take up the whole 2 hrs
[13:54:55 CDT(-0500)] <michelled> sounds good