Attempting to deploy code with full storage deletes current robot program
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- java
- Domain
- devops, infrastructure
Research direction
Trace the deployment flow and its SFTP failure handling, then identify where the current robot program is deleted and where SystemCore storage availability can be checked. Done means a full-storage deployment preserves the existing program and reports a specific out-of-storage error instead of a generic SFTP failure.
Written by the indexing model from the issue text.
Description
When attempting to deploy code when the internal storage of SystemCore is full, the deployment process will delete the current code, then fail to deploy with a generic SFTP failure error message. This leaves the robot with no code, and no clear indication of why deployment is failing.
This process can be improved by determining if SystemCore has enough available storage space before deleting the current robot program, then printing a more specific "out of storage space" error instead of a generic SFTP error.
- Dominant language
- Java
- Stars
- 190
- Forks
- 25
- Avg merge
- 6h 20m
- Merged PRs (30d)
- 12
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from wpilibsuite/SystemcoreTesting
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
wpilibsuite/SystemcoreTesting#380 ·
Maintainers usually reply within 1 day
-
Limelight Pending
Difficulty 1/5 Under an hour Newbie friendliness 78/100
wpilibsuite/SystemcoreTesting#315 ·
Maintainers usually reply within 1 day
-
CAN FD not workingOpen
Difficulty 4/5 3-5 days Newbie friendliness 35/100
wpilibsuite/SystemcoreTesting#412 · 14 comments ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
wpilibsuite/SystemcoreTesting#411 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
wpilibsuite/SystemcoreTesting#406 · 4 comments ·
Maintainers usually reply within 1 day
All issues in wpilibsuite/SystemcoreTesting
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Make branch and label autocomplete matching locale-independentPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
jenkinsci/gitlab-plugin#1950 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
commons-app/apps-android-commons#6984 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
It's not necessary to copy the memory block in the readWrite() of org.h2.store.fs.mem.FileMemDataOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
h2database/h2database#4435 ·
Maintainers usually reply within 1 day