ivy dependency not working on windows or linux, native TF code not found on classpath
Nessuno ha ancora preso questa issue.
- Lingua principale
- Java
- Stelle
- 928
- Fork
- 227
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template
System information
- OS Platform and Distribution (e.g., Linux Ubuntu 16.04 x86_64): Linux Ubuntu 23.04_ x86_64
- TensorFlow installed from (source or binary): binary
- TensorFlow version: 0.4.2
- Java version (i.e., the output of
java -version): 1.8.1 - Java command line flags (e.g., GC parameters):
- Installed from Maven Central?: Yes, via ivy
- Bazel version (if compiling from source):
- GCC/Compiler version (if compiling from source):
- CUDA/cuDNN version:
- GPU model and memory:
Describe the problem
I'm trying to use tensorflow 2 with ivy.xml in java project. The problem is that the maven download is not complete. It only downloads either 1. no native platform, or 2. if I specify 2 platforms (windows and linux), it only downloads one of them. AND 3. when I manually download the relevant jars, it cannot find the native hooks.
Provide the exact sequence of commands / steps that you executed before running into the problem
I first tried ivy using these dependencies in various combinations, each time making sure to delete existing tensorflow jars from my ivy local cache folder:
<dependency org="org.tensorflow" name="tensorflow-core-api" rev="0.4.2" m:classifier="linux-x86_64-gpu"/>
<dependency org="org.tensorflow" name="tensorflow-core-api" rev="0.4.2" m:classifier="windows-x86_64-gpu"/>
<dependency org="org.tensorflow" name="tensorflow-core-api" rev="0.4.2"/>
Since this did not work (I never got the full set of native jars), I downloaded the jars and put them in my local project jars folder, which is on the classpath.
jars/tensorflow-core-api-0.4.2.jar
jars/tensorflow-core-api-0.4.2-linux-x86_64-gpu.jar
jars/tensorflow-core-api-0.4.2-windows-x86_64-gpu.jar
These jars are added to the project classpath in netbeans 8.2 project dialog
Any other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.
Here is the log output:
WARNING: java.lang.NoClassDefFoundError: java.lang.ClassNotFoundException: org.tensorflow.internal.c_api
at org.bytedeco.javacpp.Loader.load(Loader.java:918)
at org.bytedeco.javacpp.Loader.load(Loader.java:870)
at org.tensorflow.NativeLibrary.load(NativeLibrary.java:48)
at org.tensorflow.TensorFlow.<clinit>(TensorFlow.java:156)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at org.tensorflow.SavedModelBundle.<clinit>(SavedModelBundle.java:651)
at net.sf.jaer.eventprocessing.filter.MLPNoiseFilter.loadNetwork(MLPNoiseFilter.java:720)
at net.sf.jaer.eventprocessing.filter.MLPNoiseFilter.initFilter(MLPNoiseFilter.java:550)
at net.sf.jaer.eventprocessing.filter.NoiseTesterFilter.initFilter(NoiseTesterFilter.java:1073)
at net.sf.jaer.eventprocessing.FilterChain.initFilters(FilterChain.java:454)
at net.sf.jaer.graphics.AEViewer.setChip(AEViewer.java:5863)
at net.sf.jaer.graphics.AEViewer.constructChip(AEViewer.java:1020)
at net.sf.jaer.graphics.AEViewer.setAeChipClass(AEViewer.java:928)
at net.sf.jaer.graphics.AEViewer.<init>(AEViewer.java:520)
at net.sf.jaer.JAERViewer$RunningThread.run(JAERViewer.java:231)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:756)
at java.awt.EventQueue.access$500(EventQueue.java:97)
at java.awt.EventQueue$3.run(EventQueue.java:709)
at java.awt.EventQueue$3.run(EventQueue.java:703)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:726)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)
Caused by: java.lang.ClassNotFoundException: org.tensorflow.internal.c_api
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:348)
at org.bytedeco.javacpp.Loader.load(Loader.java:913)
... 29 more
Here is the screenshot showing contents of the linux native jar:
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Direzione di ricerca
Inizia dalle dichiarazioni delle dipendenze Ivy e dai tre jar TensorFlow 0.4.2 elencati, quindi segui lo stack trace da org.tensorflow.NativeLibrary.load attraverso org.bytedeco.javacpp.Loader.load. Verifica perché gli artefatti nativi specifici della piattaforma non espongono org.tensorflow.internal.c_api nel classpath. Il lavoro è completato quando le dipendenze native richieste vengono risolte per le piattaforme segnalate e l'inizializzazione di SavedModelBundle non genera più ClassNotFoundException.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- java
- Ambito
- build-system
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 35/100