-
Notifications
You must be signed in to change notification settings - Fork 89
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
Plugin crash on delete #39
Comments
Hi, I see that the sync.RWMutex that was set to provide some sort of connection pooling is not working as expected, this is an easy fix that I should be able to take care of later this or next week. Thanks for reporting. |
Hello, some updates since I have begun working on this, this has nothing to do with the connection pooling feature (fortunately) and is actually an edge case with projects deletion: the sync.RWMutex object is present to handle concurrent modification of the same project, while allowing for simultaneous reads of that project (for example adding a project token, or modifying a project syncWindow are competing operations that will impact each other) to offer acceptable performance on large TF plans that include a lot of ArgoCD resources. It seems the TF test framework differs a bit from reality, since this has never been an issue during the automated CI: the Go objects instanciated within the testing automated plan part are kept in memory during the automated destruction part. I will publish an hotfix soon that should not break anything, and will definitely solve the issue highlighted by your logs above. |
@rojopolis , release 0.4.8 contains the aforementioned fix (#40), feedback would be much appreciated! |
Hi @oboukili It seems to be fixed! Thanks so much for taking care of it. |
Glad to hear it :) ! |
I tend to get a lot of plugin crashes while deleting application and project resources. Here's a stacktrace in case it's useful:
The text was updated successfully, but these errors were encountered: