-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Intermittent Input Loop Issue When Entering Application Name #20392
Comments
Similar #19819 also, I wasn't able to reproduce the looping problem during the sync process for the application. However, the input fields do behave strangely, such as re-rendering characters that were just deleted. |
I'm experiencing the same issue across several instances of Argo CD. These separate instances are installed on separate clusters. We've taken a look in the firefox browser console and don't see any network traffic being fired off. We do have a Source Map Error:
We tried upgrading from to 2.12.3 to 2.12.6 without seeing the issue go away. We see it in both versions, and across upgrades. We did not see it in the older version we had deployed, 2.7.0. Happy to provide any debug information you can think of that'd be useful tracking this down. |
We made progress over here by getting some applications that were out of sync to start synchronising, actually by removing I'm working on the other instance now: I have an externalSecret that's never synced correctly due to something to do with the decodingStrategy and conversationStrategy fields |
Describe the bug
I'm running into a weird issue when creating an application in Argo CD. Specifically, there’s an input loop happening when I enter the Application Name. It seems to occur more often with longer strings, but it’s not consistent. Reloading the page fixes it temporarily, and I can input the name again.
To Reproduce
Expected behavior
The application name should be entered without any looping or repetition issues.
Version
Screenshots
argocd-application-loop.mov
Additional Context
Has anyone else encountered this problem? Are there any known solutions or updates that address this?
Thanks!
The text was updated successfully, but these errors were encountered: