These are chat archives for opal/opal

4th
Jul 2015
Vais Salikhov
@vais
Jul 04 2015 02:33

@elia something's broken in the latest rubyspec, I'm consistently getting this:

..........FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory
rake aborted!

I am able to run your new String#split specs separately though, so the problem must be somewhere else, I will track it down after I fix String#split per the new specs. When it rains it pours.

Vais Salikhov
@vais
Jul 04 2015 03:50
@elia fixed the FATAL ERROR problem above and updated to latest rubyspec here opal/opal#976. Next step once this and opal/opal#974 are merged into master is to uncomment the failures for your new String#split specs in filters/bugs/string.rb, run the spec suite (everything should pass at that point), and commit. Makes sense?
@ryanstout we're getting there :)
Ryan Stout
@ryanstout
Jul 04 2015 03:53
@vais thanks, I owe you one :-)
Elia Schito
@elia
Jul 04 2015 09:44
@vais still around?
Vais Salikhov
@vais
Jul 04 2015 10:02
@elia What's up?
Elia Schito
@elia
Jul 04 2015 10:03
@vais hey, was just asking for help on how to test opal/opal#969 before merging
question is still valid of course :grin:
btw I'm going to release rc2 in a few moments
Vais Salikhov
@vais
Jul 04 2015 10:06
Sorry, @elia, didn't have time to wrap my mind around that one. Now I am on mobile on a crappy wifi, so definitely have no answer for you at this time...
Elia Schito
@elia
Jul 04 2015 10:08
no worries at all
Elia Schito
@elia
Jul 04 2015 10:19
@/all 0.8.0.rc2 is out 🌝 please try it out! cc @ryanstout
Vais Salikhov
@vais
Jul 04 2015 13:16
@elia so will 0.8 include everything on master up to the point of release, or will it be capped at a certain commit?
Elia Schito
@elia
Jul 04 2015 13:18
@vais stops just before the merge of .JS stuff from jeremy evans
there was enough stuff already, had set a limit :D
the rest is set for 0.9 for which we can set our goals or just let some time pass by
Vais Salikhov
@vais
Jul 04 2015 13:21
@elia that's kind of a bummer cause there's been quite a fees bug fixes since then.
a few (typing on my phone, sorry)
Elia Schito
@elia
Jul 04 2015 13:22
Yeah, I know, my intention is to get out 0.9 way faster
Vais Salikhov
@vais
Jul 04 2015 13:25
Hmm I guess I'm trying to understand it from e.g. @ryanstout perspective maintaining a framework that depends on Opal. Volt is still on 0.6? If Volt updates to 0.8, how long will it be until Volt updates to 0.9?
I.e does it even make sense for them to update to 0.8 or just wait for 0.9? I'm definitely out of my depth here, just curious and wondering how people manage this kind of stuff.
Elia Schito
@elia
Jul 04 2015 13:30
@vais once 0.8 is out imo is time to start the works for 0.9
also unless sprockets 4 is released in the meanwhile 0.9 will be mostly new feat & fixes
and 0.8 is so important for users bc it brings back working sourcmaps
Vais Salikhov
@vais
Jul 04 2015 13:35
:+1:
Re Sprockets 4.0 is that kinda like Perl 6 :trollface:
Elia Schito
@elia
Jul 04 2015 13:55
lol, I keep good hope tho, v3 is basically v4 with v2 backward compatibility, for opal 0.9 I might even be able to remove some hacks I had to do to make sourcemaps work for v2, but I need to update processors to the new format first
Vais Salikhov
@vais
Jul 04 2015 14:02
Yep, trolling aside, I really hope so as well. Thank you for all the work you've put in to make source maps work with the existing setup! Working source maps are absolutely critical to Opal' success if that even needs to be stated.
Elia Schito
@elia
Jul 04 2015 14:04
🌟
Ryan Stout
@ryanstout
Jul 04 2015 19:17
@vais volt is currently on 0.7.2
the upgrade to 0.8 wasn't too bad, so far the only thing that took some rethinking was the module system (since we were generating script tags ourself)
@elia and @vais thanks for fixing that issue, nice work