-
Notifications
You must be signed in to change notification settings - Fork 283
Update RLIs for 2027 alpha 1 #3055
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
Conversation
/inspector fix all |
\inspector fix all |
\inspector check all |
Inspector ReportUp To Date
Outdated - Automatically Fixed
Invalid - Manual Intervention Needed |
\inspector check all |
\inspector check all |
\inspector check all |
\inspector check all |
\inspector fix all |
\inspector check all |
\inspector check all |
\inspector fix all |
\inspector check all |
@@ -100,7 +100,7 @@ To begin, ensure you are on the :guilabel:`Monitor` tab and click :guilabel:`Hea | |||
:alt: Location of heap dump button in VisualVM | |||
:width: 700 | |||
|
|||
This heap dump will be stored on the target system (roboRIO) and must be retrieved using SFTP. See :doc:`this article </docs/software/roborio-info/roborio-ftp>` for information on retrieving the dump from the roboRIO. | |||
This heap dump will be stored on the target system (SystemCore) and must be retrieved using SFTP. See :doc:`this article </docs/software/roborio-info/roborio-ftp>` for information on retrieving the dump from the SystemCore. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Assuming these changes are correct, are they in scope of this PR?
Given that these pages are in a directory named after the RIO, perhaps a separate PR should be done to update both content and directory structure?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, the ftp document is going to need a bigger update, but that should be done separately. The visualvm article should be fine with these minor changes.
No description provided.