Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
 Back  |  Find  |  Login  |  Help 
icon4.gif   Crash report involving propagate and replies, posted by Stephen on Tue Nov 26 16:24:39 2013 elogd.cfg
    icon2.gif   Re: Crash report involving propagate and replies, posted by David Pilgram on Tue Nov 26 21:49:42 2013 
       icon2.gif   Re: Crash report involving propagate and replies, posted by Stephen on Wed Nov 27 15:22:37 2013 
    icon2.gif   Re: Crash report involving propagate and replies, posted by Andreas Luedeke on Mon Dec 2 09:27:35 2013 elogd.cfg
    icon2.gif   Re: Crash report involving propagate and replies, posted by Andreas Luedeke on Mon Dec 2 09:58:42 2013 elogd.cfgelog.png
       icon2.gif   Re: Crash report involving propagate and replies, posted by Stephen on Mon Dec 2 23:02:45 2013 
          icon2.gif   Re: Crash report involving propagate and replies, posted by Andreas Luedeke on Tue Dec 3 11:30:43 2013 
             icon2.gif   Re: Crash report involving propagate and replies, posted by Hung Dao on Fri Jan 3 21:33:40 2014 error1.jpgerror2.jpgerror3.jpg
                icon2.gif   Re: Crash report involving propagate and replies, posted by Stefan Ritt on Mon Jan 6 10:25:03 2014 
                icon2.gif   Re: Crash report involving propagate and replies, posted by Andreas Luedeke on Mon Jan 6 10:32:43 2014 
                   icon2.gif   Re: Crash report involving propagate and replies, posted by Hung Dao on Sun Jan 12 04:48:12 2014 test.jpgtest2.jpg
                      icon2.gif   Re: Crash report involving propagate and replies, posted by Stefan Ritt on Mon Jan 13 09:01:31 2014 
    icon2.gif   Re: Crash report involving propagate and replies, posted by Stefan Ritt on Mon Jan 13 09:30:09 2014 
       icon2.gif   Re: Crash report involving propagate and replies, posted by Stephen on Fri Jan 24 18:59:17 2014 
          icon2.gif   Re: Crash report involving propagate and replies, posted by Stephen on Wed Jan 29 17:13:55 2014 
          icon2.gif   Re: Crash report involving propagate and replies, posted by Hung Dao on Mon Feb 3 22:45:10 2014 
Message ID: 67630     Entry time: Wed Nov 27 15:22:37 2013     In reply to: 67629
Icon: Reply  Author: Stephen  Author Email: swgallman@bpa.gov 
Category: Bug report  OS: Windows  ELOG Version: 2.9.2 
Subject: Re: Crash report involving propagate and replies 

David Pilgram wrote:

Stephen wrote:

Using Elog 2.9.2

Elog crashes when making 10 replies, I narrowed the crash down to the Propagate Attributes setting.

I have an attribute "Status" that can be toggled between "Open" and "Closed" and that propagates all replies.  On the 10th reply the application crashed, this is repeatable 100% of the time.  Without the propagate option everything works fine.

Attached is my config file parsed down.

Is there a way around this, or is there a way on reply to change the attribute of the log note you replied to from open to closed without using the propagate option?

Hi Stephen,

I see that you don't allow branching in your threads.  Why do you need to propagate the Status throughtout the thread?  Why not just mark the latest entry and (incase it is necessary) 'collapse to last = 1'

I'm not saying that the bug (if bug it is, rather than a preset limitation) you've found should not be fixed, but I'm puzzled as to why you happen to use the feature.  I can see the point if an initial entry provides a whole tree of branches (and a limit of 10 is rather limiting).  OK, I know if it is historic, it cannot easily be changed because of other users.  Or if some users will primarily be responding to emails rather viewing the logbook via a browser.  I'm a single (ab)user elog system myself, so I'm very tolerant of changing how elog works if it offers an improvement.

 Thank you for the reply, the not allowing branching was added during the troubleshooting phase of the crashing.  Initially I thought the branches caused the issue because crashing only occured on log notes that branched as I only saw the crash on notes that branched, this proved not to be the case.  Even with branches the system will crash once there are 10 replies in the note with propagate on.

As for use case, with  a few users I needed a way to represent a note as open so that the next person knew work still needed to be done.  Once work was completed all notes close, the reason for not using edit is so I have a clear record of what happened (although I may need to change to edit if 10 is the max).  I will experiment with the collapse to last to see how it looks.  Any other suggestions would be helpful.

ELOG V3.1.5-fe60aaf