public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: Tim Buck <tbuck@rrinc.com>
To: Chad Walstrom <chewie@wookimus.net>
Cc: help-gnats@gnu.org
Subject: Re: gnatsd problems with 4.0.1
Date: Thu, 06 Jan 2005 16:03:00 -0000	[thread overview]
Message-ID: <65360F34-5FFC-11D9-A76B-000393C83AC4@rrinc.com> (raw)
In-Reply-To: <20050105222435.GA23939@wookimus.net>


On Jan 5, 2005, at 5:24 PM, Chad Walstrom wrote:

> Tim Buck wrote:
>> However, the debugging binary doesn't work correctly. Some commands
>> (such as DBLS) work, but most EXPR commands return "415 invalid
>> expression" (the same expressions work in gnats 4.0).
>
> This is strange.  There were no changes to the regex code between 4.0
> and 4.0.1.  Have you tested simple expressions as well as more complex
> ones?  If you could share what you've tried, perhaps we can test on our
> own as well.

Here's a very simple example. This query string was generated by
GNATSweb. Both versions of GNATS were built on the same machine &
platform (FreeBSD 5.3/amd64):

using GNATS 4.0:
200 maytag.rrinc.com GNATS server 4.0 ready.
CHDB default
210-Now accessing GNATS database 'default'
210 User access level set to 'edit'
EXPR (State[type]!="closed") & (Responsible~"^tim$")
210 Ok.

using GNATS 4.0.1:
200 maytag.rrinc.com GNATS server 4.0.1 ready.
CHDB default
210-Now accessing GNATS database 'default'
210 User access level set to 'edit'
EXPR (State[type]!="closed") & (Responsible~"^tim$")
415 Invalid expression.

However, if I use a simpler version of that expression without the
extraneous parentheses (rather than the one generated from GNATSweb),
it works:

200 maytag.rrinc.com GNATS server 4.0.1 ready.
CHDB default
210-Now accessing GNATS database 'default'
210 User access level set to 'edit'
EXPR State[type]!="closed" & Responsible~"tim"
210 Ok.

I hope this info helps.

Tim Buck * Information Technology Manager * Recognition Research, Inc.
PHONE +1 540 961-6500 * FAX +1 540 961-3568 * EMAIL tbuck@rrinc.com
The only thing to do with good advice is to pass it on. -- Oscar Wilde




_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnats

      parent reply	other threads:[~2005-01-06 16:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-05 18:23 Tim Buck
2005-01-05 22:24 ` Chad Walstrom
2005-01-06  9:18   ` Mike M. Volokhov
2005-01-06 17:07     ` Chad Walstrom
2005-02-07 15:47       ` Mike M. Volokhov
2005-02-07 17:15         ` Mark D. Baushke
2005-02-07 19:17           ` Chad Walstrom
2005-02-09 12:50           ` Removing libiberty (was Re: gnatsd problems with 4.0.1) Mike M. Volokhov
2005-02-09 17:15             ` Mark D. Baushke
2005-02-07 17:45         ` Chad Walstrom
2005-02-09 10:56           ` Mike M. Volokhov
     [not found]             ` <20050221235730.GC31157@wookimus.net>
     [not found]               ` <20050222175714.30bc1593.mishka@apk.od.ua>
2005-02-24 22:17                 ` Soon to come: RC3 Chad Walstrom
2005-02-24 22:40                   ` RC2 (was Re: Soon to come: RC3) Chad Walstrom
2005-01-06 16:03   ` Tim Buck [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=65360F34-5FFC-11D9-A76B-000393C83AC4@rrinc.com \
    --to=tbuck@rrinc.com \
    --cc=chewie@wookimus.net \
    --cc=help-gnats@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).