Open nedsociety opened 6 months ago
Since this issue happens when using the systemd
scheduler, could you run git maintenance start --scheduler=crontab
to check if the problem repeats when using cron
? If that works, then it would be a valuable workaround.
Since this issue happens when using the systemd scheduler, could you run git maintenance start --scheduler=crontab to check if the problem repeats when using cron? If that works, then it would be a valuable workaround.
I currently don't have access to the machine for a while, may be able to report in 5~6 days. Though in terms of workaround I'm not sure if switching to crond is a better way against just removing those two lines.
git maintenance start --scheduler=crontab
returned immediately with no output (exitcode was zero). Nothing had been registered to any of /etc/crontab
, /etc/cron.*/*
.
EDIT: Okay /var/spool/cron/crontabs
has the configuration. I'm not sure how to trigger them manually though. I also noted that the systemd timers were gone.
Update: the cron scheduler succeeded for both hourly and daily runs :+1:
git-for-windows/git
tracker.Setup
microsoft/git
are you using? Is it 32-bit or 64-bit?Are you using Scalar or VFS for Git?
Yes (scalar)
Nope, it's Ubuntu 22.04 jammy.
Details
The command succeeds.
I believe this is repo-agnostic
Additional info
Similar to #604 I've found that the problem resolves when I try to comment out two lines from
~/.config/systemd/user/git-maintenance@.service
:pass
to work. Otherwise changing ExecStart tobash -c 'pass list'
shows as if pass has an empty password store. I have no clue what syscalls other than@system-service
is needed for pass to work.git-credential-manager
to run. Otherwise changing ExecStart tobash -c '(echo ...) | git-credential-manager get'
segfaults. For this one though I understand whyMemoryDenyWriteExecute
is needed since gcm is a dotnet application which may use JIT.I didn't check if the upstream git has the same problem (it probably has), but since git-maintenance is probably mostly used by scalar I felt this issue is to be reported here.
X-post (gcm): https://github.com/git-ecosystem/git-credential-manager/issues/1521