On 2009-12-21, at 9:38 AM, Adrian Schröter wrote:

Am Montag, 21. Dezember 2009 15:12:14 schrieb Anas Nashif:

...

Hi, While many operation using osc 0.124 work as expected with obs 1.6.0, I just noticed that submitrequest does not work and fails with:

constructor needs either REXML::Element, String or Hash

Is the 1.6 API compatible with osc 0.124?

it should be, but frankly, I don't have a running 1.6.0 around anymore.

I really want to use the 1.7 snapshots, but this is undergoing heavy development right now. I spent some time trying to use the latest 1.6.83 packages, but without success, What is the best way to keep in sync with the git HEAD and deploy changes from git?

Can you send me a bit more detailed snippet from your server log ?

[nashif@taybeh quilt]$ osc -d --apiurl http://api.xxxxx.org sr Trunk -m "spec cleanup" GET http://api.xxxxx.org/source/Trunk/quilt/_meta GET http://api.xxxxx.org/search/request?match=(state/@name='new')%20and%20@type='submit'%20and%20(action/target/@project='Trunk'%20or%20action/source/@project='Trunk')%20and%20(action/target/@package='quilt'%20or%20action/source/@package='quilt')%20and%20action/@type='submit' GET http://api.xxxxx.org/search/request?match=(state/@name='new')%20and%20@type='submit'%20and%20(submit/target/@project='Trunk'%20or%20submit/source/@project='Trunk')%20and%20(submit/target/@package='quilt'%20or%20submit/source/@package='quilt')%20and%20submit/@type='submit' GET http://api.xxxxx.org/source/home:nashif/quilt?rev=latest POST http://api.xxxxx.org/request?cmd=create Server returned an error: HTTP Error 500: Internal Server Error Connection: close Content-Type: application/xml; charset=utf-8 X-Opensuse-APIVersion: 0.1.1 X-Opensuse-Errorcode: uncaught_exception Content-Length: 4935 Cache-Control: no-cache Date: Mon, 21 Dec 2009 15:09:31 GMT Server: lighttpd/1.4.20 <?xml version="1.0" encoding="UTF-8"?> <status code="uncaught_exception"> <summary>constructor needs either REXML::Element, String or Hash</summary> <details></details> <exception> <type>RuntimeError</type> <message>constructor needs either REXML::Element, String or Hash</message> <backtrace> <line>/srv/www/obs/common/lib/activexml/node.rb:135:in `initialize'</line> <line>/srv/www/obs/common/lib/activexml/base.rb:75:in `initialize'</line> <line>/srv/www/obs/frontend/app/controllers/request_controller.rb:40:in `new'</line> <line>/srv/www/obs/frontend/app/controllers/request_controller.rb:40:in `create_create'</line> <line>/srv/www/obs/frontend/app/controllers/application.rb:354:in `__send__'</line> <line>/srv/www/obs/frontend/app/controllers/application.rb:354:in `create'</line> <line>/usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/base.rb:1166:in `send'</line> <line>/usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/base.rb:1166:in `perform_action_without_filters'</line> <line>/usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/filters.rb:579:in `call_filters'</line> <line>/usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/filters.rb:572:in `perform_action_without_benchmark'</line> <line>/usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue'</line> <line>/usr/lib/ruby/1.8/benchmark.rb:293:in `measure'</line> <line>/usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue'</line> <line>/usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/rescue.rb:201:in `perform_action_without_caching'</line> <line>/usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/caching/sql_cache.rb:13:in `perform_action'</line> <line>/usr/lib/ruby/gems/1.8/gems/activerecord-2.1.2/lib/active_record/connection_adapters/abstract/query_cache.rb:33:in `cache'</line> <line>/usr/lib/ruby/gems/1.8/gems/activerecord-2.1.2/lib/active_record/query_cache.rb:8:in `cache'</line> <line>/usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/caching/sql_cache.rb:12:in `perform_action'</line> <line>/usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/base.rb:529:in `send'</line> <line>/usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/base.rb:529:in `process_without_filters'</line> <line>/usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/filters.rb:568:in `process_without_session_management_support'</line> <line>/usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/session_management.rb:130:in `process'</line> <line>/usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/base.rb:389:in `process'</line> <line>/usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:149:in `handle_request'</line> <line>/usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:107:in `dispatch'</line> <line>/usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:104:in `synchronize'</line> <line>/usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:104:in `dispatch'</line> <line>/usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:120:in `dispatch_cgi'</line> <line>/usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:35:in `dispatch'</line> <line>/usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:103:in `process_request'</line> <line>/usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:153:in `with_signal_handler'</line> <line>/usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:101:in `process_request'</line> <line>/usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:78:in `process_each_request'</line> <line>/usr/lib/ruby/vendor_ruby/1.8/fcgi.rb:612:in `each_cgi'</line> <line>/usr/lib/ruby/vendor_ruby/1.8/fcgi.rb:609:in `each'</line> <line>/usr/lib/ruby/vendor_ruby/1.8/fcgi.rb:609:in `each_cgi'</line> <line>/usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:77:in `process_each_request'</line> <line>/usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:76:in `catch'</line> <line>/usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:76:in `process_each_request'</line> <line>/usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:50:in `process!'</line> <line>/usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:24:in `process!'</line> <line>/srv/www/obs/frontend/public/dispatch.fcgi:24</line> </backtrace> </exception> </status> constructor needs either REXML::Element, String or Hash

