search for: 0.10.1

Hi (Eric?), A couple of questions while using the 'virsh blockpull' Summary: 1] Created snapshots this way: base<-snap1<-snap2<-snap3 (online, external snapshot --disk-only) 2] I did a 'virsh blockpull' from snap2 into snap3 3] Next, did another 'virsh blockpull' from snap1 into snap3 - Here, 'qemu-img info /path/to/snap3' shows its backing file

I am getting this issue also... Does anyone know what this is? When will Acts as Ferret be available for v10? Thanks for your help in desperation! Caspar wrote: > Okay previous post related to me trying to fix this problem with an > upgrade to ferret 0.10.0 but acts as ferret is obviously not compatible > with this new version of ferret. > My app is about to go into production and

Hi all, I''ve just released Ferret-0.10.1. It contains some important bug fixes and the minor addition of the Ferret::I class which is just an alias for Ferret::Index::Index. I still need to write up a release announcement for the 0.10.0 series. I haven''t forgotten about it and it may seem strange that I''ve already released 0.10.1 before writing the announcement.

I just upgraded (gem update) to 0.10.1, and now my projects I created just a few days ago under 0.10.0 don''t work anymore. I get the following message (for the database table "projects): $ script/generate scaffold Project script/generate:27: undefined method `instance'' for Rails::Generator:Module (NoMethodError) If I create a new rails project and run the same command,

I just did an upgrade to Rails 0.10.1. It seems to have broken my app. I get this error (nothing works): ActionController::RoutingError (No route for path: ""): /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.5.1/lib/action_controller/routing.rb:258:in `recognize!'' /usr/local/lib/ruby/gems/1.8/gems/rails-0.10.0/lib/dispatcher.rb:32:in `dispatch''

So, do I really want to upgrade to 0.10.1? Seems like a lot of people are having issues. Joe

hi, i'm added another patch to chan_ss7 it's from Denis Smirnov http://download.seiros.ru/SeirosPBX/chan_ss7/ New in version 0.10.1 (community version) - support for more than 256 channels - zap style addressing http://download.seiros.ru/SeirosPBX/chan_ss7/ http://www.freevoice.cz/chan_ss7/chan_ss7-0.10.1.tar.gz md5sum a3ca3031f8f4ef96d505be3b297b47cc

Hello all, I'm trying to take advantage of libvirt's VLAN and OVS support in the 0.10.1 release and consistently getting an "error: internal error corrupted profileid string" when starting a guest. I've defined a network using virsh; the configuration looks like this: <network> <name>ovs-network</name>

Is is still the standard to require models in the Application Controller for objects stored in the Session? As of upgrading to 0.10.1 Rail fails to load the model consistently under Webrick. Anyone have any suggestions or solutions other than downgrading to 0.10? -- Lon

I''ve got a view template that contains this: <%= render_component(:controller => ''reviews'', :action => ''show'', :params => { ''id'' => review.id }) %> In Rails 0.10.0 this worked just fine. After I upgraded to 0.10.1 I get this error: ActiveRecord::RecordNotFound in

Sorry for all the newbie questions, but I''m also getting this after I generate a new scaffold for an object and click on "New" on the list page: Routing Error No route for path: "new" Failure reasons: <ActionController::Routing::Route ":controller/service.wsdl" when {:action=>"wsdl"}> failed because no controller found at

I seem to have come to a strange problem getting started on rails. I had everything working in a virtual machine and then set up a seperate machine just for rails developement. It now seems something is broken a little. ruby 1.8.2, rails 0.10.1, postgres, using webrick: i created a table "users", then "generate scaffold User" view localhost/users works fine, shows the

Hi i''m using ferret to enable geographical postcode. I take a postcode and distance in miles from the user, strip off the outcode and then retrieve the associated x y coordinates in metres from the db. Then i get two temp x''s and y''s and search for all results that are within the box, see code below. Problems start to occur when i search on big distances so for

Renato, Kristof, I confirm this is due to the latest Flask --- Flask-0.11 was released this weekend --- and for some unknown (to me at least) reason, although LNT's requirements.txt pins Flask to version 0.10.1, pip installs Flask-0.11. Forcing Flask to 0.10.1 gets the situation back to normal. Reading pip's documentation makes me think it's not able to resolve dependencies

Hi i like the new version of ferret, has solved a few of my problems but i''m unsure of how to implement the following code in the new version of ferret? if section if !section.empty? qp = Ferret::QueryParser.new("section") query = qp.parse("\"#{section}\"") bq.add_query(query, Ferret::Search::BooleanClause::Occur::MUST) filter_on =true end

This is the point release to tie up the various loose ends introduced with Rails 0.10.0. Action Web Service has seen the most interesting improvements feature-wise with a new generator and tie-ins with the testing setup. There''s better support for XML-RPC: Instead of performing type checking on the parameters the remote client sends, AWS does casting to try and make it compatible

http://dev.rubyonrails.com/changeset/856 looks to me like it''s not going to work, since there''s no way of specifying a password to pg_dump/dropdb/createdb. If you set PGPASSWORD in your environment it might work, but that''s not documented anywhere and isn''t done automatically in the Rakefile. See http://thread.gmane.org/gmane.comp.lang.ruby.rails/3693 for

Anyone else having problems with :anchor? Until 0.10.0 it was working fine but with this recent update it''s just not doing anything. Thanks, Pedro

Running Ruby 1.8.2 on Mac OS X 10.3.7. I had been working on a small app based on the To Do tutorial and, since I''m just playing around, I installed tonight''s Rails update. Now I get a 404 error when browsing to my app''s top level. I''m using the built-in WEBrick server, started from within my app directory with "ruby script/server", which had

Daniel, Tobias, Renato and myself have been looking a little bit at the potential underlying reason for why http://llvm.org/perf/ is instable, and have found some clues. I want to share them here to give people with more experience in the frameworks used by LNT (flask, sqlalchemy, wsgi, .) a chance to check if our reasoning below seems plausible. Daniel noticed the following backtrace in the