| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
3185
|
12 Dec 2025 |
Konstantin Olchanski | Bug Report | odbxx memory leak with JSON ODB dump | > > Confirmed fixed, thanks! There are 2 small
changes I made in odbxx.h, please pull.
> There was one missing enable_jsroot in |
|
|
3192
|
14 Jan 2026 |
Derek Fujimoto | Bug Report | DEBUG messages not showing and related | I have an application where I want to (optionally)
send my own debugging messages to the midas.log
file, but am having some problems with this: |
|
|
3193
|
14 Jan 2026 |
Stefan Ritt | Bug Report | DEBUG messages not showing and related | MT_DEBUG messages are there for debugging,
not logging. They only go into the SYSMSG
buffer and NOT to the log file. If you want |
|
|
3194
|
14 Jan 2026 |
Derek Fujimoto | Bug Report | DEBUG messages not showing and related | Ok thanks for the quick and clear response!
Derek
|
|
|
3200
|
05 Feb 2026 |
Konstantin Olchanski | Bug Report | omnibus bugs from running DarkLight | We finished running the DarkLight experiment
and I am reporting accumulated bugs that
we have run into.
|
|
|
3201
|
06 Feb 2026 |
Stefan Ritt | Bug Report | omnibus bugs from running DarkLight | Thanks for the detailed report. Let me reply
one-by-one.
|
|
|
3202
|
06 Feb 2026 |
Stefan Ritt | Bug Report | omnibus bugs from running DarkLight | > 3) ODB editor clicking on hex number versus
decimal number no longer allows editing in
hex, Stefan implemented
|
|
|
3203
|
06 Feb 2026 |
Stefan Ritt | Bug Report | omnibus bugs from running DarkLight | > 4) ODB editor "right click" to "delete"
or "rename" key does not work, the right-click
menu disappears
|
|
|
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.
>
|
|