| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
3204
|
06 Feb 2026 |
Stefan Ritt | Bug Report | omnibus bugs from running DarkLight | > 5) ODB editor "create link" link target
name is limited to 32 bytes, links cannot
be created (dl-server-2), ok
|
|
|
3205
|
12 Feb 2026 |
Stefan Ritt | Bug Report | omnibus bugs from running DarkLight | Now I had a similar case that the browser
froze when showing 24h of data. Tuned out
that 80k points are a bit much. I changed |
|
|
3210
|
23 Apr 2026 |
Pavel Murat | Bug Report | increasing the max number of hot links in ODB | Dear MIDAS experts,
when I attempted to increase the max number |
|
|
Draft
|
23 Apr 2026 |
Nick Hastings | Bug Report | increasing the max number of hot links in ODB | > Dear MIDAS experts,
>
> when I attempted to increase the max number |
|
|
3212
|
24 Apr 2026 |
Konstantin Olchanski | Bug Report | increasing the max number of hot links in ODB | > when I attempted to increase the max number
of hotlinks in ODB , defined as
> #define MAX_OPEN_RECORDS 256 |
|
|
3213
|
25 Apr 2026 |
Pavel Murat | Bug Report | increasing the max number of hot links in ODB | I see - thank you for the explanation!
Indeed, updating MIDAS clients on each and |
|
|
3214
|
26 Apr 2026 |
Stefan Ritt | Bug Report | increasing the max number of hot links in ODB | I wonder why one needs more than 256 hotlinks
at all. Please note that with the odbxx "watch"
API, you can hotline a whole subdirectory, |
|
|
3215
|
27 Apr 2026 |
Konstantin Olchanski | Bug Report | increasing the max number of hot links in ODB | > Indeed, updating MIDAS clients on each and
every RPI etc in a running experiment may
be a real challenge.
|
|
|
3216
|
27 Apr 2026 |
Konstantin Olchanski | Bug Report | increasing the max number of hot links in ODB | > I wonder why one needs more than 256 hotlinks
at all.
|
|
|
3217
|
27 Apr 2026 |
Nick Hastings | Bug Report | increasing the max number of hot links in ODB | For the record, the ND280 (T2K near detector)
MIDAS GSC was initially set up
with MAX_OPEN_RECORDS = 2560 and MAX_CLIENTS |
|
|
3218
|
27 Apr 2026 |
Pavel Murat | Bug Report | increasing the max number of hot links in ODB | > I wonder why one needs more than 256 hotlinks
at all. Please note that with the odbxx "watch"
API, you can hotline a whole subdirectory, |
|
|
3219
|
27 Apr 2026 |
Pavel Murat | Bug Report | increasing the max number of hot links in ODB | > > I wonder why one needs more than 256 hotlinks
at all.
>
|
|
|
3220
|
27 Apr 2026 |
Pavel Murat | Bug Report | increasing the max number of hot links in ODB | > > Indeed, updating MIDAS clients on each
and every RPI etc in a running experiment
may be a real challenge.
|
|
|
170
|
22 Oct 2004 |
Konstantin Olchanski | Bug Fix | mhttpd message colouring | I commited a fix to mhttpd logic that decides
which messages should be shown in
"red" colour- before, any message with square |
|
|
174
|
09 Nov 2004 |
Pierre-Andre Amaudruz | Bug Fix | New transition scheme | Problem:
If cm_set_transition_sequence() is used for
changing the sequence number, the
|
|
|
200
|
25 Feb 2005 |
Konstantin Olchanski | Bug Fix | fixed: double free in FORMAT_MIDAS ybos.c causing lazylogger crashes | We stumbled upon and fixed a "double free"
bug in src/ybos.c causing crashes in
lazylogger writing .mid files in the FORMAT_MIDAS |
|
|
211
|
05 May 2005 |
Konstantin Olchanski | Bug Fix | fix: minor bit rot in the example experiment | I fixed some minor bit rot in the example
experiment: a few minor Makefile
problems, make the analyzer use the current |
|
|
212
|
02 Aug 2005 |
Konstantin Olchanski | Bug Fix | fix odb corruption when running analzer for the first time | I have been plagued by ODB corruption when
I run the analyzer for the first time
after setting up the new experiment. Some |
|
|
216
|
18 Aug 2005 |
Konstantin Olchanski | Bug Fix | fix race condition between clients on run start/stop, pause/resume | It turns out that the new priority sequencing
of run state transitions had a
flaw: the frontends, the analyzer and the |
|
|
219
|
01 Sep 2005 |
Stefan Ritt | Bug Fix | fix race condition between clients on run start/stop, pause/resume | > It turns out that the new priority sequencing
of run state transitions had a
> flaw: the frontends, the analyzer and the |
|