This message was deleted.
# community-support
s
This message was deleted.
d
This is usually an edge eviction bug in Gradle's dependency graph resolver. Often reordering dependencies, adjusting excludes, etc. can avoid it
g
I got similar bug only when synchronizing project in idea when I has activated dependency locking. At the same time a build from terminal was successful. It seems idea mucks with dependencies while synchronizing leading to some data race. IIRC, locking was active for some configurations and issue disappeared after changing locking config.
m
Yes! i have same behavior. Gradle build work but synchronizing project in idea was failed
Can you tell how you disabled the locking in idea?
g
I didn't. Issue was transient and after some changes (dependency versions, number of configurations to lock) idea started to synchronize again
l
If you manage a reproducer, please open an issue. You could also try a 7.5 nightly as a couple fixes are already available.
m
No, in my project we use private repository. But i can create scan. I found one strange dependency, when i remove it project successful import. If i now this dependency, can i get more information about graph resolver error?
Copy code
implementation(group = "ru.tinkoff.tdk", name = "spring-boot-starter-tdk")
g
I've lost state where it was reproducible but if I manage to get it again I'll try to file an issue