headers
William Morgan | 1 Nov 2009 15:39

Re: [PATCH] minor nits in exception apology message

Reformatted excerpts from Tero Tilus's message of 2009-10-31:
> How about setting up a loose team which would handle the incoming bug
> reports (for you), track/sort all of them and fix what they feel like
> fixing and maybe upon request/occasionally report somewhere the
> current status (how many minors and majors open).

As far as I'm concerned, that would be great. I'm open to suggestions
about how to organize this. At this point I'm pretty convinced I will
never actually like a bug tracker, and I don't have the energy to write
another one, so for someone else to take the initiative would be
awesome.
--

-- 
William <wmorgan-sup <at> masanjin.net>
Permalink | Reply | 12 comments |
headers
William Morgan | 1 Nov 2009 15:45

Re: [PATCH] minor nits in exception apology message

[resend to list]

Reformatted excerpts from Jon Dugan's message of 2009-10-30:
> I've attached a patch that just make the BASE_DIR tweak.  I'll leave
> changing the instructions to you...

Applied to master. (Had to tweak it to make the path actually correct,
but no worries.)  Thanks!
--

-- 
William <wmorgan-sup <at> masanjin.net>
Permalink | Reply | 0 comments |
headers
William Morgan | 1 Nov 2009 15:53

Re: Recovering a busted ferret db?

Reformatted excerpts from Steven Walter's message of 2009-10-30:
> I am able to Ctrl-C sup-dump when it hangs.  Here's the ruby backtrace:
> 
> /var/lib/gems/1.8/gems/sup-0.9/lib/sup/util.rb:206:in `split': Interrupt
>         from /var/lib/gems/1.8/gems/sup-0.9/lib/sup/util.rb:206:in
> `split_on_commas'

It looks like you have some crazy long recipient email in some list
that's triggering worst-case behavior in a regexp. Can you try again
after applying this patch, please? (And I'd be curious how long the
address list was, if you find out what message is triggering this.)

diff --git a/lib/sup/person.rb b/lib/sup/person.rb
index 4b1c80b..dbedc79 100644
--- a/lib/sup/person.rb
+++ b/lib/sup/person.rb
 <at>  <at>  -105,6 +105,10  <at>  <at>  class Person

   def self.from_address_list ss
     return [] if ss.nil?
+    ## #split_on_commas has some bad behavior for long strings. so here we do
+    ## something nasty and just truncate the string at the nearest comma <= 500
+    ## characters.
+    ss = ss[0, ss.rindex(",", 500)] if ss.length > 500
     ss.split_on_commas.map { |s| self.from_address s }
   end

--

-- 
William <wmorgan-sup <at> masanjin.net>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Nicolas Pouillard | 1 Nov 2009 16:24
Picon
Gravatar

Re: [PATCH] minor nits in exception apology message

Excerpts from William Morgan's message of Sun Nov 01 15:39:25 +0100 2009:
> Reformatted excerpts from Tero Tilus's message of 2009-10-31:
> > How about setting up a loose team which would handle the incoming bug
> > reports (for you), track/sort all of them and fix what they feel like
> > fixing and maybe upon request/occasionally report somewhere the
> > current status (how many minors and majors open).
> 
> As far as I'm concerned, that would be great. I'm open to suggestions
> about how to organize this. At this point I'm pretty convinced I will
> never actually like a bug tracker, and I don't have the energy to write
> another one, so for someone else to take the initiative would be
> awesome.

Have strong points against Ditz or this is also a lake of energy?

--

-- 
Nicolas Pouillard
http://nicolaspouillard.fr
Permalink | Reply | 4 comments |
headers
William Morgan | 1 Nov 2009 17:19

Re: [PATCH] minor nits in exception apology message

Reformatted excerpts from Nicolas Pouillard's message of 2009-11-01:
> Have strong points against Ditz or this is also a lake of energy?

Both, really. Ditz was an experiment, and after using it for a while I
decided it was more trouble than it was worth. I also realized that I
*did* want a centralized web site after all, and not necessarily a
complicated distributed thing, both because I want non-technical users
to be able to submit bug reports, and because development, in reality,
*is* centralized.

