From: Dirk Schenkewitz <Dirk.Schenkewitz@interface-ag.com>
To: Mel Hatzis <hatzis@juniper.net>, help-gnats <help-gnats@gnu.org>
Subject: Re: too many 'changed' entries
Date: Fri, 28 Mar 2003 16:57:00 -0000 [thread overview]
Message-ID: <3E847B8B.900B6EC8@interface-ag.com> (raw)
In-Reply-To: <3E833FD7.9050902@juniper.net>
Mel Hatzis schrieb:
>
> On 03/27/2003 06:04 AM, Dirk Schenkewitz submitted:
>
> >Dirk Schenkewitz schrieb:
> >
> >
> >>Hi All,
> >>
> >>Can someone give me a hint to get rid of this:
> >>
> >>Every time a PR is edited (via Gnatsweb) it happens that stuff is noted as
> >>'changed' in the Audit-Trail, although the only "change" was the formatting,
> >>and even there the user did not change anything - all of this happens auto-
> >>matically.
> >>
> >>As an example, here is something I found in one audit-trail.
> >>/
> >>| Description-Changed-From-To: In einer Mehrfachauswahl wird auf einen String mit einem '#D ' abgefragt. Entspricht der Wert,
> >>| verläuft zunächst alles gut. Entspricht der Wert nicht und muss er nur überlesen werden, kommt Fehler: Variable Konstante
> >>| erwartet.
> >>| ->In einer Mehrfachauswahl wird auf einen String mit einem '#D
> >>| ' abgefragt. Entspricht der Wert, verläuft zunächst alles
> >>| gut. Entspricht der Wert nicht und muss er nur überlesen
> >>| werden, kommt Fehler: Variable Konstante erwartet.
> >>\
> >>
> >>We're using Gnatsweb v3.99.3, Gnats v4.0-beta1 (taken from the GnatsWeb
> >>display) - is this a known bug which can be removed by updating, perhaps ?
> >>Or did I make a configuration mistake ?
(browser related stuff deleted)
> >Has nobody else observed this ?
> >(Please, people, give me a hint, even if it is something obvious -
> >right now i'm just out of ideas.)
> >
> I noticed this too. In my case, I setup a field as 'required' and
> it wasn't working via gnatsweb, because gnatsweb was inserting a
> newline (thereby making the field look like it had a value).
>
> I fixed it by changing the 'fix_multiline_val' sub, as follows:
>
> sub fix_multiline_val
> {
> my $val = shift;
> $val =~ s/\r\n?/\n/g;
> $val .= "\n" unless $val =~ /\n$/;
> if ($val =~ /^\s*$/)
> {
> # don't allow whitespace values to circumvent 'required' fields
> $val = "";
> }
> $val;
> }
>
> This basically prevents whitespace only values from being entered
> as the (multiline) field value which I consider to be a good fix.
Absolutely.
> This should help you in the case where a newly created PR is edited
> for the first time - since this is when gnatsweb will add the
> newline, thereby changing the field and adding a change log to the
> audit trail.
Weird observation, perhaps pure chance and completely unrelated, but
- it seems to remove even my problem, which also happens when there
already is something in a field. I have no idea what is going on.
> Hope this helps.
It did, so far! I'm not sure if I can believe that it's gone forever.
But right now it seems to be. (Even if it comes back, now I have an
idea where to tweak things.)
Thanks a lot, I owe you a beer, at least. :-)
Have fun
dirk
--
Dirk Schenkewitz
InterFace AG fon: +49 (0)89 / 610 49 - 126
Leipziger Str. 16 fax: +49 (0)89 / 610 49 - 83
D-82008 Unterhaching
http://www.interface-ag.de mailto:dirk.schenkewitz@interface-ag.de
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats
next prev parent reply other threads:[~2003-03-28 16:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-24 10:49 Dirk Schenkewitz
2003-03-27 14:06 ` Dirk Schenkewitz
2003-03-27 18:19 ` Mel Hatzis
2003-03-28 16:57 ` Dirk Schenkewitz [this message]
2003-04-29 21:05 ` Yngve Svendsen
2003-05-07 17:05 ` Dirk Schenkewitz
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=3E847B8B.900B6EC8@interface-ag.com \
--to=dirk.schenkewitz@interface-ag.com \
--cc=hatzis@juniper.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).