Feed polling is too naïve
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ibid |
New
|
Low
|
Unassigned |
Bug Description
07:37 < tibid> New item in AngryDeveloper: angrydeveloper: Yeah but airplanes are flying
07:41 < tibid> New item in AngryDeveloper: angrydeveloper: CW: "I just found a random hair on
my keyboard." AD: "Yeah, I was rubbing my balls all over your keyboard earlier."
07:43 -!- swazi [~<email address hidden>] has left #compsci []
07:47 < tibid> New item in AngryDeveloper: angrydeveloper: Yeah but airplanes are flying
07:51 < tibid> New item in AngryDeveloper: angrydeveloper: CW: "I just found a random hair on
my keyboard." AD: "Yeah, I was rubbing my balls all over your keyboard earlier."
08:01 < tibid> New item in AngryDeveloper: angrydeveloper: Yeah but airplanes are flying
08:07 < tibid> New item in AngryDeveloper: angrydeveloper: CW: "I just found a random hair on
my keyboard." AD: "Yeah, I was rubbing my balls all over your keyboard earlier."
11:00 <@tumbleweed> looks like it's oscillating between announcicng the front and back items
11:01 <@tumbleweed> i.e. it sometimes gets served the new feed, sometimes the old one
We should do more caching of old results so we don't see these duplicates under odd situations.
Changed in ibid: | |
status: | New → Invalid |
Changed in ibid: | |
status: | Invalid → Incomplete |
description: | updated |
Changed in ibid: | |
status: | Incomplete → New |
Sam: Any particular reason you marked this as being invalid?