Back Midas Rome Roody Rootana
  Midas DAQ System  Not logged in ELOG logo
Entry  05 Feb 2026, Konstantin Olchanski, Bug Report, omnibus bugs from running DarkLight 
    Reply  06 Feb 2026, Stefan Ritt, Bug Report, omnibus bugs from running DarkLight Lakeshore-Temperatures_A-20260204-120628-20260205-120628.png
    Reply  06 Feb 2026, Stefan Ritt, Bug Report, omnibus bugs from running DarkLight Screenshot_2026-02-06_at_12.44.16.png
    Reply  06 Feb 2026, Stefan Ritt, Bug Report, omnibus bugs from running DarkLight 
    Reply  06 Feb 2026, Stefan Ritt, Bug Report, omnibus bugs from running DarkLight 
Message ID: 3204     Entry time: 06 Feb 2026     In reply to: 3200
Author: Stefan Ritt 
Topic: Bug Report 
Subject: 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 
> on daq17 with current MIDAS.

Works for me with the current version.


> 6) MIDAS on dl-server-2 is "installed" in such a way that there is no connection to the git repository, no way 
> to tell what git checkout it corresponds to. Help page just says "branch master", git-revision.h is empty. We 
> should discourage such use of MIDAS and promote our "normal way" where for all MIDAS binary programs we know 
> what source code and what git commit was used to build them.

Not sure if you have seen it. I make a "install" script to clone, compile and install midas. Some people use this already. Maybe give it a shot. Might need 
adjustment for different systems, I certainly haven't covered all corner cases. But on a RaspberryPi it's then just one command to install midas, modify 
the environment, install mhttpd as a service and load the ODB defaults. I know that some people want it "their way" and that's ok, but for the novice user 
that might be a good starting point. It's documented here: https://daq00.triumf.ca/MidasWiki/index.php/Install_Script

The install script is plain shell, so should be easy to be understandable. 

> 6a) MIDAS on dl-server-2 had a pretty much non-functional history display, I reported it here, Stefan provided 
> a fix, I manually retrofitted it into dl-server-2 MIDAS and we were able to run the experiment. (good)
> 
> 6b) bug (5) suggests that there is more bugs being introduced and fixed without any notice to other midas 
> users (via this forum or via the bitbucket bug tracker).

If I would notify everybody about a new bug I introduced, I would know that it's a bug and I would not introduce it ;-)

For all the fixes I encourage people to check the commit log. Doing an elog entry for every bug fix would be considered spam by many people because 
that can be many emails per week. The commit log is here: https://bitbucket.org/tmidas/midas/commits/branch/develop

If somebody volunteers to consolidate all commits and make a monthly digest to be posted here, I'm all in favor, but I'm not that individual.

Stefan
ELOG V3.1.4-2e1708b5