sync: auto-sync from GURU-BEAST-ROG at 2026-06-30 15:11:06
Author: Mike Swanson Machine: GURU-BEAST-ROG Timestamp: 2026-06-30 15:11:06
This commit is contained in:
@@ -0,0 +1,73 @@
|
||||
## User
|
||||
- **User:** Mike Swanson (mike)
|
||||
- **Machine:** GURU-BEAST-ROG
|
||||
- **Role:** admin
|
||||
|
||||
## Session Summary
|
||||
|
||||
Short maintenance span following the 2026-06-19 re-clone-recovery / VWP-time-sync session
|
||||
(logged in `2026-06-19-mike-reclone-recovery-and-vwp-time-sync.md`). Across several routine
|
||||
`/sync` runs the `projects/discord-bot` submodule kept being reported by `sync.sh` as having
|
||||
uncommitted changes, which prompted a closer look.
|
||||
|
||||
Root cause: the recovered Python virtualenv lives at `.venv/` (the leading-dot convention from
|
||||
`python -m venv .venv`), but the submodule's `.gitignore` only ignored `venv/` — so `.venv/`
|
||||
showed as untracked and every parent sync flagged the submodule dirty. There were no actual bot
|
||||
code changes; the prior code fix (`0487b15`) was already committed and pushed. Fixed by adding
|
||||
`.venv/` to `projects/discord-bot/.gitignore`, committed in the submodule on `main`
|
||||
(`2c91a2a`) and pushed to the acg-discord-bot Gitea repo. Subsequent `/sync` confirmed the
|
||||
submodule is now reported clean (`[branch main]`, not "uncommitted changes").
|
||||
|
||||
Also during this span, routine syncs pulled fleet work (gitea/synology/screenconnect/datto-edr
|
||||
skills, Bitdefender + GuruRMM buildout, Khalsa/Jimmy/Four Paws client work) and the vault picked
|
||||
up several new client/infra credentials. The vault repo's git identity was found set to Howard
|
||||
Enos on this machine and was auto-corrected to Mike Swanson by `sync.sh`'s identity reconcile
|
||||
before committing a local Four Paws credential. The CRITICAL harness-guard macOS-bash-3.2 fix
|
||||
(`4c51be5`) was pulled and self-check confirmed GREEN (PASS 83/0/0); census published.
|
||||
|
||||
## Key Decisions
|
||||
|
||||
- **Fix the gitignore gap, never commit the venv.** The "uncommitted changes" was an untracked
|
||||
`.venv/`, not real work. Correct fix is ignoring `.venv/` (a venv must never be committed), not
|
||||
committing or force-cleaning it.
|
||||
- **Commit in the submodule's own history, not the parent.** The `.gitignore` belongs to the
|
||||
discord-bot repo; committed there on `main` and pushed. Parent gitlink intentionally left
|
||||
unadvanced (sync's default; `--with-submodules` would be needed to bump the pin).
|
||||
|
||||
## Configuration Changes
|
||||
|
||||
- Modified: `projects/discord-bot/.gitignore` — added `.venv/` under the virtualenv block.
|
||||
Submodule commit `2c91a2a` on `main`, pushed `0487b15..2c91a2a` to acg-discord-bot.git.
|
||||
|
||||
## Credentials & Secrets
|
||||
|
||||
- None created/discovered this span. Vault auto-committed a pre-existing local
|
||||
`clients/four-paws/localadmin.sops.yaml` and pulled new entries (cascades-tucson/meredith-kuhn,
|
||||
four-paws/staff-workgroup, infrastructure/windows-pro-mak) from the fleet — all via vault sync,
|
||||
none handled manually here.
|
||||
|
||||
## Infrastructure & Servers
|
||||
|
||||
- discord-bot submodule origin: `git.azcomputerguru.com/azcomputerguru/acg-discord-bot.git`.
|
||||
- Bot service: `ClaudeToolsDiscordBot` (nssm), runs from `projects/discord-bot/.venv` on GURU-BEAST-ROG.
|
||||
|
||||
## Commands & Outputs
|
||||
|
||||
- `git -C projects/discord-bot check-ignore .venv` -> not ignored (before) / `.venv` (after fix).
|
||||
- Submodule was detached HEAD at origin/main; `git checkout -B main origin/main` then commit/push.
|
||||
- Post-fix `/sync`: `sync: leaving submodule with local work untouched: projects/discord-bot [branch main]`
|
||||
(previously reported `[uncommitted changes]`).
|
||||
|
||||
## Pending / Incomplete Tasks
|
||||
|
||||
- `ClaudeTools.old` deletion still pending Mike's go (fully drained + verified in the 2026-06-19
|
||||
session; ~30GB, irreversible).
|
||||
- VWP member time-sync converged (verified 2026-06-19/20); 3 then-offline members
|
||||
(DESKTOP-S4GNL8O, VWP-ChrisG-L, VWP-JR-L) apply config on reconnect — no action unless a drive
|
||||
issue recurs.
|
||||
|
||||
## Reference Information
|
||||
|
||||
- Submodule commit: `2c91a2a` (gitignore .venv). Prior bot code fix: `0487b15`.
|
||||
- Harness-guard fix pulled: `4c51be5`. Self-check: GREEN, census `selfcheck_GURU-BEAST-ROG`.
|
||||
- Prior session log: `session-logs/2026-06/2026-06-19-mike-reclone-recovery-and-vwp-time-sync.md`.
|
||||
@@ -1,2 +1,3 @@
|
||||
# Bot Activity Log - 2026-06-25
|
||||
16:47 PT - Winter/Mike - Tedards #32228 agencyzoomify.com emails to trash - Applied TABL sender allow (permanent) on tedards.net; resolved Syncro ticket; sent outreach email to lindsay@agencyzoomify.com (CC y226@tedards.net) re Wirechunk DKIM fix
|
||||
19:13 PT - Mike - Tedards agencyzoomify investigation (bt@tedards.net trace, Lindsay replies, GuruProtect analysis) - bot session closed; Mike continuing on ticket #5070
|
||||
|
||||
Reference in New Issue
Block a user