import java.awt._
import java.io._
import javax.imageio._

def captureScreenshot(filepath : String) = {
  val screenRect = new Rectangle(Toolkit.getDefaultToolkit().getScreenSize())
  val capture = new Robot().createScreenCapture(screenRect)
  ImageIO.write(capture, "png", new File(filepath, "screen.png"))
}

SQL> @ "foo.sql"
DOC>
DOC>  -- The GUID of the document i
DOC>  doc_guid varchar2(33) not null
DOC>);
DOC>
DOC>create table mx_values (
DOC>  mx_values_id varchar2(33) not null primary key,
DOC>  value_id integer not null,

The problem turned out to be caused by having newlines in my SQL commands. E.g.:

CREATE TABLE foo (
  -- The id of the foo
  id integer not null,

  -- The data of the foo
  data varchar2(200) not null
);

I did this to provide visual breaks in the code. SQL Developer was fine with it, but SQL*Plus blew up. My solution was to just make the empty lines comments using the -- comment syntax.

1/26/11 26 Jan 8:13:49 PM [0x0-0x1c61c6].com.apple.systempreferences[88942] /usr/local/mysql/support-files/mysql.server: line 256: my_print_defaults: command not found

A MySQL bug thread suggested that the server could be started directly:

sudo /usr/local/mysql/support-files/mysql.server start

however, I got the same error:

$ sudo /usr/local/mysql/support-files/mysql.server start
/usr/local/mysql/support-files/mysql.server: line 256: my_print_defaults: command not found
Starting MySQL
ERROR! Couldn't find MySQL server (./bin/mysqld_safe)

Later in that same bug thread, the actual solution can be found. The problem was a recent update to the mysql.server script. By manually specifying the install location of MySQL on mysql.server line 46:

basedir=/usr/local/mysql

the problem is resolved

$ sudo /usr/local/mysql/support-files/mysql.server start
Starting MySQL
SUCCESS!

This also corrects the problem with the preference pane.

The second parameter to the post method (or any of the Rack::Test methods) is parameters that are sent up with your request. This is also where you specify your JSON data. The only other thing you need to do is specify your content type as JSON.

For example, suppose you have specified the following endpoint in Sinatra that expects posted JSON data:

post '/foo' do
    data = JSON.parse(request.body.read.to_s)
    # rest of logic here
end

You could test that endpoint by posting test JSON like this:

def test_create_choice
    post '/foo', {:bar => "baz"}.to_json, "CONTENT_TYPE" => "application/json"
    # validate response here
end

Hope this helps any other n00bs out there wondering the same thing.

$ sudo make install

You may still get an error when trying to run tesseract:

$ tesseract foo.png bar
tesseract: error while loading shared libraries: libtesseract_api.so.3 cannot open shared object file: No such file or directory

You need to update the cache for the runtime linker. The following should get you up and running:

$ sudo ldconfig

DataMapper.setup(:default, ENV['DATABASE_URL'])

Where my DATABASE_URL was set as an environment variable to something along the lines of the following:

DATABASE_URL=mysql://username:password@localhost:3306/database_name

The key point to note is that I’m trying to point it to TCP port 3306 on my local machine. When I’d trying to load up a model object and hit the database, I got the following error:

DataObjects::SQLError: Can't connect to local MySQL server through socket '/opt/local/var/run/mysql5/mysqld.sock' (2)

Full stack trace:

DataObjects::SQLError: Can't connect to local MySQL server through socket '/opt/local/var/run/mysql5/mysqld.sock' (2)
	/Library/Ruby/Gems/1.8/gems/data_objects-0.10.2/lib/data_objects/connection.rb:76:in `initialize'
	/Library/Ruby/Gems/1.8/gems/data_objects-0.10.2/lib/data_objects/connection.rb:76:in `send'
	/Library/Ruby/Gems/1.8/gems/data_objects-0.10.2/lib/data_objects/connection.rb:76:in `__new'
	/Library/Ruby/Gems/1.8/gems/data_objects-0.10.2/lib/data_objects/pooling.rb:177:in `new'
	/Library/Ruby/Gems/1.8/gems/data_objects-0.10.2/lib/data_objects/pooling.rb:172:in `synchronize'
	/Library/Ruby/Gems/1.8/gems/data_objects-0.10.2/lib/data_objects/pooling.rb:172:in `new'
	/Library/Ruby/Gems/1.8/gems/data_objects-0.10.2/lib/data_objects/pooling.rb:119:in `new'
	/Library/Ruby/Gems/1.8/gems/data_objects-0.10.2/lib/data_objects/connection.rb:65:in `new'
	/Library/Ruby/Gems/1.8/gems/dm-do-adapter-1.0.2/lib/dm-do-adapter/adapter.rb:235:in `open_connection'
	/Library/Ruby/Gems/1.8/gems/dm-do-adapter-1.0.2/lib/dm-do-adapter/adapter.rb:260:in `with_connection'
	/Library/Ruby/Gems/1.8/gems/dm-do-adapter-1.0.2/lib/dm-do-adapter/adapter.rb:138:in `read'
	/Library/Ruby/Gems/1.8/gems/dm-core-1.0.2/lib/dm-core/repository.rb:162:in `read'
	/Library/Ruby/Gems/1.8/gems/dm-core-1.0.2/lib/dm-core/model.rb:379:in `first'
	./routes/services.rb:11:in `GET /v1/:choice_id'
	/Library/Ruby/Gems/1.8/gems/sinatra-1.1.0/lib/sinatra/base.rb:1032:in `call'
	/Library/Ruby/Gems/1.8/gems/sinatra-1.1.0/lib/sinatra/base.rb:1032:in `compile!'
	/Library/Ruby/Gems/1.8/gems/sinatra-1.1.0/lib/sinatra/base.rb:620:in `instance_eval'
	/Library/Ruby/Gems/1.8/gems/sinatra-1.1.0/lib/sinatra/base.rb:620:in `route_eval'
	/Library/Ruby/Gems/1.8/gems/sinatra-1.1.0/lib/sinatra/base.rb:604:in `route!'
	/Library/Ruby/Gems/1.8/gems/sinatra-1.1.0/lib/sinatra/base.rb:656:in `process_route'
	/Library/Ruby/Gems/1.8/gems/sinatra-1.1.0/lib/sinatra/base.rb:653:in `catch'
	/Library/Ruby/Gems/1.8/gems/sinatra-1.1.0/lib/sinatra/base.rb:653:in `process_route'
	/Library/Ruby/Gems/1.8/gems/sinatra-1.1.0/lib/sinatra/base.rb:603:in `route!'
	/Library/Ruby/Gems/1.8/gems/sinatra-1.1.0/lib/sinatra/base.rb:602:in `each'
	/Library/Ruby/Gems/1.8/gems/sinatra-1.1.0/lib/sinatra/base.rb:602:in `route!'
	/Library/Ruby/Gems/1.8/gems/sinatra-1.1.0/lib/sinatra/base.rb:741:in `dispatch!'
	/Library/Ruby/Gems/1.8/gems/sinatra-1.1.0/lib/sinatra/base.rb:530:in `call!'
	/Library/Ruby/Gems/1.8/gems/sinatra-1.1.0/lib/sinatra/base.rb:706:in `instance_eval'
	/Library/Ruby/Gems/1.8/gems/sinatra-1.1.0/lib/sinatra/base.rb:706:in `invoke'
	/Library/Ruby/Gems/1.8/gems/sinatra-1.1.0/lib/sinatra/base.rb:706:in `catch'
	/Library/Ruby/Gems/1.8/gems/sinatra-1.1.0/lib/sinatra/base.rb:706:in `invoke'
	/Library/Ruby/Gems/1.8/gems/sinatra-1.1.0/lib/sinatra/base.rb:530:in `call!'
	/Library/Ruby/Gems/1.8/gems/sinatra-1.1.0/lib/sinatra/base.rb:516:in `call'
	/Library/Ruby/Gems/1.8/gems/rack-1.2.1/lib/rack/showexceptions.rb:24:in `call'
	/Library/Ruby/Gems/1.8/gems/rack-1.2.1/lib/rack/lint.rb:48:in `_call'
	/Library/Ruby/Gems/1.8/gems/rack-1.2.1/lib/rack/lint.rb:36:in `call'
	/Library/Ruby/Gems/1.8/gems/rack-1.2.1/lib/rack/showexceptions.rb:24:in `call'
	/Library/Ruby/Gems/1.8/gems/rack-1.2.1/lib/rack/commonlogger.rb:18:in `call'
	/Library/Ruby/Gems/1.8/gems/rack-1.2.1/lib/rack/content_length.rb:13:in `call'
	/Library/Ruby/Gems/1.8/gems/rack-1.2.1/lib/rack/chunked.rb:15:in `call'
	/Library/Ruby/Gems/1.8/gems/rack-1.2.1/lib/rack/handler/mongrel.rb:67:in `process'
	/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:159:in `process_client'
	/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:158:in `each'
	/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:158:in `process_client'
	/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:285:in `run'
	/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:285:in `initialize'
	/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:285:in `new'
	/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:285:in `run'
	/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:268:in `initialize'
	/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:268:in `new'
	/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:268:in `run'
	/Library/Ruby/Gems/1.8/gems/rack-1.2.1/lib/rack/handler/mongrel.rb:38:in `run'
	/Library/Ruby/Gems/1.8/gems/rack-1.2.1/lib/rack/server.rb:213:in `start'
	/Library/Ruby/Gems/1.8/gems/rack-1.2.1/lib/rack/server.rb:100:in `start'
	/Library/Ruby/Gems/1.8/gems/rack-1.2.1/bin/rackup:4
	/usr/bin/rackup:19:in `load'
	/usr/bin/rackup:19

Despite the fact that I was telling it to go after a TCP port, it was attempting to connect to MySQL via a socket (the reason it was getting the error is it was looking for the socket at /opt/local/var/run/mysql5/mysqld.sock and mine was configured /tmp/mysql.sock — but that's not the point, it shouldn't have been looking there to begin with

Through trial and error I found that it appears that DataMapper automatically falls back to socket based communication with MySQL when you specify localhost. I was able to correct the error by specifying an IP address instead:

DATABASE_URL=mysql://username:password@127.0.0.1:3306/database_name

var closure;

for(var i = 0; i <= 5; i++) {
  var x = i * i;
  if( i == 1 ) {
    closure = function() { alert(x); };
  }
}

closure();

What do you think the output of the alert box will be? At first blush it's easy to think it will be 1 because the variable x is declared within the for loop.

Run Code

In reality, though, the output is 25 because despite the variable declaration in the for loop, the code is functionally equivalent to this:

var closure;
var x;

for(var i = 0; i <= 5; i++) {
  x = i * i;
  if( i == 1 ) {
    closure = function() { alert(x); };
  }
}

closure();

This is important to remember when working with closures in loops.

So how do solve this problem? Manually create a new scope by creating and invoking an anonymous function.

var closure;

for(var i = 0; i <= 5; i++) {
  var x = i * i;
  if( i == 1 ) {
    (function(x) {
      closure = function() { alert(x); };
    })(x);
  }
}

closure();

Run Code

With the newly introduce lexical scope, the program returns 1 as one would expect.

Everything compiled fine, but when I went to view the ASXM in the browser to manually invoke the methods to test it, the normal automatically generated info page didn’t come up. Trying to grab the WSDL also gave me a blank page.

I then attached the debugger to IIS to observe what was happening when I tried to view the ASMX info page. By breaking on exceptions, I was able to uncover the following error:

The XML element ‘XXX’ from namespace ‘http://tempuri.org/’ references a method and a type. Change the method’s message name using WebMethodAttribute or change the type’s root element using the XmlRootAttribute.

With a little more thinking, I was able uncover what I believe was going on.

I had defined a complex type to return as a response:

public class FooResponse {...}

[WebMethod]
public FooResponse Foo() {...}

Note that here the exact name pairing of Foo/Foo+Response is important. When I changed the method name as follows, the problem went away:

public class FooResponse {...}

[WebMethod]
public FooResponse Fooxxx() {...}

What I believe is happening is .NET is attempting to automatically wrap the response coming from the Foo method with an element named FooResponse. The use of that same name as the object you want to return creates ambiguity. By changing the name of my response object, or the name of my method I was able to avoid this collision.

I have also posted this information in response to a question on StackOverflow.