| ID | 
Date | 
Author | 
Topic | 
Subject | 
Text | 
  | 
| 
  2373  
 | 
24 Mar 2022 | 
Konstantin Olchanski | Bug Report | data missing in runXXXXXX.mid | > One idea: we should have a look at mlogger::close_channels().
 
> There the SYSTEM buffer is emptied through 
the cm_yield() call.
 | 
   | 
| 
  2372  
 | 
24 Mar 2022 | 
Stefan Ritt | Bug Report | data missing in runXXXXXX.mid | One idea: we should have a look at mlogger::close_channels(). 
There the SYSTEM buffer is emptied through 
the cm_yield() call. Instrumenting this with | 
   | 
| 
  2371  
 | 
24 Mar 2022 | 
Stefan Ritt | Bug Fix | mhttpd bug fixed | I see, now I understand.
 
 
As for the browser cache problem: This Chrome | 
   | 
| 
  2370  
 | 
24 Mar 2022 | 
Konstantin Olchanski | Bug Report | data missing in runXXXXXX.mid | > > It would be good to pin point there the 
data is lost. This is the sequence:
 
> > 
 | 
   | 
| 
  2369  
 | 
24 Mar 2022 | 
Konstantin Olchanski | Bug Fix | fix for event buffer corruption in bm_flush_cache() | > Thanks for the investigation. Back in 2020, 
we had some issues
 
> of losing data between the system buffer | 
   | 
| 
  2368  
 | 
24 Mar 2022 | 
Konstantin Olchanski | Bug Fix | mhttpd bug fixed | > > 1st wget stops (by ctrl-C), socket is 
closed, mongoose frees it's mg_connection 
object
 | 
   | 
| 
  2367  
 | 
24 Mar 2022 | 
Stefan Ritt | Bug Fix | fix for event buffer corruption in bm_flush_cache() | > > ... instead of struggling with all your 
locks.
 
> 
 | 
   | 
| 
  2366  
 | 
24 Mar 2022 | 
Stefan Ritt | Bug Fix | mhttpd bug fixed | > 1st wget stops (by ctrl-C), socket is closed, 
mongoose frees it's mg_connection object
 
> (corresponding worker is still labouring, | 
   | 
| 
  2365  
 | 
23 Mar 2022 | 
Hunter Lowe | Forum | ODB has issue with example analyzer | Trying to play with midas file but I get error:
 
 
[Analyzer,ERROR] [odb.cxx:845:db_validate_name,ERROR] | 
   | 
| 
  2364  
 | 
23 Mar 2022 | 
Konstantin Olchanski | Bug Fix | mhttpd bug fixed | the mhttpd bug should be fixed now (branch 
feature/buffer_mutex).
 
 | 
   | 
| 
  2363  
 | 
23 Mar 2022 | 
Konstantin Olchanski | Bug Fix | fix for event buffer corruption in bm_flush_cache() | I confirm, there is no problem in single-threaded 
programs, and
 
there is no problem if all bm_send_event() | 
   | 
| 
  2362  
 | 
23 Mar 2022 | 
Konstantin Olchanski | Bug Fix | mhttpd ipv6 bind should be fixed now | > Something changed after my initial implementation 
of ipv6 in mhttpd
 
> and listening to ipv6 http/https connections | 
   | 
| 
  2361  
 | 
23 Mar 2022 | 
Ivo Schulthess | Bug Fix | fix for event buffer corruption in bm_flush_cache() | Thanks for the investigation. Back in 2020, 
we had some issues of losing data between 
the system buffer and the logger writing | 
   | 
| 
  2360  
 | 
22 Mar 2022 | 
Stefan Ritt | Bug Fix | fix for event buffer corruption in bm_flush_cache() | Thanks Konstantin for your detailed description. 
 
 | 
   | 
| 
  2359  
 | 
22 Mar 2022 | 
Konstantin Olchanski | Bug Fix | fix for event buffer corruption in bm_flush_cache() | multithreaded frontends have an unusual event 
buffer corruption if the write 
 
cache is enabled. For a long time now I had | 
   | 
| 
  2358  
 | 
22 Mar 2022 | 
Stefan Ritt | Info | New midas sequencer version | After several days of testing in various experiments, 
the new sequencer has
 
been merged into the develop branch. One | 
   | 
| 
  2357  
 | 
21 Mar 2022 | 
Stefan Ritt | Bug Report | Python ODB watch | What you describe is a well-known problem 
with the ODB. At PSI we have similar issues. 
There are
 | 
   | 
| 
  2356  
 | 
16 Mar 2022 | 
Ben Smith | Bug Report | Python ODB watch | > It seems that the second write operation 
"overlaps" the first one...
 
 | 
   | 
| 
  2355  
 | 
16 Mar 2022 | 
Stefan Ritt | Info | New midas sequencer version | A new version of the midas sequencer has been 
developed and now available in the 
 
develop/seq_eval branch. Many thanks to Lewis | 
   | 
| 
  2354  
 | 
15 Mar 2022 | 
Konstantin Olchanski | Bug Fix | mhttpd ipv6 bind should be fixed now | Something changed after my initial implementation 
of ipv6 in mhttpd
 
and listening to ipv6 http/https connections | 
   |