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

Inherited function type resolution is flaky #2187

Closed
owengray-google opened this issue Oct 14, 2021 · 2 comments · Fixed by #2400
Closed

Inherited function type resolution is flaky #2187

owengray-google opened this issue Oct 14, 2021 · 2 comments · Fixed by #2400
Labels
bug feedback: Google An issue/PR submitted by colleagues at Google, most likely related to the Android API reference docs

Comments

@owengray-google
Copy link
Contributor

(this debugging regards kotlinSubclassFunction as inherited from KotlinSubclass by JavaLeafClass : KotlinSubclass)
Screen Shot 2021-10-14 at 9 34 55 AM

Sometimes, the type of kotlinSubclassFunction in JavaLeafClass : KotlinSubclass does not resolve and becomes null. This has been observed (so far exclusively, but I have suspicions some other cases are related) in java types inheriting Kotlin class functions that don't have explicit return types (i.e. use fun foo() = "string").

Expected behaviour
The return type of kotlinSubclassFunction should be String, not null, as it is for kotlin types inheriting such things.
Our source is here:
https://cs.android.com/androidx/platform/tools/dokka-devsite-plugin/+/master:testData/inheritance/source/

Dokka version 1.6.0-dev-122

As this is flaky and seems likely to be a concurrency issue, maybe this is related to #2052?

@vmishenev vmishenev added the feedback: Google An issue/PR submitted by colleagues at Google, most likely related to the Android API reference docs label Oct 28, 2021
@vmishenev
Copy link
Member

I have opened an issue for IDE team:
https://youtrack.jetbrains.com/issue/KT-50111
But it can be fixed not soon.

@IgnatBeresnev
Copy link
Member

KT-50111 has been fixed and I believe it should've been included into 1.6.20.

Closing this for now, but do let us know if this problem occurs again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug feedback: Google An issue/PR submitted by colleagues at Google, most likely related to the Android API reference docs
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants