-
Notifications
You must be signed in to change notification settings - Fork 15
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
Issue after 0.4.0 Release #67
Comments
cc: @qwert2603 |
I'm going to try and look into it now as it won't allow us to upgrade, and will block others potentially if they update. I had issues resolving the snapshot in my large project config, and thought it was fine in the testing I did in a smaller project, but looks like something is up. I don't have an open source repro case at this point unfortunately. |
This is definitely something regarding reading the After manually deleting the file causing issue above, I started running into:
|
Good news. It looks like after removing the validation code: Lines 164 to 172 in 2a4d18a
Now it's working. So, need to fix that. |
Issues seem to be because configuration is not available yet. Therefore configuration can't be validated and tasks can't be created based on config yet. 🤔 |
Some debug output, but the only picked up configurations at that point in time are for the
|
Worked here: dropbox/dropbox-sdk-java#484 But not working in our large monorepo. 🤔 @qwert2603 - Let me know how it works out in your monorepo. |
@handstandsam Hi! I've checked version |
Based on the error output, the exception is thrown by Lines 164 to 168 in 2a4d18a
Can you provide the |
Another error is described in #68. I think, tasks configuration validation may be moved back to the task's action. Also the validation code might be refactored to make it simpler. Now there are two checks in |
@SimonMarquis here is the new ticket to track in. Tagging you so you'll get updates. |
Looks like the configuration validation can't be easily moved to the task's execution phase, because method |
@handstandsam after looking again on the error I've noticed that error happens in non-root module:
Are there any custom configurations created for that module? And is |
Furthermore, such error is thrown is case when |
TL;DR - I think using In my case, it looks like it works now on my huge project. I bumped from
Looking good now in this project. 🤞 Note: I think the other error mentioned needs to still be looked at as it is possibly different. ... Maybe, CI just failed, even with adding |
Interesting. The task is working when I run
Ahh, that is because when I run it, it's only running it for my buildscript classpath. Here is the output confirming:
It does Not run for |
I removed my config for monitoring the |
I just used Gradle's Lines 38 to 39 in f875dee
Lines 50 to 58 in f875dee
Removed that filter. and...
|
Based on the last comment & output, it looks like the problem is that we don't have access to the The configuration cache documentation Gradle looks like it potentially provides a way to workaround this (or at least calls out some differences when accessing the Classpath during a Task. Documentation: https://docs.gradle.org/current/userguide/configuration_cache.html#config_cache:requirements |
It looks like these Not there:
There:
|
Last guess of the night. Configuration Cache Documentation says to use Currently
Could be:
Maybe that'll work? @qwert2603 - Let me know if you have any luck. Thanks again! |
Hooray, after #70, I am testing in my large project where I had the issue, and I am seeing that we now get the correct output when doing validations of configuration names. 🎉
Previously it was only seeing:
|
I'm monitoring the buildscript classpath, and after bumping to
0.4.0
, it correctly detects there was a change. HOWEVER, if I do run the./gradlew :dependencyGuardBaseline
task it does not create a new baseline file and just continues to show the error.I then deleted the
rm dependencies/classpath.txt
file and re-ran the baseline task, but am seeing the same issue. I additionally attempted to add--no-configuration-cache
and it still doesn't work as expected. No new baseline file is created, and the same error above is shown.The text was updated successfully, but these errors were encountered: