Skip to content
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

Bug: duplicate git source that cannot be deleted #6158

Open
2 tasks done
yuvii opened this issue Dec 4, 2024 · 4 comments
Open
2 tasks done

Bug: duplicate git source that cannot be deleted #6158

yuvii opened this issue Dec 4, 2024 · 4 comments
Assignees
Labels
bug Something isn't working needs-triage Issue is not approved or ready-to-work on

Comments

@yuvii
Copy link

yuvii commented Dec 4, 2024

📜 Description

I'm not sure how to recreate this but it has happened to me more than once. In short, it happens when trying to create a new application, and adding a git source. Sometimes that process fails with this message:

image

If I reload the page there are no git sources configured. So naturally I try to add the git source again. It works the second time around, but by the time I reach the pipeline configuration, I see that I have two souces. Looking back at the git source configuration page, I will now have the same git source configured twice.

When I try to delete one of them, it doesn't work. My only recourse is to completely delete the app and start all over again.

👟 Reproduction steps

Not sure, it's doesn't always happen, so I can't consistently make it happen, but as mentioned I've encountered this more than once

👍 Expected behavior

I should always be able to delete a git source. The fact that the same git source was created twice is an issue too, but the real problem is that I then couldn't delete it.

👎 Actual Behavior

I can't delete the duplicated source.

☸ Kubernetes version

EKS 1.30

Cloud provider

AWS

🌍 Browser

Chrome

🧱 Your Environment

No response

✅ Proposed Solution

No response

👀 Have you spent some time to check if this issue has been raised before?

  • I checked and didn't find any similar issue

🏢 Have you read the Code of Conduct?

@yuvii yuvii added the bug Something isn't working label Dec 4, 2024
@satyampsoni satyampsoni added the needs-triage Issue is not approved or ready-to-work on label Dec 26, 2024
@satyampsoni
Copy link
Contributor

Thank you for raising the issue @yuvii. I attempted to replicate the bug you reported but was unable to achieve the same outcome. Nonetheless, I will escalate this issue to the team to investigate further and identify the potential cause.

@yuvii
Copy link
Author

yuvii commented Jan 5, 2025

@satyampsoni I think it has to do with our source code on github being especially big. It's a large monorepo with a long history of commits and branches, and I think devtron is trying to do some kind of crawling or reading of this history, which makes it take a long time. The action still eventually completes successfully but in the window of time where it's still reading the source, I can re-add it. Once it's been added twice, it can't be removed anymore.

@satyampsoni
Copy link
Contributor

That's a good point, @yuvii. There are indeed some challenges with handling large monorepos, and we are continuously seeking feedback from our users. Could you please raise a bug for this issue:

"The action still eventually completes successfully, but in the window of time where it's still reading the source, I can re-add it."

This will help us track and address the problem more effectively. Thank you for pointing this out
.

@yuvii
Copy link
Author

yuvii commented Jan 7, 2025

what do you mean raise a bug for this issue - isn't that what I did right here? Or do you want me to edit my comment into the original ticket?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs-triage Issue is not approved or ready-to-work on
Projects
None yet
Development

No branches or pull requests

4 participants