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

Can't find node by signature spam #184

Closed
dumptruckman opened this issue Jul 8, 2017 · 28 comments
Closed

Can't find node by signature spam #184

dumptruckman opened this issue Jul 8, 2017 · 28 comments
Labels
Milestone

Comments

@dumptruckman
Copy link

I have a Java annotation that is imported in my class and I refer to it in the KDoc with [AnnotationName]. IntelliJ correctly links to the annotation but Dokka just spams Can't find node by signature foo.bar.AnnotationName. Additionally, the generated Javadoc does not link correctly to the annotation class.

@semoro
Copy link
Contributor

semoro commented Jul 15, 2017

May be this related @FrancoSabadini

@semoro semoro added the bug label Jul 15, 2017
@francos
Copy link

francos commented Jul 15, 2017

Yes this seems more like the issue I'm having. Thanks @semoro.

@sdeleuze
Copy link

Hey, I am adding Kotlin documentation to Spring Framework 5, and I also face this issue which pollute a lot our build logs (you can have a look by running ./gradlew dokka on sdeleuze/spring-framework@SPR-15659.

In addition to the logs, these links don't work in the generated documentation.

The related classes are in the Dokka Kotlin compiler classpath, but not the sources (since I want only generate documentation for Kotlin specific classes and functions).

A fix before Spring 5 Framework GA would be much appreciated if that's possible.

Can't find node by signature org.springframework.web.reactive.function.server.RequestPredicates$POST(kotlin.String)
Can't find node by signature org.springframework.web.reactive.function.server.RouterFunctions$route(org.springframework.web.reactive.function.server.RequestPredicate, org.springframework.web.reactive.function.server.HandlerFunction((org.springframework.web.reactive.function.server.RouterFunctions.route.T)))
Can't find node by signature org.springframework.web.reactive.function.server.RequestPredicates$PUT(kotlin.String)
Can't find node by signature org.springframework.web.reactive.function.server.RouterFunctions$route(org.springframework.web.reactive.function.server.RequestPredicate, org.springframework.web.reactive.function.server.HandlerFunction((org.springframework.web.reactive.function.server.RouterFunctions.route.T)))
...

@semoro
Copy link
Contributor

semoro commented Nov 5, 2017

@sdeleuze Your case fixed in d6d320e and will be available in 0.9.16

@dumptruckman Is this annotation is part of your sources, or from a library?

@sdeleuze
Copy link

sdeleuze commented Nov 5, 2017

@semoro Thanks!

@ZacSweers
Copy link

Is 0.9.16 in active development? I've noticed there haven't been any commits since August

@ZacSweers
Copy link

Ah nevermind, just saw there's a dev branch 👍

@dumptruckman
Copy link
Author

@semoro Ah, I'm sorry, I can't recall which it was. I haven't been working on that project lately. Too busy with school.

@sdeleuze
Copy link

sdeleuze commented Dec 8, 2017

@semoro Could you please release Dokka 0.9.16 in order to allow us to fix this issue in time for Spring Framework 5.0.3 and Boot 2.0.0.RC1 ?

@semoro
Copy link
Contributor

semoro commented Dec 9, 2017

@sdeleuze
Are you need full 0.9.16 release or some EAP will be sufficient?

@sdeleuze
Copy link

sdeleuze commented Dec 9, 2017

We can't use EAP version for Spring releases, so I guess full 0.9.16 would be needed.

Unrelated side note: we are also trying to fix a regression caused by JetBrains/kotlin@5ce514b that prevent us to generate the documentation only for the Kotlin code.

@mattbdean
Copy link

@semoro An EAP would be appreciated for the rest of us experiencing this issue :)

@ZacSweers
Copy link

This is still occurring on the 0.9.16 EAPs

@semoro
Copy link
Contributor

semoro commented Feb 5, 2018

@hzsweers Please, file full form issue

@ZacSweers
Copy link

You want me to file a separate issue rather than comment on this one?

@semoro
Copy link
Contributor

semoro commented Feb 5, 2018

@hzsweers Yes

@ZacSweers
Copy link

I've made it in #269, but it's effectively a duplicate of this issue.

@sdeleuze
Copy link

sdeleuze commented Apr 4, 2018

It seems that this issue is fixed in 0.9.16, shouldn't this issue be closed and added to 0.9.16 milestone? Also the fact that there is this issue and #269 is confusing.

