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

'Conflicting feedback across revisions' triggers on posts with no feedback #286

Closed
Undo1 opened this issue Nov 26, 2017 · 6 comments
Closed
Labels
status: review Issues which require revisiting because they may have become obsolete or changed in some way type: bug Buggy or otherwise incorrect behaviour.

Comments

@Undo1
Copy link
Member

Undo1 commented Nov 26, 2017

In this example, the first post/revision had tp feedback while the second had no feedback at the time of the chat message being posted.

Looks like an issue in this call:

conflicting_revisions = Post.where(link: link)
                                               .where.not(id: id)
                                               .where('is_tp != ? or is_fp != ?', is_tp, is_fp)

triggering based on is_tp != true (due to complete lack of feedback).

@quartata
Copy link
Member

I had a different predicate initially, which was a bit clunkier in terms of interactions wirh NAAs but didn't do this. Art suggested changing it to the current one -- I pointed out that this would occur, but at the time I think we were both OK with it because it didn't seem that common.

@quartata
Copy link
Member

#280 for the full discussion

@ArtOfCode-
Copy link
Member

I think I also misunderstood exactly what case it would trigger on :P

@angussidney angussidney added the type: bug Buggy or otherwise incorrect behaviour. label Mar 10, 2018
@Undo1
Copy link
Member Author

Undo1 commented Jul 8, 2018

Apparently I "fixed" this by just shutting off the conflicting feedback warnings in 571cbe7. Ping @quartata - think this is worth fixing?

@thesecretmaster
Copy link
Member

@quartata Pinging again re: above

@thesecretmaster thesecretmaster added the status: review Issues which require revisiting because they may have become obsolete or changed in some way label Sep 5, 2018
@ArtOfCode-
Copy link
Member

Closing as no longer relevant with these messages disabled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: review Issues which require revisiting because they may have become obsolete or changed in some way type: bug Buggy or otherwise incorrect behaviour.
Development

No branches or pull requests

5 participants