Repository navigation
Conversation
If an operator moves or deletes .enc backup files while leaving .complete, restarting the container skipped initial backup. This checks for .enc files and removes stale .complete markers before deciding whether to skip initial backup. Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the
|
If an operator moves or deletes .enc backup files while leaving .complete, restarting the container skipped initial backup. This checks for .enc files and removes stale .complete markers safely without stopping container startup if removal fails. Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
If an operator moves or deletes .enc backup files while leaving .complete, restarting the container skipped initial backup. This checks for .enc files and removes stale .complete markers safely without stopping container startup if removal fails. Also ensures E2E test session unlocks vault after login. Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
If an operator moves or deletes .enc backup files while leaving .complete, restarting the container skipped initial backup. This checks for .enc files and removes stale .complete markers safely without stopping container startup if removal fails. Also ensures E2E test session unlocks vault after login. Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
If an operator moves or deletes .enc backup files while leaving .complete, restarting the container skipped initial backup. This checks for .enc files and removes stale .complete markers safely without stopping container startup if removal fails. Also ensures E2E test session unlocks vault after login and only skips E2E workflow when ADMIN_TOKEN is missing on pull requests. Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
This change updates
run.shto check for.encbackup files when.completemarker is present. If no.encbackup files exist in the backup directory,run.shremoves the stale.completemarker and runs the initial backup. Unit tests intests/test_run.pywere updated and added to cover this scenario.PR created automatically by Jules for task 5606918260970887226 started by @mvfc


Confidence Score: 5/5
The PR appears safe to merge; no new actionable issues remain.Summary
run.shremoves a stale.completemarker when no.encbackups remain, then attempts an initial backup.ADMIN_TOKENis unavailable.Reviews (5) · Last reviewed commit: "Remove stale .complete marker in run.sh ..." · Reviewed by Greptile