| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
1657
|
09 Aug 2019 |
Konstantin Olchanski | Bug Report | Fetest History Plot | > Hi, our logger was running.
|
|
|
1658
|
09 Aug 2019 |
Konstantin Olchanski | Bug Report | Fetest History Plot | > Hi, our logger was running.
Please do these simple tests:
|
|
|
1664
|
14 Aug 2019 |
Konstantin Olchanski | Bug Report | ROOTANA bug? | > - ss_suspend_set_dispatch_ipc(NULL);
> + // ss_suspend_set_dispatch_ipc(NULL);
>
|
|
|
1680
|
08 Sep 2019 |
Vinzenz Bildstein | Bug Report | https redirect and ODB access | I'm not sure if these issues are related or
not, but I'm getting an error
message when I want to access the root of |
|
|
1686
|
16 Sep 2019 |
Konstantin Olchanski | Bug Report | https redirect and ODB access | > I'm not sure if these issues are related
or not, but I'm getting an error
> message when I want to access the root |
|
|
1700
|
20 Sep 2019 |
Frederik Wauters | Bug Report | lazylogger in cmake & max_event_size | compiling:
----------
|
|
|
1709
|
27 Sep 2019 |
Konstantin Olchanski | Bug Report | lazylogger in cmake & max_event_size | > The compile option -DHAVE_FTPLIB checked
in mdsupport.cxx disappeared if you
> compile with cmake.
|
|
|
1719
|
06 Oct 2019 |
Nik Berger | Bug Report | History data size mismatch | Logging a list of variables to the history
via links in the history ODB subtree,
we get messages as follows at every run start:
|
|
|
1720
|
06 Oct 2019 |
Stefan Ritt | Bug Report | History data size mismatch | I wonder why do you this via ODB links. The
"standard" way of writing to the history
should be to create events for an equipment |
|
|
1721
|
10 Oct 2019 |
Konstantin Olchanski | Bug Report | History data size mismatch | >
> In our history, a long list of doubles
(64 Bit) fas followed by three floats (32 |
|
|
1722
|
10 Oct 2019 |
Nik Berger | Bug Report | History data size mismatch | >I wonder why do you this via ODB links. The
"standard" way of writing to the history
should be to create events for an equipment |
|
|
1723
|
10 Oct 2019 |
Stefan Ritt | Bug Report | History data size mismatch | > Yes, we could have
> kept that apart, yes, in this case a double
would also work (and not break things), but |
|
|
1724
|
14 Oct 2019 |
Stefan Ritt | Bug Report | lazylogger in cmake & max_event_size | > > The compile option -DHAVE_FTPLIB checked
in mdsupport.cxx disappeared if you
> > compile with cmake.
|
|
|
1730
|
24 Oct 2019 |
Konstantin Olchanski | Bug Report | lazylogger in cmake & max_event_size | > > > The compile option -DHAVE_FTPLIB checked
in mdsupport.cxx disappeared if you
> > > compile with cmake.
|
|
|
1731
|
08 Nov 2019 |
Pierre Gorel | Bug Report | Newly installed MIDAS on OSX: mhttpd crahes | Context: out of the box MIDAS (using cmake)
on OSX Mojave.
|
|
|
1732
|
12 Nov 2019 |
Konstantin Olchanski | Bug Report | Newly installed MIDAS on OSX: mhttpd crahes | > Context: out of the box MIDAS (using cmake)
on OSX Mojave.
>
|
|
|
1734
|
15 Nov 2019 |
Pierre Gorel | Bug Report | Newly installed MIDAS on OSX: mhttpd crahes | It is reproducible alright.
Here are the core dump and the backtrace
(I think the former is more informative).
|
|
|
1736
|
15 Nov 2019 |
Konstantin Olchanski | Bug Report | Newly installed MIDAS on OSX: mhttpd crahes | > It is reproducible alright.
Thanks. At first blush, a guess, read_passwords() |
|
|
1742
|
28 Nov 2019 |
Konstantin Olchanski | Bug Report | midas alarm sound unreliable in google-chrome | I accidentally discovered a problem with the
alarm sounds played by midas.
|
|
|
1743
|
28 Nov 2019 |
Stefan Ritt | Bug Report | midas alarm sound unreliable in google-chrome | The document
https://docs.google.com/document/d/1_278v_plodvgtXSgnEJ0yjZJLg14Ogf-ekAFNymAJoU/edit
|
|