Replies: 2 comments
-
Interesting idea. Originally created by @sebastian-brunner ([email protected]) at 2018-03-20 08:25:43+00:00 (moved from RMC internal repository) |
Beta Was this translation helpful? Give feedback.
0 replies
-
So I add the execution log to the baked session issue, too. It would be easy to send state machines and logs for examination to another user. Originally created by @Rbelder at 2018-08-16 13:35:17+00:00 (moved from RMC internal repository) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
After debugging a bug which was found in a complex setup of library states and RAFCON configuration parameters I would like to discuss an implementation that extends the baked state machine feature to a baked session feature. Kind of goal is that an user has a problem and reproduce it and bake the session as it is and sent it to the developer which can open the baked session. Sometimes this ends in the failure which the user was reproducing and sometimes this will not work out but this baked session still has all information we need to figure out the particular problem in 99% of failure/bug.
The extension would fully or party target the following elements:
storing of notifications on higher level with a debug flag which is used to track down higher problems e.g. state machine manager or execution engine and which can not be seen in logger messages (this would be a string format of readable gtkmvc notifications)This is an enhancement and discussion issue. Feel welcome to add ideas and notes.
Originally created by @Rbelder at 2018-03-19 15:35:26+00:00 (moved from RMC internal repository)
Beta Was this translation helpful? Give feedback.
All reactions