fluid-tech IRC Logs-2013-08-27
[15:19:12 CDT(-0500)] <Bosmon> Hi yzen - did you get any further with the kettle context issue?
[15:21:54 CDT(-0500)] <yzen> so a quick question
[15:21:55 CDT(-0500)] <yzen> if i m removing all wrapping stuf
[15:21:56 CDT(-0500)] <yzen> f
[15:21:57 CDT(-0500)] <yzen> does it mean i can get rid of with environment and just call the function as is ?
[15:22:13 CDT(-0500)] <Bosmon> yzen - you shouldn't need withEnvironment any more, right
[15:22:20 CDT(-0500)] <Bosmon> The component tree should be good enough just by itself
[15:22:27 CDT(-0500)] <yzen> ok trying
[15:22:28 CDT(-0500)] <yzen>
[15:25:13 CDT(-0500)] <yzen> Bosmon: and in cases when i used to do:
[15:25:14 CDT(-0500)]
<yzen> fluid.expand("
", {
[15:25:15 CDT(-0500)] <yzen> fetcher: fluid.makeEnvironmentFetcher()
[15:25:16 CDT(-0500)] <yzen> });
[15:25:28 CDT(-0500)] <Bosmon> yzen - that should also be unnecessary
[15:25:37 CDT(-0500)] <yzen> so where would i get a request from
[15:25:50 CDT(-0500)] <yzen> for example in case where we want to handle errors
[15:25:51 CDT(-0500)] <yzen> in utils
[15:25:51 CDT(-0500)] <Bosmon> The request should be one of your parents in the tree ....
[15:26:10 CDT(-0500)] <Bosmon> Ah, errors
[15:26:26 CDT(-0500)] <Bosmon> Well, you should try to always have a component to hand
[15:26:57 CDT(-0500)] <Bosmon> humm
[15:27:35 CDT(-0500)] <Bosmon> This stuff is still so annoying
[15:27:46 CDT(-0500)] <Bosmon> I'll need to have more shower thoughts
[15:47:44 CDT(-0500)] <yzen> ok
[16:09:27 CDT(-0500)] <Bosmon> yzen - perhaps it is not possible to fix after all
[16:09:31 CDT(-0500)] <kasparnet> is that sneaky Brit trying to hide from our annoying questions in the fluid-work channel
[16:09:37 CDT(-0500)] <Bosmon> Especially in the case of things like "uncaughtException"
[16:09:41 CDT(-0500)] <Bosmon> kasparnet - yes
[16:10:02 CDT(-0500)] <yzen> Bosmon:
[16:10:07 CDT(-0500)] <Bosmon> I have just been learning about how King Alfred BAPTISED THE PAGAN .......
[16:11:24 CDT(-0500)] <Bosmon> The vicious KING GUTHRUM OF THE VIKINGS
[16:12:15 CDT(-0500)] <kasparnet> haha, I dont know either of those
[16:12:43 CDT(-0500)] <Bosmon> http://en.wikipedia.org/wiki/Treaty_of_Wedmore
[16:15:09 CDT(-0500)] <michelled> kasparnet: are you hiding from me
[16:17:55 CDT(-0500)] <kasparnet> michelled: hehe sorry - I didn't see your ping
[16:18:21 CDT(-0500)] <kasparnet> but you're probably gonna ask me about the status of the release.. and in that case, I might try to hide from you
[16:19:00 CDT(-0500)] <michelled> I was going to ask if you wanted to meet with me tomorrow before the arch meeting
[16:19:16 CDT(-0500)] <michelled> and then I was going to ask you about the release
[16:19:19 CDT(-0500)] <kasparnet> Bosmon, yura: is there a magic place where I can put a breakpoint that'll catch all th exceptions thrown during the flowmanager flow
[16:19:38 CDT(-0500)] <Bosmon> kasparnet - you could have been paying attention to our discussion
[16:19:57 CDT(-0500)] <kasparnet> michelled: I can meet before before the architecture meeting... That is 16:00 CEST = 10 am EST
[16:19:59 CDT(-0500)] <Bosmon> For example, if they are REAL exceptions, you can find them in utils.js
[16:20:08 CDT(-0500)] <Bosmon> Although the stack frame will be gone by that time
[16:20:33 CDT(-0500)] <kasparnet> there is a device reporter meeting immediately before the arch. meeting
[16:20:40 CDT(-0500)] <michelled> sounds good kasparnet
[16:20:51 CDT(-0500)] <michelled> 10 EST it is
[16:20:59 CDT(-0500)] <kasparnet> cool - putting it on my calendar! Thanks michelled
[16:21:06 CDT(-0500)] <michelled> np
[16:21:11 CDT(-0500)] <Bosmon> There's also the "onErrorHandler" in requests.js - kasparnet
[16:22:08 CDT(-0500)] <Bosmon> DDAMMMNNN YYYOOUUUU, KASSPPAAARNEEETTTTT!!!!
[16:22:34 CDT(-0500)] <kasparnet> haha, I was just about to write thanks, Bosmon.. but now I'm not so sure
[16:30:33 CDT(-0500)] <Bosmon> Hey yzen
[16:30:41 CDT(-0500)] <Bosmon> Were were just talking about kettle with michelled
[16:30:45 CDT(-0500)] <Bosmon> Would you like to join?