Description
Deleting an auto in the GUI does not remove it from ".../deploy/pathplanner/autos" directory. If the auto is invalid (ex. illegal subsystem use), it will continue to be included in the SendableChooser from AutoBuilder.buildAutoChooser(), resulting in an Exception and the failure of the construction of the chooser. This does not align with the expected result of deleting a problematic file eliminating the problem.
To Reproduce
- Create an illegal auto (easiest way is to use two of the same NamedCommand blocks in a parallel group)
- Deploy the code
- Delete the auto
- Re-deploy the code
- Robot code fails to start
Expected behavior
Deleting an auto should remove it from the ".../deploy/pathplanner/autos" directory, preventing it from being loaded into a chooser
Versions:
- OS: Windows 11
- GUI Version: v2026.1.2
- PPLib Version: 2026.1.2
- PPLib Language: Java
Additional Information
The issue can be resolved by using FileZilla or SSH to delete the problematic files, but this may not be intuitive to new teams.
The issue also applies to .path files, but they are unlikely to prevent startup.
Teams are likely to encounter this issue if they develop a new auto during a competition. If it causes an Exception, either canceling the Chooser or crashing the code depending on whether or not the Exception was caught, they may elect to delete the file rather than search for the problem in order to save time. Deleting the auto will not fix the problem; it only make s it more difficult to resolve, and teams may miss a match before finding a solution.
Recommended Solution
The GUI should add an "autolist.txt" (or similar) file to ".../deploy/pathplanner/autos" to track which autos still exist. AutoBuilder should delete.auto files not listed in autolist.txt from the RIO during initialization.
Description
Deleting an auto in the GUI does not remove it from ".../deploy/pathplanner/autos" directory. If the auto is invalid (ex. illegal subsystem use), it will continue to be included in the SendableChooser from AutoBuilder.buildAutoChooser(), resulting in an Exception and the failure of the construction of the chooser. This does not align with the expected result of deleting a problematic file eliminating the problem.
To Reproduce
Expected behavior
Deleting an auto should remove it from the ".../deploy/pathplanner/autos" directory, preventing it from being loaded into a chooser
Versions:
Additional Information
The issue can be resolved by using FileZilla or SSH to delete the problematic files, but this may not be intuitive to new teams.
The issue also applies to .path files, but they are unlikely to prevent startup.
Teams are likely to encounter this issue if they develop a new auto during a competition. If it causes an Exception, either canceling the Chooser or crashing the code depending on whether or not the Exception was caught, they may elect to delete the file rather than search for the problem in order to save time. Deleting the auto will not fix the problem; it only make s it more difficult to resolve, and teams may miss a match before finding a solution.
Recommended Solution
The GUI should add an "autolist.txt" (or similar) file to ".../deploy/pathplanner/autos" to track which autos still exist. AutoBuilder should delete.auto files not listed in autolist.txt from the RIO during initialization.