From: cworth@cworth.org (Carl Worth)
Subject: [sup-talk] Exception trying to run git source
Date: Wed, 19 Aug 2009 10:53:54 -0700 [thread overview]
Message-ID: <1250704257-sup-3308@yoom> (raw)
In-Reply-To: <1250699596-sup-8133@ntdws12.chass.utoronto.ca>
Excerpts from Ben Walton's message of Wed Aug 19 09:34:09 -0700 2009:
> Also, is bin/sup part of your git checkout (meaning it lines up with
> the rest of your lib/, etc)?
Yes.
> Are you running from the next branch?
> I'm looking at bin/sup here (5f393122), and the line numbers don't
> "add up." Line 152 is where I see the call into
> SentManager.source_uri, not 171.
No, I was running from master, (so line 171 does make sense there).
I tried running from next and got a different failure (see below). I
suspected I might have something just broken in my configuration, so I
moved ~/.sup away for the run below, (which didn't seem to change
anything).
This new failure seems to be occurring earlier, so I bisected,
(labelling the previous source_uri exception as "good" and the new
no-SentManager-instance as "bad"), and that pointed at the following
commit:
9dd4f50b9f62ab5642241359bf6f7c291ccfa738 is first bad commit
commit 9dd4f50b9f62ab5642241359bf6f7c291ccfa738
Author: William Morgan <wmorgan-sup at masanjin.net>
Date: Wed Aug 12 13:14:34 2009 -0400
rewrite Singleton to not require i_am_the_instance
The flip side is that you have to use .init instead of .new.
I'm really wondering why I'm getting what appear to be unique crashes
compared to others. Is it my ruby version:
$ ruby --version
ruby 1.8.7 (2009-06-12 patchlevel 174) [i486-linux]
Any ideas?
-Carl
0:~/src/sup:(next)$ ruby -I lib -w ./bin/sup
./lib/sup/util.rb:9: warning: method redefined; discarding old gen_lock_id
./lib/sup/util.rb:20: warning: method redefined; discarding old dump_lock_id
./lib/sup/message-chunks.rb:36: warning: method redefined; discarding old make_tmpname
./lib/sup/imap.rb:118: warning: ambiguous first argument; put parentheses or even spaces
/usr/lib/ruby/1.8/chronic/repeaters/repeater_month_name.rb:13: warning: useless use of > in void context
/usr/lib/ruby/1.8/chronic/repeaters/repeater_month_name.rb:19: warning: useless use of > in void context
/usr/lib/ruby/1.8/chronic/repeaters/repeater_month_name.rb:25: warning: useless use of < in void context
[Wed Aug 19 10:26:50 -0700 2009] WARNING: Warning: $KCODE is NONE.
./lib/sup/index.rb:54: warning: instance variable @lock_update_thread not initialized
./bin/sup:127: warning: global variable `$cursing' not initialized
./bin/sup:329: warning: global variable `$die' not initialized
[Wed Aug 19 10:26:50 -0700 2009] ERROR: oh crap, an exception
----------------------------------------------------------------
I'm very sorry. It seems that an error occurred in Sup. Please
accept my sincere apologies. If you don't mind, please send the
contents of ~/.sup/exception-log.txt and a brief report of the
circumstances to sup-talk at rubyforge dot orgs so that I might
address this problem. Thank you!
Sincerely,
William
----------------------------------------------------------------
--- RuntimeError from thread: main
no Redwood::SentManager instance defined in method call to i_am_the_instance!
./lib/sup/util.rb:512:in `method_missing'
/usr/lib/ruby/1.8/sup/sent.rb:10:in `initialize'
./lib/sup/util.rb:524:in `new'
./lib/sup/util.rb:524:in `init'
./lib/sup.rb:110:in `start'
./bin/sup:138
next prev parent reply other threads:[~2009-08-19 17:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 0:49 Carl Worth
2009-08-19 2:47 ` Ben Walton
2009-08-19 15:59 ` Ben Walton
2009-08-19 16:19 ` William Morgan
2009-08-19 16:33 ` Carl Worth
2009-08-19 16:34 ` Ben Walton
2009-08-19 17:53 ` Carl Worth [this message]
2009-08-19 18:08 ` Ben Walton
2009-08-19 18:52 ` William Morgan
2009-08-19 19:40 ` Carl Worth
2009-08-19 20:02 ` William Morgan
2009-08-19 21:37 ` Carl Worth
2009-08-22 20:23 ` William Morgan
2009-08-26 21:26 ` Carl Worth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1250704257-sup-3308@yoom \
--to=cworth@cworth.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox