umputun / feed-master / 35483667476

75%

push

github

fix: say what the yt-dlp updater will actually do at startup (#180)

the yt-dlp updater's startup line keyed off the interval alone, so it could not be trusted as a signal that the `ytdlp_update` section had been read.

two cases were actively misleading. An interval with no command logged `yt-dlp updater enabled, interval 24h` and then never executed anything, because the tick path is guarded on the command being non-empty. `force_on_startup: true` with no interval logged `yt-dlp periodic updater is disabled`, which reads as the whole feature being off even though the startup run does happen.

the line now states the resulting behaviour: disabled when no command is set, on startup only, every interval, both, or never when a command is set with neither trigger.

it also moved inside the goroutine, after the `disable_updates` early return. Where it was, a config with a command and `disable_updates: true` announced work that `Do` was never reached to perform, which is the same untruthful status this change is about.

`README.md` said an omitted interval means yt-dlp will not be updated. That is false when `force_on_startup` is set.

context is #169, where the reporter sees no evidence the command is invoked. This does not diagnose that report and it stays open; the startup line was simply not good enough to tell the two situations apart.

Related to #169

12 of 15 new or added lines in 1 file covered. (80.0%)

1487 of 1984 relevant lines covered (74.95%)

10.69 hits per line