| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
1699
|
18 Sep 2019 |
Nick Hastings | Forum | History plot problems for frontend with multiple indicies | Hi Konstantin,
> > [local:e666:S]History>ls -l /History/Events
|
|
|
1710
|
27 Sep 2019 |
Konstantin Olchanski | Forum | History plot problems for frontend with multiple indicies | We should fix this for midas-2019-10.
https://bitbucket.org/tmidas/midas/issues/193/confusion-in-history-event-ids
|
|
|
1986
|
24 Aug 2020 |
Konstantin Olchanski | Forum | History plot problems for frontend with multiple indicies | This turned out to be a tricky problem. I
am adding a warning about it in mlogger.
This should go into midas-
|
|
|
2015
|
19 Nov 2020 |
Joseph McKenna | Forum | History plot consuming too much memory |
A user reported an issue that if they were |
|
|
2016
|
19 Nov 2020 |
Stefan Ritt | Forum | History plot consuming too much memory | The history code is right now programmes in
such a way that when you request
an old time window, then all data from that |
|
|
2017
|
20 Nov 2020 |
Joseph McKenna | Forum | History plot consuming too much memory | Poking at the behavior of this, its fairly
clear the slow response is from the data
|
|
|
2018
|
20 Nov 2020 |
Stefan Ritt | Forum | History plot consuming too much memory | > Taking this down a tangent, I have a mild
concern that a user could temporarily
> flood our gigabit network if we do have |
|
|
2028
|
27 Nov 2020 |
Konstantin Olchanski | Forum | History plot consuming too much memory | >
> Tested with midas-2020-08-a up until the
HEAD of develop
|
|
|
2029
|
27 Nov 2020 |
Konstantin Olchanski | Forum | History plot consuming too much memory | >
> With the current code, we are limited to
loading history data up to 50% of
|
|
|
2030
|
27 Nov 2020 |
Konstantin Olchanski | Forum | History plot consuming too much memory | >
> Are you sure that the delay comes from
the browser or actually from mhttpd
|
|
|
2031
|
27 Nov 2020 |
Konstantin Olchanski | Forum | History plot consuming too much memory | >
> Taking this down a tangent, I have a mild
concern that a user could temporarily
|
|
|
1445
|
07 Feb 2019 |
Stefan Ritt | Info | History panels in custom pages | A new tag has been implemented to display
history panels in custom pages, integrated
in the
|
|
|
1446
|
08 Feb 2019 |
Thomas Lindner | Info | History panels in custom pages | > A new tag has been implemented to display
history panels in custom pages, integrated
in the
|
|
|
1682
|
12 Sep 2019 |
Pintaudi Giorgio | Info | History panels in custom pages | > > A new tag has been implemented to display
history panels in custom pages, integrated
in the
|
|
|
1683
|
12 Sep 2019 |
Stefan Ritt | Info | History panels in custom pages | Indeed there was a bug in some JavaScript
code, which I fixed here: https://bitbucket.org/tmidas/midas/commits/d2b1a783240e252820c622001e15c09c5d7798c0
|
|
|
1684
|
13 Sep 2019 |
Pintaudi Giorgio | Info | History panels in custom pages | Dear Stefan,
thank you very much for the prompt reply.
Your suggestions worked wonderfully. Now |
|
|
2166
|
12 May 2021 |
Pierre Gorel | Bug Report | History formula not correctly managed | OS: OSX 10.14.6 Mojave
MIDAS: Downloaded from repo on April 2021.
|
|
|
2201
|
02 Jun 2021 |
Konstantin Olchanski | Bug Report | History formula not correctly managed | > OS: OSX 10.14.6 Mojave
> MIDAS: Downloaded from repo on April 2021.
>
|
|
|
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 |
|