fnichol

A Common .ruby-version File For Ruby Projects

Background

I've been using this technique in most of my Ruby projects lately where Ruby versions are required:

• Create .rbenv-version containing the target Ruby using a definition name defined in ruby-build (example below). These strings are a proper subset of RVM Ruby string names so far...
• Create .rvmrc (with rvm --create --rvmrc "1.9.3@myapp") and edit the environment_id= line to fetch the Ruby version from .rbenv-version (example below).

Today I learned about another Ruby manager, rbfu, where the author is using a similar technique with .rbfu-version.

fetep

input {
  stdin {
    type => rails
  }
}

filter {
  grok {
    type => "rails"
    pattern => "Completed %{GREEDYDATA:operation} in %{NUMBER:time:int}ms"

lukemelia

require 'bundler/setup'
require 'sass'
require 'compass'
require 'rake-pipeline'
require 'listen'
require 'rack/lock'
require 'ruby-debug'
require 'securerandom'

STDOUT.sync = true

srinivasmohan

#Knife invocations supply FQDN as the node name at creation time and this becomes hostname( option -N)

execute "Configure Hostname" do
  command "hostname --file /etc/hostname"
  action :nothing
end

#Ensure the hostname of the system is set to knife provided node name
file "/etc/hostname" do
  content node.name

rlivsey

Ember.HandlebarsTransformView = Ember.View.extend(Ember._Metamorph, {
  rawValue: null,
  transformFunc: null,

  value: function(){
    var rawValue = this.get('rawValue'),
        transformFunc = this.get('transformFunc');
    return transformFunc(rawValue);
  }.property('rawValue', 'transformFunc').cacheable(),

lancejpollard

Some random notes on the pangs of ember. Will be expanding as they are uncovered.

Building a form

Say you have a form that maps to a model, something like:

<form>
  <fieldset>
    <legend>Who are you?</legend>

wycats

Relationship Semantics

The new relationship semantics change the current app/store/transaction/adapter APIs in several ways:

Changes to the Application API

At present, a record can be freely moved across transactions as long as it has no changes. Once a record accumulates at least one change, an application cannot move it out of its current transaction until the transaction is committed or rolled back.

sundbp

- Perhaps can get to it without any java code: https://gist.github.com/1680784 
- Interpreter only flags: https://github.com/quix/boc/blob/master/jext/boc/BocService.java 

Code sections that are relevant:
- Kernel#binding: return RubyBinding.newBinding(context.runtime, context.currentBinding());

- ThreadContext: 
-   1223     public Binding currentBinding(IRubyObject self) {
-   1224         Frame frame = getCurrentFrame();
-   1225         return new Binding(self, frame, frame.getVisibility(), getRubyClass(), getCurrentScope(), backtrace[backtraceIndex].clone());

rlivsey

App.NavSectionMixin = Ember.Mixin.create({
  enter: (router, context) ->
    router.set("sectionNavigationController.current", @get("section"))
    @_super(router, context)

  exit: (router, context) ->
    router.set("sectionNavigationController.current", null)
    @_super(router, context)
})

headius

Java 7 does not currently have tiered compilation on by default, and we do not enable invokedynamic.

Default settings (no indy, no tiered)

system ~/projects/jruby $ (pickjdk 4 ; time jruby -e 1)
New JDK: jdk1.7.0_07.jdk

real	0m1.255s
user	0m1.953s
sys	0m0.084s