From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] trying sup again, couple of crashes, etc
Date: Sun, 17 Jan 2010 11:06:33 -0500 [thread overview]
Message-ID: <1263744149-sup-2441@masanjin.net> (raw)
In-Reply-To: <4B4EB5A9.8050001@exys.org>
Hi Arvid,
Sorry to hear about your negative experience. Sounds like it's several
unrelated issues all adding up.
Reformatted excerpts from Arvid Picciani's message of 2010-01-14:
> The interface only responds to shift-q. Typing only "q" will prompt and
> that prompt can not be answered with y Y ^y sane for the ^C prompt.
Sounds like you're using Ruby 1.9. You can either use Ruby 1.8, sup next
(bleeding-edge code, as you see below), or wait for Sup 0.10.
> So i went to the git next tree: It takes 30 seconds to start on a
> core2, and uses 100% cpu polling for new messages apparantly. Screen
> is flooded with ruby warnings, so it is unusable.
Can you run sup-sync before running Sup the first time? Adding new
messages does take a lot of CPU, but it's typically only an issue if you
have to add lots of documents.
> /home/aep/kram/mainline/lib/sup/xapian_index.rb:52:in `save_index':
> undefined method `flush' for nil:NilClass (NoMethodError)
Fixed in next already. Sorry about that.
> --- NoMethodError from thread: poll after loading inbox
> undefined method `[]' for nil:NilClass
> /home/aep/kram/mainline/lib/sup/xapian_index.rb:570:in `mkterm'
> /home/aep/kram/mainline/lib/sup/xapian_index.rb:345:in `find_docid'
I believe this is also fixed in next.
Please try again.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2010-01-17 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 6:11 Arvid Picciani
2010-01-15 0:03 ` Tero Tilus
2010-01-17 16:06 ` William Morgan [this message]
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=1263744149-sup-2441@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--cc=sup-talk@rubyforge.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