21335 0 false 2009-10-19T09:34:01+02:00 73609 86 after-clean-install-i-get-an-error-and-no-login-page 59 11831 new argumenterror haml 2009-12-24T12:32:57+02:00 22164 Roland Moriz Remco Voorderhake Kenneth Kalmer http://kennethkalmer.lighthouseapp.com/projects/11831/tickets/86 I get the following error: Processing DashboardController#index (for ::ffff:192.168.10.176 at 2009-10-19 09:19:51) [GET] ArgumentError (Cannot yield from a Proc type filter. The Proc must take two arguments and execute #call on the second argument.): haml (2.2.5) [v] rails/./lib/sass/plugin/rails.rb:19:in `process' I get this on all my systems which run defferent versions of ruby. Google doesn't help. I use the latest master release from 19-10-2009. TIA, Remco I get the following error: Processing DashboardController#index (for ::ffff:192.168.10.176 at 2009-10-19 09:19:51) [GET] ArgumentError (Cannot yield from a Proc type filter. The Proc must take two arguments and execute #call on the second argument.): haml (2.2.5) [v] rails/./lib/sass/plugin/rails.rb:19:in `process' I get this on all my systems which run defferent versions of ruby. Google doesn't help. I use the latest master release from 19-10-2009. TIA, Remco <div><p>I get the following error:<br> Processing DashboardController#index (for ::ffff:192.168.10.176 at 2009-10-19 09:19:51) <a href="/projects/11831/changesets/GET" title="Changeset [GET]">[GET]</a></p> <p>ArgumentError (Cannot yield from a Proc type filter. The Proc must take two arguments and execute #call on the second argument.):<br> haml (2.2.5) <a href="/projects/11831/changesets/v" title= "Changeset [v]">[v]</a> rails/./lib/sass/plugin/rails.rb:19:in <code>process'</code></p> <p>I get this on all my systems which run defferent versions of ruby. Google doesn't help. I use the latest master release from 19-10-2009.</p> <p>TIA,<br> Remco</p></div> 21335 0 false 2009-12-04T20:20:20+02:00 78602 91 alias-domains 64 11831 new 2009-12-04T20:20:23+02:00 78602 jam jam Kenneth Kalmer http://kennethkalmer.lighthouseapp.com/projects/11831/tickets/91 It would be nice to have the ability for PowerDNS on Rails to manage alias domains. For instance, in BIND you can configure multiple different domains to use the same zone configuration file. While I realize that PowerDNS does not have the ability for alias domains (not that I could find anyway), PowerDNS on Rails could provide for this feature by automatically updating all records for all domains which happen to be aliases of each other. And when you create a new domain aliased to an existing domain, PowerDNS on Rails would automatically copy all of the records to the new aliased domain. I hope I haven't overlooked the availability of this type of functionality with macros and templates, but I don't see how it would be possible and/or easy to manage that way. The lack of aliased domains in PowerDNS or a way to mimic this functionality with some front-end like PowerDNS on Rails is the only thing holding my company back from switching away from BIND. It would be nice to have the ability for PowerDNS on Rails to manage alias domains. For instance, in BIND you can configure multiple different domains to use the same zone configuration file. While I realize that PowerDNS does not have the ability for alias domains (not that I could find anyway), PowerDNS on Rails could provide for this feature by automatically updating all records for all domains which happen to be aliases of each other. And when you create a new domain aliased to an existing domain, PowerDNS on Rails would automatically copy all of the records to the new aliased domain. I hope I haven't overlooked the availability of this type of functionality with macros and templates, but I don't see how it would be possible and/or easy to manage that way. The lack of aliased domains in PowerDNS or a way to mimic this functionality with some front-end like PowerDNS on Rails is the only thing holding my company back from switching away from BIND. <div><p>It would be nice to have the ability for PowerDNS on Rails to manage alias domains. For instance, in BIND you can configure multiple different domains to use the same zone configuration file. While I realize that PowerDNS does not have the ability for alias domains (not that I could find anyway), PowerDNS on Rails could provide for this feature by automatically updating all records for all domains which happen to be aliases of each other. And when you create a new domain aliased to an existing domain, PowerDNS on Rails would automatically copy all of the records to the new aliased domain. I hope I haven't overlooked the availability of this type of functionality with macros and templates, but I don't see how it would be possible and/or easy to manage that way.</p> <p>The lack of aliased domains in PowerDNS or a way to mimic this functionality with some front-end like PowerDNS on Rails is the only thing holding my company back from switching away from BIND.</p></div> 21335 0 false 2009-11-29T22:46:17+02:00 23371 90 restrict-creating-sub-domains 63 11831 new permissions 2009-11-29T22:46:18+02:00 23371 Ask Bjørn Hansen Ask Bjørn Hansen Kenneth Kalmer http://kennethkalmer.lighthouseapp.com/projects/11831/tickets/90 If user 1 owns 'example.com', user 2 shouldn't be able to create 'test.example.com'. (It makes it trivial for unrelated users to "take over" a domain). If user 1 owns 'example.com', user 2 shouldn't be able to create 'test.example.com'. (It makes it trivial for unrelated users to "take over" a domain). <div><p>If user 1 owns 'example.com', user 2 shouldn't be able to create 'test.example.com'. (It makes it trivial for unrelated users to "take over" a domain).</p></div> 21335 0 false 2009-11-29T22:45:17+02:00 23371 89 share-templates 62 11831 new templates 2009-11-29T22:45:17+02:00 23371 Ask Bjørn Hansen Ask Bjørn Hansen Kenneth Kalmer http://kennethkalmer.lighthouseapp.com/projects/11831/tickets/89 I expected a template with '-' owner would be available to all users, but such templates don't show up for regular domain users. I expected a template with '-' owner would be available to all users, but such templates don't show up for regular domain users. <div><p>I expected a template with '-' owner would be available to all users, but such templates don't show up for regular domain users.</p></div> 21335 0 false 2009-11-29T22:44:15+02:00 23371 88 macros-not-found 61 11831 new macros 2009-11-29T22:44:15+02:00 23371 Ask Bjørn Hansen Ask Bjørn Hansen Kenneth Kalmer http://kennethkalmer.lighthouseapp.com/projects/11831/tickets/88 After adding a macro the entry is correctly created in the macros table, but I get an "Couldn't find Macro with ID=3" error on http://localhost:3000/macros/3. Nothing is created in the macro_steps table. ' The /macros page says "macro was successfully created" amnd then "You currently don't have any macros defined." After adding a macro the entry is correctly created in the macros table, but I get an "Couldn't find Macro with ID=3" error on http://localhost:3000/macros/3. Nothing is created in the macro_steps table. ' The /macros page says "macro was successfully created" amnd then "You currently don't have any macros defined." <div><p>After adding a macro the entry is correctly created in the macros table, but I get an "Couldn't find Macro with ID=3" error on <a href= "http://localhost:3000/macros/3">http://localhost:3000/macros/3</a>. Nothing is created in the macro_steps table.<br> '</p> <p>The /macros page says "macro was successfully created" amnd then "You currently don't have any macros defined."</p></div> 21335 1 false 2008-06-10T16:46:53+02:00 21335 11691 5 import-existing-zone-files 2 11831 new bind import 2009-11-29T21:47:18+02:00 23371 Ask Bjørn Hansen Kenneth Kalmer Kenneth Kalmer http://kennethkalmer.lighthouseapp.com/projects/11831/tickets/5 Medium Priority Provide tools to import existing zone files into the BIND DLZ database for management by the system. Provide tools to import existing zone files into the BIND DLZ database for management by the system. <div><p> Provide tools to import existing zone files into the BIND DLZ database for management by the system. </p></div> 21335 0 false 2009-02-26T22:01:15+02:00 21335 11690 62 prevent-same-records-of-different-types 13 11831 new bug records 2009-11-29T21:42:53+02:00 23371 Ask Bjørn Hansen Kenneth Kalmer Kenneth Kalmer http://kennethkalmer.lighthouseapp.com/projects/11831/tickets/62 High Priority Saw a client do this: www IN A 127.0.0.1 www IN CNAME www.example.com Prevent this from happening. Saw a client do this: www IN A 127.0.0.1 www IN CNAME www.example.com Prevent this from happening. <div><p>Saw a client do this:</p> <p>www IN A 127.0.0.1 www IN CNAME <a href="http://www.example.com">www.example.com</a></p> <p>Prevent this from happening.</p></div> 21335 0 false 2009-10-22T02:11:26+02:00 73997 87 error-on-access-to-users-page 60 11831 new 2009-10-22T02:11:29+02:00 73997 Tim Tim Kenneth Kalmer http://kennethkalmer.lighthouseapp.com/projects/11831/tickets/87 I made a new install with CentOS 5.3 this afternoon to test out the web interface. I seem to have hit a bug on the /users page that causes an error when accessing it. The server logs are below from my attempt to access the /users page. [2009-10-21 20:06:10] INFO WEBrick::HTTPServer#start: pid=19522 port=3000 SQL (0.2ms) SET SQL_AUTO_IS_NULL=0 Processing UsersController#index (for ::ffff:10.xx.xx.135 at 2009-10-21 20:06:14) [GET] User Columns (1.0ms) SHOW FIELDS FROM `users` User Load (0.4ms) SELECT * FROM `users` WHERE (`users`.`id` = 1) LIMIT 1 roles_users Columns (0.7ms) SHOW FIELDS FROM `roles_users` Role Load (0.3ms) SELECT * FROM `roles` INNER JOIN `roles_users` ON `roles`.id = `roles_users`.role_id WHERE (`roles_users`.user_id = 1 ) Role Columns (0.5ms) SHOW FIELDS FROM `roles` User Load (0.3ms) SELECT * FROM `users` ORDER BY login Rendering template within layouts/application Rendering users/index CACHE (0.0ms) SELECT * FROM `roles` INNER JOIN `roles_users` ON `roles`.id = `roles_users`.role_id WHERE (`roles_users`.user_id = 1 ) ActionView::TemplateError (can't convert Symbol into Integer) on line #15 of app/views/users/_user.html.haml: 12: %td= link_to user.login, user_path( user ) 13: %td= user.email 14: %td= user.has_role?('admin') ? t("label_user_role.admin") : t("label_user_role.user") 15: %td 16: - unless user.suspended? 17: = prototip_info_icon('flag_green.png', "active-user-#{user.id}") 18: - else app/views/users/_user.html.haml:15:in `_run_haml_app47views47users47_user46html46haml_locals_object_user_user_counter' haml (2.2.5) [v] lib/haml/helpers/action_view_mods.rb:11:in `block in render_with_haml' haml (2.2.5) [v] lib/haml/helpers.rb:96:in `non_haml' haml (2.2.5) [v] lib/haml/helpers/action_view_mods.rb:11:in `render_with_haml' app/views/users/index.html.haml:10:in `_run_haml_app47views47users47index46html46haml' haml (2.2.5) [v] lib/haml/helpers/action_view_mods.rb:13:in `render_with_haml' haml (2.2.5) [v] lib/haml/helpers/action_view_mods.rb:13:in `render_with_haml' haml (2.2.5) [v] lib/sass/plugin/rails.rb:19:in `process' <internal:prelude>:8:in `synchronize' /usr/local/lib/ruby/1.9.1/webrick/httpserver.rb:111:in `service' /usr/local/lib/ruby/1.9.1/webrick/httpserver.rb:70:in `run' /usr/local/lib/ruby/1.9.1/webrick/server.rb:183:in `block in start_thread' Rendered rescues/_trace (120.9ms) Rendered rescues/_request_and_response (1.3ms) Rendering rescues/layout (internal_server_error) I made a new install with CentOS 5.3 this afternoon to test out the web interface. I seem to have hit a bug on the /users page that causes an error when accessing it. The server logs are below from my attempt to access the /users page. [2009-10-21 20:06:10] INFO WEBrick::HTTPServer#start: pid=19522 port=3000 SQL (0.2ms) SET SQL_AUTO_IS_NULL=0 Processing UsersController#index (for ::ffff:10.xx.xx.135 at 2009-10-21 20:06:14) [GET] User Columns (1.0ms) SHOW FIELDS FROM `users` User Load (0.4ms) SELECT * FROM `users` WHERE (`users`.`id` = 1) LIMIT 1 roles_users Columns (0.7ms) SHOW FIELDS FROM `roles_users` Role Load (0.3ms) SELECT * FROM `roles` INNER JOIN `roles_users` ON `roles`.id = `roles_users`.role_id WHERE (`roles_users`.user_id = 1 ) Role Columns (0.5ms) SHOW FIELDS FROM `roles` User Load (0.3ms) SELECT * FROM `users` ORDER BY login Rendering template within layouts/application Rendering users/index CACHE (0.0ms) SELECT * FROM `roles` INNER JOIN `roles_users` ON `roles`.id = `roles_users`.role_id WHERE (`roles_users`.user_id = 1 ) ActionView::TemplateError (can't convert Symbol into Integer) on line #15 of app/views/users/_user.html.haml: 12: %td= link_to user.login, user_path( user ) 13: %td= user.email 14: %td= user.has_role?('admin') ? t("label_user_role.admin") : t("label_user_role.user") 15: %td 16: - unless user.suspended? 17: = prototip_info_icon('flag_green.png', "active-user-#{user.id}") 18: - else app/views/users/_user.html.haml:15:in `_run_haml_app47views47users47_user46html46haml_locals_object_user_user_counter' haml (2.2.5) [v] lib/haml/helpers/action_view_mods.rb:11:in `block in render_with_haml' haml (2.2.5) [v] lib/haml/helpers.rb:96:in `non_haml' haml (2.2.5) [v] lib/haml/helpers/action_view_mods.rb:11:in `render_with_haml' app/views/users/index.html.haml:10:in `_run_haml_app47views47users47index46html46haml' haml (2.2.5) [v] lib/haml/helpers/action_view_mods.rb:13:in `render_with_haml' haml (2.2.5) [v] lib/haml/helpers/action_view_mods.rb:13:in `render_with_haml' haml (2.2.5) [v] lib/sass/plugin/rails.rb:19:in `process' <internal:prelude>:8:in `synchronize' /usr/local/lib/ruby/1.9.1/webrick/httpserver.rb:111:in `service' /usr/local/lib/ruby/1.9.1/webrick/httpserver.rb:70:in `run' /usr/local/lib/ruby/1.9.1/webrick/server.rb:183:in `block in start_thread' Rendered rescues/_trace (120.9ms) Rendered rescues/_request_and_response (1.3ms) Rendering rescues/layout (internal_server_error) <div><p>I made a new install with CentOS 5.3 this afternoon to test out the web interface. I seem to have hit a bug on the /users page that causes an error when accessing it. The server logs are below from my attempt to access the /users page.</p> <p>[2009-10-21 20:06:10] INFO WEBrick::HTTPServer#start: pid=19522 port=3000 SQL (0.2ms) SET SQL_AUTO_IS_NULL=0</p> <p>Processing UsersController#index (for ::ffff:10.xx.xx.135 at 2009-10-21 20:06:14) <a href="/projects/11831/changesets/GET" title="Changeset [GET]">[GET]</a><br> User Columns (1.0ms) SHOW FIELDS FROM <code>users</code> User Load (0.4ms) SELECT * FROM <code>users</code> WHERE (<code>users</code>.<code>id</code> = 1) LIMIT 1 roles_users Columns (0.7ms) SHOW FIELDS FROM <code>roles_users</code> Role Load (0.3ms) SELECT * FROM <code>roles</code> INNER JOIN <code>roles_users</code> ON <code>roles</code>.id = <code>roles_users</code>.role_id WHERE (<code>roles_users</code>.user_id = 1 ) Role Columns (0.5ms) SHOW FIELDS FROM <code>roles</code> User Load (0.3ms) SELECT * FROM <code>users</code> ORDER BY login Rendering template within layouts/application<br> Rendering users/index<br> CACHE (0.0ms) SELECT * FROM <code>roles</code> INNER JOIN <code>roles_users</code> ON <code>roles</code>.id = <code>roles_users</code>.role_id WHERE (<code>roles_users</code>.user_id = 1 )</p> <p>ActionView::TemplateError (can't convert Symbol into Integer) on line <a href="/projects/11831/tickets/15" title= "Ticket #15">#15</a> of app/views/users/_user.html.haml:<br> 12: %td= link_to user.login, user_path( user )<br> 13: %td= user.email<br> 14: %td= user.has_role?('admin') ? t("label_user_role.admin") : t("label_user_role.user")<br> 15: %td<br> 16: - unless user.suspended?<br> 17: = prototip_info_icon('flag_green.png', "active-user-#{user.id}")<br> 18: - else</p> <pre> <code>app/views/users/_user.html.haml:15:in `_run_haml_app47views47users47_user46html46haml_locals_object_user_user_counter' haml (2.2.5) [v] lib/haml/helpers/action_view_mods.rb:11:in `block in render_with_haml' haml (2.2.5) [v] lib/haml/helpers.rb:96:in `non_haml' haml (2.2.5) [v] lib/haml/helpers/action_view_mods.rb:11:in `render_with_haml' app/views/users/index.html.haml:10:in `_run_haml_app47views47users47index46html46haml' haml (2.2.5) [v] lib/haml/helpers/action_view_mods.rb:13:in `render_with_haml' haml (2.2.5) [v] lib/haml/helpers/action_view_mods.rb:13:in `render_with_haml' haml (2.2.5) [v] lib/sass/plugin/rails.rb:19:in `process' &lt;internal:prelude&gt;:8:in `synchronize' /usr/local/lib/ruby/1.9.1/webrick/httpserver.rb:111:in `service' /usr/local/lib/ruby/1.9.1/webrick/httpserver.rb:70:in `run' /usr/local/lib/ruby/1.9.1/webrick/server.rb:183:in `block in start_thread'</code> </pre> <p>Rendered rescues/<em>trace (120.9ms)<br> Rendered rescues/</em>request_and_response (1.3ms)<br> Rendering rescues/layout (internal_server_error)</p></div> 21335 0 false 2009-06-12T01:45:18+02:00 59795 79 soa-record-isnt-created-when-adding-a-new-native-domain 52 11831 new 2009-10-12T14:55:55+02:00 72842 Cees Velt ronin-59795 (at lighthouseapp) Kenneth Kalmer http://kennethkalmer.lighthouseapp.com/projects/11831/tickets/79 It appears the SOA recorded is never created or saved when adding a new domain. It appears the SOA recorded is never created or saved when adding a new domain. <div><p>It appears the SOA recorded is never created or saved when adding a new domain.</p></div> 21335 0 false 2009-07-31T10:01:59+02:00 64634 85 ability-to-assign-templates-globally 58 11831 new templates 2009-07-31T10:02:02+02:00 64634 Campbell Campbell Kenneth Kalmer http://kennethkalmer.lighthouseapp.com/projects/11831/tickets/85 It would be very handy to be able to assign a template globally so that any user, rather than just the user that created the template could use it. Perhaps only users in the Admin group would be allowed to create these "global" templates? It would be very handy to be able to assign a template globally so that any user, rather than just the user that created the template could use it. Perhaps only users in the Admin group would be allowed to create these "global" templates? <div><p>It would be very handy to be able to assign a template globally so that any user, rather than just the user that created the template could use it. Perhaps only users in the Admin group would be allowed to create these "global" templates?</p></div> 21335 0 false 2009-07-18T02:47:46+02:00 63159 83 initial-seed-throws-error 56 11831 new 2009-07-22T09:37:43+02:00 62858 Jan Åge Johnsen fitz Kenneth Kalmer http://kennethkalmer.lighthouseapp.com/projects/11831/tickets/83 [root powerdns-on-rails]# RAILS_ENV=development rake db:seed --trace (in /root/git-1.6.3.3/powerdns-on-rails) ** Invoke db:seed (first_time) ** Invoke environment (first_time) ** Execute environment ** Execute db:seed == Seeding from example_dot_star.rb ======================== - Domain {:name=>"example.com"} - NS {:domain_id=>1, :content=>"ns1.example.com."} - NS {:domain_id=>1, :content=>"ns2.example.com."} - A {:name=>"ns1.example.com", :domain_id=>1} - A {:name=>"ns2.example.com", :domain_id=>1} - A {:name=>"@.example.com", :domain_id=>1} - MX {:name=>"@.example.com", :domain_id=>1} - A {:name=>"mail.example.com", :domain_id=>1} ============================================================ == Seeding from templates.rb =============================== - ZoneTemplate {:name=>"East Coast Data Center"} rake aborted! You have a nil object when you didn't expect it! The error occurred while evaluating nil.name /root/git-1.6.3.3/powerdns-on-rails/app/models/record.rb:101:in `append_domain_name!' /root/git-1.6.3.3/powerdns-on-rails/app/models/record.rb:69:in `before_validation_without_content' /root/git-1.6.3.3/powerdns-on-rails/app/models/soa.rb:111:in `before_validation' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/callbacks.rb:347:in `send' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/callbacks.rb:347:in `callback' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/callbacks.rb:311:in `valid?' /root/git-1.6.3.3/powerdns-on-rails/app/models/record_template.rb:96:in `validate' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/validations.rb:1030:in `valid_without_callbacks?' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/callbacks.rb:315:in `valid?' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/validations.rb:1018:in `save_without_dirty!' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/dirty.rb:87:in `save_without_transactions!' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/transactions.rb:200:in `save!' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/database_statements.rb:136:in `transaction' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/transactions.rb:182:in `transaction' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/transactions.rb:200:in `save!' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/transactions.rb:208:in `rollback_active_record_state!' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/transactions.rb:200:in `save!' /root/git-1.6.3.3/powerdns-on-rails/vendor/plugins/seed-fu/lib/seeder.rb:34:in `plant!' /root/git-1.6.3.3/powerdns-on-rails/vendor/plugins/seed-fu/lib/seeder.rb:7:in `plant' /root/git-1.6.3.3/powerdns-on-rails/vendor/plugins/seed-fu/lib/seeder.rb:71:in `seed' /root/git-1.6.3.3/powerdns-on-rails/db/fixtures/templates.rb:6 /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activesupport/lib/active_support/dependencies.rb:145:in `load_without_new_constant_marking' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activesupport/lib/active_support/dependencies.rb:145:in `load' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activesupport/lib/active_support/dependencies.rb:521:in `new_constants_in' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activesupport/lib/active_support/dependencies.rb:145:in `load' /root/git-1.6.3.3/powerdns-on-rails/vendor/plugins/seed-fu/tasks/seed_fu_tasks.rake:6 /root/git-1.6.3.3/powerdns-on-rails/vendor/plugins/seed-fu/tasks/seed_fu_tasks.rake:4:in `each' /root/git-1.6.3.3/powerdns-on-rails/vendor/plugins/seed-fu/tasks/seed_fu_tasks.rake:4 /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `call' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `execute' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `each' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `execute' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:597:in `invoke_with_call_chain' /usr/local/lib/ruby/1.8/monitor.rb:242:in `synchronize' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:583:in `invoke' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2051:in `invoke_task' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `each' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2001:in `run' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in `run' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:31 /usr/local/bin/rake:19:in `load' /usr/local/bin/rake:19 [root powerdns-on-rails]# [root powerdns-on-rails]# RAILS_ENV=development rake db:seed --trace (in /root/git-1.6.3.3/powerdns-on-rails) ** Invoke db:seed (first_time) ** Invoke environment (first_time) ** Execute environment ** Execute db:seed == Seeding from example_dot_star.rb ======================== - Domain {:name=>"example.com"} - NS {:domain_id=>1, :content=>"ns1.example.com."} - NS {:domain_id=>1, :content=>"ns2.example.com."} - A {:name=>"ns1.example.com", :domain_id=>1} - A {:name=>"ns2.example.com", :domain_id=>1} - A {:name=>"@.example.com", :domain_id=>1} - MX {:name=>"@.example.com", :domain_id=>1} - A {:name=>"mail.example.com", :domain_id=>1} ============================================================ == Seeding from templates.rb =============================== - ZoneTemplate {:name=>"East Coast Data Center"} rake aborted! You have a nil object when you didn't expect it! The error occurred while evaluating nil.name /root/git-1.6.3.3/powerdns-on-rails/app/models/record.rb:101:in `append_domain_name!' /root/git-1.6.3.3/powerdns-on-rails/app/models/record.rb:69:in `before_validation_without_content' /root/git-1.6.3.3/powerdns-on-rails/app/models/soa.rb:111:in `before_validation' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/callbacks.rb:347:in `send' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/callbacks.rb:347:in `callback' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/callbacks.rb:311:in `valid?' /root/git-1.6.3.3/powerdns-on-rails/app/models/record_template.rb:96:in `validate' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/validations.rb:1030:in `valid_without_callbacks?' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/callbacks.rb:315:in `valid?' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/validations.rb:1018:in `save_without_dirty!' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/dirty.rb:87:in `save_without_transactions!' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/transactions.rb:200:in `save!' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/database_statements.rb:136:in `transaction' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/transactions.rb:182:in `transaction' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/transactions.rb:200:in `save!' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/transactions.rb:208:in `rollback_active_record_state!' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/transactions.rb:200:in `save!' /root/git-1.6.3.3/powerdns-on-rails/vendor/plugins/seed-fu/lib/seeder.rb:34:in `plant!' /root/git-1.6.3.3/powerdns-on-rails/vendor/plugins/seed-fu/lib/seeder.rb:7:in `plant' /root/git-1.6.3.3/powerdns-on-rails/vendor/plugins/seed-fu/lib/seeder.rb:71:in `seed' /root/git-1.6.3.3/powerdns-on-rails/db/fixtures/templates.rb:6 /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activesupport/lib/active_support/dependencies.rb:145:in `load_without_new_constant_marking' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activesupport/lib/active_support/dependencies.rb:145:in `load' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activesupport/lib/active_support/dependencies.rb:521:in `new_constants_in' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activesupport/lib/active_support/dependencies.rb:145:in `load' /root/git-1.6.3.3/powerdns-on-rails/vendor/plugins/seed-fu/tasks/seed_fu_tasks.rake:6 /root/git-1.6.3.3/powerdns-on-rails/vendor/plugins/seed-fu/tasks/seed_fu_tasks.rake:4:in `each' /root/git-1.6.3.3/powerdns-on-rails/vendor/plugins/seed-fu/tasks/seed_fu_tasks.rake:4 /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `call' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `execute' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `each' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `execute' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:597:in `invoke_with_call_chain' /usr/local/lib/ruby/1.8/monitor.rb:242:in `synchronize' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:583:in `invoke' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2051:in `invoke_task' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `each' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2001:in `run' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in `run' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:31 /usr/local/bin/rake:19:in `load' /usr/local/bin/rake:19 [root powerdns-on-rails]# <div><p>[root powerdns-on-rails]# RAILS_ENV=development rake db:seed --trace (in /root/git-1.6.3.3/powerdns-on-rails) <strong>Invoke db:seed (first_time)</strong> Invoke environment (first_time) <strong>Execute environment</strong> Execute db:seed</p> <p>== Seeding from example_dot_star.rb ======================== - Domain {:name=&gt;"example.com"} - NS {:domain_id=&gt;1, :content=&gt;"ns1.example.com."} - NS {:domain_id=&gt;1, :content=&gt;"ns2.example.com."} - A {:name=&gt;"ns1.example.com", :domain_id=&gt;1} - A {:name=&gt;"ns2.example.com", :domain_id=&gt;1} - A {:name=&gt;"@.example.com", :domain_id=&gt;1} - MX {:name=&gt;"@.example.com", :domain_id=&gt;1}</p> <h1>- A {:name=&gt;"mail.example.com", :domain_id=&gt;1}</h1> <p>== Seeding from templates.rb =============================== - ZoneTemplate {:name=&gt;"East Coast Data Center"} rake aborted! You have a nil object when you didn't expect it! The error occurred while evaluating nil.name /root/git-1.6.3.3/powerdns-on-rails/app/models/record.rb:101:in <code>append_domain_name!' /root/git-1.6.3.3/powerdns-on-rails/app/models/record.rb:69:in</code>before_validation_without_content' /root/git-1.6.3.3/powerdns-on-rails/app/models/soa.rb:111:in <code>before_validation' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/callbacks.rb:347:in</code>send' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/callbacks.rb:347:in <code>callback' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/callbacks.rb:311:in</code>valid?' /root/git-1.6.3.3/powerdns-on-rails/app/models/record_template.rb:96:in <code>validate' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/validations.rb:1030:in</code>valid_without_callbacks?' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/callbacks.rb:315:in <code>valid?' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/validations.rb:1018:in</code>save_without_dirty!' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/dirty.rb:87:in <code>save_without_transactions!' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/transactions.rb:200:in</code>save!' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/database_statements.rb:136:in <code>transaction' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/transactions.rb:182:in</code>transaction' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/transactions.rb:200:in <code>save!' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/transactions.rb:208:in</code>rollback_active_record_state!' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/transactions.rb:200:in <code>save!' /root/git-1.6.3.3/powerdns-on-rails/vendor/plugins/seed-fu/lib/seeder.rb:34:in</code>plant!' /root/git-1.6.3.3/powerdns-on-rails/vendor/plugins/seed-fu/lib/seeder.rb:7:in <code>plant' /root/git-1.6.3.3/powerdns-on-rails/vendor/plugins/seed-fu/lib/seeder.rb:71:in</code>seed' /root/git-1.6.3.3/powerdns-on-rails/db/fixtures/templates.rb:6 /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activesupport/lib/active_support/dependencies.rb:145:in <code>load_without_new_constant_marking' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activesupport/lib/active_support/dependencies.rb:145:in</code>load' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activesupport/lib/active_support/dependencies.rb:521:in <code>new_constants_in' /root/git-1.6.3.3/powerdns-on-rails/vendor/rails/activesupport/lib/active_support/dependencies.rb:145:in</code>load' /root/git-1.6.3.3/powerdns-on-rails/vendor/plugins/seed-fu/tasks/seed_fu_tasks.rake:6 /root/git-1.6.3.3/powerdns-on-rails/vendor/plugins/seed-fu/tasks/seed_fu_tasks.rake:4:in <code>each' /root/git-1.6.3.3/powerdns-on-rails/vendor/plugins/seed-fu/tasks/seed_fu_tasks.rake:4 /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in</code>call' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in <code>execute' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in</code>each' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in <code>execute' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:597:in</code>invoke_with_call_chain' /usr/local/lib/ruby/1.8/monitor.rb:242:in <code>synchronize' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in</code>invoke_with_call_chain' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:583:in <code>invoke' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2051:in</code>invoke_task' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in <code>top_level' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in</code>each' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in <code>top_level' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in</code>standard_exception_handling' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2023:in <code>top_level' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2001:in</code>run' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in <code>standard_exception_handling' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in</code>run' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:31 /usr/local/bin/rake:19:in <code>load' /usr/local/bin/rake:19 [root powerdns-on-rails]#</code></p></div> 21335 0 false 2009-07-21T12:34:51+02:00 62858 84 dbmigrate-breaks-on-mysql-4 57 11831 new 2009-07-21T12:34:52+02:00 62858 Jan Åge Johnsen Jan Åge Johnsen Kenneth Kalmer http://kennethkalmer.lighthouseapp.com/projects/11831/tickets/84 Using InnoDB and utf8 breaks with the follwing error: Mysql::Error: Specified key was too long; max key length is 1024 bytes: CREATE INDEX `index_records_on_name_and_type` ON `records` (`name`, `type`) Fixed by adding :limit => 16 on record.type in db/migrate/002_create_records.rb Using InnoDB and utf8 breaks with the follwing error: Mysql::Error: Specified key was too long; max key length is 1024 bytes: CREATE INDEX `index_records_on_name_and_type` ON `records` (`name`, `type`) Fixed by adding :limit => 16 on record.type in db/migrate/002_create_records.rb <div><p>Using InnoDB and utf8 breaks with the follwing error:</p> <p>Mysql::Error: Specified key was too long; max key length is 1024 bytes: CREATE INDEX <code>index_records_on_name_and_type</code> ON <code>records</code> (<code>name</code>, <code>type</code>)</p> <p>Fixed by adding :limit =&gt; 16 on record.type in db/migrate/002_create_records.rb</p></div> 21335 0 false 2009-07-15T15:42:06+02:00 62858 82 migratepowerdns-breaks-on-rails-232 55 11831 new 2009-07-15T15:42:08+02:00 62858 Jan Åge Johnsen Jan Åge Johnsen Kenneth Kalmer http://kennethkalmer.lighthouseapp.com/projects/11831/tickets/82 Breaks with PowerDnsMigration is not missing constant PdnsRecord! Works by including monkeypatch from: https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/2283-unnecessary-exception-raised-in-asdependenciesload_missing_constant#ticket-2283-3 Trace: @@@ A complete log file containing verbose data will be available at the path below after the migration /root/workspace/powerdns-on-rails/log/powerdns-import-20090715175140.log rake aborted! PowerDnsMigration is not missing constant PdnsRecord! /root/workspace/powerdns-on-rails/vendor/rails/activesupport/lib/active_support/dependencies.rb:417:in `load_missing_constant' /root/workspace/powerdns-on-rails/vendor/rails/activesupport/lib/active_support/dependencies.rb:80:in `const_missing' /root/workspace/powerdns-on-rails/vendor/rails/activesupport/lib/active_support/dependencies.rb:98:in `send' /root/workspace/powerdns-on-rails/vendor/rails/activesupport/lib/active_support/dependencies.rb:98:in `const_missing' /root/workspace/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/base.rb:2197:in `compute_type' /root/workspace/powerdns-on-rails/vendor/rails/activesupport/lib/active_support/core_ext/kernel/reporting.rb:11:in `silence_warnings' /root/workspace/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/base.rb:2195:in `compute_type' /root/workspace/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/reflection.rb:156:in `send' /root/workspace/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/reflection.rb:156:in `klass' /root/workspace/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/reflection.rb:187:in `quoted_table_name' /root/workspace/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/associations/has_many_association.rb:96:in `construct_sql' /root/workspace/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/associations/association_collection.rb:21:in `initialize' /root/workspace/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/associations.rb:1262:in `new' /root/workspace/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/associations.rb:1262:in `records' /root/workspace/powerdns-on-rails/lib/tasks/migrate_from_powerdns.rake:113:in `migrate!' /root/workspace/powerdns-on-rails/lib/tasks/migrate_from_powerdns.rake:82:in `each' /root/workspace/powerdns-on-rails/lib/tasks/migrate_from_powerdns.rake:82:in `each' /root/workspace/powerdns-on-rails/lib/tasks/migrate_from_powerdns.rake:108:in `migrate!' /root/workspace/powerdns-on-rails/lib/tasks/migrate_from_powerdns.rake:292 /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `call' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `execute' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `each' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `execute' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:597:in `invoke_with_call_chain' /usr/lib/ruby/1.8/monitor.rb:238:in `synchronize' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:583:in `invoke' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2051:in `invoke_task' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `each' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2001:in `run' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in `run' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:31 /usr/bin/rake:19:in `load' /usr/bin/rake:19 @@@ Breaks with PowerDnsMigration is not missing constant PdnsRecord! Works by including monkeypatch from: https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/2283-unnecessary-exception-raised-in-asdependenciesload_missing_constant#ticket-2283-3 Trace: @@@ A complete log file containing verbose data will be available at the path below after the migration /root/workspace/powerdns-on-rails/log/powerdns-import-20090715175140.log rake aborted! PowerDnsMigration is not missing constant PdnsRecord! /root/workspace/powerdns-on-rails/vendor/rails/activesupport/lib/active_support/dependencies.rb:417:in `load_missing_constant' /root/workspace/powerdns-on-rails/vendor/rails/activesupport/lib/active_support/dependencies.rb:80:in `const_missing' /root/workspace/powerdns-on-rails/vendor/rails/activesupport/lib/active_support/dependencies.rb:98:in `send' /root/workspace/powerdns-on-rails/vendor/rails/activesupport/lib/active_support/dependencies.rb:98:in `const_missing' /root/workspace/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/base.rb:2197:in `compute_type' /root/workspace/powerdns-on-rails/vendor/rails/activesupport/lib/active_support/core_ext/kernel/reporting.rb:11:in `silence_warnings' /root/workspace/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/base.rb:2195:in `compute_type' /root/workspace/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/reflection.rb:156:in `send' /root/workspace/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/reflection.rb:156:in `klass' /root/workspace/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/reflection.rb:187:in `quoted_table_name' /root/workspace/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/associations/has_many_association.rb:96:in `construct_sql' /root/workspace/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/associations/association_collection.rb:21:in `initialize' /root/workspace/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/associations.rb:1262:in `new' /root/workspace/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/associations.rb:1262:in `records' /root/workspace/powerdns-on-rails/lib/tasks/migrate_from_powerdns.rake:113:in `migrate!' /root/workspace/powerdns-on-rails/lib/tasks/migrate_from_powerdns.rake:82:in `each' /root/workspace/powerdns-on-rails/lib/tasks/migrate_from_powerdns.rake:82:in `each' /root/workspace/powerdns-on-rails/lib/tasks/migrate_from_powerdns.rake:108:in `migrate!' /root/workspace/powerdns-on-rails/lib/tasks/migrate_from_powerdns.rake:292 /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `call' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `execute' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `each' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `execute' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:597:in `invoke_with_call_chain' /usr/lib/ruby/1.8/monitor.rb:238:in `synchronize' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:583:in `invoke' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2051:in `invoke_task' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `each' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2001:in `run' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in `run' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:31 /usr/bin/rake:19:in `load' /usr/bin/rake:19 @@@ <div><p>Breaks with PowerDnsMigration is not missing constant PdnsRecord!</p> <p>Works by including monkeypatch from: <a href="https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/2283-unnecessary-exception-raised-in-asdependenciesload_missing_constant#ticket-2283-3"> https://rails.lighthouseapp.com/...</a></p> <p>Trace:</p> <pre><code> A complete log file containing verbose data will be available at the path below after the migration /root/workspace/powerdns-on-rails/log/powerdns-import-20090715175140.log rake aborted! PowerDnsMigration is not missing constant PdnsRecord! /root/workspace/powerdns-on-rails/vendor/rails/activesupport/lib/active_support/dependencies.rb:417:in `load_missing_constant' /root/workspace/powerdns-on-rails/vendor/rails/activesupport/lib/active_support/dependencies.rb:80:in `const_missing' /root/workspace/powerdns-on-rails/vendor/rails/activesupport/lib/active_support/dependencies.rb:98:in `send' /root/workspace/powerdns-on-rails/vendor/rails/activesupport/lib/active_support/dependencies.rb:98:in `const_missing' /root/workspace/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/base.rb:2197:in `compute_type' /root/workspace/powerdns-on-rails/vendor/rails/activesupport/lib/active_support/core_ext/kernel/reporting.rb:11:in `silence_warnings' /root/workspace/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/base.rb:2195:in `compute_type' /root/workspace/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/reflection.rb:156:in `send' /root/workspace/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/reflection.rb:156:in `klass' /root/workspace/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/reflection.rb:187:in `quoted_table_name' /root/workspace/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/associations/has_many_association.rb:96:in `construct_sql' /root/workspace/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/associations/association_collection.rb:21:in `initialize' /root/workspace/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/associations.rb:1262:in `new' /root/workspace/powerdns-on-rails/vendor/rails/activerecord/lib/active_record/associations.rb:1262:in `records' /root/workspace/powerdns-on-rails/lib/tasks/migrate_from_powerdns.rake:113:in `migrate!' /root/workspace/powerdns-on-rails/lib/tasks/migrate_from_powerdns.rake:82:in `each' /root/workspace/powerdns-on-rails/lib/tasks/migrate_from_powerdns.rake:82:in `each' /root/workspace/powerdns-on-rails/lib/tasks/migrate_from_powerdns.rake:108:in `migrate!' /root/workspace/powerdns-on-rails/lib/tasks/migrate_from_powerdns.rake:292 /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `call' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `execute' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `each' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `execute' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:597:in `invoke_with_call_chain' /usr/lib/ruby/1.8/monitor.rb:238:in `synchronize' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:583:in `invoke' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2051:in `invoke_task' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `each' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2001:in `run' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in `run' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:31 /usr/bin/rake:19:in `load' /usr/bin/rake:19 </code></pre></div> 21335 0 false 2009-07-15T08:18:11+02:00 62815 81 assign-macro-to-multiple-domains 54 11831 new 2009-07-15T08:18:11+02:00 62815 Erik Weber Erik Weber Kenneth Kalmer http://kennethkalmer.lighthouseapp.com/projects/11831/tickets/81 I'm currently in the process of migrating one powerdns instance to another. In that matter I have to change a lot of records due to new naming conventions. Macros is helpful at this, but executing a macro manually on every domain is a bit tedious. Especially when/if you pass 100, not to say 1000, domains. Would it be possible to add a text field where you paste a list of domains the macro should be executed on ? I'm currently in the process of migrating one powerdns instance to another. In that matter I have to change a lot of records due to new naming conventions. Macros is helpful at this, but executing a macro manually on every domain is a bit tedious. Especially when/if you pass 100, not to say 1000, domains. Would it be possible to add a text field where you paste a list of domains the macro should be executed on ? <div><p>I'm currently in the process of migrating one powerdns instance to another. In that matter I have to change a lot of records due to new naming conventions.</p> <p>Macros is helpful at this, but executing a macro manually on every domain is a bit tedious. Especially when/if you pass 100, not to say 1000, domains.</p> <p>Would it be possible to add a text field where you paste a list of domains the macro should be executed on ?</p></div> 21335 0 false 2008-07-22T16:02:36+02:00 21335 11691 27 batch-adding-of-domains 6 11831 new batch missing templates 2009-07-01T12:44:16+02:00 61514 jdobyns Kenneth Kalmer Kenneth Kalmer http://kennethkalmer.lighthouseapp.com/projects/11831/tickets/27 Medium Priority Allow adding domains in batch style using zone templates. Allow adding domains in batch style using zone templates. <div><p> Allow adding domains in batch style using zone templates. </p></div> 21335 0 false 2008-11-12T20:16:45+02:00 36248 48 add-support-for-various-domain-types 27 11831 open domains slave ui 2009-06-27T20:06:22+02:00 21335 Kenneth Kalmer olfway Kenneth Kalmer http://kennethkalmer.lighthouseapp.com/projects/11831/tickets/48 That's not possible to set master or slave type now That's not possible to set master or slave type now <div><p>That's not possible to set master or slave type now</p></div> 21335 0 false 2009-06-25T08:05:28+02:00 23238 80 rename-databaseyml-in-the-repo 53 11831 new 2009-06-25T08:05:34+02:00 23238 hkstar hkstar Kenneth Kalmer http://kennethkalmer.lighthouseapp.com/projects/11831/tickets/80 Hi, The only file in the git repo that needs to be modified by the user is config/database.yml. The user will change this, and then upon updating the file will conflict with the repo. I suggest changing the filename in the repo to database.yml.sample (or similar) and adding config/database.yml to .gitignore. This will force the user to copy the file and change it to their own needs, and then will not conflict at update time. Pretty small suggestion but might make it that little bit easier to deploy .. thanks, Sho Hi, The only file in the git repo that needs to be modified by the user is config/database.yml. The user will change this, and then upon updating the file will conflict with the repo. I suggest changing the filename in the repo to database.yml.sample (or similar) and adding config/database.yml to .gitignore. This will force the user to copy the file and change it to their own needs, and then will not conflict at update time. Pretty small suggestion but might make it that little bit easier to deploy .. thanks, Sho <div><p>Hi,</p> <p>The only file in the git repo that needs to be modified by the user is config/database.yml. The user will change this, and then upon updating the file will conflict with the repo.</p> <p>I suggest changing the filename in the repo to database.yml.sample (or similar) and adding config/database.yml to .gitignore. This will force the user to copy the file and change it to their own needs, and then will not conflict at update time.</p> <p>Pretty small suggestion but might make it that little bit easier to deploy ..</p> <p>thanks,</p> <p>Sho</p></div> 21335 0 true 2009-05-19T01:02:49+02:00 57304 78 mx-prio-not-set 51 11831 resolved create mx prio 2009-06-03T20:06:26+02:00 57304 Jacob Leaver Jacob Leaver Kenneth Kalmer http://kennethkalmer.lighthouseapp.com/projects/11831/tickets/78 When attempting to create an MX record, after filling out all the fields, I get an error "Prio is not a number", only, it is! The problem seems to be that the value srv-prio is overriding the value from mx-prio, as it's further down the page. I'm not sure what the 'right way' to tackle this problem would be, or I'd be attaching a patch. When attempting to create an MX record, after filling out all the fields, I get an error "Prio is not a number", only, it is! The problem seems to be that the value srv-prio is overriding the value from mx-prio, as it's further down the page. I'm not sure what the 'right way' to tackle this problem would be, or I'd be attaching a patch. <div><p>When attempting to create an MX record, after filling out all the fields, I get an error "Prio is not a number", only, it is! The problem seems to be that the value srv-prio is overriding the value from mx-prio, as it's further down the page.</p> <p>I'm not sure what the 'right way' to tackle this problem would be, or I'd be attaching a patch.</p></div> 21335 1 false 2009-01-19T17:49:54+02:00 44161 51 page-results-for-large-zones-domain-list 30 11831 new pagination record 2009-06-03T20:05:51+02:00 57304 Jacob Leaver Lee Standen Kenneth Kalmer http://kennethkalmer.lighthouseapp.com/projects/11831/tickets/51 I'm looking to use this software to manage over 20,000 domains with some zones having over 30,000 records. This currently kills the users' browser and the app server. Can a feature be added to limit the number of results to some configurable amount per page (maybe 50 by default)? Searching should allow you to view the specific record, but casually clicking on a domain shouldn't bring everything to a halt. I'm looking to use this software to manage over 20,000 domains with some zones having over 30,000 records. This currently kills the users' browser and the app server. Can a feature be added to limit the number of results to some configurable amount per page (maybe 50 by default)? Searching should allow you to view the specific record, but casually clicking on a domain shouldn't bring everything to a halt. <div><p>I'm looking to use this software to manage over 20,000 domains with some zones having over 30,000 records. This currently kills the users' browser and the app server.</p> <p>Can a feature be added to limit the number of results to some configurable amount per page (maybe 50 by default)?</p> <p>Searching should allow you to view the specific record, but casually clicking on a domain shouldn't bring everything to a halt.</p></div> 21335 0 false 2009-05-17T17:55:07+02:00 27917 77 wrap-text-when-showing-records 50 11831 new bug ui 2009-05-17T19:03:58+02:00 21335 Kenneth Kalmer RvdE Kenneth Kalmer http://kennethkalmer.lighthouseapp.com/projects/11831/tickets/77 I have some very large content data in my db (DKIM and SPF records). The screen doesn't wrap that data which makes the edit and delete button go all the way to the right (several clicks on the scrollbar) which make it impossible to determine to which record they belong. Would it be possible to wrap the text of the content field when it becomes too large to show in one browser window ? Thanks in advance. I have some very large content data in my db (DKIM and SPF records). The screen doesn't wrap that data which makes the edit and delete button go all the way to the right (several clicks on the scrollbar) which make it impossible to determine to which record they belong. Would it be possible to wrap the text of the content field when it becomes too large to show in one browser window ? Thanks in advance. <div><p>I have some very large content data in my db (DKIM and SPF records). The screen doesn't wrap that data which makes the edit and delete button go all the way to the right (several clicks on the scrollbar) which make it impossible to determine to which record they belong.</p> <p>Would it be possible to wrap the text of the content field when it becomes too large to show in one browser window ?</p> <p>Thanks in advance.</p></div> 21335 0 false 2009-04-30T08:17:07+02:00 55675 76 localization-with-i18n 49 11831 new i18n localization 2009-04-30T11:51:21+02:00 21335 Kenneth Kalmer Adam Kliment Kenneth Kalmer http://kennethkalmer.lighthouseapp.com/projects/11831/tickets/76 Hello, in rails 2.2.2 is now new feature to get easier localization. See: http://guides.rubyonrails.org/i18n.html We've started to work on rewriting all static text content to use with I18n because we would like to see your great app in Czech language. It could be useful for easy translation to many other languages. Please let us know if there's someone working on it too. We can contribute. Adam Hello, in rails 2.2.2 is now new feature to get easier localization. See: http://guides.rubyonrails.org/i18n.html We've started to work on rewriting all static text content to use with I18n because we would like to see your great app in Czech language. It could be useful for easy translation to many other languages. Please let us know if there's someone working on it too. We can contribute. Adam <div><p>Hello, in rails 2.2.2 is now new feature to get easier localization. See: <a href="http://guides.rubyonrails.org/i18n.html">http://guides.rubyonrails.org/i1...</a> We've started to work on rewriting all static text content to use with I18n because we would like to see your great app in Czech language. It could be useful for easy translation to many other languages. Please let us know if there's someone working on it too. We can contribute. Adam</p></div> 21335 0 false 2009-04-28T13:44:17+02:00 21335 75 macro-ui-needs-some-love 48 11831 new bug macros ui 2009-04-28T13:44:20+02:00 21335 Kenneth Kalmer Kenneth Kalmer Kenneth Kalmer http://kennethkalmer.lighthouseapp.com/projects/11831/tickets/75 On demoing the macro UI it appears several things are severely busted: * No confirmation flash when records are added * Error messages aren't cleared when correcting errors * Hosts can't be blank? * Position needs to be auto-populated On demoing the macro UI it appears several things are severely busted: * No confirmation flash when records are added * Error messages aren't cleared when correcting errors * Hosts can't be blank? * Position needs to be auto-populated <div><p>On demoing the macro UI it appears several things are severely busted:</p> <ul> <li>No confirmation flash when records are added</li> <li>Error messages aren't cleared when correcting errors</li> <li>Hosts can't be blank?</li> <li>Position needs to be auto-populated</li> </ul></div> 21335 0 false 2009-04-24T08:06:45+02:00 44564 74 add-a-filed-to-display-the-serial-number-of-a-domain 47 11831 new 2009-04-24T08:07:29+02:00 44564 boran boran Kenneth Kalmer http://kennethkalmer.lighthouseapp.com/projects/11831/tickets/74 This is important for me in troubleshooting and I would also like to be able to set the initial value in master domains. This is important for me in troubleshooting and I would also like to be able to set the initial value in master domains. <div><p>This is important for me in troubleshooting and I would also like to be able to set the initial value in master domains.</p></div> 21335 0 false 2009-04-24T08:03:36+02:00 44564 73 authentication-of-gui-users-in-ldap-or-activedirectory-would-be-nice 46 11831 new 2009-04-24T08:03:37+02:00 44564 boran boran Kenneth Kalmer http://kennethkalmer.lighthouseapp.com/projects/11831/tickets/73 Low priority, but just to track the issue Low priority, but just to track the issue <div><p>Low priority, but just to track the issue</p></div> 21335 0 false 2008-11-02T01:31:21+02:00 36248 47 ptr-auto-generation 26 11831 new missing ptr 2009-04-24T08:02:16+02:00 44564 boran olfway Kenneth Kalmer http://kennethkalmer.lighthouseapp.com/projects/11831/tickets/47 It would be cool if it will be possible to auto-generate PTR records for A records It would be cool if it will be possible to auto-generate PTR records for A records <div><p>It would be cool if it will be possible to auto-generate PTR records for A records</p></div> 21335 0 false 2009-04-24T07:54:49+02:00 44564 72 add-sorting-of-domain-rr-entries-by-column-title 45 11831 new 2009-04-24T07:54:53+02:00 44564 boran boran Kenneth Kalmer http://kennethkalmer.lighthouseapp.com/projects/11831/tickets/72 There is no way to choose the sorting in the "Domain RR" section. Its suggested that would should be able click on hostname, type, data to sort by that column. For example its very important to sort by IP address so one can see what IPs are not yet assigned There is no way to choose the sorting in the "Domain RR" section. Its suggested that would should be able click on hostname, type, data to sort by that column. For example its very important to sort by IP address so one can see what IPs are not yet assigned <div><p>There is no way to choose the sorting in the "Domain RR" section. Its suggested that would should be able click on hostname, type, data to sort by that column.</p> <p>For example its very important to sort by IP address so one can see what IPs are not yet assigned</p></div> 21335 0 false 2009-04-23T14:43:01+02:00 21335 11690 71 js-error-on-editing-domain-notes 17 11831 new bug domains notes ui 2009-04-23T14:43:02+02:00 21335 Kenneth Kalmer Kenneth Kalmer Kenneth Kalmer http://kennethkalmer.lighthouseapp.com/projects/11831/tickets/71 High Priority When editing a domain "notes", I got "RJS Error: Type Error: element is null", but it still save the text I added, which was "Test notes". The above error is followed with a dialog with Element.hide ("note") then show(note-row), update ().. I'm using FF3 if that is relevant. When editing a domain "notes", I got "RJS Error: Type Error: element is null", but it still save the text I added, which was "Test notes". The above error is followed with a dialog with Element.hide ("note") then show(note-row), update ().. I'm using FF3 if that is relevant. <div><p>When editing a domain "notes", I got "RJS Error: Type Error: element is null", but it still save the text I added, which was "Test notes". The above error is followed with a dialog with Element.hide ("note") then show(note-row), update ().. I'm using FF3 if that is relevant.</p></div> 21335 0 false 2009-04-23T14:38:59+02:00 21335 11690 70 migration-task-should-not-abort-on-errors 16 11831 new bug migrate 2009-04-23T14:38:59+02:00 21335 Kenneth Kalmer Kenneth Kalmer Kenneth Kalmer http://kennethkalmer.lighthouseapp.com/projects/11831/tickets/70 High Priority ...but rather report failures in a coherent fashion so the administrator can figure out what went wrong and address the "invalid" data. ...but rather report failures in a coherent fashion so the administrator can figure out what went wrong and address the "invalid" data. <div><p>...but rather report failures in a coherent fashion so the administrator can figure out what went wrong and address the "invalid" data.</p></div> 21335 0 false 2009-04-22T14:58:52+02:00 54533 69 adding-step-to-macro-priority-field-cannot-be-set 44 11831 new macro priority step 2009-04-22T14:58:56+02:00 54533 Julian Pawlowski Julian Pawlowski Kenneth Kalmer http://kennethkalmer.lighthouseapp.com/projects/11831/tickets/69 Adding records of types needing the priority field does not work properly as the field does not appear for entering the data. Without this the form is not accepted by the server. Workaround: Add the record with action "remove" and edit the entry afterwards. Works fine with templates, though. Adding records of types needing the priority field does not work properly as the field does not appear for entering the data. Without this the form is not accepted by the server. Workaround: Add the record with action "remove" and edit the entry afterwards. Works fine with templates, though. <div><p>Adding records of types needing the priority field does not work properly as the field does not appear for entering the data. Without this the form is not accepted by the server.</p> <p>Workaround: Add the record with action "remove" and edit the entry afterwards.</p> <p>Works fine with templates, though.</p></div> 21335 0 false 2009-04-19T11:42:36+02:00 21335 11691 68 optional-comments-for-changes 16 11831 new audits comments missing ui 2009-04-19T11:42:39+02:00 21335 Kenneth Kalmer Kenneth Kalmer Kenneth Kalmer http://kennethkalmer.lighthouseapp.com/projects/11831/tickets/68 Medium Priority When making changes to zones, or adding new RR's to a zone, we must provide a way for the user to add a comment on the change. This, combined with the audits, serves as a great tool for support staff to know why changes were made. Comments can reference helpdesk tickets, or anything that makes sense to the users. When making changes to zones, or adding new RR's to a zone, we must provide a way for the user to add a comment on the change. This, combined with the audits, serves as a great tool for support staff to know why changes were made. Comments can reference helpdesk tickets, or anything that makes sense to the users. <div><p>When making changes to zones, or adding new RR's to a zone, we must provide a way for the user to add a comment on the change. This, combined with the audits, serves as a great tool for support staff to know why changes were made. Comments can reference helpdesk tickets, or anything that makes sense to the users.</p></div>