| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
2904
|
26 Nov 2024 |
Nick Hastings | Bug Report | TMFE::Sleep() errors | Hello,
I've noticed that SC FEs that use the TMFE |
|
|
2905
|
26 Nov 2024 |
Maia Henriksson-Ward | Bug Report | TMFE::Sleep() errors | > Hello,
>
> I've noticed that SC FEs that use the TMFE |
|
|
2906
|
27 Nov 2024 |
Konstantin Olchanski | Bug Report | TMFE::Sleep() errors | > [tmfe.cxx:1033:TMFE::Sleep,ERROR] select()
returned -1, errno 22 (Invalid argument).
|
|
|
2907
|
27 Nov 2024 |
Konstantin Olchanski | Bug Report | TMFE::Sleep() errors | >
> I wonder also if now that midas requires
stricter/newer c++ standards if there maybe
|
|
|
2908
|
27 Nov 2024 |
Konstantin Olchanski | Bug Report | TMFE::Sleep() errors | > status = select(1, &fdset, NULL, NULL,
&timeout);
>
|
|
|
2909
|
30 Nov 2024 |
Pavel Murat | Bug Report | EQ_PERIODIC-only equipment ? | Dear Midas experts,
I'm running into something which looks like |
|
|
2910
|
01 Dec 2024 |
Stefan Ritt | Bug Report | EQ_PERIODIC-only equipment ? | There is no requirement that you pair an EQ_PERIODIC
with an EQ_TRIGGER. Take for exmaple
|
|
|
2911
|
01 Dec 2024 |
Pavel Murat | Bug Report | EQ_PERIODIC-only equipment ? | > There is no requirement that you pair an
EQ_PERIODIC with an EQ_TRIGGER. Take for
exmaple
|
|
|
2912
|
02 Dec 2024 |
Stefan Ritt | Bug Report | ODB key picker does not close when creating link / Edit-on-run string box too large | > Actual result:
> The key picker does not close.
|
|
|
2913
|
02 Dec 2024 |
Stefan Ritt | Bug Report | ODB key picker does not close when creating link / Edit-on-run string box too large | > Another more minor visual problem is the
edit-on-start dialog. There seems to be no
upper bound to the
|
|
|
2915
|
04 Dec 2024 |
Konstantin Olchanski | Bug Report | ODB key picker does not close when creating link / Edit-on-run string box too large | > > Actual result:
> > The key picker does not close.
>
|
|
|
2916
|
05 Dec 2024 |
Konstantin Olchanski | Bug Report | ODB key picker does not close when creating link / Edit-on-run string box too large | > > Another more minor visual problem is the
edit-on-start dialog. There seems to be no
upper bound to the
|
|
|
2918
|
06 Dec 2024 |
Konstantin Olchanski | Bug Report | TMFE::Sleep() errors | > > status = select(1, &fdset, NULL,
NULL, &timeout);
> > On error, -1 is returned, ... timeout |
|
|
2919
|
06 Dec 2024 |
Konstantin Olchanski | Bug Report | TMFE::Sleep() errors | > Commit [develop 06735d29] improve TMFE::Sleep()
Report of test_sleep on Ubuntu-22 (Intel |
|
|
2923
|
17 Dec 2024 |
Lukas Gerritzen | Bug Report | [History plots] "Jump to current time" resets x range to 7d | To reproduce:
- Open a history plot, click [-] a few times
until the x axis shows more than 7 days.
|
|
|
2924
|
19 Dec 2024 |
Stefan Ritt | Bug Report | [History plots] "Jump to current time" resets x range to 7d | I had put in a check which limits the range
to 7d into the past if you press the "play"
button, but now I'm not sure why this was |
|
|
2936
|
01 Feb 2025 |
Pavel Murat | Bug Report | MIDAS history system not using the event timestamps ? | > I have a time series of slow control measurements
in an ASCII format -
> data records in a format (run_number, time, |
|
|
2943
|
19 Feb 2025 |
Lukas Gerritzen | Bug Report | Default write cache size for new equipments breaks compatibility with older equipments | We have a frontend for slow control with a
lot of legacy code. I wanted to add a new
equipment using the
|
|
|
2944
|
24 Feb 2025 |
Stefan Ritt | Bug Report | Default write cache size for new equipments breaks compatibility with older equipments | The commit that introduced the write cache
size check is https://bitbucket.org/tmidas/midas/commits/3619ecc6ba1d29d74c16aa6571e40920018184c0
|
|
|
2947
|
11 Mar 2025 |
Federico Rezzonico | Bug Report | python hist_get_events not returning events, but javascript does | After starting midas (mhttpd &, and mlogger
-D) and running the `fetest` frontend I went
into the midas/python/examples directory |
|