From: dfortunato@gmail.com (David Fortunato)
Subject: [sup-talk] crash with 'Too many clauses'
Date: Thu, 17 Jan 2008 19:11:22 -0500 [thread overview]
Message-ID: <12ACF456-3FEA-4BC0-B4AD-BD918B80C095@gmail.com> (raw)
I've run into a problem with sup 0.3. I tried the current git HEAD
and have the same problem.
It seems similar to http://rubyforge.org/pipermail/sup-talk/2007-December/000688.html
The crash log is attached, any ideas?
Thanks,
Dave
--- Ferret::StateError from thread: load threads for thread-index-mode
State Error occured at <except.c>:93 in xraise
Error occured in q_boolean.c:1595 - bq_add_query_nr
Two many clauses. The max clause limit is set to <1024> but
your query has <1024> clauses
. You can try increasing :max_clause_count for the BooleanQuery or
using a different type of quer
y.
/Library/Ruby/Gems/1.8/gems/sup-0.3/lib/sup/index.rb:270:in `add_query'
/Library/Ruby/Gems/1.8/gems/sup-0.3/lib/sup/index.rb:270:in
`each_message_in_thread_for'
/Library/Ruby/Gems/1.8/gems/sup-0.3/lib/sup/index.rb:268:in `each'
/Library/Ruby/Gems/1.8/gems/sup-0.3/lib/sup/index.rb:268:in
`each_message_in_thread_for'
/Library/Ruby/Gems/1.8/gems/sup-0.3/lib/sup/thread.rb:321:in
`load_thread_for_message'
/Library/Ruby/Gems/1.8/gems/sup-0.3/lib/sup/thread.rb:313:in
`load_n_threads'
/Library/Ruby/Gems/1.8/gems/sup-0.3/lib/sup/index.rb:217:in
`each_id_by_date'
/Library/Ruby/Gems/1.8/gems/sup-0.3/lib/sup/index.rb:217:in `each'
/Library/Ruby/Gems/1.8/gems/sup-0.3/lib/sup/index.rb:217:in
`each_id_by_date'
/Library/Ruby/Gems/1.8/gems/sup-0.3/lib/sup/thread.rb:308:in
`load_n_threads'
/Library/Ruby/Gems/1.8/gems/sup-0.3/lib/sup/modes/thread-index-mode.rb:
415:in `__unprotected_load
_n_threads'
(eval):12:in `load_n_threads'
/Library/Ruby/Gems/1.8/gems/sup-0.3/lib/sup/modes/thread-index-mode.rb:
404:in `load_n_threads_bac
kground'
/Library/Ruby/Gems/1.8/gems/sup-0.3/lib/sup.rb:69:in `reporting_thread'
/Library/Ruby/Gems/1.8/gems/sup-0.3/lib/sup.rb:67:in `initialize'
/Library/Ruby/Gems/1.8/gems/sup-0.3/lib/sup.rb:67:in `new'
/Library/Ruby/Gems/1.8/gems/sup-0.3/lib/sup.rb:67:in `reporting_thread'
/Library/Ruby/Gems/1.8/gems/sup-0.3/lib/sup/modes/thread-index-mode.rb:
403:in `load_n_threads_bac
kground'
/Library/Ruby/Gems/1.8/gems/sup-0.3/lib/sup/modes/thread-index-mode.rb:
454:in `__unprotected_load
_threads'
(eval):12:in `load_threads'
bin/sup:185
--- SystemExit from thread: main
State Error occured at <except.c>:93 in xraise
Error occured in q_boolean.c:1595 - bq_add_query_nr
Two many clauses. The max clause limit is set to <1024> but
your query has <1024> clauses
. You can try increasing :max_clause_count for the BooleanQuery or
using a different type of quer
y.
/Library/Ruby/Gems/1.8/gems/sup-0.3/lib/sup.rb:73:in `select'
/Library/Ruby/Gems/1.8/gems/sup-0.3/lib/sup/buffer.rb:31:in
`nonblocking_getch'
bin/sup:198
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: sup-exception-log-git.txt
Url: http://rubyforge.org/pipermail/sup-talk/attachments/20080117/e139b3e0/attachment.txt
-------------- next part --------------
next reply other threads:[~2008-01-18 0:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 0:11 David Fortunato [this message]
2008-01-18 2:56 ` David Fortunato
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=12ACF456-3FEA-4BC0-B4AD-BD918B80C095@gmail.com \
--to=dfortunato@gmail.com \
/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