| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
2069
|
06 Jan 2021 |
Isaac Labrie Boulay | Info | Recovering a corrupted ODB using odbinit. | Hi all,
I am currently trying to recover my corrupted |
|
|
528
|
20 Nov 2008 |
Jimmy Ngai | Info | Recommended platform for running MIDAS | Dear All,
Is there any recommended platforms for running |
|
|
529
|
20 Nov 2008 |
Stefan Ritt | Info | Recommended platform for running MIDAS | > Dear All,
>
> Is there any recommended platforms for |
|
|
882
|
06 May 2013 |
Konstantin Olchanski | Info | Recent-ish SVN changes at PSI | A little while ago, PSI made some changes
to the SVN hosting. The main SVN URL seems
to remain the
|
|
|
201
|
04 Mar 2005 |
Stefan Ritt | Info | Real-Time 2005 Conference in Stockholm | Dear Midas users,
may I kindly invite you present your work |
|
|
570
|
07 May 2009 |
Konstantin Olchanski | Info | RPC.SHM gyration | When using remote midas clients with mserver,
you may have noticed the zero-size .RPC.SHM
files
|
|
|
586
|
02 Jun 2009 |
Konstantin Olchanski | Info | RPC.SHM gyration | > When using remote midas clients with mserver,
you may have noticed the zero-size .RPC.SHM
files
|
|
|
589
|
04 Jun 2009 |
Stefan Ritt | Info | RPC.SHM gyration | > Right now, MIDAS does not have an abstraction
for "local multi-thread mutex" (i.e. pthread_mutex
& co) and mostly uses global semaphores
|
|
|
673
|
20 Nov 2009 |
Konstantin Olchanski | Info | RPC.SHM gyration | > When using remote midas clients with mserver,
you may have noticed the zero-size .RPC.SHM
files
|
|
|
2414
|
25 Jun 2022 |
Joseph McKenna | Bug Report | RPC timeout for manalyzer over network |
In ALPHA, I get RPC timeouts running a (reasonably |
|
|
2415
|
18 Jul 2022 |
Konstantin Olchanski | Bug Report | RPC timeout for manalyzer over network | > In ALPHA, I get RPC timeouts running a (reasonably
heavy) analyzer on a remote machine (connected
directly via a ~30 meter 10Gbe Ethernet cable) |
|
|
1849
|
06 Mar 2020 |
Lars Martin | Forum | RPC error | I ported a bunch of frontends to C++ and now
I'm occasionally getting this RPC
error message:
|
|
|
1850
|
08 Mar 2020 |
Konstantin Olchanski | Forum | RPC error | I do not see this error, but there was one
more report (they did not clearly say what
http errors
|
|
|
1835
|
18 Feb 2020 |
Lukas Gerritzen | Bug Report | RPC Error: ACK or other control chars from "db_get_values" | Hi,
for some reason we occasionally get JSON
errors in the browser when accessing MIDAS. |
|
|
1836
|
18 Feb 2020 |
Stefan Ritt | Bug Report | RPC Error: ACK or other control chars from "db_get_values" | You are the first one reporting this error,
so it must be due to your values in the ODB.
Can you track it down to specific ODB contents? |
|
|
1837
|
20 Feb 2020 |
Konstantin Olchanski | Bug Report | RPC Error: ACK or other control chars from "db_get_values" | > The unexpected token is \0x6
> RPC Error json parser exception: SyntaxError:
JSON.parse: bad control character in string |
|
|
2398
|
08 May 2022 |
Stefan Ritt | Info | RO_STOPPED with triggered events | We had issues in one of our experiment that
people used RO_STOPPED in the
equipment list together with triggered events |
|
|
Draft
|
08 May 2022 |
Konstantin Olchanski | Info | RO_STOPPED with triggered events | > If events are sent when a run is stopped,
this leads to many unexpected results
|
|
|
2400
|
08 May 2022 |
Konstantin Olchanski | Info | RO_STOPPED with triggered events | > some old front-end are not running any more
since they do use RO_ALWAYS together with
|
|
|
2402
|
16 May 2022 |
Konstantin Olchanski | Info | RO_STOPPED with triggered events | > > some old front-end are not running any
more since they do use RO_ALWAYS together
with
|
|