From: anonymous <sup-bugs@masanjin.net>
To: sup-devel@rubyforge.org
Subject: [sup-devel] [issue94] sup crashes on thread labelling
Date: Wed, 21 Apr 2010 08:36:11 +0000 [thread overview]
Message-ID: <1271838971.05.0.229170305885.issue94@masanjin.net> (raw)
In-Reply-To: <1271838971.05.0.229170305885.issue94@masanjin.net>
[-- Attachment #1: Type: text/plain, Size: 770 bytes --]
New submission from anonymous:
sup crashes when labelling a certain thread with an existing label (i.e. other
same labeled threads exist). Labelling this thread in not possible, even afte
restart, other thread can be labeled with the given label.
label was "sopra2010"
exception log attached, may be a Xapian problem
----------
files: exception-log.txt
messages: 218
nosy: anonymous
priority: bug
ruby_version: ruby 1.8.7 (2010-01-10 patchlevel 249) [x86_64-linux]
status: unread
sup_version: sup/git last commitFri Apr 16 16:32:51 2010
title: sup crashes on thread labelling
_________________________________________
Sup issue tracker <sup-bugs@masanjin.net>
<http://masanjin.net/sup-bugs/issue94>
_________________________________________
[-- Attachment #2: exception-log.txt --]
[-- Type: text/plain, Size: 1174 bytes --]
--- ArgumentError from thread: index sync
InvalidArgumentError: Term `I9998' is not present in document, in Xapian::Document::Internal::remove_term()
/home/guedemann/source/sup/lib/sup/index.rb:665:in `remove_term'
/home/guedemann/source/sup/lib/sup/index.rb:665:in `index_message_locations'
/home/guedemann/source/sup/lib/sup/index.rb:665:in `each'
/home/guedemann/source/sup/lib/sup/index.rb:665:in `index_message_locations'
/home/guedemann/source/sup/lib/sup/index.rb:605:in `sync_message'
/home/guedemann/source/sup/lib/sup/index.rb:125:in `update_message_state'
/home/guedemann/source/sup/lib/sup/index.rb:428:in `run_sync_worker'
/home/guedemann/source/sup/lib/sup/index.rb:415:in `start_sync_worker'
/home/guedemann/source/sup/lib/sup.rb:77:in `reporting_thread'
/home/guedemann/source/sup/lib/sup.rb:75:in `initialize'
/home/guedemann/source/sup/lib/sup.rb:75:in `new'
/home/guedemann/source/sup/lib/sup.rb:75:in `reporting_thread'
/home/guedemann/source/sup/lib/sup/index.rb:415:in `start_sync_worker'
/home/guedemann/source/sup/lib/sup/util.rb:580:in `send'
/home/guedemann/source/sup/lib/sup/util.rb:580:in `method_missing'
/home/guedemann/source/sup/bin/sup:155
[-- Attachment #3: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
parent reply other threads:[~2010-04-21 8:39 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1271838971.05.0.229170305885.issue94@masanjin.net>]
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=1271838971.05.0.229170305885.issue94@masanjin.net \
--to=sup-bugs@masanjin.net \
--cc=sup-devel@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