community/pipermail-archives/sup-devel/2012-11.txt (3491B) - raw
1 From sup-asheesh@asheesh.org Sun Nov 25 04:45:48 2012
2 From: sup-asheesh@asheesh.org (Asheesh Laroia)
3 Date: Sat, 24 Nov 2012 23:45:48 -0500 (EST)
4 Subject: [sup-devel] Backtrace, and confusion
5 Message-ID: <alpine.DEB.2.02.1211242342310.7520@rose.makesad.us>
6
7 Hey all,
8
9 I presume sup is sort of end-of-life'd at this point, but I wondered if
10 some people here might have an idea for how to address the following
11 crash.
12
13 I experience it with current git on my sup database; I just start sup, and
14 get the familiar sup screen only to nearly immediately see it crash with
15 this backtrace:
16
17 --- NoMethodError from thread: load threads for thread-index-mode
18 undefined method `person_for' for
19 #<Redwood::ContactManager:0x7f123d552570>
20 ./lib/sup/util.rb:572:in `send'
21 ./lib/sup/util.rb:572:in `method_missing'
22 ./lib/sup/person.rb:82:in `from_name_and_email'
23 ./lib/sup/index.rb:215:in `build_message'
24 ./lib/sup/index.rb:216:in `[]'
25 ./lib/sup/index.rb:216:in `build_message'
26 ./lib/sup/index.rb:155:in `each_id_by_date'
27 ./lib/sup/thread.rb:338:in `call'
28 ./lib/sup/thread.rb:338:in `load_n_threads'
29 ./lib/sup/index.rb:155:in `each_id_by_date'
30 ./lib/sup/index.rb:252:in `each_id'
31 ./lib/sup/index.rb:252:in `each'
32 ./lib/sup/index.rb:252:in `each_id'
33 ./lib/sup/index.rb:155:in `each_id_by_date'
34 ./lib/sup/thread.rb:334:in `load_n_threads'
35 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:640:in
36 `__unprotected_load_n_threads'
37 (eval):12:in `load_n_threads'
38 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:624:in
39 `load_n_threads_background'
40 ./lib/sup.rb:79:in `reporting_thread'
41 ./lib/sup.rb:77:in `initialize'
42 ./lib/sup.rb:77:in `new'
43 ./lib/sup.rb:77:in `reporting_thread'
44 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:623:in
45 `load_n_threads_background'
46 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:694:in
47 `__unprotected_load_threads'
48 (eval):12:in `load_threads'
49 bin/sup:223
50
51
52 I reproduced it against current git by running:
53
54 ruby -I lib -w bin/sup
55
56 I also reproduced it wih sup 0.11 as packaged in Debian.
57
58 I'm actually a bit confused; I tried to debug it, but it seems the
59 NoMethodError is somewhat unwarranted; the method is defined in
60 lib/sup/person.rb. Unless I don't underestand Ruby, which is actually very
61 likely; I'm more of a Python programmer myself.
62
63 So, hope to hear back,
64
65 -- Asheesh.
66
67 From alvherre@alvh.no-ip.org Mon Nov 26 12:46:38 2012
68 From: alvherre@alvh.no-ip.org (Alvaro Herrera)
69 Date: Mon, 26 Nov 2012 09:46:38 -0300
70 Subject: [sup-devel] Backtrace, and confusion
71 In-Reply-To: <alpine.DEB.2.02.1211242342310.7520@rose.makesad.us>
72 References: <alpine.DEB.2.02.1211242342310.7520@rose.makesad.us>
73 Message-ID: <20121126124638.GA4227@alvh.no-ip.org>
74
75 Asheesh Laroia wrote:
76 > Hey all,
77 >
78 > I presume sup is sort of end-of-life'd at this point, but I wondered
79 > if some people here might have an idea for how to address the
80 > following crash.
81 >
82 > I experience it with current git on my sup database; I just start
83 > sup, and get the familiar sup screen only to nearly immediately see
84 > it crash with this backtrace:
85 >
86 > --- NoMethodError from thread: load threads for thread-index-mode
87 > undefined method `person_for' for
88 > #<Redwood::ContactManager:0x7f123d552570>
89
90 Due to the EOL state of Sup you mention I didn't pursue a similar crash
91 I had, but I observed that parts of the ContactManager used case
92 sensitive lookups; so when I entered an address of mine using uppercase
93 letters, it caused pretty funky behavior. I have no patch to offer,
94 though.
95
96 --
97 Alvaro Herrera
98