Re: "Slow script" problem posting/editing from Safari -- browser hangs, times out, posted by Michael Kelsey on Sun Apr 15 08:03:21 2018
|
Thank you for your suggestion, Stefan! The sysadmin who handles our e-Log server implemented your suggestion earlier today (Saturday). I
have been able to successfully create and modify e-Log entries with Safari since then. Since the "slow script" issue has been intermittent
in the past, I plan to continue testing and monitoring for the next day or so. Nevertheless, it appears that removing the waiting loop has alleviated |
Re: "Slow script" problem posting/editing from Safari -- browser hangs, times out, posted by Stefan Ritt on Mon Apr 16 08:19:16 2018
|
Ok, I removed the code from the official code now.
A bit background: The "autosave" mechanism in elog saves regularly the current content in a "draft" message, so that the
data does not get lost if the browser for example crashes. The saving is done asynchronously via some AJAX call. This call takes some time, since it's |
Elog ID entry bug at >99999 entries, posted by Joseph McKenna on Fri May 4 14:43:35 2018 
|
We have a possible bug with elog that the ID for an elog entry at over 99,999 entires reads as 10,000...
68792/1 Illistrates the problem, we use this ID often to cross reference from out datalog...
Is this a know bug we can find a fix for? We are using: elogd 2.9.2 built Jul 14 2015, 18:58:06 revision |
|
Re: Elog ID entry bug at >99999 entries, posted by Andreas Luedeke on Fri May 4 16:05:32 2018
|
I am not sure I understand your bug report.
I can easily create IDs greater than 100'000 (see attached picture), but that is not your problem, or is it?
Cheers, Andreas |
|
Re: Elog ID entry bug at >99999 entries, posted by Chris Rasmussen on Sat May 5 11:22:50 2018
|
Hi Andreas, I'm working on the same experiment as Joseph who submitted the bug report.
You are right, IDs greater than 10^5 are created no problem. The issue is with the internal elog link, in this case of the form elog:SequencerEvents/XXXXX
The link generated uses only the first 5 digits of the message ID, and therefore links to the wrong message. In the two attachments you can see our sequencer |
|
Re: Elog ID entry bug at >99999 entries, posted by Andreas Luedeke on Sat May 5 20:55:23 2018
|
Well, in my example the ID link worked just fine.
There could be a string length limitation, but it could be as well the way you are creating the ID that is the source of the problem: I would
need the part of your elogd.cfg that defines how you format your ID in order to try to reproduce your problem. |
|
Re: Elog ID entry bug at >99999 entries, posted by Stefan Ritt on Mon May 7 14:24:18 2018
|
As Andreas said we have to reproduce the problem. What is special in your case is the elog:SequencerEvents/XXXXX.
This is non-standard and must be created through your configuration of elog or by an external script. I just guess that you have something like
Preset ID = elog:SequencerEvents/##### |
|
Re: Elog ID entry bug at >99999 entries, posted by Chris Rasmussen on Mon May 7 18:10:20 2018
|
ah yes, that was a helpful clue. Our elogd.cfg file led me to a .js file which redefines the ID to the elog:SequencerEvents/XXXXX
format and it indeed had a silly hard coded length of that string.
Since I am pretty sure this is our code, I think it is safe to say that this is not a bug in the elog |