| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
67652
|
Tue Jan 14 21:50:50 2014 |
 | Grant | enzedder@me.com | Question | All | 2.9.2 | Users logged out? |
Hi All,
I'm looking for a way (or if it is even possible?) for users to browse between logbooks without being logged out of their current logbook if they click on a logbook they are not authorised to access?
If they accidentally choose the wrong logbook they are forced to log back in again?
No guest access has been configured on any log.
TIA
|
|
67657
|
Mon Jan 20 19:15:24 2014 |
| Daniel Campora | dcampora@cern.ch | Request | All | 2.9.2 | [Not] Submit on pressing enter key |
Hello community,
I have a feature request for the form of the ELOG.
For some users, especially coming from a MAC background, it is very inconvenient to press enter (ie. on the subject field) and post a message (or get prompted to do so). Instead, enter in these fields should work as a tab.
Cheers, keep up the good work,
Daniel |
|
67658
|
Tue Jan 21 13:17:52 2014 |
 | Stefan Ritt | stefan.ritt@psi.ch | Request | All | 2.9.2 | Re: [Not] Submit on pressing enter key |
| Daniel Campora wrote: |
|
Hello community,
I have a feature request for the form of the ELOG.
For some users, especially coming from a MAC background, it is very inconvenient to press enter (ie. on the subject field) and post a message (or get prompted to do so). Instead, enter in these fields should work as a tab.
Cheers, keep up the good work,
Daniel
|
Have a look at this forum. If you press <enter> on the subject field, you get asked "do you really want to submit this entry" and you have the chance to cancel and continue editing. You should get the same with the current elog version. |
| Attachment 1: Screen_Shot_2014-01-21_at_13.16.48_.png
|
|
|
67659
|
Fri Jan 24 18:59:17 2014 |
| Stephen | swgallman@bpa.gov | Bug report | Windows | 2.9.2 | Re: Crash report involving propagate and replies |
| Stefan Ritt 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?
|
Was a tricky problem. When you use "Propagate Attributes", a routine is called inside elogd which recursively goes through all replies. It uses quite some memory for temporary storage of attributes and attachments. So after a certain time you get a stack overflow since you run out of memory. Since the stack size is different under different operating systems, it was hard for me to reproduce it initially. Now I use some different memory (dynamic heap instead stack) which should fix the problem. Can you pull from GIT and give it a try?
/Stefan
|
Unfortunately, I am a little outside of my element when trying to compile it. I will ask around and see if someone here could give me a hand. Thanks for looking into this for me.
PS. If anyone else has managed to compile this could you give me a hand =) |
|
67660
|
Wed Jan 29 17:13:55 2014 |
| Stephen | swgallman@bpa.gov | Bug report | Windows | 2.9.2 | Re: Crash report involving propagate and replies |
| Stephen wrote: |
|
| Stefan Ritt 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?
|
Was a tricky problem. When you use "Propagate Attributes", a routine is called inside elogd which recursively goes through all replies. It uses quite some memory for temporary storage of attributes and attachments. So after a certain time you get a stack overflow since you run out of memory. Since the stack size is different under different operating systems, it was hard for me to reproduce it initially. Now I use some different memory (dynamic heap instead stack) which should fix the problem. Can you pull from GIT and give it a try?
/Stefan
|
Unfortunately, I am a little outside of my element when trying to compile it. I will ask around and see if someone here could give me a hand. Thanks for looking into this for me.
PS. If anyone else has managed to compile this could you give me a hand =)
|
This resolved the issue, thanks for the help. I have tested it on server machines and was able to go over 10 each time.
Thank you for resolving this issue for me. |
|
67661
|
Mon Feb 3 22:45:10 2014 |
| Hung Dao | hungtdao@yahoo.com | Bug report | Windows | 2.9.2 | Re: Crash report involving propagate and replies |
| Stephen wrote: |
|
| Stefan Ritt 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?
|
Was a tricky problem. When you use "Propagate Attributes", a routine is called inside elogd which recursively goes through all replies. It uses quite some memory for temporary storage of attributes and attachments. So after a certain time you get a stack overflow since you run out of memory. Since the stack size is different under different operating systems, it was hard for me to reproduce it initially. Now I use some different memory (dynamic heap instead stack) which should fix the problem. Can you pull from GIT and give it a try?
/Stefan
|
Unfortunately, I am a little outside of my element when trying to compile it. I will ask around and see if someone here could give me a hand. Thanks for looking into this for me.
PS. If anyone else has managed to compile this could you give me a hand =)
|
I was able to manage and compile the latest code from GIT. It runs fine so far. Just a hint, in order to compile successfully, there are some steps that you may need to modify your header file depend on how you store your mxml, krb5, OpenSSL files and directories. |
|
67662
|
Tue Feb 18 21:32:27 2014 |
| Matthew Deller | dellzoid@hotmail.com | Question | Linux | 2.9.2 | Unable to resize images in browser |
I am unable to resize/ manipulate images in browser. Image Magick detected Version: ImageMagick 6.6.9-7 2012-08-17.
Output when running elog with verbose option shows buffer overflow when resize attempted:
[[Going to execute: /bin/sh -c "identify -format '%wx%h %c' '/home/elog/elog-2.9.2/logbooks/HardwareLog/140218_120423_2014-02-18_remod_(extended_II).png.png'" > /tmp/elog-shell 2>&1
Falling back to default group "elog"
Falling back to default user "elog"
*** buffer overflow detected ***: elogd terminated
Any ideas how to fix this? I'm not sure if this is a problem with the elog / Ubuntu / Image Magick? |
|
67666
|
Fri Feb 21 13:09:48 2014 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.9.2 | Re: Unable to resize images in browser |
| Matthew Deller wrote: | I am unable to resize/ manipulate images in browser. Image Magick detected Version: ImageMagick 6.6.9-7 2012-08-17.
Output when running elog with verbose option shows buffer overflow when resize attempted:
[[Going to execute: /bin/sh -c "identify -format '%wx%h %c' '/home/elog/elog-2.9.2/logbooks/HardwareLog/140218_120423_2014-02-18_remod_(extended_II).png.png'" > /tmp/elog-shell 2>&1
Falling back to default group "elog"
Falling back to default user "elog"
*** buffer overflow detected ***: elogd terminated
Any ideas how to fix this? I'm not sure if this is a problem with the elog / Ubuntu / Image Magick? |
What happens if you execute the command manually, like
$ identify -format '%wx%h %c' '/home/elog/elog-2.9.2/logbooks/HardwareLog/140218_120423_2014-02-18_remod_(extended_II).png.png
The "identify" command just checks the size in pixels of your image and expects something like 800x600. Let me know if this command returns something completely different.
/Stefan |