ERROR main JsonNodeDocuGenerator Could not call getBundleName #38
Comments
|
Hi HaveF, nice to see that you're using our tool! The “error” log which you posted is actually meant to be more a “warning”. Our classification of logging it as error doesn't make much sense - it's meant to inform the user that we couldn't extract some information as desired, but the documentation should still be generated completely or successfully. Can you confirm if you receive the desired data as output? We will update the log output in the next update to be less alarming :-) Best, |
* there's nothing we can do about these exceptions, anyways, and they are treated as graceful as possible, so `error` doesn't make sense * shorten log output and remove stacktrace * closes #38
* there's nothing we can do about these exceptions, anyways, and they are treated as graceful as possible, so `error` doesn't make sense * shorten log output and remove stacktrace * closes #38
|
@qqilihq hi, qq :-)
I only got the above error message and nothing else. Still don't know if I messed up somewhere. |
|
@danielesser Any idea if the configuration might be missing something? @HaveF Could you post the complete log output here? Do you see any error message within a dialog? Is this a “fresh” KNIME installation or did you install any other extensions? If so, could you please retry with a clean KNIME installation with only the JSON generator installed? In whic OS and environment are you running this? |
|
I installed your new version of extension. And the error problem was located. Mainly because of the
no problem.
and I get nothing. I have I use MacOS 12. |
|
I just gave this another try, I realized that in our NodePit crawler we supply some more parameters now - the readme seems outdated. Here's a more complete example which will also include logging output: ./knime \
-nosplash \
-data /path/to/temporary-workspace \
--launcher.suppressErrors \
-application de.philippkatz.knime.jsondocgen.application.JsonNodeDocumentationGenerator \
-destination /path/to/node-docs \
-category /io \
-vmargs \
-Dlog4j.debug=true \
-Dlog4j.configuration=/path/to/log4j.xml \
--add-opens=java.base/java.lang=ALL-UNNAMED \
--add-opens=java.base/java.lang.invoke=ALL-UNNAMED \
--add-opens=java.base/java.net=ALL-UNNAMED \
--add-opens=java.base/java.nio=ALL-UNNAMED \
--add-opens=java.base/java.nio.channels=ALL-UNNAMED \
--add-opens=java.base/java.util=ALL-UNNAMED \
--add-opens=java.base/sun.nio.ch=ALL-UNNAMED \
--add-opens=java.base/sun.nio=ALL-UNNAMED \
--add-opens=java.desktop/javax.swing.plaf.basic=ALL-UNNAMED \
--add-opens=java.base/sun.net.www.protocol.http=ALL-UNNAMEDUse the following <?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
<log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/">
<appender name="console" class="org.apache.log4j.ConsoleAppender">
<param name="Target" value="System.out"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d{HH:mm:ss.SSS} [%t] %-5p %c{1}:%L - %m%n"/>
</layout>
</appender>
<root>
<level value="DEBUG" />
<appender-ref ref="console" />
</root>
</log4j:configuration>Let me know how that works please! If it still doesn't work then at least the log output should give some hints now :-) |
|
Thank you so much! With a complete log, it seems much more convenient. This should be a flaw in the program. But I found that if I use the full path of
Thanks for your help, again!(And your help in the forum ☕ ) @qqilihq |
Ahh, point taken. In this case the output is generated next to the For now, absolute paths (or using Thank you very much for your input! |
Aha, it turns out they are here, haha |
|
@HaveF Thank you again for the feedback 👍 - we have improved the following things in v1.13.4 which I just pushed to the update site:
|
|
@qqilihq Nice. thanks for this valuable tool! |
Hi, NodePit developers! ❤️
My environment is KNIME 5.2.2, I don't know if I messed up somewhere.
╰─$
./knime -nosplash --launcher.suppressErrors -application de.philippkatz.knime.jsondocgen.application.JsonNodeDocumentationGenerator -destination docs_by_generator -plugin org.knime.expressions.baseThe text was updated successfully, but these errors were encountered: