RE: Unparseable replies from GNATS server

* RE: Unparseable replies from GNATS server
@ 2004-08-26 20:15 Stuart Stevens
  0 siblings, 0 replies; 5+ messages in thread
From: Stuart Stevens @ 2004-08-26 20:15 UTC (permalink / raw)
  To: 'Stuart Stevens', help-gnats

Ok, I have a working solution to get around two different problems.  The
Note has to be before Notes and Notes needs a default value.  I need to do
some more analysis to propose a code change.

Here is my currently working solution for an append field.

field "Note" {
    multitext
    on-change {
        append-to-field "Notes" {
"\n================================================\n%D  %s\n\n%s\n"
                "$CurrentDate" "$EditUserEmailAddr" "$NewValue"
        }
    }
    on-change {
        set-field "Note" {
            ""
        }
    }
    on-change {
        add-audit-trail
    }
}

field "Notes" {
    multitext {
        default ""
    }
    read-only
}

-----Original Message-----
From: Stuart Stevens [mailto:stuart_stevens@sierralogic.com] 
Sent: Thursday, August 12, 2004 10:27 AM
To: 'Stuart Stevens'; help-gnats@gnu.org
Subject: RE: Unparseable replies from GNATS server

Hi

Does anybody have a recommendation on how to add an append-only comments
field?

I would like edits to allow new additions to the field and views to show the
whole field.

Stuart

-----Original Message-----
From: Stuart Stevens [mailto:stuart_stevens@sierralogic.com]
Sent: Wednesday, August 04, 2004 7:49 PM
To: 'Stuart Stevens'; help-gnats@gnu.org
Subject: RE: Unparseable replies from GNATS server

In edit.c, set_field is being called with old_value set to 0x00.

     if ((old_value == NULL && new_value != NULL)
         || (new_value == NULL && old_value != NULL)
         || (new_value != old_value && strcmp (old_value, new_value) != 0))
       {
         /* Ignore changes to readonly fields.  */
         if (fieldDefForIndex (field)->readonly)
           {
             fieldsChanged[x] = 0;
             set_field (new_pr, field, old_value, err);
           }
         else
           {
             fieldsChanged[x] = 1;
           }
       }

-----Original Message-----
From: Stuart Stevens [mailto:stuart_stevens@sierralogic.com]
Sent: Wednesday, August 04, 2004 5:08 AM
To: 'Stuart Stevens'; help-gnats@gnu.org
Subject: RE: Unparseable replies from GNATS server

I am running GNATS 4.0 on Linux - Red Hat 9.  I pulled the TOT and rebuilt
this morning.  I then run the daemon directly and I got a memory fault.  The
daemon fails with the following field "Comment-new" added to dbconfig:

field "Comments" {
    multitext
    read-only
}

field "Comment-new" {
    multitext
    on-change {
        append-to-field "Comments" {
                "Comment added by %s  on %D\n\n%s"
                "$EditUserEmailAddress" "$CurrentDate" "$NewValue"
        }
    }
    on-change {
        set-field "Comment-new" {
            ""
        }
    }
} 

I issued the following commands:

lock 2511 stuart
editaddr stuart
edit 2511
<email with changes>

Next step is to get into the debugger.

Any ideas?

Thanks
Stuart

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

^ permalink raw reply	[flat|nested] 5+ messages in thread