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

Autoflagging breaks off when a moderator is selected #216

Closed
Glorfindel83 opened this issue Jul 4, 2017 · 8 comments
Closed

Autoflagging breaks off when a moderator is selected #216

Glorfindel83 opened this issue Jul 4, 2017 · 8 comments
Assignees
Labels
type: bug Buggy or otherwise incorrect behaviour.

Comments

@Glorfindel83
Copy link
Member

Glorfindel83 commented Jul 4, 2017

Autoflagging breaks off when a moderator is selected, e.g. on this post: https://metasmoke.erwaysoftware.com/post/74869

The tooltip on the 'Fail' message (https://metasmoke.erwaysoftware.com/flagging/logs) says:

User is a moderator on this site; not flagging: User is a moderator on this site; not flagging | /var/railsapps/metasmoke/releases/20170629174329/app/models/user.rb:172:in `spam_flag'
/var/railsapps/metasmoke/releases/20170629174329/app/models/post.rb:106:in `send_autoflag'
/var/railsapps/metasmoke/releases/20170629174329/app/models/post.rb:76:in `block in autoflag'
/var/railsapps/metasmoke/releases/20170629174329/app/models/post.rb:74:in `each'
/var/railsapps/metasmoke/releases/20170629174329/app/models/post.rb:74:in `autoflag'
/var/railsapps/metasmoke/releases/20170629174329/app/models/post.rb:35:in `block (2 levels) in <class:Post>'

I'd expect metasmoke to select another user instead of Undo and continue with flagging.

The same thing happened with DavidPostill on SuperUser, see here.

@Undo1
Copy link
Member

Undo1 commented Jul 4, 2017

That's interesting, I was sure it used to behave properly in that case. I'll take a look.

@Undo1 Undo1 self-assigned this Jul 4, 2017
@Undo1 Undo1 closed this as completed in 169bd09 Jul 7, 2017
@Undo1
Copy link
Member

Undo1 commented Jul 7, 2017

That should fix it, let me know if it pops up again

@Undo1
Copy link
Member

Undo1 commented Jul 8, 2017

Possible that I actually broke it more. https://chat.stackexchange.com/transcript/11540?m=38647805#38647805

@Undo1 Undo1 reopened this Jul 8, 2017
@ArtOfCode- ArtOfCode- added the type: bug Buggy or otherwise incorrect behaviour. label Aug 2, 2017
@ArtOfCode-
Copy link
Member

Is this still happening?

@Undo1
Copy link
Member

Undo1 commented Aug 4, 2017

It should be. I meant to come back to this and fix it, never got around to it. It's not a crippling issue, but probably still one to have open.

@Glorfindel83
Copy link
Member Author

This is probably another instance: https://metasmoke.erwaysoftware.com/post/80665 but I can't find corresponding logs in metasmoke.

tripleee pushed a commit to tripleee/metasmoke that referenced this issue Oct 18, 2017
@ArtOfCode-
Copy link
Member

Re-poke. Has anyone seen this issue come up again recently?

@Glorfindel83
Copy link
Member Author

@ArtOfCode- nope. Might very well be fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Buggy or otherwise incorrect behaviour.
Development

No branches or pull requests

3 participants