feat(efb): troubleshooting page #9747
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Benjozork
requested changes
Jan 14, 2025
| export const TroubleshootingContextProvider: React.FC<TroubleshootingContextProps> = ({ eventBus, children }) => { | ||
| const [errorLog, setErrorLog] = useState([] as string[]); | ||
|
|
||
| eventBus |
There was a problem hiding this comment.
This will leak subscriptions every time it renders.
You should place this in a useEffect (with an empty dependency array) whose cleanup function destroys the subscription.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #[issue_no]
Summary of Changes
Adds a troubleshooting page under the about page in the EFB for advanced user support. The idea here is to log things that have user visible errors that don't provide enough info to determine the cause, e.g. "INTERNAL ERROR" in the FMS. It is not intended to be a general-purpose error log as it would lose it's usefulness when filled with lots of random messages like the debugger.
Hopefully we can figure out the recent spike in these INTERNAL ERRORs.
Needs #9559 merged first (for isMsfs2024 function).
Screenshots (if necessary)
References
Additional context
Discord username (if different from GitHub):
Testing instructions
Go to the about page on the EFB, and then click Troubleshooting.. check that the info displayed is accurate and the layout reasonable. If you know of a repro to cause an INTERNAL ERROR on the A32NX, you could also try it to see the message in the troubleshooting log.
How to download the PR for QA
Every new commit to this PR will cause new A32NX and A380X artifacts to be created, built, and uploaded.