Preventing metdata postprocessor from running on skipped posts

[powerfulsaber]

I have a metadata postprocessor running at event post for instagram, but I've noticed it will create a metadata file for a post despite skipping over it.

I tested this by adding subcategory to its filename, downloaded the first page of a user's reels, and then downloaded the first page of the user's posts. Assuming the user has a portion of their reels available on their posts, there'll be two metadata files of the same reel: one with subcategory posts and another with subcategory reels. This can be mitigated by using type instead of subcategory, so it'd have a consistent filename to prevent duplicates, but it's not ideal since it's unnecessarily overwriting it every time.

Based on the documentation, event post isn't meant to run for skipped posts, so this is likely a bug. I also tried post-after but the same issue occurred. I recall experiencing this before when using a filter on a user's tagged page; it'd download metadata files of posts/reels that don't pass the filter, despite the event being only meant for posts it'll download (reminds me of #7814).

[mikf]

The current code has no concept of actual posts, let alone "skipped" posts.

The only thing that can be skipped are files, nothing else. "event": "post" running for all posts is "expected behavior".

You can probably implement some form of workaround using a postprocessor filter, but this is currently not directly supported.

[powerfulsaber]

I noticed there's a metadata.skip option, so it'd make the consistent filename ideal by preventing overwrites if enabled. But it seems the no-skip flag doesn't bypass it. Is there a way to set it to false in the CLI?

[mikf]

-O skip=false
(capital -O instead of -o)