Hey all, I'd like to check whether a community PR ...
# kontributors
t
Hey all, I'd like to check whether a community PR would be welcome for KT-76147 (Gradle Configuration Cache: 'compile*KotlinMetadata' caused invocation of 'Task.project' in 'commonizeCInterop'). It isn't tagged
up-for-grabs
and it's assigned to Anton Lakotka, so I don't want to jump in here if it's not welcomed or cuts across anything already in flight. I figured I'd ask because it's presently marked as unscheduled, and it hard-blocks Isolated Projects for any KMP module that declares its own cinterop and consumes it from an intermediate source set. The two known workarounds (
notCompatibleWithConfigurationCache
, or
configuration-cache.problems=warn
) that are mentioned in the ticket conversation aid in getting builds working, but sacrifice configuration-cache correctness. I commented on the ticket a little while ago pinpointing
outputFilesProvider
as the origin, and I've since got a fix working locally against
master
. I also put together an accompanying regression test in
CommonizerIT
to validate the change (it fails before the change and passes after). Is a PR for these changes useful/acceptable here, or is this already being picked up internally? I'm happy to open it, rework the approach first, or park it (whichever helps most).
a
if you already have a working tested fix then create a PR and we can look
t
Thanks @Adam Semenenko, I brought the local branch up-to-date (rebased on the latest changes in
master
) and raised a PR. Hopefully it helps, though if there's anything that requires alteration, please let me know and I'll be happy to make the requested changes.