| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
961
|
18 Feb 2014 |
Konstantin Olchanski | Info | Custom page header implemented | I am not sure what to do with the javascript
snippet - I understand it should be somehow
connected to /Custom/Header, but if I create |
|
|
965
|
19 Feb 2014 |
Stefan Ritt | Info | Custom page header implemented | > I am not sure what to do with the javascript
snippet
|
|
|
1307
|
25 Jul 2017 |
Stefan Ritt | Info | Current git repository "develop" branch broken | Dear all,
we are currently undergoing major modifications |
|
|
9
|
10 Mar 2004 |
Jan Wouters | | Creation of secondary Midas output file. | Dear Midas Team,
I have run into a problem with Midas and |
|
|
10
|
10 Mar 2004 |
Stefan Ritt | | Creation of secondary Midas output file. | Dear Jan,
I had a look at your code. You create a gPhysicsEventHeader |
|
|
11
|
11 Mar 2004 |
Renee Poutissou | | Creation of secondary Midas output file. | Jan ,
Do you need to log this stage 1 output? |
|
|
2845
|
16 Sep 2024 |
Marius Köppel | Bug Report | Crash using ODB watch | Hi all,
last week I was running MIDAS with the commit |
|
|
2846
|
16 Sep 2024 |
Stefan Ritt | Bug Report | Crash using ODB watch | The answer is in the error message: „Object
went out of scope“. When your frontent_init()
exits, the odb objects are destroyed. When |
|
|
2847
|
16 Sep 2024 |
Marius Koeppel | Bug Report | Crash using ODB watch | This is not the case here. Note that the error
message: "Callback received for a midas::odb
object which went out of scope" is not called! |
|
|
2848
|
16 Sep 2024 |
Stefan Ritt | Bug Report | Crash using ODB watch | Well, the object *went* out of scope. For
my code it‘s hard to realize this, so the
error reporting is poor. Also the first object |
|
|
2849
|
16 Sep 2024 |
Marius Koeppel | Bug Report | Crash using ODB watch | Okay, but this is then a big issue IMO. For
Mu3e we do this in every frontend and I also
checked again all of these watches are broken |
|
|
2850
|
16 Sep 2024 |
Mark Grimes | Bug Report | Crash using ODB watch | Hi,
Maybe I've misunderstood the code, but odb::watch()
creates a deep copy of itself to set the |
|
|
2851
|
17 Sep 2024 |
Konstantin Olchanski | Bug Report | Crash using ODB watch | > {
> odb new_settings("/Equipment/Test FE/Settings");
> new_settings.watch(watch); // <-- here |
|
|
2852
|
18 Sep 2024 |
Marius Koeppel | Bug Report | Crash using ODB watch | I created a PR to fix this issue https://bitbucket.org/tmidas/midas/pull-requests/42.
The crash happened since the change in commit
3ad98c5 always got the ODB via XML.
|
|
|
2853
|
20 Sep 2024 |
Stefan Ritt | Bug Report | Crash using ODB watch | The problem has been fixed in the current
version. Here is my analysis:
|
|
|
819
|
04 Jul 2012 |
Konstantin Olchanski | Bug Report | Crash after recursive use of rpc_execute() | I am looking at a MIDAS kaboom when running
out of space on the data disk - everything
was freezing
|
|
|
820
|
04 Jul 2012 |
Konstantin Olchanski | Bug Report | Crash after recursive use of rpc_execute() | > ... I see a recursive call to rpc_execute():
rpc_execute() calls tr_stop() calls cm_yield()
calls
|
|
|
821
|
13 Jul 2012 |
Stefan Ritt | Bug Report | Crash after recursive use of rpc_execute() | > Then I realized that I see a recursive call
to rpc_execute(): rpc_execute() calls tr_stop()
calls cm_yield() calls
|
|
|
618
|
18 Aug 2009 |
Denis Calvet | Suggestion | Could not create strings other than 32 characters with odbedit -c "..." command | Hi,
I am writing shell scripts to create some
tree structure in an ODB. When
|
|
|
627
|
03 Sep 2009 |
Stefan Ritt | Suggestion | Could not create strings other than 32 characters with odbedit -c "..." command | > Hi,
> I am writing shell scripts to create some
tree structure in an ODB. When
|
|