bye adrian

--

Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de

-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

The first part of the patch I tried already, seems to solve just part of the problem resulting in a different error. The second part references and changes code that does not exist in 1.6.0 Anas On 2009-12-21, at 10:25 AM, Marcus Rueckert wrote:

see attached patch

-- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org

-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

Am Montag, 21. Dezember 2009 16:16:03 schrieb Anas Nashif:

On 2009-12-21, at 9:38 AM, Adrian Schröter wrote:

...

Am Montag, 21. Dezember 2009 15:12:14 schrieb Anas Nashif:

...

Hi, While many operation using osc 0.124 work as expected with obs 1.6.0, I just noticed that submitrequest does not work and fails with:

constructor needs either REXML::Element, String or Hash

Is the 1.6 API compatible with osc 0.124?

it should be, but frankly, I don't have a running 1.6.0 around anymore.

I really want to use the 1.7 snapshots, but this is undergoing heavy development right now. I spent some time trying to use the latest 1.6.83 packages, but without success, What is the best way to keep in sync with the git HEAD and deploy changes from git?

http://en.opensuse.org/Build_Service/Run_from_git

...

Can you send me a bit more detailed snippet from your server log ?

[nashif@taybeh quilt]$ osc -d --apiurl http://api.xxxxx.org sr Trunk -m "spec cleanup" GET http://api.xxxxx.org/source/Trunk/quilt/_meta GET

... interessting ... one could argue that this is a server side bug, but I wonder why we trigger this suddenly with a new osc. This still worked with osc 0.123 ? bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

On Tuesday 22 December 2009 14:42:15 Anas Nashif wrote:

[D|#23696] User nashif initialised [D|#23696] User's source backend <:> [D|#23696] Cache read: workerstatus [D|#23696] Cache write: workerstatus [I|#23696] Sending data [F|#23696] NoMethodError (undefined method `bytesize' for nil:NilClass): app/controllers/status_controller.rb:80:in `workerstatus' public/dispatch.fcgi:24

Hmm, this is something we need to fix before 1.7 I guess. The API is only serving workerstatus from cache and if you do not have a cron job filling that cache you will have no worker status. This cron way is overkill for smaller instances, so we need to make this configurable (and turn it off by default). Greetings, Stephan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

On Thursday 24 December 2009 09:00:48 Adrian Schröter wrote:

Am Donnerstag, 24. Dezember 2009 08:06:36 schrieb Stephan Kulow:

...

On Tuesday 22 December 2009 14:42:15 Anas Nashif wrote:

...

[D|#23696] User nashif initialised [D|#23696] User's source backend <:> [D|#23696] Cache read: workerstatus [D|#23696] Cache write: workerstatus [I|#23696] Sending data [F|#23696] NoMethodError (undefined method `bytesize' for nil:NilClass): app/controllers/status_controller.rb:80:in `workerstatus' public/dispatch.fcgi:24

Hmm, this is something we need to fix before 1.7 I guess. The API is only serving workerstatus from cache and if you do not have a cron job filling that cache you will have no worker status. This cron way is overkill for smaller instances, so we need to make this configurable (and turn it off by default).

My plan was actually to deliver the cron job with the packages .. but forgot it so far.

We only need a cron job if we want timeline graphs, but I'm not sure most are interested in having these for the price of a cron running every minute. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org