adambeynon changed the topic of #opal to: - Ruby runtime and library on top of Javascript | 1.0.0 is near | This channel is logged at
<elia> 0 fails so far
<meh`> yeah, it happens like, 1/8 runs
<elia> I'll keep trying
<elia> btw
<elia> safari support is marked as partial
<elia> ^^^ this can be related
<elia> my history is full of lols now
<meh`> it should pop them tho
<elia> hmm
<meh`> I don't know, I can't reproduce it but I don't like allowing the failures when it's something that stupid
<elia> meh`, lol is the only one that sticks in the history
<meh`> I don't know, the failure is something wrong happening
<meh`> something weird
<elia> printing the random seed used by rspec could help
<meh`> probably something about the history changes being asynchronous sometimes
<elia> if pit's used
<elia> meh`, I thought the same
<elia> too bad there's no sleep lol
<meh`> it must be the history.back(2) not going through properly
<meh`> or the specs running in a weird order
<elia> meh`, my guess is that while the async expectation is still to be ran another spec starts and pushes history
<meh`> yeah
<meh`> but why would that happen
<elia> on my box doesn't so it maybe the BS box has less resources and gives time for the –false– bug to emerge
<elia> meh`, problem is window.location (and window.history) are globals
<elia> meh`, I could be tot wrong
<elia> async examples seem to be ran after regular ones
<meh`> elia, yeah, I know about that
<meh`> but what we're saying is not compatible with that
<elia> right
<meh`> saying?
<meh`> seeing
barry__ has joined #opal
barry_ has quit [Ping timeout: 272 seconds]
<elia> I see
<elia> lol
<meh`> async specs need a good fixing
<elia> meh`, I think the issue could be with #back
<meh`> elia, yes
<meh`> I think so as well
<elia> or window.history.go
<meh`> yeah, something is going back too far or not far enough
<elia> added a #back spec and fails
<elia> the latter probably
<meh`> fucking Apple not continuing Safari on Windows
<elia> wat!
<meh`> #back already does that
<meh`> it uses go
<meh`> the thing is #back is asynchronous
<meh`> well, go
<meh`> hella hard to test
<meh`> almost tempted to not test at all
<elia> as much as it sucks a $window.after(1) around the run_async probably will fix it
<elia> meh`, bedtime
<elia> hasta mañana
<meh`> yeah
<meh`> night
aantix has quit [Quit: aantix]
fkchang has quit [Ping timeout: 272 seconds]
e_dub has joined #opal
e_dub has quit [Ping timeout: 272 seconds]
barry_ has joined #opal
barry__ has quit [Ping timeout: 246 seconds]
e_dub has joined #opal
elia has quit [Ping timeout: 272 seconds]
RoxasShadowRS has quit [Quit: Leaving]
GitHub107 has joined #opal
<GitHub107> [opal-browser] meh pushed 1 new commit to master:
<GitHub107> opal-browser/master 4573b4f meh: spec: use the new expect style
GitHub107 has left #opal [#opal]
travis-ci has joined #opal
travis-ci has left #opal [#opal]
<travis-ci> [travis-ci] Build details :
<travis-ci> [travis-ci] opal/opal-browser#64 (master - 4573b4f : meh): The build passed.
GitHub32 has joined #opal
GitHub32 has left #opal [#opal]
<GitHub32> opal-browser/master ea2edd8 meh: spec: take Safari 7 out of allowed failures
<GitHub32> [opal-browser] meh pushed 1 new commit to master:
skofo has joined #opal
travis-ci has joined #opal
<travis-ci> [travis-ci] opal/opal-browser#65 (master - ea2edd8 : meh): The build passed.
travis-ci has left #opal [#opal]
<travis-ci> [travis-ci] Build details :
skofo has quit [Client Quit]
aantix has joined #opal
aantix has quit [Client Quit]
barry_ has quit [Remote host closed the connection]
barry_ has joined #opal
barry_ has quit [Ping timeout: 252 seconds]
GitHub194 has joined #opal
<GitHub194> [opal-browser] meh pushed 2 new commits to master:
<GitHub194> opal-browser/master 6779e3e meh: socket: cleanup some documentation
GitHub194 has left #opal [#opal]
<GitHub194> opal-browser/master 95b0e1a meh: spec: set the timeout at 9 minutes
travis-ci has joined #opal
<travis-ci> [travis-ci] opal/opal-browser#66 (master - 6779e3e : meh): The build passed.
<travis-ci> [travis-ci] Build details :
travis-ci has left #opal [#opal]
meh` has quit [Ping timeout: 252 seconds]
fkchang has joined #opal
fkchang has quit [Ping timeout: 260 seconds]
fkchang has joined #opal
barry has joined #opal
barry has quit [Ping timeout: 246 seconds]
dragonkh has quit [Read error: Connection reset by peer]
dragonkh has joined #opal
dragonkh has quit [Ping timeout: 248 seconds]
ryanstout has quit [Quit: ryanstout]
barry has joined #opal
barry has quit [Ping timeout: 252 seconds]
marcandre has quit [Remote host closed the connection]
barry has joined #opal
barry has quit [Ping timeout: 252 seconds]
barry has joined #opal
dfranciosi has joined #opal
elia has joined #opal
RoxasShadowRS has joined #opal
e_dub has quit [Ping timeout: 272 seconds]
barry has quit [Remote host closed the connection]
barry has joined #opal
barry has quit [Ping timeout: 260 seconds]
barry has joined #opal
barry has quit [Remote host closed the connection]
barry has joined #opal
barry has quit [Ping timeout: 260 seconds]
fkchang has quit [Ping timeout: 252 seconds]
kludge` has quit [Ping timeout: 248 seconds]
kludge` has joined #opal
barry has joined #opal
e_dub has joined #opal
barry has quit [Remote host closed the connection]
barry has joined #opal
barry has quit [Ping timeout: 260 seconds]
barry has joined #opal
e_dub has quit [Quit: It's a hard knock life]
barry has quit []
elia has quit [Quit: (IRC Client:]
dfranciosi has quit [Remote host closed the connection]
meh` has joined #opal
dfranciosi has joined #opal
elia has joined #opal
gravityblast has joined #opal
<elia> benvenuto gravityblast
<gravityblast> hello everyone :)
<meh`> hello
jsilver has quit [Read error: Connection reset by peer]
<meh`> adambeynon, do we have an extend helper?
<adambeynon> meh`: helper? you mean `#extended()` ?
<meh`> no
<meh`> helper
<meh`> merge two javascript objects
<meh`> like jquery extend
<meh`> (working on IE support in opal-browser)
<adambeynon> oh right
<meh`> first time I need it
<adambeynon> nope, opal doesnt have one
<meh`> should I write my own or does it make sense to have it as helper?
<meh`> I think I should write my own, it's the first time since ever that I need it
<meh`> and it's only because IE is retarded
<adambeynon> meh`: yeah, i havent needed it before
wmnnd has joined #opal
<wmnnd> Hey there, is there a way to find out what is the corresponding line in the original code when there is a Javascript error?
<meh`> wmnnd, use source maps
RoxasShadowRS has quit [Ping timeout: 272 seconds]
<wmnnd> meh`: Is there a source maps feature built into Opal?
<meh`> wmnnd, yep
<meh`> they're enabled by default IIRC
<meh`> you just have to check your browser supports them
RoxasShadowRS has joined #opal
<wmnnd> meh`: Both Chrome and FF Nightly give me source maps. Do I have to enable it in Opal?
<meh`> wmnnd, possibly, I don't remember if it's disabled or enabled by default
<wmnnd> meh`: It seems to be enabled by default, but doesn't link to the correct path.
<meh`> wmnnd, what Opal version are you on?
<wmnnd> meh`: The latest gem.
<meh`> try with master
<wmnnd> I can't do that because then bundler says, opal-sprockets needs opal 0.5.0.
<meh`> wmnnd, remove opal-sprockets
<meh`> it's been merged into opal
<wmnnd> Ah, okay.
<wmnnd> meh`: Still, the source map path seems to be invalid.
<meh`> weird
<meh`> adambeynon, elia, ^
<wmnnd> It looks like it's jus not not handling the /__opal_source_maps__/ path correctly.
<wmnnd> It mentions source mappings for all my files, but Sinatra doesn't know those ditties ;-)
<meh`> guess it's a problem with the sinatra example
<wmnnd> Maybe something is wrong with the sprockets configuration?
<meh`> wmnnd, no, I think it's just a missing #map
<meh`> because the map isn't coming from /assets
<wmnnd> meh`: Well, should I use Opal::Server instead of map and Opal::Environment?
<meh`> wmnnd, you could try cascading like I do
<meh`> wmnnd, or look into Opal::Server code and map to the SourceMap thing
<meh`> I'd go with the latter
<wmnnd> meh`: I just don't know where to look for this, there don't seem to be examples for that out there.
<meh`> wmnnd, gimme a sec
<meh`> you have to map to that
<meh`> derp
<elia> meh`, I'm back
RoxasShadowRS has quit [Read error: Connection reset by peer]
<wmnnd> meh, I have now set up Opal::Server and it works fine for the opal/care libraries. However, my own code doesn't seem to get mapped.
<wmnnd> This is how I'm doing it:
<meh`> wmnnd, don't run the opal server
RoxasShadowRS has joined #opal
<meh`> just create the SourceMap thing yourself
<meh`> and map it normally
Kilo`byte has quit [Quit:]
<wmnnd> meh`: I'm not quite sure if I understand what you mean. If I do it like this, my own code still doesn't get mapped, but it works fine for opal/stdlib things:
<meh`> wmnnd, weird
<meh`> sorry, I don't have any more ideas, guess you'll have to go with the cascading thing like I do in opal-browserf
<wmnnd> meh`: However, unlike when I try to use a path under /__opal_source_maps__/ that actually doesn't exist, the links to where my maps should be return an empty 200.
Kilo`byte has joined #opal
<wmnnd> So *something* seems to be there, maybe Opal is just not actually generating the maps.
gravityblast has quit [Read error: Connection reset by peer]
gravityblast has joined #opal
<gravityblast> has anyone already tried ruby with opal on v8 loaded from c# on monogame deployed on wp8? cause I'm going to try, just to waste some time.
<meh`> nope
<gravityblast> nice answer, I can start then.
GitHub13 has joined #opal
<GitHub13> [opal-browser] meh pushed 2 new commits to master:
GitHub13 has left #opal [#opal]
<GitHub13> opal-browser/master 9e98954 meh: history: cleanup code and documentation
<GitHub13> opal-browser/master 13ef6a3 meh: storage: cleanup code and documentation
<elia> lol
travis-ci has joined #opal
<travis-ci> [travis-ci] opal/opal-browser#67 (master - 9e98954 : meh): The build was broken.
travis-ci has left #opal [#opal]
<travis-ci> [travis-ci] Build details :
<meh`> travis-ci, fuck you too
<meh`> and fuck safari
<meh`> and fuck this
<meh`> and fuck that
marcandre has joined #opal
travis-ci has joined #opal
<travis-ci> [travis-ci] opal/opal-browser#67 (master - 9e98954 : meh): The build passed.
<travis-ci> [travis-ci] Build details :
travis-ci has left #opal [#opal]
<meh`> travis-ci, yeah, you better be passing
<elia> man that travis!
DouweM has joined #opal
<meh`> mh
<meh`> something weird is going on
<meh`> everything is green, but the results don't come up
elia has quit [Ping timeout: 272 seconds]
Kilo`byte has quit [Quit:]
Kilo`byte has joined #opal
gravityblast has quit [Read error: Connection reset by peer]
gravityblast has joined #opal
<meh`> adambeynon, ping
<adambeynon> meh`: hey
<meh`> adambeynon, the way async specs are ran is kind of broken
<meh`> I'm trying to fix that and add timeout support
<meh`> using the #current_example is going to assplode
<meh`> is there no way for the #run_async call to know which example async was coming from?
<meh`> I mean, as I see it, the AsyncHelpers are bound to the group rather than the example
<adambeynon> meh`: yes, but only 1 async example is ever run at the same time
<adambeynon> it queues them
<meh`> adambeynon, I know that, but if you add a timeout
<meh`> the current one will be failed
<meh`> and go to the next
<meh`> but the current one might still be going on
<meh`> and without a timeout
<meh`> the results won't be shown
<meh`> so if an async specs fail
<meh`> it will just timeout
<meh`> and you won't even know which one it was
<adambeynon> are we on about what currently happens, or if we add a way to set timeouts on the actual examples?
<meh`> adambeynon, both :D
<meh`> adambeynon, I'm trying to add timeouts to async specs
<meh`> I can't because the timeout and the async spec run at the same time
<adambeynon> meh`: add a check in run_async()
<meh`> adambeynon, and what does it check?
<adambeynon> self.example_timedout
<adambeynon> or something like that
<meh`> and what do I check in the timeout?
<meh`> but is self an AsyncExample?
<meh`> or something else?
<meh`> this I don't understand
<adambeynon> meh`: yes, self will be an Async example, so we can just add an extra attribute
<adambeynon> example_completed
<adambeynon> or something
<meh`> ok, I can go from there
<meh`> I tried inspectin self.class
<adambeynon> that is set to true either on timeout or on failure
<meh`> but it's a buttload of weirdly named classes
<meh`> so I couldn't figure it out
<adambeynon> meh`: also, I had a thought for async specs
<adambeynon> could we just stub Exception.allocate
<adambeynon> so any exceptions we can catch
<adambeynon> ahh, but we wouldnt know if it passes
<adambeynon> never mind
<meh`> yeah
<meh`> adambeynon, but there's something
<meh`> I don't understand
<meh`> AsyncHelpers isn't mixed in AsyncExample
<meh`> so how can self be an AsyncExample there?
<meh`> yeah, it's false
<adambeynon> meh`: I added it through RSpec.configure
<adambeynon> meh`: I cant remeber why, but its "the recommended way"
<meh`> adambeynon, I still think your idea won't work
<meh`> current_example is always used
<meh`> so when the current_example time outs
<meh`> current_example will be the next
<meh`> in the meantime the async works on current_example, which is now the next
<meh`> adambeynon, in short, run_async can't use current_example
<adambeynon> meh`: run_async doesnt *have* to use RSpec.current_example
<adambeynon> im not sure why it does tbh
<meh`> adambeynon, so I can just run continue_async?
<meh`> because it doesn't work that way
<meh`> self ain't an AsyncExample in there
<adambeynon> meh`: what is self in that context?
<meh`> #<RSpec::ExampleGroups::Proc_2::Nestedefer:3182>
<meh`> RSpec::ExampleGroups::Proc_2::Nestedefer, Opal::RSpec::AsyncHelpers, RSpec::ExampleGroups::Proc_2::Nestedefer::LetDefinitions, RSpec::ExampleGroups::Proc_2, Opal::RSpec::AsyncHelpers, RSpec::ExampleGroups::Proc_2::LetDefinitions, RSpec::Core::ExampleGroup, RSpec::Core::MemoizedHelpers, RSpec::Core::Pending, RSpec::Core::MockFrameworkAdapter, RSpec::Matchers, Object, BasicObject]
<meh`> the ancestors
<adambeynon> ah yes. rspec and its ridiculous complexity
<meh`> yep
<adambeynon> meh`: that instance probably has an #example attribute
<adambeynon> let me check
<meh`> I can check
<meh`> no worries
<meh`> nope
gravityblast has quit [Read error: Connection reset by peer]
<adambeynon> meh`: indeed it doesnt
<adambeynon> but
<adambeynon> we override the #run method, so we could use instance_variable_set()
<meh`> I'll give it a shot
<adambeynon> meh`: Its all coming back how painful it was to customize the rspec stuff for our current async stuff
<meh`> adambeynon, is there a way to know if an example has finished?
<adambeynon> meh`: again, not built into rspec, so we would need to track that manually inside the subclass
<meh`> man
<meh`> this shit is awful
<meh`> I think I'm done
<meh`> just have to stand up and go back to my room to test =_=
<adambeynon> meh`: try looking through the rspec2 codebase :P rspec3 is much nicer
<adambeynon> meh`: lol :D
<meh`> ok, just a small problem
<meh`> the header remains as passed
<meh`> even if there are async failures
<meh`> and it doesn't work in IE11
<meh`> but that's another story
<meh`> it works in Safari 5.1
<meh`> adambeynon, were you using the async specs?
<wmnnd> I'm having trouble with using erb files again. I have my file, item.opalerb and I have required it. But when I use Template["item"], I get a NilClass.
<adambeynon> meh`: yes, quite a bit actually
<adambeynon> It may be struggling due to the dom wrappers in IE11
gravityblast has joined #opal
<adambeynon> I have only tried those in chrome
<adambeynon> wmnnd: try inspecting Template.paths
<adambeynon> It lists all templates
<meh`> well, this should work
<meh`> adambeynon, want to review the patch before I push it?
<meh`> adambeynon,
<wmnnd> adambeynon: It does list the template.
<wmnnd> Oh, I have to use Template[full/path/to/template] ...
ryanstout has joined #opal
dfranciosi has quit [Remote host closed the connection]
gravityblast has quit [Quit: gravityblast]
<wmnnd> adambeynon: If I want to pass a variable with a certan name to the template, do I have to do this via a wrapper class or is there a more elegant way?
elia has joined #opal
elia has quit [Quit: Computer has gone to sleep.]
<adambeynon> wmnnd: variables in templates is a little tricky, as the template is getting compiled ahead of time
<adambeynon> during compilation we dont know what are variables, and what are method calls
<meh`> adambeynon, is the patch fine?
<adambeynon> meh`: yeah looks fine
<meh`> ok, pushing
<adambeynon> if you want to use it now, you need to bump the gem release too
<adambeynon> (and add a note in the changelog under "edge")
<meh`> right
<adambeynon> meh`: also, make sure to "rake build" first ;)
<meh`> I can't
<meh`> adambeynon, you have to do the release, I can't push the gem
<adambeynon> meh`: oh, thats true
<adambeynon> ok
<meh`> pushing the change
<meh`> then do your thing whenever
<meh`> I'm using it from path temporarily
<meh`> still a long night to fix it to work on IE11 =_=
GitHub133 has joined #opal
<GitHub133> [opal-rspec] meh pushed 1 new commit to master:
<GitHub133> opal-rspec/master c7d6e14 meh: Add a timeout to async examples
GitHub133 has left #opal [#opal]
<meh`> and by it
<meh`> I mean opal-browser
<meh`> adambeynon, yeah, wait a sec before pushing the gem
<meh`> I have to figure out if the syntax error is in rspec or somewhere else
<meh`> forgot about it
<meh`> adambeynon, yeah, I didn't introduce the syntax error
<adambeynon> meh`: so there isnt one?
<meh`> there is one
<meh`> it's pointing at runner.rb:24
<meh`> specifically at the compiled source of
<meh`> I tried replacing setTimeout
<meh`> with $$.setTimeout
<meh`> so it's not the inlined thing that's broken
<adambeynon> meh`: what complains? the opal compiler?
<meh`> no, IE11
<meh`> it raises a SyntaxError
<adambeynon> meh`: can you copy/paste the generated source line
<meh`> adambeynon, yeah, gimme a sec
<meh`> trying to install IE6 so I can see what's going on
<adambeynon> meh`: it might be something before that, and the parse keeps on parsing optimistically
<meh`> IE6 fails with "world not a method of RSpec" instead
<adambeynon> hmmm.. I dont know
<adambeynon> the ie6 error is probably a runtime error
<adambeynon> on our part
<adambeynon> some for-in loop not copying some variable over
<meh`> adambeynon, the one in IE11 isn't clear at all
<meh`> because the runner actually runs
<meh`> only the timeouts don't run
<meh`> or only the results don't get updated
<meh`> somehow
<meh`> yeah, in IE11 it gets stuck somewhere
<meh`> on should get element by xpath
<meh`> probably the syntax error is in the used xpath
<meh`> and for some reason the stacktrace has nothing to do with the spec at all
<adambeynon> meh`: rspec uses a lot of try/catch blocks, so it could well be mucking up any stack traces
<meh`> but still
<meh`> it fucks it all up instead of failing it
<meh`> :|
<meh`> fucking IE
<meh`> I confirm it
<meh`> it's the xpath
<meh`> throwing an uncatchable exception
<meh`> with a fucked up and unrelated stacktrace
elia has joined #opal
<meh`> and it works in Safari 5.1
<meh`> my god, they can't do one thing right
<adambeynon> meh`: uncatchable exception? I remember something about not all errors inheriting from Error.prototype in IE
<adambeynon> maybe thats one of them
<adambeynon> (non Error subclasses wont get caught by opal)
<meh`> adambeynon, no, javascript supports uncatchable exceptions
<meh`> they can't be catched with catch, at all
<adambeynon> meh`: how do they work?
<meh`> they're only internal
<meh`> in the engine
<meh`> they don't have a public interface
<meh`> the engine can throw uncatchable exceptions
<meh`> like in this xpath case
<adambeynon> and IE decided that an unsupported xpath needs to completely break the running app?
<meh`> yep
<meh`> good ol' IE
<meh`> I'd be fine with it if the microsoft shills stopped saying the new IE is awesome, fast and compliant
<meh`> when we're in motherfucking 2014
<meh`> and all my shit works in every browser EXCEPT IE11
<meh`> all of my rage
<meh`> I should sue them for killing me with stress
<meh`> I'm starting to think it's not xpath either
<meh`> it might be querySelector
<meh`> not
<ryanstout> is it just me, or is sprockets really complex for what it does?
<meh`> ryanstout, same as rspec
<meh`> same as anything by the W3C
<meh`> same as anything in computers
<meh`> I don't want to live on this planet anymore
<ryanstout> meh`: bad day?
<meh`> ryanstout, adding IE support to opal-browser
<meh`> so yes, very bad day
<ryanstout> ah
<ryanstout> yea, thats tough
<ryanstout> IE's the worse
<ryanstout> also, with everything sprockets does, I don't get why I can't append_path at a location in the logical path
elia has quit [Quit: Computer has gone to sleep.]
elia has joined #opal
fkchang has joined #opal
<elia> ryanstewart, tell me about append_path
<elia> ouch
<elia> ryanstout, I mean
<ryanstout> basically, I want to be able to do env.append_path('/path/on/disk', '/path/in/url')
<ryanstout> if that makes since
<elia> ryanstout, and then have requires go find stuff in the right place, right?
<ryanstout> yea
<elia> i think that could come more easily once the real-requires branch is finished
<elia> gh482
<ryanstout> elia: what's the real requires branch?
<elia> basicaly switches from passing requires from sprockets directly to handling them inside the processor
<ryanstout> cool, I like that idea
<elia> required files are included as sources inside Opal.modules
<elia> and then executed at the require place
<ryanstout> so then opal wouldn't depend on sprockets?
<elia> probably
<elia> I copied a bunch of stuff from the sass_importer inside sprockets itself
wmnnd has quit [Ping timeout: 260 seconds]
<ryanstout> for my framework, my asset compilation is sort of different from how sprockets does it, so I'm debating if I want to write a simple thing to do the basics of what sprockets does, but how I need it
<elia> how's different?
<ryanstout> so I've got it where stuff is broken up into components like this: app/component1/controller, app/component1/views, app/component2/controller, etc... So I want it where you could go to /assets/component1 and get the stuff from component1, but the problem is if I just ass the /app/component1 to the path, then all of the other files will be visible, some of which within the component shouldn't be. If that makes since
<meh`> adambeynon, it wasn't what I thought
<meh`> adambeynon, it was actually querySelectorAll
<meh`> I didn't think it would raise on syntax error in the selector
<meh`> so I didn't wrap it up
mneorr has joined #opal
<meh`> but still
<meh`> none of those xpaths work
<meh`> must have done something wrong that doesn't work in IE
<meh`> wait
<meh`> what
<meh`> they discontinued xpath in IE10
<meh`> ...
<meh`> this is madness
<ryanstout> meh`: really?
<meh`> UPDATE 26/7/2013 IE11 isn't stable yet, but it still doesn't support document.evaluate. If it won't support it in the stable release, I doubt it will ever support it. Needless to say this is ridicolous.
<meh`> yes
<meh`> really
<meh`> UPDATE 23/11/2013 IE11 is stable now but, sadly, it doesn't support document.evaluate. As heavy-weight XML documents are used less and less in web applications in favor of JSON or other light notation formats, this is becoming less of a problem, but still.
<meh`> what the fuck is wrong with them
<ryanstout> meh`: that sucks, I was looking up special comments with that
<meh`> I don't even
<meh`> why do they even try
<meh`> they're doing more damage than good
<ryanstout> meh`: looks like there is a work aroundish
<ryanstout> meh`: there are pure JS fallbacks
<meh`> ryanstout, I'm not going to add a huge dependency like that to opal-browser
<meh`> especially not something by Google
<ryanstout> yea
<ryanstout> you could just say if you want IE11 support, conditionally include it
<ryanstout> what do you use xpath for in opal-browser?
<meh`> ryanstout, tests
RoxasShadowRS has quit [Quit: Leaving]
gravityblast has joined #opal
<meh`> ryanstout, you know what? fuck that, I'll support wgxpath
<meh`> adambeynon, can we fix async specs ending up in random groups?
<meh`> it's not helpful
<meh`> adambeynon, also I think there's a bug in IE with yield
<meh`> without I think, it's failing, hard
<adambeynon> meh`: I suppose we could tag the example group elements with an id, based on its object id to make them easier to find later on
<meh`> adambeynon, even having them format AFTER everything would be better than this
<meh`> now I'm getting even asynchronous issues with IE11
<meh`> that don't make sense
<meh`> and since I can't trust stacktraces
<meh`> I don't even know what I'm looking at
wmnnd has joined #opal
gravityblast has quit [Quit: gravityblast]
gravityblast has joined #opal
<meh`> adambeynon, disregard that
<meh`> it works
<meh`> adambeynon, ok, all is green
<meh`> adambeynon, how do we proceed with opal-rspec?
<meh`> I can't push these changes without those fixes
<meh`> I think
gravityblast has quit [Quit: gravityblast]
gravityblast has joined #opal
<gravityblast> the first day in the opal channel has been exciting. I've also drunk a lot o camomilla and I'm going to sleep. have a good night brothers. coding vobiscum. aloha.