@semoro semoro added this to the 0.9.16 milestone Apr 4, 2018
@semoro semoro closed this as completed Apr 4, 2018
@kirill-grouchnikov
Copy link

This is still happening on 0.9.17.

@DanySK
Copy link

DanySK commented Oct 25, 2018

I confirm this is happening in 0.9.17

DanySK added a commit to AlchemistSimulator/Alchemist that referenced this issue Jan 19, 2019
@atoulme
Copy link

atoulme commented May 5, 2019

I confirm this is still happening in 0.9.18.

@xeruf
Copy link

xeruf commented Jun 21, 2019

I didn't have this previously, but now I'm drowning in these messages...

@pavelaizen
Copy link

pavelaizen commented Jan 20, 2020

I confirm this is still happening in 0.10.0

Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
null:-1:-1: Tag @see cannot be used in inline documentation.  It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method.
null:-1:-1: Tag @see cannot be used in inline documentation.  It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method.
null:-1:-1: Tag @see cannot be used in inline documentation.  It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method.
null:-1:-1: Tag @see cannot be used in inline documentation.  It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method.
null:-1:-1: Tag @see cannot be used in inline documentation.  It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method.
null:-1:-1: Tag @see cannot be used in inline documentation.  It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method.
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
null:-1:-1: Tag @see cannot be used in inline documentation.  It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method.
null:-1:-1: Tag @see cannot be used in inline documentation.  It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method.
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
null:-1:-1: Tag @see cannot be used in inline documentation.  It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method.
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
null:-1:-1: Tag @see cannot be used in inline documentation.  It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method.
null:-1:-1: Tag @see cannot be used in inline documentation.  It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method.
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies

@mrclrchtr
Copy link

This is still happening in 0.10.1

@msilva-verimatrix
Copy link

Can this ticket be reopened? I am observing the same behavior in version 0.10.1:
...
[WARNING] Can't find node by signature android.view.SurfaceHolder, referenced at ... This is probably caused by invalid configuration of cross-module dependencies
[WARNING] Can't find node by signature android.view.Surface, referenced at ... This is probably caused by invalid configuration of cross-module dependencies
[WARNING] Can't find node by signature android.media.AudioManager$setStreamVolume(kotlin.Int, kotlin.Int, kotlin.Int), referenced at ... This is probably caused by invalid configuration of cross-module dependencies
[WARNING] Can't find node by signature android.view.SurfaceHolder, referenced at ... This is probably caused by invalid configuration of cross-module dependencies
[WARNING] Can't find node by signature android.view.Surface, referenced at ... This is probably caused by invalid configuration of cross-module dependencies
[WARNING] Can't find node by signature android.graphics.SurfaceTexture, referenced at ... This is probably caused by invalid configuration of cross-module dependencies
[WARNING] Can't find node by signature android.graphics.SurfaceTexture$getTimestamp(), referenced at ... This is probably caused by invalid configuration of cross-module dependencies
[WARNING] Can't find node by signature android.view.Surface, referenced at ... This is probably caused by invalid configuration of cross-module dependencies
[WARNING] Can't find node by signature android.media.AudioManager$setStreamVolume(kotlin.Int, kotlin.Int, kotlin.Int), referenced at ... This is probably caused by invalid configuration of cross-module dependencies
[WARNING] Can't find node by signature android.media.audiofx.EnvironmentalReverb, referenced at ... This is probably caused by invalid configuration of cross-module dependencies
[WARNING] Can't find node by signature android.media.audiofx.AudioEffect$getId(), referenced at ... This is probably caused by invalid configuration of cross-module dependencies
[WARNING] Can't find node by signature android.media.MediaPlayer.OnErrorListener, referenced at ... This is probably caused by invalid configuration of cross-module dependencies
...

Thank you,

Moacir

@asarkar
Copy link

asarkar commented Nov 12, 2020

I created #1617. If you've this problem too, feel free to vote for it to be fixed.

@DanySK
Copy link

DanySK commented Nov 12, 2020

Why opening a duplicate of a solved bug? Dokka 1.4.x does not have this issue anymore, for me at least.

@xeruf
Copy link

xeruf commented Nov 26, 2020

For anyone still on that version, boggled by this stuff, add this line to the configuration of your DokkaTask (Kotlin DSL, may need to be slightly adjusted for Groovy)

        logging.level = LogLevel.QUIET

See also: https://stackoverflow.com/a/39736281

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests