-
Notifications
You must be signed in to change notification settings - Fork 207
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Task ID Not Valid in CFE_ES_DeleteApp #374
Comments
Is it possible to get a stack trace when the error occurs? Or can you compile your same mission config on Linux via e.g. SIMULATION=native and reproduce the error, where it is possible to get a stack trace? Of note here, is that that However, I do see that the Basically, the line: I will push a fix for the above, but I'd still like to explain why you saw this in relation to |
Fix 2 areas where the CFE_ES_GetTaskInfo() function could have been passed an App ID rather than a task ID, which would create an incorrect result.
Looks like the commit fixed the events in the delete app, is more information still needed? |
Nope, its all fixed. I was able to reproduce it locally. This should be good to go. |
Could you submit a pull request? Whoops, nevermind. |
Fix 2 areas where the CFE_ES_GetTaskInfo() function could have been passed an App ID rather than a task ID, which would create an incorrect result.
Fix 2 areas where the CFE_ES_GetTaskInfo() function could have been passed an App ID rather than a task ID, which would create an incorrect result.
Describe the bug
When deleting an app the Task ID Not Valid message was observed:
The app was still deleted.
To Reproduce
Steps to reproduce the behavior:
(I haven't had a chance to verify myself)
Expected behavior
AppID = 8, TaskID seem to start in the 655xx range. I'd expect the code to use the right values in the right calls.
Code snips
Needs investigation
System observed on:
Additional context
Seen during build verification testing.
Reporter Info
Jacob Hageman - NASA/GSFC
Found by Walt M.
The text was updated successfully, but these errors were encountered: