Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update xseed_qbit_cat_filter.sh #15

Merged
merged 1 commit into from
May 9, 2024
Merged

Conversation

bobokun
Copy link
Contributor

@bobokun bobokun commented May 9, 2024

  • Fixes regex bug with variables
  • only logs when cross-seed searches based on filters

- Fixes regex bug with variables
- only logs when cross-seed searches based on filters
@bakerboy448 bakerboy448 merged commit 18fc743 into bakerboy448:main May 9, 2024
Comment on lines -64 to +66
[ "$xseed_resp" != "204" ] && sleep 30 && xseed_resp=$(cross_seed_request "path=$TORRENT_PATH")
[ "$xseed_resp" != "204" ] && sleep 30 && xseed_resp=$(cross_seed_request "path=$TORRENT_PATH") && log "[\033[1m$TORRENT_NAME\033[0m] [$TORRENT_CAT]"
elif [[ "$TORRENT_TRACKER" =~ ($FILTERED_TRACKER) ]]; then
xseed_resp=$(cross_seed_request "infoHash=$TORRENT_INFOHASH");
[ "$xseed_resp" != "204" ] && sleep 30 && xseed_resp=$(cross_seed_request "path=$TORRENT_PATH")
[ "$xseed_resp" != "204" ] && sleep 30 && xseed_resp=$(cross_seed_request "path=$TORRENT_PATH") && log "[\033[1m$TORRENT_NAME\033[0m] [$TORRENT_TRACKER]"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

will this only log when the response from infohash search is 204 (not found) - I think this needs to go on the next (it's own) line?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No it’ll log when the info hash search is not 204

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, I'm thinking announce endpoint.

send info hash search
if it receives 204 - which is success - then it does not log at all.

It should instead log outside of the condition that infohash fails

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants