Quick Answers Filter -- weird
-
I was happily browsing in QA and suddenly the filter changed to MongoDB, and now i cannot get rid of it. Has a hamster had a seizure? [edit] Now it appears to have cleared itself. But, watch this space. [/edit] [more edit] It appears that somehow the 'tag' property in the URL got stuck and could not be removed by clearing the filter and pressing 'Update' [/more edit] No idea how it started but it seems OK now. (Google Chrome 83.0.4103.106)
-
I was happily browsing in QA and suddenly the filter changed to MongoDB, and now i cannot get rid of it. Has a hamster had a seizure? [edit] Now it appears to have cleared itself. But, watch this space. [/edit] [more edit] It appears that somehow the 'tag' property in the URL got stuck and could not be removed by clearing the filter and pressing 'Update' [/more edit] No idea how it started but it seems OK now. (Google Chrome 83.0.4103.106)
Did you click on that tag anywhere?
cheers Chris Maunder
-
I was happily browsing in QA and suddenly the filter changed to MongoDB, and now i cannot get rid of it. Has a hamster had a seizure? [edit] Now it appears to have cleared itself. But, watch this space. [/edit] [more edit] It appears that somehow the 'tag' property in the URL got stuck and could not be removed by clearing the filter and pressing 'Update' [/more edit] No idea how it started but it seems OK now. (Google Chrome 83.0.4103.106)
This is a re-occurring issue that has been driving us crazy for a while. The latest theory is that the hamsters have been chewing on the Redis server network cable resulting in bad data. We are trying to track this one down, but it is a tricky one. BTW, we did have a bunch of Redis issues earlier today, which might account for any recent weirdness.
"Time flies like an arrow. Fruit flies like a banana."
-
Did you click on that tag anywhere?
cheers Chris Maunder
I don't think so, but it is always possible that I hit a tag somewhere. But the strangest part was when I deleted the tag and clicked the Update button. The page would refresh without the tag, and then automatically put it back. Eventually I killed the page and opened a new one and that was OK. I did have a re-occurrence yesterday, but was able to clear it immediately.
-
This is a re-occurring issue that has been driving us crazy for a while. The latest theory is that the hamsters have been chewing on the Redis server network cable resulting in bad data. We are trying to track this one down, but it is a tricky one. BTW, we did have a bunch of Redis issues earlier today, which might account for any recent weirdness.
"Time flies like an arrow. Fruit flies like a banana."