These are chat archives for opal/opal

8th
Jun 2015
Vais Salikhov
@vais
Jun 08 2015 01:45
@eregon yeah, I was surprised that some benchmarks are actually faster on Opal. Kinda makes me doubt my code to be honest, hope I didn't mess up somewhere :sweat_smile:
Vais Salikhov
@vais
Jun 08 2015 02:21
Just a little over a week ago we celebrated Opal passing 5005 RubySpec examples. That number today is 5122 (!) Not only that, but we are running more of the cruby (MRI) test suite now, albeit that number is only a total of 43 assertions thus far. Go Opal team and everyone who has contributed! Looking forward to the next week in Opal!
Elia Schito
@elia
Jun 08 2015 06:06
Adam Beynon
@adambeynon
Jun 08 2015 06:16
@vais good work! :+1:
Elia Schito
@elia
Jun 08 2015 09:31
@adambeynon @meh @vais I think we should release v0.8.0
Adam Beynon
@adambeynon
Jun 08 2015 09:51
@elia yeap, happy with that. what was the outcome with the native calling stuff? leaving it on master or in the release?
Elia Schito
@elia
Jun 08 2015 09:51
I'd leave them on master until we try them out on some of our apps
Adam Beynon
@adambeynon
Jun 08 2015 09:54
agreed. seeing as I havent been able to do much in regards to 0.8, want the honours of releasing?
Elia Schito
@elia
Jun 08 2015 09:55
thanks for the offer, but if you can do that I'd prefer as I'm a bit busy here at work :)
Adam Beynon
@adambeynon
Jun 08 2015 09:56
ha
no problem
is opal-rails etc working with master
Elia Schito
@elia
Jun 08 2015 09:57
just realized "on the fence" doesn't mean what I thought :)
@adambeynon yes, I just have some problems with travis file-system
but just for running specs, so, even if it turns out to be something else I don't think it should be a problem
Mitch VanDuyn
@catmando
Jun 08 2015 14:16
is there a way in the browser to tell what version of opal happens to be running?
Adam Jahn
@ajjahn
Jun 08 2015 14:35
@catmando console.log(Opal.RUBY_ENGINE_VERSION)
Mitch VanDuyn
@catmando
Jun 08 2015 14:36
@ajjahn thanks!
Adam Jahn
@ajjahn
Jun 08 2015 14:38
You bet!
Mitch VanDuyn
@catmando
Jun 08 2015 14:47
what is the state of 0.8? I am just considering moving to that from 0.7.2... wondering how stable it is? Should we wait a bit or go for it. I have a a team using it, so I don't want to be too disruptive :-)
to them
Elia Schito
@elia
Jun 08 2015 14:49
@catmando I'm using it on a site we have in production, but any other feedback would be useful
@catmando rails?
Mitch VanDuyn
@catmando
Jun 08 2015 14:50
@elia yes rails
Okay well first step is I will give it a whirl, and see if all the tests pass :-)
Elia Schito
@elia
Jun 08 2015 14:50
@catmando should be fine, possible issues are related to opal-rspec
please let me know
Mitch VanDuyn
@catmando
Jun 08 2015 14:51
So perhaps tests won't pass :-(
Elia Schito
@elia
Jun 08 2015 14:51
it's more like checking if they start at all
Mitch VanDuyn
@catmando
Jun 08 2015 14:55
@elia so I get
Could not find gem 'opal (~> 0.7.0) ruby', which is required by gem 'opal-rails (>= 0) ruby', in any of the sources.
do I have to also pull in a different opal-rails version?
Elia Schito
@elia
Jun 08 2015 14:55
gem 'opal-rails',  github: 'opal/opal-rails'
gem 'opal',        github: 'opal/opal'
gem 'opal-haml',   github: 'opal/opal-haml'
gem 'opal-rspec',  github: 'opal/opal-rspec'
gem 'opal-jquery', github: 'opal/opal-jquery'
@catmando that's what I'm using right now
Mitch VanDuyn
@catmando
Jun 08 2015 14:58
we are still on rails 3.2 .... i think that is problematic? I am getting
Bundler could not find compatible versions for gem "sprockets":
  In snapshot (Gemfile.lock):
    sprockets (2.2.3)

  In Gemfile:
    opal-rspec (>= 0) x86-mingw32 depends on
      opal (< 0.9, >= 0.7.0) x86-mingw32 depends on
        sprockets (~> 3.1) x86-mingw32

Running `bundle update` will rebuild your snapshot from scratch, using only
the gems in your Gemfile, which may resolve the conflict.
Elia Schito
@elia
Jun 08 2015 14:59
Not sure if sprockets 3 is supported on rails 3…
Mitch VanDuyn
@catmando
Jun 08 2015 14:59
I don't think easily
Elia Schito
@elia
Jun 08 2015 15:00
try with bundle update sprockets
My current app is 4.1
Mitch VanDuyn
@catmando
Jun 08 2015 15:04
no joy - oh well :-(
Bundler could not find compatible versions for gem "sprockets":
  In Gemfile:
    sprockets (~> 2.2.1) x86-mingw32

    sprockets (3.1.0)
Elia Schito
@elia
Jun 08 2015 15:04
:(
@catmando do you have sprockets directly in the gemfile?
Mitch VanDuyn
@catmando
Jun 08 2015 15:05
nope
that seemed weird to me as well
Elia Schito
@elia
Jun 08 2015 15:05
I know bundler improved error messages over time
maybe it's an older version
Mitch VanDuyn
@catmando
Jun 08 2015 15:07
still I think I went through this already with react.rb and it was a black hole
Elia Schito
@elia
Jun 08 2015 15:08
@catmando if you can share the Gemfile + .lock I can try to make it work locally
Mitch VanDuyn
@catmando
Jun 08 2015 15:10
i did on your private chat line
Elia Schito
@elia
Jun 08 2015 15:11
:+1:
Ryan Stout
@ryanstout
Jun 08 2015 18:36
I've got a weird opal-rspec issue I was wondering if anyone could help me with or point me in the right direction to fix. I'm using RSpec.shared_context. In MRI if I have a let block in my shared_context and the same let in a describe block, the describe block is used. But in opal, the shared_context one is.
Jared White
@jaredcwhite
Jun 08 2015 18:54
@vais I'd love to promote your quote about the RubySpec examples and cruby test suite, etc. If you want to elaborate slightly more in a marketing-ish way, I'll put it in this week's Opalist issue :)
Elia Schito
@elia
Jun 08 2015 20:12
@ryanstout can it be related to the fact that current opal-rspec is 3.0.0.beta?
Ryan Stout
@ryanstout
Jun 08 2015 20:42
@elia I'm not running a pre-release and am on opal 0.7.2
Elia Schito
@elia
Jun 08 2015 21:41
@ryanstout what I meant is that opal-rspec ships a rather outdated rspec version
which is 3.0 beta
Ryan Stout
@ryanstout
Jun 08 2015 21:41
ah
I doubt this behavior has changed recently, but I'll look through their commit log to see if I can verify