I noticed a weird looking feed item.
This was the actual event(s).
Maybe this is some sort of batching/coalescing bug? Right now it looks like the comment and the herald triggering got jammed together.
• sshannin | |
Jul 24 2015, 9:45 PM |
F1240680: pasted_file | |
Apr 21 2016, 7:38 PM |
F659434: actual.png | |
Jul 24 2015, 9:45 PM |
F659432: weird_feed.png | |
Jul 24 2015, 9:45 PM |
I noticed a weird looking feed item.
This was the actual event(s).
Maybe this is some sort of batching/coalescing bug? Right now it looks like the comment and the herald triggering got jammed together.
This is displaying as intended. That is, if there is no image available, we still outline the actor space for consistency.
This behavior is "correct" in some sense (Herald really did perform the "strongest" action in the transaction group) but the sorting on tiebreakers is likely wrong (see D14680 for a similar case) and we should sort actions by real users over actions by Herald at the same strength.
That is, there were three actions here:
I haven't actually looked at the values, but the result might be because of something like this:
(2) has the weakest strength (any other transaction is always more interesting than "added a comment", since we show the comment anyway), so we have a choice between (1) and (3) as the title of the feed story. We incorrectly select (3) as a stronger action, when a better choice would be (1).
However, it's actually possible that we're already doing strengths correctly -- I think we may have a special rule to make "user added <themselves> as a subscriber" into a very weak action. This legitimately makes the Herald action stronger. It should not be, so maybe we just add a rule to make "<any application> <did anything> <to subcribers>" extremely weak because that is soooo boring.
I'm not sure what we should do in this case:
In this case, "close" is legitimately very strong. What should we do?
Offhand, I'm inclined to still publish "Herald closed the task." in the "subscribe + close" hypothetical, which I think is the current behavior.
Maybe slightly always ding a computer action vs. a human action. That is, if a human adds a subscriber, and herald adds a subscriber, that weight is (human action weight - 1), or something along those lines? Then if human adds a subscriber, but herald closes, the weight of the close action even though gets dinged, is likely still stronger.
From T10822, we currently choose [Changed Subscribers] as a stronger action than [Merged] for tasks in some cases in email subject lines. This is probably not the correct heuristic, [Merged] is normally a strong action.
I think that story strength thing is non-retroactive? This may not really be fixed if new stories aren't better.
very nice
if it breaks again we can try adding some more 0.000000000's first and see if that helps
That's because it was deliberate self-subscribe which is so completely boring that we normally wouldn't even show it. I think it's arguably correct to show the Herald story? Maybe?
I think if you add me and Herald adds eadler, it will show "chad added epriestley".
But if you add yourself (SO BORING) and Herald adds eadler, it shows "Herald added eadler".
If we don't do that, self-adds sometimes show up and sometimes don't which is a little weird maybe? I'm not sure there's any way to resolve this that's consistent/obvious/predictable/always makes sense.
Like just don't show it at all? That seems reasonable to me, although 0.00000000001 is very funny and we would be losing a truly great joke at such a young age.
0.00000000001 is very funny and we would be losing a truly great joke at such a young age
F
This actually died earlier in D20540, but got to live for far longer than it probably should have.