similar to: stack level too deep when parsing xml

Displaying 20 results from an estimated 10000 matches similar to: "stack level too deep when parsing xml"

2017 Feb 24
1
Call for samples: Please help us build a Samba AD performance measuring tool
On Fri, 2017-02-17 at 11:11 +1300, Gary Lockyer wrote: > Script to provide an anonymous summary from tshark > > The tshark command needs to output a PDML XML stream, which this > command > will read. The summary is intended not to expose private or customer > data while allowing a good view on the range and frequency of the > network traffic. The script Gary posted, which is
2023 Feb 20
2
Using 'dummy.ups' for a real application, not just testing...
Tom via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> writes: >>That makes sense. So you'll have input voltage, output voltage, and >>output current I would guess. You might consider a nodemcu (ESP8266) >>publishing via MQTT to reduce power and use of unobtainium. > > Yes, that is exactly what I was planning to instrument. Maybe battery > voltage too
2006 Jun 06
1
stack level too deep
Iam new to ferret Iam trying to do a sample application on ferret this is my code: class SearchController < ApplicationController require ''ferret'' include Ferret index = Index::Index.new(:path => ''/path/to/index'') def list end def index index << {:title => "Programming Ruby", :content => "blah blah blah"}
2006 Mar 22
3
stack level too deep error : Pulling my hairs out
Hello, I''ve changed something in my test application and since I can''t find the cause of the "stack level too deep" raising on every request. I''ve removed almost every part of code and the error still occurs, eg with this url : www.myhost.com/main/index routes.rb (nothing else in this file) map.connect '':controller/:action/:id''
2007 Dec 25
1
puppetd: err: Got an uncaught exception of type SystemStackError: stack level too deep
i''m having trouble with a file resource with 0.24.1. the manifest is very simple: file { "/": ensure => directory, owner => "root", group => "root", mode => 755 } when i run puppetd, i get the attached stack trace. removing this resource enables puppetd to complete its run successfully. any ideas? didn''t have this
2007 Dec 31
0
Install woes : ''Stack level too deep'' exceptions
I have Ruby 1.8.6 03-13-2007 patch rails 2.0.2 Subversion is 1.4.5 I took the cruisecontrol-1.2.1.tgz download. I followed the steps in the getting started guide. On the "cruise add project" step I get a failure ''stack level too deep'' - No log files are created. Any ideas ? -- Gishu -------------- next part -------------- An HTML attachment was scrubbed...
2009 Jan 20
0
alias_method_chain in Facebooker Causing Stack Level Too Deep
I installed the Facebooker plugin and upon placing it on a staging server, I keep running into stack level too deep errors. It seems to stem from Facebooker using alias_method_chain to override some of the ActionController methods. I believe it''s getting loaded twice causing confusion. I''ve tried various methods include wrapping a unless respond_to?(:method) around the
2008 May 12
1
'Stack level too deep' error
Hi, Sometimes I am getting "Stack level too deep" exception. I have know no idea on when I am getting and why I am getting. Please give your suggestions. Thanks in advance... -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
2007 May 16
2
Hit mongrel once...all is well, hit it again...stack level too deep?
Hi there. I''ve dropped a mongrel log item here: http://pastie.caboo.se/62052 I can hit my app fine, once. Hitting it again gives me a 500 error and this log entry. I think it''s application code causing the problem as I have a second app running that doesn''t have this behavior, but I''m unsure how to proceed finding root cause here. Suggestions?
2006 Jan 20
1
stack level too deep from has_many / belongs_to relationship
I have the following 3 models (2 models joined by an intermediate): 1. class Exercise < ActiveRecord::Base 2. has_many :routines, :class_name=>''RoutineExercise'' 3. end 1. class Routine < ActiveRecord::Base 2. has_many :exercises, 3. :class_name=>''RoutineExercise'', 4. :order=>''position'' 5. end 1. class
2009 Jan 18
2
after_save -- stack level too deep
Hi all, I''m running into a brick wall trying to figure out my problem here. I have a model that has a boolean property called "paid". I''d like to add the following to my model: def after_save self.amount == self.splits.sum(:amount) ? self.update_attribute (:paid, true) : self.update_attribute(:paid, false) end The problem is, when I do this I get an error that
2006 May 24
2
"Stack Level Too Deep" issue in HABTM Unit / Functional Test
Hello guys. I was able to figure out that my "stack level too deep" error I was getting with my HABTM destroy method was the result of a bug in rails 1.0. I upgraded to 1.1.2 and now the views and any console-run commands for destroying AR objects linked together via HABTM work just fine. I have HABTM setup between stories and submissions. The issue is that the destroy methods in
2010 Jun 14
2
stack level too deep
I''m getting this on my client: Jun 14 15:21:26 s_sys@app09.fr.xxx.com puppetd[24751]: Could not retrieve catalog: stack level too deep on node app09.fr.twofish.com Jun 14 15:21:26 s_sys@app09.fr.xxx.com puppetd[24751]: Not using cache on failed catalog Since running puppetd in debug gives no useful info: info: Starting handler for Runner info: Starting server for Puppet version 0.24.8
2006 Jul 18
1
Fixtures Max Size? SystemStackError: stack level too deep
Hello, I have a table of zipcodes that I am using in my application, so there are approximately 50,000 rows in this table. I have dumped the table to a fixture yaml file to represent this data, but when I try to load it, I get this error: SystemStackError: stack level too deep Is there a max size allowed for a fixture file..? Here is the --trace output: rake db:fixtures:load --trace **
2008 Aug 31
2
stack level too deep - an elusive bug?
I was experimenting with template chains and detected the following issue with webgen-0.5.3: Generating tree... An error has occurred: stack level too deep The weird thing is that after deleting `webgen.cache`, website compilation is successfully. When `webgen` is run immediately after this successful compilation (i.e. without changing any files), the error above shows up. After
2008 Jun 05
2
RSpec Story - SystemStackError: stack level too deep
I have a story that executes the following (as an example to show the bug I''m experiencing): ---------------------------------------------- Given "I have a fake post saved" do @postCount = Post.find(:all).length @post = Post.new @post.employee_id = 123 @post.name = "Name of the Post" @post.description = "Description of the Post"
2007 Apr 18
1
stack level too deep for method missing when using drb
I set up ferret and it''s running fine normally. Now I want to hook up the backgroundrb server. However whenever I try to do a search, I get this error: (druby://localhost:9010) /usr/local/lib/ruby/1.8/drb/drb.rb:1075:in `method_missing'' (druby://localhost:9010) ./vendor/plugins/acts_as_ferret/lib/remote_index.rb:20:in `find_id_by_contents'' (druby://localhost:9010)
2006 Aug 15
0
SystemStackError: stack level too deep
Hi I have two models Keyword and KeywordResult, they basically look like this: class KeywordResult < ActiveRecord::Base belongs_to :keyword validates_presence_of :title, :url, :keyword_id end class Keyword < ActiveRecord::Base has_many :keyword_results, :dependent => :delete_all acts_as_tree :order => "text", :foreign_key => "top_keyword" end Before you
2007 Jun 01
0
"Exception: stack level too deep" on collection.clear?
Without getting too deep into my app I''m wondering if anyone has any clues what might give rise to the error posted below. It occurs when I run my unit tests. class Actor < AR:Base belongs_to :court_case end class CaseCause < AR:Base belongs_to :court_case end class CourtCase < AR:Base has_many :actors has_many :case_causes ... end def my_test_method ...
2007 Aug 30
1
alias_method_chain stack level too deep in Rake test only
I have an odd error. I have the following module: module ActionController module SslSupport def self.included(base) raise "#{base} does not define url_for" unless base.method_defined?(:url_for) unless base.respond_to?(:url_for_without_ssl_supprt) base.send :include, InstanceMethods base.send :alias_method_chain, :url_for, :ssl_support end