Camelia, the Perl 6 bug

IRC log for #mojo, 2012-07-17

| Channels | #mojo index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:53 bird joined #mojo
00:57 laouji joined #mojo
01:12 scott_ joined #mojo
01:17 Lucas1 joined #mojo
01:22 freman joined #mojo
01:23 freman Hi, I'm trying to do something rather... unique... with mojo - we have a full app built around it and are loving it, but now I'd like to integrate a IO::Socket::Multicast - any tips? I'm looking at Mojo::IOLoop::Stream - right direction?
01:27 amirite joined #mojo
01:59 d4rkie joined #mojo
02:11 noganex_ joined #mojo
02:13 lungching joined #mojo
02:34 Psyche^ joined #mojo
03:03 freman no-one?
03:32 tempire freman: your question is too abstract.
03:32 tempire Mojo::IOLoop::Stream is considered an internal API, so be aware that it might change from time to time.
03:34 freman I'm not sure how to make it less abstract - which is probably part of my problem. The idea is these mojo apps are going to become part of a group with a master that'll be sending out a multicast packet every 30 seconds with updated info that the mojo apps need to deal with (usually just setting internal variables, sometimes sending a message via websocket to any connected clients)
03:45 patspam joined #mojo
03:50 patspam joined #mojo
03:51 patspam joined #mojo
04:00 freman Seems I can grab the Mojo::IOLoop->singleton->reactor and thwo a $reactor->io() watcher on the socket
04:08 freman is that the best way to do it?
05:05 xaka joined #mojo
05:10 jwang joined #mojo
05:15 ovnimancer joined #mojo
05:18 Coff joined #mojo
05:19 * Coff is starting to realize that he needs irssi running in a screen somewhere, not xchat on laptop.
05:30 spleenjack joined #mojo
05:48 freman coff I make use of znc on a server then whatever client is available on whatever machine is around
05:50 Coff Huh. Znc does not look entirely like a stupid idéa. *reading* thanks for the tip!
05:50 batman joined #mojo
05:58 batman joined #mojo
06:20 Coff joined #mojo
06:28 Foxcool joined #mojo
07:03 negher joined #mojo
07:14 Vandal joined #mojo
07:19 taryk joined #mojo
07:21 batman joined #mojo
07:23 patspam joined #mojo
07:23 patspam joined #mojo
07:27 patspam joined #mojo
07:28 xaka1 joined #mojo
07:31 pau4o joined #mojo
07:33 iambatman joined #mojo
07:35 daxim joined #mojo
07:37 baton8 joined #mojo
07:59 fhelmber_ joined #mojo
08:07 jontaylor joined #mojo
08:10 jontaylor joined #mojo
08:37 marcus phk++
08:53 cosmincx joined #mojo
08:55 * nic wonders how frequently to take the http://www.amiaunicorn.com/ test
09:03 crab that site seems to imply that unicorns are horses.
09:03 crab how insulting.
09:35 xaka joined #mojo
10:13 xaka joined #mojo
10:19 phillipadsmith joined #mojo
10:20 chansen joined #mojo
12:59 ryozi joined #mojo
13:06 gryphon joined #mojo
13:10 Coff joined #mojo
13:23 Coff joined #mojo
13:32 d4rkie joined #mojo
13:47 amirite joined #mojo
13:57 tadamo_ joined #mojo
14:04 daniel_ joined #mojo
14:08 d4rkie joined #mojo
14:11 inokenty joined #mojo
14:31 sri \o\
14:31 sri /o/
14:32 daxim // escapes / in the beginning
14:32 sri tempire: not sure internal apis change more than normal ones
14:33 jnap joined #mojo
14:34 sri i think it mostly means we won't extend the api with anything we don't use in core ourselves
14:35 sri even for spdy support i don't see the stream api change much in 4.0
14:38 sri biggest change will prolly be the removal of the http and websocket parsers from Mojo::Transaction::* and Mojo::Message::*
14:38 lammel2 joined #mojo
14:39 xaka joined #mojo
14:40 sri even Mojo::IOLoop->stream($id)->timeout(300) might stay and just change semantics a little
14:42 * sri starts to get an idea for how the channel layer will work
14:46 ovnimancer left #mojo
16:12 ilbot2 joined #mojo
16:12 Topic for #mojo is now Mojolicious real-time web framework 3.0 🌈 http://mojolicio.us 🌈 http://irclog.perlgeek.de/mojo/today
16:31 pau4o left #mojo
17:11 bc547 joined #mojo
17:16 mire joined #mojo
18:08 jnap joined #mojo
18:17 * tempire wonders if blog entries on blogs.perl.org are more likely to be read than ironman feed-only entries
18:31 rem_lex| joined #mojo
18:37 gryphon joined #mojo
18:38 sri tempire: let me know if you find out :)
18:39 tempire well it's a lot easier to comment on disqus than moveable type, that's for sure
18:43 sri indubitably
18:50 sri oh damn
18:50 sri i never made the connection... $calar, @rray
18:53 whee I will never unsee that
18:53 whee why would you do this to me
19:01 sri :D
19:04 tabbi joined #mojo
19:06 whee may you see a thousand fedex trucks carrying goodwill clothing and used sun computers
19:07 Foxcool joined #mojo
19:17 iambatman joined #mojo
19:23 athenot joined #mojo
19:37 tabbi hi, is there a simple way to route a subfolder of the folder "public" through a authentication bridge so that i can put images there which should only be visible to logged in users?
19:42 moritz joined #mojo
19:42 moritz oh hail loltoads
19:42 moritz erm
19:42 moritz \o
19:42 moritz s/hail/hai
19:43 moritz in Mojo::Test, how do I add additional diagnosis if a test fails?
19:43 moritz erm, Test::Mojo
19:43 moritz with Test::More, I'd do ok(...) or diag(...)
19:44 moritz but Test::Mojo allows chaining, so something like $t->status_is(..) always returns something true
20:01 sri moritz: don't think there is
20:01 moritz sri: might be worth thinking about, if others want that too
20:01 sri i'm open for suggestions
20:02 moritz could be  $t->status_is(200)->diag_on_failure("here's what went wrong")
20:05 sri not very pretty
20:08 moritz $t->status_is(200)->or( sub { diag "foo" }) ?
20:08 moritz or simply
20:08 moritz ->or('diag message')
20:10 sri it would have to be before the actual test
20:10 moritz why?
20:11 moritz can't we keep the state of one test around?
20:11 sri don't think so
20:11 moritz why not?
20:12 sri would make the code suck pretty bad i believe
20:14 sri can't actually think of any implementation i would like tbh
20:14 moritz well, we'd need to change   Test::More::...   with $self->{lasttest} = Test::More::...
20:14 moritz in all the test subs
20:15 sri that's like a dozen extra lines of code :S
20:15 moritz that's not a small change, but not complicated either
20:15 moritz rm -rf lib/; # reduce code size dramatically
20:17 osprey_ joined #mojo
20:19 sri every single case also needs to be unit tested
20:25 sri the cost/gain ratio of the feature doesn't excite me much, maybe the other core devs like it more
20:34 tabbi left #mojo
20:56 jontaylor joined #mojo
21:56 osprey_ left #mojo
22:24 sri moritz: funny thing is, if done right your feature actually results in less code
22:24 moritz sri: how?
22:25 sri i'll commit a cleanup in a few mins :)
22:25 moritz \o/
22:27 sri still not sure about the ->or() though
22:27 sri tempire, marcus, crab: thoughts?
22:27 sri $t->status_is(200)->or('What the hell did i do?')
22:42 sri and when i say less code i mean... damn! it's a lot less code
22:42 sri like 40-50 lines less
22:42 moritz my proposed git rm -rf lib/ would be lots and lots of less code :-)
22:43 sri moritz: but it wouldn't be backwards compatible! ;p
22:43 tempire %ash?
22:44 sri $scalar, @array, %ash
22:44 sri noo
22:44 sri i accidentally!
22:44 sri $calar, @rray, %ash
22:46 sri tempire: ->or() yay or nay?
22:46 tempire ->or('what is the point of this');
22:46 tempire ->or(sub {'is this the real use case'})
22:48 moritz tempire: the point is to emit diagnostic messages for failed tests
22:48 tempire then I'm a yay
22:49 tempire I'm also for it
22:49 tempire if it's 50 less lines of code, then it's hard to be against it
22:50 sri well, it's 50 lines less after the preparations to make ->or() possible :)
22:50 sri with ->or() it will only be like 45 ;p
22:51 tempire right now, I use ok, or
22:51 tempire ->or seems like it would clean things up
22:53 sri i'm ok with the feature, my main worry was more untestable code, now it's less untestable code in the end...
22:57 tempire why is it untestable?
22:58 sri how do you test Test::Mojo?
22:58 tempire mojolicious philosophy
22:59 * tempire ponders
23:00 tempire I didn't know there weren't tests.  seems pretty easy to me - you just have a lite app that gives expected responses.
23:00 tempire am I missing something?
23:02 sri btw. it was almost 60 lines in the end :D
23:02 * tempire loves the state keyword
23:02 sri tempire: that doesn't really test that Test::Mojo works
23:03 tempire oh, you're talking about testing the tap output.
23:03 * sri nods
23:18 GitHub168 joined #mojo
23:18 GitHub168 [mojo] kraih pushed 1 new commit to master: http://git.io/NnuuEw
23:18 GitHub168 [mojo/master] added or method to Test::Mojo - Sebastian Riedel
23:18 GitHub168 left #mojo
23:20 sri tempire: https://github.com/kraih/mojo/commit/22ee9​faf8364bf81baebcfa578414ea66ac9608e#L2R630
23:20 sri :)
23:20 tempire oJ
23:21 tempire I need a backwards J
23:38 gryphon joined #mojo

| Channels | #mojo index | Today | | Search | Google Search | Plain-Text | summary