Repository navigation
Fix SourceSetContainer lookup in buildSamples task configuration - #635
Merged
Saloed merged 1 commit intoNov 1, 2026
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Saloed
approved these changes
Nov 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
#634 broke
ci-pythononmain(run https://github.com/UnitTestBot/usvm/actions/runs/41299659885): withcpythonActivated=true, Gradle fails to create:usvm-python:buildSampleswithExtension of type 'SourceSetContainer' does not exist. InregisterBuildSamplesTask, the replacement for thesourceSetsaccessor callsextensionsinside thetasks.register<JavaExec> { ... }configuration block, where it resolves to the task's extensions instead of the project's. The removed accessor was defined only onProject, so it did not have this problem.Use
project.extensionsthere. The other replacements from #634 are called directly onProjectand are unaffected.Validation: with
-PcpythonActivated=true, both./gradlew -m :usvm-python:testand./gradlew tasks --all(which creates every task in every project) fail on currentmainwith the CI error and pass with this change. The Python tests themselves were not run locally, since they require a CPython build; my validation for #634 missed this because it ran withoutcpythonActivated, so the lazily registered task was never created.🤖 Generated with Claude Code