Back Midas Rome Roody Rootana
  Midas DAQ System, Page 52 of 150  Not logged in ELOG logo
New entries since:Wed Dec 31 16:00:00 1969
ID Date Author Topic Subjectdown Text Attachments
  389   11 Jun 2007 Stefan RittForumcrash when analyzing multiple runs offline> I have hunted down "my" segfault problem
to the fact that I book histograms not 
> in <module>_init, but in <module>_bor.
  
  390   12 Jun 2007 Randolf PohlForumcrash when analyzing multiple runs offlineHi

> So I guess your solution is not a real
  
  702   12 Jun 2010 hai quForumcrash on start runDear experts,

I use fedora 12 and midas 4680. there is
  
  703   14 Jun 2010 Stefan RittForumcrash 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 quForumcrash on start run> - does your feTCPPacketReceiver die during
the start-of-run? Maybe you do some segfault
  
  2934   30 Jan 2025 Pavel MuratForumconverting 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 MuratForumconverting 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 RobertsBug Reportcontrol characters not sanitized by json_write - can cause JSON.parse of mhttpd result to failI've recently run into issues when using JSON.parse
on ODB keys containing 
8-bit data.
  
  1204   30 Sep 2016 Konstantin OlchanskiBug Reportcontrol 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 LindnerBug Reportcontrol 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 LindnerBug Reportcontrol 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.
 odb_modifications.txt 
  1227   15 Jan 2017 Thomas LindnerBug Reportcontrol 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 LindnerBug Reportcontrol 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 RittBug Reportcontrol 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 OlchanskiBug Reportcontrol 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   01 Feb 2017 Stefan RittBug Reportcontrol 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 PiacentiniInfoconnection to a MySQL server: retry procedure in the LoggerDear all,

we are experiencing a connection problem
  
  2459   22 Feb 2023 Stefan RittInfoconnection to a MySQL server: retry procedure in the Logger> Dear all,

> we are experiencing a connection problem
  
  2464   07 Mar 2023 Stefano PiacentiniInfoconnection to a MySQL server: retry procedure in the Logger> > Dear all,
> > 
> > we are experiencing a connection problem
  
  1071   15 Jul 2015 Konstantin OlchanskiBug Fixcompiler warnings cleaned upLatest C/C++ compilers (MacOS 10.10, GCC on
RHEL7 and Ubuntu) generate a large number
of new 
  
ELOG V3.1.4-2e1708b5