| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
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...
|
|
|
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.
|
|
|
1280
|
26 Apr 2017 |
Konstantin Olchanski | Info | added db_get_value_string() | Since we have been regularly running into
problems with db_get_xxx(TID_STRING) and
string buffers of mismatched size,
|
|
|
1284
|
02 May 2017 |
Konstantin Olchanski | Info | added db_resize_string() | > Since we have been regularly running into
problems with db_get_xxx(TID_STRING) and
string buffers of mismatched size,
|
|
|
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...
|
|
|
1286
|
02 May 2017 |
Konstantin Olchanski | Info | mhttpd inline-editor change | I changed the mhttpd odb inline editor to
use the json-rpc interface. Good things:
|
|
|
1287
|
02 May 2017 |
Konstantin Olchanski | Forum | Problem with logger at run start | > Wed Apr 26 23:03:12 2017 [mhttpd,ERROR]
[midas.c:9106:rpc_client_connect,ERROR] cannot
connect to host "scar
|
|
|
1288
|
02 May 2017 |
Konstantin Olchanski | Bug Report | run start/stop oddity |
I should really get around to fix this junk
error message:
|
|
|
1289
|
02 May 2017 |
Konstantin Olchanski | Info | added db_get_value_string() | > Just some thought for discussion:
Even more thoughts:
|
|
|
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 |
|
|
1293
|
16 May 2017 |
Konstantin Olchanski | Bug Report | problem with odb strings and db_get_record() | Suddenly the mhttpd odb inline editor is truncating
the odb string entries to the actual length
of the
|
|
|
1294
|
31 May 2017 |
Konstantin Olchanski | Info | modified db_watch() arguments | for reasons unknown, db_watch() did not have
an "info" parameter passed through to the
callback
|
|
|
1295
|
31 May 2017 |
Konstantin Olchanski | Bug Report | problem with odb strings and db_get_record() | > What a mess.
The mess with db_get_record() and db_open_record() |
|
|
1296
|
31 May 2017 |
Konstantin Olchanski | Bug Report | problem with odb strings and db_get_record() | > 2) replace all uses of db_open_record(MODE_READ)
with db_watch() in conjunction with db_get_record1().
|
|
|
1298
|
06 Jun 2017 |
Konstantin Olchanski | Bug Report | problem with odb strings and db_get_record() | > Done to all in-tree programs, except for
mana.c (not using it), sequencer.cxx (cannot
test it) and a few places where watching |
|