The `new_comments` search filter appears to be broken.
By
D'Archangel
on March 09, 2010
Kind of hard to notice when our dashboards are busted, but consider this search (which I still had saved; draw your own conclusion). It seems to particularly hate admitting that I've seen claims where my comment is the last; you might need to insert your OpenID to duplicate the effect.
Embed Claim
Make a related claim
Similar claims
- 6-3 The vote status text (agreed/disagreed) does not represent my actual vote on my own profile page.
- 12-1 It should be possible to remove all claim filters with a single click.
- 16-3 The "Recent Activity" tab should not show claims by people on my ignore list.
- 20-0 There should be a token that means "all my contacts" in Advanced Search OpenID lists
- 6-7 Names of voters are showing up more than once.
Discussion (13)
I mailed them to save you the hassle.
Yeah. Under 'watched conversation' I found that it didn't know not to show it if the last comment was mine.
I have one to show new comments on anything I've visited, but the results aren't changing.
This release is clearly a bust, time to rollback.
I think it's fixed now.
[who use to agree:] Good point.
D'A
Works for me.
[who used to disagree:] It's busted again. Same symptoms as before.
D'A
Used to work for me.
works again. please tag "fixed, done" -- also, perhaps "advanced search, new comments, unread"
It's still broken for me; it throws up claims that I've seen many times since the most recent comment.
and those many times include times since the fix? e.g., if you view a claim, and then reload the list, that claim is still there?
They come and go. I can visit a claim, and hours later, or seconds later, it will be back in the list.
An example claim that keeps popping up in that list for me is this one. At the time I write this comment, it has *never had* any comment on it other than one from me. It should, by my reckoning, never have shown up in the list of "claims with new comments after bignose".
note that your own comment was at one point, due to a bug, considered "new" to you. And it's considered "after" yours because, actually, the definition used of after yours is "on a comment on which you have claimed" because that's easier to code and indistinguishable when "new" is properly implemented. ( :
that behavior, though, does certainly sound like a bug, possibly a caching one. Having not seen such behavior myself, i'd like to rule out simple browser caching on your end; also possibly other (proxy?) caching. Maybe next time you see this odd behavior, try reloading, and then force-full reloading (shift-reload, in firefox) to see if the list changes when you change nothing about the situation?