http://bugzilla.lysator.liu.se/show_bug.cgi?id=149
ceder(a)lysator.liu.se changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=1127
------- Additional Comments From ceder(a)lysator.liu.se 2003-08-29 17:54 -------
It could, but due to bug 1095 and the fact that version 2.1.2 is due within
a few days, I'm very reluctant to do so.
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=1127
------- Additional Comments From kent(a)lysator.liu.se 2003-08-29 15:58 -------
Can the aux-items.conf file on LysLysKOM be changed without a restart?
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=1129
ceder(a)lysator.liu.se changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=194
ceder(a)lysator.liu.se changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
Target Milestone|Future |2.1.2
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=1129
ceder(a)lysator.liu.se changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Target Milestone|--- |2.1.2
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=1129
Summary: garb running too slow
Product: lyskomd
Version: 2.1.1
Platform: All
OS/Version: All
Status: NEW
Severity: major
Priority: P1
Component: server
AssignedTo: ceder(a)lysator.liu.se
ReportedBy: ceder(a)lysator.liu.se
QAContact: lyskomd-qa(a)lists.lysator.liu.se
The garb thread in 2.1.1 seems to be running at too low a priority.
It started running at 2003-08-27 09:37:15 and now, more than 24 hours
later, it still hasn't completed its first sweep of the texts.
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=149
ceder(a)lysator.liu.se changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=1121
ceder(a)lysator.liu.se changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
------- Additional Comments From ceder(a)lysator.liu.se 2003-08-29 01:23 -------
Fixed. The problem was that some code expected the range list to be in
its normal form during the mark-as-read operation -- but during it, the
ranges may actually be joined. adjust_read() will normalize the range
list.
I've also updated fparse_read_range_0() so that it can read a data structure
damaged by this bug. (The code in 2.1.0 and 2.1.1 can also read the structure,
but the damage will continue to exist.)
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=1127
kent(a)lysator.liu.se changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.