fedifetcher ignores --reply-interval-in-hours=0

[strafplanet]

I'm using fedifetcher with the latest docker image 57bdc5b7f7ef. It seems to be ignoring the command line option --reply-interval-in-hours=0 Whether I add the option or drop it completely, fedifetcher always quits with the error message below. The only way to run it for me is with a token that has 'admin:read:accounts'.

Expected behaviour: Fedifetcher runs for tokens without 'admin:read:accounts' when --reply-interval-in-hours=0 is set or if --reply-interval-in-hours is not set at all (it's not mentioned as a default option).

Does this work for someone?

2024-04-04 19:09:40.220328 UTC: Starting FediFetcher
2024-04-04 19:09:40.378930 UTC: Job failed after 0:00:00.158590.
    reply_toots = get_all_reply_toots(
                  ^^^^^^^^^^^^^^^^^^^^
  File "/app/find_posts.py", line 410, in get_all_reply_toots
    reply_toots = list(
                  ^^^^^
  File "/app/find_posts.py", line 411, in <genexpr>
    itertools.chain.from_iterable(
                                 ^
  File "/app/find_posts.py", line 395, in get_active_user_ids
    raise Exception(
Exception: Error getting user IDs on server mstdn.strafpla.net. Status code: 403. Make sure you have the
 admin:read:accounts scope enabled for your access token.

[nanos]

can you just omit this? 0 should be the default value.

[strafplanet]

Sorry if my post is not clear: It does not matter if I add the option or if I omit it - it always crashes like this. It only runs if the token used has the scope admin:read:accounts.

[nanos]

Ah. Apologies, I missed that. That's weird. Are you possibly having a config file that also provides values? This would override the command line flag.

[nanos]

I'm going to close this issue now, as there has been no activity in 2 weeks.