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

[Bug]: pmcaptcha plugin: Incomplete verification for forwarded messages #180

Open
4 tasks done
py233 opened this issue Mar 27, 2024 · 0 comments
Open
4 tasks done

Comments

@py233
Copy link

py233 commented Mar 27, 2024

请确保您已阅读以上注意事项,并勾选下方的确认框。

  • 我已经使用一个干净且无其它非必要的插件的环境测试过,问题依旧存在。
  • 我已经在 Issue Tracker 中找过我要提出的问题,没有找到相同问题的ISSUE。
  • 我已知晓并同意,此处仅用于汇报程序中存在的问题。若这个 Issue 是关于其他非程序本身问题,则我的 Issue 可能会被无条件自动关闭或/并锁定。
  • 我已知晓并同意,如果我不按照模板提供的指示进行填写,则我的 Issue 可能会被无条件删除。

PagerMaid 版本 (或 Commit Id)

1.4.10,pmcaptcha version: v2.32

运行环境

Linux

运行架构

None

导致错误的插件是什么?

pmcaptcha

重现步骤

  1. Forward the message to the account that runs the pmcaptcha plugin
  2. Simulate a verification failure
  3. Observe if records and the user are deleted/banned

Video:

IMG_5533.MP4

期望的结果是什么?

Upon verification failure, records should be deleted and users should be banned immediately.

实际的结果是什么?

During verification failure, records and user bans only occur after manually sending a message and waiting for a period of time.

简单的复现代码/链接(可选)

No response

日志记录(可选)

No response

补充说明(可选)

The pmcaptcha plugin triggers verification when forwarding messages, but only sends a verification message. Regardless of whether the verification is passed or failed, it doesn't affect the configured actions of deleting records and banning users.

I have set it to directly delete records and ban users upon verification failure, but the failure process doesn't seem to trigger. Only when I manually send a message after a while does the verification failure process activate.

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

No branches or pull requests

1 participant