ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
1747
|
04 Dec 2019 |
Konstantin Olchanski | Release | midas-2019-09-e | > I created the release branch for midas-2019-09
and tag midas-2019-09-a.
> Since the previous release midas-2019-06, |
|
|
1746
|
03 Dec 2019 |
Joseph McKenna | Info | mfe.c: MIDAS frontend's 'Equipment name' can embed hostname, determined at run-time | A little advertised feature of the modifications
needed support the msysmon program is
that MIDAS equipment names can support the |
|
|
1745
|
28 Nov 2019 |
Konstantin Olchanski | Bug Fix | improvement for midas web page resource use (alarm sound and fit_message) | > > > I noticed that midas web pages consume
unexpectedly large amount of resources, as
observed by the chrome browser
|
|
|
1744
|
28 Nov 2019 |
Konstantin Olchanski | Bug Fix | improvement for midas web page resource use (alarm sound and fit_message) | > > I noticed that midas web pages consume
unexpectedly large amount of resources, as
observed by the chrome browser
|
|
|
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
|
|
|
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.
|
|
|
1741
|
18 Nov 2019 |
Konstantin Olchanski | Suggestion | javascript comunication | > > Hi, Stefan - I did not look at your code,
if all midas tabs are inactive, will the
alarm sound still play?
|
|
|
1740
|
18 Nov 2019 |
Stefan Ritt | Suggestion | javascript comunication | > a) google chrome slows down the execution
of javascript in inactive tabs, leading to
trouble
|
|
|
1739
|
18 Nov 2019 |
Stefan Ritt | Suggestion | javascript comunication | > Hi, Stefan - I did not look at your code,
if all midas tabs are inactive, will the
alarm sound still play?
|
|
|
1738
|
17 Nov 2019 |
Konstantin Olchanski | Suggestion | javascript comunication | > Very good idea. And thanks for finding the
document.hidden solution. I put it in, so
give it a try.
|
|
|
1737
|
17 Nov 2019 |
Konstantin Olchanski | Suggestion | javascript comunication | > I am currently testing the new history system
on the mhttpd side and stumbled over the
following issue:
|
|
|
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() |
|
|
1735
|
15 Nov 2019 |
Stefan Ritt | Suggestion | javascript comunication | Very good idea. And thanks for finding the
document.hidden solution. I put it in, so
give it a try.
|
|
|
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).
|
|
|
1733
|
15 Nov 2019 |
Andreas Suter | Suggestion | javascript comunication | I am currently testing the new history system
on the mhttpd side and stumbled over the
following issue: typically our user open |
|
|
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.
>
|
|
|
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.
|
|
|
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.
|
|
|
1729
|
23 Oct 2019 |
Konstantin Olchanski | Forum | Data for key truncated | > I keep on getting messages like this:
> 16:25:35 [fecaen,ERROR] [odb.c:4567:db_get_data,ERROR]
data for key
|
|
|
1728
|
21 Oct 2019 |
Vinzenz Bildstein | Forum | Data for key truncated | I keep on getting messages like this:
16:25:35 [fecaen,ERROR] [odb.c:4567:db_get_data,ERROR] |
|