do_sqlite3 fails under ruby-1.9.2-rc2: dm-do-adapter-1.0.0/lib/dm-do-adapter/adapter.rb:140:in `set_types': Invalid type given (ArgumentError)
Reported by mbj | July 24th, 2010 @ 01:19 PM
Here is my stripped down problem:
$ ruby -v
ruby 1.9.2dev (2010-07-11 revision 28618) [x86_64-linux]
$ cat fail.rb
require 'dm-core'
class Person
include DataMapper::Resource
property :id,Serial
property :firstname,String
property :lastname,String
end
DataMapper.setup(:default,"sqlite://:memory:")
Person.first
$ ruby fail.rb
/home/mbj/.rvm/gems/ruby-1.9.2-rc2/gems/dm-do-adapter-1.0.0/lib/dm-do-adapter/adapter.rb:140:in `set_types': Invalid type given (ArgumentError)
from /home/mbj/.rvm/gems/ruby-1.9.2-rc2/gems/dm-do-adapter-1.0.0/lib/dm-do-adapter/adapter.rb:140:in `block in read'
from /home/mbj/.rvm/gems/ruby-1.9.2-rc2/gems/dm-do-adapter-1.0.0/lib/dm-do-adapter/adapter.rb:260:in `with_connection'
from /home/mbj/.rvm/gems/ruby-1.9.2-rc2/gems/dm-do-adapter-1.0.0/lib/dm-do-adapter/adapter.rb:138:in `read'
from /home/mbj/.rvm/gems/ruby-1.9.2-rc2/gems/dm-core-1.0.0/lib/dm-core/repository.rb:162:in `read'
from /home/mbj/.rvm/gems/ruby-1.9.2-rc2/gems/dm-core-1.0.0/lib/dm-core/model.rb:385:in `first'
from fail.rb:12:in `<main>'
I traced execution down to do_sqlite3 at do_sqlite3.c#cCommand_set_types and here my current knowledge about do and ruby-c extensions ends for today.
I'm not affected by this Problem under ruby-1.9.2-rc1
Comments and changes to this ticket
-
Dan Kubb (dkubb) July 28th, 2010 @ 12:56 AM
- Assigned user set to “Dirkjan Bussink”
- State changed from “new” to “unconfirmed”
-
Dirkjan Bussink July 30th, 2010 @ 01:55 AM
Do you have more details on your platform? I've tried to reproduce the issue myself but it works fine with 1.9.2-rc2 here on my system.
-
mbj July 30th, 2010 @ 02:15 AM
- Assigned user cleared.
Thx for your (now) wasted time,
The platform is (was) and Amd64 based server, it miserably failed this night. I migrated the services to an ec2 instance (32bit), and know ruby-1.9.2-rc2 works fine with do_sqlite3. This seems like an irreproducible error (the hardware is unfixable). We can close this issue.
Again thx for your time. I'm sorry, the machine should have gone into the wild a few days before, so your time would not have been wasted.
Am I to dump to find the "ticket can be closed" Button in Lighthouse???
-
Dirkjan Bussink July 30th, 2010 @ 10:24 AM
- State changed from “unconfirmed” to “not-applicable”
Probably only project members can close tickets. Don't feel too sorry for posting an issue, better to have this than to not have any report at all.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Dan Kubb (dkubb)
Dirkjan Bussink
mbj