(I had been doing some work on Sheila, which would've provided a web
frontent that people could use to submit bug reports, but even that
wouldn't be quite what I wanted.)

Having thought about it for a while, I think what I *really* want for
Sup is something that tracks bugs/feature requests at the feature branch
level (i.e. assumes that each feature branch provides a new feature or a
bugfix), has a web interface for non-technical users to submit bug
reports and for developers to browse/modify state on bugs, and which
uses email for discussion, like I did with Whisper. (And I would be fine
with it being git-specific.)

I am now spending all my energy trying to keep myself from building such 
a thing.
--

-- 
William <wmorgan-sup <at> masanjin.net>
Permalink | Reply | 3 comments |
headers
William Morgan | 1 Nov 2009 17:32

Re: Can't search without crashing

Reformatted excerpts from Steve Goldman's message of 2009-10-26:
> Wow, I guess I haven't tried to search in a while... I can't search
> for *anything* without it crashing hard.  Every time.  I'm on master.

In ~/.sup/sources.yaml, do you have a source with "id: 4"?
--

-- 
William <wmorgan-sup <at> masanjin.net>
Permalink | Reply | 2 comments |
headers
Steve Goldman | 1 Nov 2009 17:48

Re: Can't search without crashing

Excerpts from William Morgan's message of Sun Nov 01 11:32:35 -0500 2009:
> Reformatted excerpts from Steve Goldman's message of 2009-10-26:
> > Wow, I guess I haven't tried to search in a while... I can't search
> > for *anything* without it crashing hard.  Every time.  I'm on master.
> 
> In ~/.sup/sources.yaml, do you have a source with "id: 4"?

No.

Although a few weeks ago I cleared out a bunch of sources that I
thought were defunct from that file.

I'm replacing those sources (at least I backed up the sources.yaml
file) and will see how that goes.

And now I'm feeling stupid...
--

-- 

Steve Goldman
sgoldman <at> tower-research.com

T: 212.219.6014
F: 212.219.6007

Tower Research Capital, LLC
377 Broadway, 11th Fl.
New York, NY 10013
Permalink | Reply | 1 comment |
headers
Nicolas Pouillard | 1 Nov 2009 17:48
Picon
Gravatar

Re: [PATCH] minor nits in exception apology message

Excerpts from William Morgan's message of Sun Nov 01 17:19:23 +0100 2009:
> Reformatted excerpts from Nicolas Pouillard's message of 2009-11-01:
> > Have strong points against Ditz or this is also a lake of energy?
> 
> Both, really. Ditz was an experiment, and after using it for a while I
> decided it was more trouble than it was worth. I also realized that I
> *did* want a centralized web site after all, and not necessarily a
> complicated distributed thing, both because I want non-technical users
> to be able to submit bug reports, and because development, in reality,
> *is* centralized.

I think I see your point, however I think there is no less no more to
centralize in a bugtracker than in a source code management tool. Indeed
in most projects using a DVCS, they have a central repository, this
does not reduce the benefits of distributed tools. Distributed bugtrackers
does not necessary exclude having a central point.  What I found cool
about distributed bugtrackers is that the bug-closing action can follow
the code that fixes the bug. Being in a branch, or being reviewed...

About non-technical users, I think that just a mail (thread) on the
mailing-list could suffice. Of course some web app can make things clearer.

> (I had been doing some work on Sheila, which would've provided a web
> frontent that people could use to submit bug reports, but even that
> wouldn't be quite what I wanted.)

> Having thought about it for a while, I think what I *really* want for
> Sup is something that tracks bugs/feature requests at the feature branch
> level (i.e. assumes that each feature branch provides a new feature or a
> bugfix), has a web interface for non-technical users to submit bug
(Continue reading)

Permalink | Reply | 2 comments |
headers
Steve Goldman | 1 Nov 2009 17:49

What happened to the log buffer?


I'm somewhere near the next branch.

Formerly, when I started sup I could cycle through a few buffers with
'b', two of which were some sort of log buffers.  These are gone now.

Anyone know?

Thanks.
--

-- 

Steve Goldman
sgoldman <at> tower-research.com

T: 212.219.6014
F: 212.219.6007

Tower Research Capital, LLC
377 Broadway, 11th Fl.
New York, NY 10013
Permalink | Reply | 1 comment |
headers
William Morgan | 1 Nov 2009 17:23

Re: Arch Linux Sup Package (Ruby 1.9.1 + Sup 0.9)

Reformatted excerpts from Andrei Thorp's message of 2009-10-18:
>  - I've applyed Lloyd's patch for fixing the UTF-8 check.

Which patch was this? The only "Lloyd patch" one I'm aware of is:
http://github.com/lloyd/sup/commit/d07986419b87053b41f7ed4bd7b6d1e537704864

which a) I don't quite understand, and b) isn't about utf8.
--

-- 
William <wmorgan-sup <at> masanjin.net>
Permalink | Reply | 1 comment |

Gmane