| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
1258
|
10 Apr 2017 |
Andreas Suter | Bug Report | Equipment Expand doesn't work anymore | > > I'd liked very much the possibility to
hide away Equipment on the main page. It
> > is also nice to have the '+' to get it |
|
|
1259
|
13 Apr 2017 |
Andreas Suter | Bug Report | stop form odbedit broken | when I try to stop a run from odbedit I get
a core dump.
|
|
|
1260
|
13 Apr 2017 |
Andreas Suter | Bug Report | stop form odbedit broken | > when I try to stop a run from odbedit I
get a core dump.
>
|
|
|
1264
|
15 Apr 2017 |
Konstantin Olchanski | Bug Report | Equipment Expand doesn't work anymore | > > > I'd liked very much the possibility
to hide away Equipment on the main page.
It
|
|
|
1265
|
15 Apr 2017 |
Konstantin Olchanski | Bug Report | stop form odbedit broken | > > when I try to stop a run from odbedit
I get a core dump.
> >
|
|
|
1268
|
15 Apr 2017 |
Konstantin Olchanski | Bug Report | where to report bugs, stop form odbedit broken | >
> What is the preferred channel to report
potential bugs (elog / bitbucket issues)? |
|
|
1269
|
15 Apr 2017 |
Konstantin Olchanski | Bug Report | badly managed case in history_schema.cxx: dat file empty | > For an unknown reason, Logger died few days
ago while writing the history. The
> file mhf_1489577446_20170315_system.dat |
|
|
1270
|
15 Apr 2017 |
Konstantin Olchanski | Bug Report | stop form odbedit broken | > when I try to stop a run from odbedit I
get a core dump.
> [ODBEdit1,INFO] Run #31 stopped odbedit: |
|
|
1271
|
15 Apr 2017 |
Konstantin Olchanski | Bug Report | MAX_STRING_LENGTH, stop form odbedit broken | >
> I shall check on the use of MAX_STRING_LENGTH
at least in odb itself...
|
|
|
1272
|
15 Apr 2017 |
Konstantin Olchanski | Bug Report | MAX_STRING_LENGTH, stop form odbedit broken | > >
> > I shall check on the use of MAX_STRING_LENGTH
at least in odb itself...
|
|
|
1273
|
18 Apr 2017 |
Andreas Suter | Bug Report | run start/stop oddity | I stumbled over an oddity which I would like
to understand better. Here the
boundaries:
|
|
|
1274
|
19 Apr 2017 |
Stefan Ritt | Bug Report | MAX_STRING_LENGTH, stop form odbedit broken | ODB name lengths (the name of a key) are limited
to 256 characters, the length of strings
in the ODB should NOT be limited. At some |
|
|
1275
|
19 Apr 2017 |
Stefan Ritt | Bug Report | MAX_STRING_LENGTH, stop form odbedit broken | > Fixed a small buglet, now saving and reloading
odb in the old ".odb" format will silently
truncate all overlong strings to 256 bytes. |
|
|
1276
|
22 Apr 2017 |
Konstantin Olchanski | Bug Report | MAX_STRING_LENGTH, stop form odbedit broken | > > Fixed a small buglet, now saving and reloading
odb in the old ".odb" format will silently
truncate all overlong strings to 256 bytes. |
|
|
1277
|
22 Apr 2017 |
Konstantin Olchanski | Bug Report | MAX_STRING_LENGTH, stop form odbedit broken | > ODB name lengths (the name of a key) are
limited to 256 characters, the length of
strings in the ODB should NOT be limited.
|
|
|
1278
|
24 Apr 2017 |
Stefan Ritt | Bug Report | stop form odbedit broken | > CSS File = STRING : [1024] mhttpd.css
> Sqlite dir = STRING : [1024]
> History dir = STRING : [1024]
|
|
|
1285
|
02 May 2017 |
Konstantin Olchanski | Bug Report | mhttpd inline-editor and web MAX_STRING_LENGTH, stop form odbedit broken | > > I shall check on the use of MAX_STRING_LENGTH
at least in odb itself...
|
|
|
1288
|
02 May 2017 |
Konstantin Olchanski | Bug Report | run start/stop oddity |
I should really get around to fix this junk
error message:
|
|
|
1291
|
09 May 2017 |
Andreas Suter | Bug Report | mhttpd / history / export data | A handy feature of the history of the mhttpd
is to export the data. However, this
seems to be broken. It currently only works |
|
|
1292
|
16 May 2017 |
Konstantin Olchanski | Bug Report | mhttpd / history / export data | > A handy feature of the history of the mhttpd
is to export the data. However, this
> seems to be broken. It currently only works |
|