We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
建议内容: 我发现我的两个账号在挂直播时长时,一个新号可以正常推送到我的自定义api里面,另外一个比较老的不行,因为后面的这个账号需要完成13个直播间的挂时长,每一个直播间需要在日志的information打印出70个心跳包发送成功,也就是说,光是打印心跳包发送成功,就用了910行日志,我觉得,不管是自定义API或者其他的推送服务都不支持那么多行数信息。 如果加入选项,可以控制心跳包发送成功的日志是否打印在information,这910行日志可以精简为几行“第几个心跳包发送失败”或者一行“心跳包全部发送成功”,这肯定可以大大提高发送成功的概率。
information
The text was updated successfully, but these errors were encountered:
可以这样显示心跳包日志(其他粉丝牌升级项目中看到的):up1 up2 up3 up4等共 n 个直播间的第n次心跳包已发送(n/65)
Sorry, something went wrong.
No branches or pull requests
建议内容:
我发现我的两个账号在挂直播时长时,一个新号可以正常推送到我的自定义api里面,另外一个比较老的不行,因为后面的这个账号需要完成13个直播间的挂时长,每一个直播间需要在日志的
information
打印出70个心跳包发送成功,也就是说,光是打印心跳包发送成功,就用了910行日志,我觉得,不管是自定义API或者其他的推送服务都不支持那么多行数信息。如果加入选项,可以控制心跳包发送成功的日志是否打印在
information
,这910行日志可以精简为几行“第几个心跳包发送失败”或者一行“心跳包全部发送成功”,这肯定可以大大提高发送成功的概率。The text was updated successfully, but these errors were encountered: