-
Notifications
You must be signed in to change notification settings - Fork 896
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Purge dated VimPerformanceStates #11868
Comments
This issue has been automatically marked as stale because it has not been updated for at least 6 months. If you can still reproduce this issue on the current release or on Thank you for all your contributions! |
@kbrock Is this still on your plate and if so, do you want to un-stale it? |
@Fryguy think this one is still not purged. It slipped through the cracks. Sorry I did not state this on Mar 1 (when I reopened) What logic do we use to determine stale/old/purgeable |
Probably you can use the timestamp? |
This issue has been automatically marked as stale because it has not been updated for at least 6 months. If you can still reproduce this issue on the current release or on Thank you for all your contributions! |
@isimluk is this still a valid issue. If not can you close. |
Closing issue. If you feel the issue needs to remain open, please let me know and it will be reopened. |
This was fixed in #16754 |
Resurrecting this issue... purging just orphaned states means we still retain "live" object's states forever. |
@isimluk 'isimluk' is an invalid assignee, ignoring... |
@isimluk sorry about the ping... When I reopened the issue, I guess the bot replied to your initial comment to assign yourself. I hope you're doing well. 👋 |
Hello @jrafanie, I hope you are doing well too. And no need to apologize. I have fond memories of ManageIQ team and the codebase, and don't mind being reminded of it every morning. So, I am sorry about vandalizing the purging issue with a gif. Take care. |
As per #11016 (comment) we are not purging datad VimPerformanceStates
/cc @gtanzillo
The text was updated successfully, but these errors were encountered: