Sim docs #113
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,3 @@ | ||
| This folder contains extra assets for the odometry, 3D field, and joystick views. For more details, see the "Custom Fields/Robots/Joysticks" page in the AdvantageScope documentation (available through the documentation tab in the app or the URL below). | ||
|
|
||
| https://docs.advantagescope.org/more-features/custom-assets |
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,57 @@ | ||
| { | ||
| "name": "3847 - FM", | ||
| "isFTC": false, | ||
| "disableSimplification": false, | ||
| "rotations": [ | ||
| { | ||
| "axis": "x", | ||
| "degrees": 90 | ||
| }, | ||
| { | ||
| "axis": "z", | ||
| "degrees": 90 | ||
| } | ||
| ], | ||
| "position": [ | ||
| 0, | ||
| 0, | ||
| 0 | ||
| ], | ||
| "cameras": [], | ||
| "components": [ | ||
| { | ||
| "zeroedRotations": [ | ||
| { | ||
| "axis": "x", | ||
| "degrees": 90 | ||
| }, | ||
| { | ||
| "axis": "z", | ||
| "degrees": 90 | ||
| } | ||
| ], | ||
| "zeroedPosition": [ | ||
| 0, | ||
| 0, | ||
| 0 | ||
| ] | ||
| }, | ||
| { | ||
| "zeroedRotations": [ | ||
| { | ||
| "axis": "x", | ||
| "degrees": 90 | ||
| }, | ||
| { | ||
| "axis": "z", | ||
| "degrees": 90 | ||
| } | ||
| ], | ||
| "zeroedPosition": [ | ||
| 0, | ||
| 0, | ||
| 0 | ||
| ] | ||
| } | ||
| ] | ||
| } |
Binary file not shown.
Binary file not shown.
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,54 @@ | ||
| { | ||
| "name": "3847 - PM", | ||
| "isFTC": false, | ||
| "disableSimplification": false, | ||
| "rotations": [{ | ||
| "axis": "x", | ||
| "degrees": 90 | ||
| }, { | ||
| "axis": "z", | ||
| "degrees": 90 | ||
| }], | ||
| "position": [ | ||
| 0, | ||
| 0, | ||
| 0 | ||
| ], | ||
| "cameras": [], | ||
| "components": [ | ||
| { | ||
| "zeroedRotations": [ | ||
| { | ||
| "axis": "x", | ||
| "degrees": 90 | ||
| }, | ||
| { | ||
| "axis": "z", | ||
| "degrees": 90 | ||
| } | ||
| ], | ||
| "zeroedPosition": [ | ||
| 0, | ||
| 0, | ||
| 0 | ||
| ] | ||
| }, | ||
| { | ||
| "zeroedRotations": [ | ||
| { | ||
| "axis": "x", | ||
| "degrees": 90 | ||
| }, | ||
| { | ||
| "axis": "z", | ||
| "degrees": 90 | ||
| } | ||
| ], | ||
| "zeroedPosition": [ | ||
| 0, | ||
| 0, | ||
| 0 | ||
| ] | ||
| } | ||
| ] | ||
| } |
Binary file not shown.
Binary file not shown.
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
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.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: Spectrum3847/2026-Spectrum
Length of output: 250
🏁 Script executed:
Repository: Spectrum3847/2026-Spectrum
Length of output: 1257
🌐 Web query:
Java debug settings onBuildFailureProceed last successful artifact after build failure documentation💡 Result:
The setting
java.debug.settings.onBuildFailureProceedis a configuration option specifically for the Visual Studio Code Debugger for Java extension [1][2]. It is unrelated to retrieving artifacts after a build failure [3]. ### Understanding java.debug.settings.onBuildFailureProceed This setting controls whether the VS Code Java debugger automatically continues and launches the program even if the workspace build (compilation) fails [1]. * When set totrue: The debugger suppresses the "Build failed, do you want to continue?" prompt and proceeds with the launch using the previously compiled (and potentially outdated) classes [1][3]. * When set tofalse(default): The debugger displays a warning prompt when a build failure occurs, allowing the user to choose whether to continue, always continue (which updates the setting totrue), or fix the errors [1][4][3]. This setting does not manage or retrieve build artifacts; it solely dictates the debugger's behavior in the presence of compiler errors within the IDE [3]. ### Managing Artifacts After Build Failures If you are looking to retrieve artifacts from a "last successful build" after a failure, this functionality is typically found in CI/CD platforms rather than local Java debugger settings [5][6][7]. * Jenkins: The Copy Artifact plugin allows you to select artifacts from the "Last successful build" of a project [6]. Pipeline scripts can use selectors likelastSuccessful()to target these builds [8][9]. * TeamCity: Artifact dependencies can be configured to import artifacts from the "Latest successful build" specifically [7]. If you are encountering build failures in a local VS Code environment, thejava.debug.settings.onBuildFailureProceedsetting will not help you access a previous successful build; it will only force the debugger to run the current, broken state of your code [3]. If you need a stable version, you should revert your source code to the last known good commit using your version control system (e.g., Git) [1][4].Citations:
Do not proceed after a failed build
java.debug.settings.onBuildFailureProceedshould befalsehere; when enabled, the debugger skips the build-failed prompt and can launch with stale classes, which makes validation results misleading.Suggested setting
📝 Committable suggestion
🤖 Prompt for AI Agents