You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Traceback (most recent call last):
File "Absent.java", line 47, in com.google.common.base.Absent.get
Exception: Java Exception
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/Users/runner/work/eddy/eddy/eddy/plugins/ontology-importer/ontology_importer.py", line 1158, in doOpenOntologyFile
File "/Users/runner/work/eddy/eddy/eddy/plugins/ontology-importer/ontology_importer.py", line 1010, in doOpenOntologyFile
java.lang.java.lang.IllegalStateException: java.lang.IllegalStateException: Optional.get() cannot be called on an absent value
Affected Versions
3.5, 3.5.1
Installation
macOS dmg
Operating System
Windows
Operating System Version
macOC 12.6
Operating System Architecture
x86_64
Log
No response
The text was updated successfully, but these errors were encountered:
Idealmente direi di no, però per evitare situazioni di errore che poi ci tocca gestire, potremmo anche pensare che se c'è modo di generarne una (in stile protege per intenderci), lo facciamo.
Altrimenti comunque cerchiamo di lanciare un messaggio di errore parlante.
Ho messo una proposta di fix nella PR allegata, al momento uso la URI del file contenente l'ontologia per permettere al db di identificarla. Fatemi sapere che ne pensate.
Backport of 81e8c69
If the ontology to import is anonymous, set the ontology id to be
the local file uri as the ontology iri, and no version iri.
Fixes#270
Describe the bug
Scegliendo la modalità di creazione di una ontologia da file OWL, Eddy restituisce un errore.
Reproduction Steps
Allego l'ontologia che genera l'errore.
GPTdocu.owl.zip
Expected Result
No response
Actual Result
Stacktrace dell'errore:
Affected Versions
3.5, 3.5.1
Installation
macOS
dmg
Operating System
Windows
Operating System Version
macOC 12.6
Operating System Architecture
x86_64
Log
No response
The text was updated successfully, but these errors were encountered: