You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the chrome extension starts forgetting items due to the predefined limit, it often starts with the top level parent stories that provide structure to the rest of what's going on. This usually results in nonsensical, confusing output.
When stuff is being forgotten, it should start with the log items from the leaf stories (say, an even selection of the oldest log items from every leaf story). Only once a story has no more children should it be deleted.
The text was updated successfully, but these errors were encountered:
Could you maybe share some steps to reproduce, or maybe screenshots of what you mean? Even better: maybe you could consider adding a failing test to the suite? In principle (see this test), the forgetting algorithm should work just as you describe…
When the chrome extension starts forgetting items due to the predefined limit, it often starts with the top level parent stories that provide structure to the rest of what's going on. This usually results in nonsensical, confusing output.
When stuff is being forgotten, it should start with the log items from the leaf stories (say, an even selection of the oldest log items from every leaf story). Only once a story has no more children should it be deleted.
The text was updated successfully, but these errors were encountered: