| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
702
|
12 Jun 2010 |
hai qu | Forum | crash on start run | Dear experts,
I use fedora 12 and midas 4680. there is |
|
|
703
|
14 Jun 2010 |
Stefan Ritt | Forum | crash on start run | > I use fedora 12 and midas 4680. there is
problem to start run when the frontend
> application runs fine.
|
|
|
704
|
14 Jun 2010 |
hai qu | Forum | crash on start run | > - does your feTCPPacketReceiver die during
the start-of-run? Maybe you do some segfault
|
|
|
3131
|
21 Nov 2025 |
Konstantin Olchanski | Info | cppcheck | > (rules for running cppcheck have gone missing,
I hope I find them).
|
|
|
2934
|
30 Jan 2025 |
Pavel Murat | Forum | converting non-MIDAS slow control data into MIDAS history format ? | Dear MIDAS experts,
I have a time series of slow control measurements |
|
|
2935
|
31 Jan 2025 |
Pavel Murat | Forum | converting non-MIDAS slow control data into MIDAS history format ? | I think I found an answer to my question:
a user-controlled event header does have
a time stamp:
|
|
|
1196
|
08 Sep 2016 |
Amy Roberts | Bug Report | control characters not sanitized by json_write - can cause JSON.parse of mhttpd result to fail | I've recently run into issues when using JSON.parse
on ODB keys containing
8-bit data.
|
|
|
1204
|
30 Sep 2016 |
Konstantin Olchanski | Bug Report | control characters not sanitized by json_write - can cause JSON.parse of mhttpd result to fail | > I've recently run into issues when using
JSON.parse on ODB keys containing
> 8-bit data.
|
|
|
1217
|
25 Oct 2016 |
Thomas Lindner | Bug Report | control characters not sanitized by json_write - can cause JSON.parse of mhttpd result to fail | > > I've recently run into issues when using
JSON.parse on ODB keys containing
> > 8-bit data.
|
|
|
1223
|
01 Dec 2016 |
Thomas Lindner | Bug Report | control characters not sanitized by json_write - can cause JSON.parse of mhttpd result to fail | > > I've recently run into issues when using
JSON.parse on ODB keys containing
> > 8-bit data.
|
|
|
1227
|
15 Jan 2017 |
Thomas Lindner | Bug Report | control characters not sanitized by json_write - can cause JSON.parse of mhttpd result to fail | > > In other words, non-UTF-8 strings are
following non-IEEE-754 floating point values
into oblivion - as
|
|
|
1228
|
23 Jan 2017 |
Thomas Lindner | Bug Report | control characters not sanitized by json_write - can cause JSON.parse of mhttpd result to fail |
> At Konstantin's suggestion, I committed
the function I found for checking if a string |
|
|
1229
|
30 Jan 2017 |
Stefan Ritt | Bug Report | control characters not sanitized by json_write - can cause JSON.parse of mhttpd result to fail | >
> > At Konstantin's suggestion, I committed
the function I found for checking if a string |
|
|
1230
|
01 Feb 2017 |
Konstantin Olchanski | Bug Report | control characters not sanitized by json_write - can cause JSON.parse of mhttpd result to fail | >
> I see you put some switches into the environment
("MIDAS_INVALID_STRING_IS_OK"). Do you think |
|
|
1235
|
02 Feb 2017 |
Stefan Ritt | Bug Report | control characters not sanitized by json_write - can cause JSON.parse of mhttpd result to fail | > Some additional explanation.
>
> Time passed, the world turned, and the |
|
|
2458
|
22 Feb 2023 |
Stefano Piacentini | Info | connection to a MySQL server: retry procedure in the Logger | Dear all,
we are experiencing a connection problem |
|
|
2459
|
22 Feb 2023 |
Stefan Ritt | Info | connection to a MySQL server: retry procedure in the Logger | > Dear all,
>
> we are experiencing a connection problem |
|
|
2464
|
07 Mar 2023 |
Stefano Piacentini | Info | connection to a MySQL server: retry procedure in the Logger | > > Dear all,
> >
> > we are experiencing a connection problem |
|
|
1071
|
15 Jul 2015 |
Konstantin Olchanski | Bug Fix | compiler warnings cleaned up | Latest C/C++ compilers (MacOS 10.10, GCC on
RHEL7 and Ubuntu) generate a large number
of new
|
|
|
360
|
06 Mar 2007 |
Konstantin Olchanski | Info | commited mhttpd fixes & improvements | I commited the mhttpd fixes and improvements
to the history code accumulated while running
the ALPHA
|
|