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
When i run java -jar matching-eval-client-latest.jar --systems logmap-melt-oaei-2021-web-latest.tar --track conference
the docker matcher is not correctly loaded (and an HTTP / API matcher is assumed which results in errors). In the last years the matchers were *.tar.gz, but this year they are *.tar.
To Reproduce
Steps to reproduce the behavior:
run the command provided above.
I used the one from the link in the documentation.
Full log output
Please paste the FULL log output (which is generated during your run) below:
java -jar matching-eval-client-latest.jar --systems logmap-melt-oaei-2021-web-latest.tar --track http://oaei.webdatacommons.org/tdrs/ dh 2024all
WARNING: sun.reflect.Reflection.getCallerClass is not supported. This will impact performance.
2024-09-19 13:44:03,777 INFO MeltUtil - Welcome to
__ __ ______ _ _______
| \/ | ____| | |__ __|
| \ / | |__ | | | |
| |\/| | __| | | | |
| | | | |____| |____| |
|_| |_|______|______|_| 3.4-SNAPSHOT (git commit 403d384)
2024-09-19 13:44:03,784 INFO Track - Track cache folder is: /Users/felixernst/oaei_track_cache
Recognized HTTP URL matcher endpoint:
../Matcher/DockerMatcher/logmap-melt-oaei-2021-web-latest.tar
Exception in thread "main" java.lang.NullPointerException: Cannot invoke "String.equals(Object)" because the return value of "java.net.URI.getScheme()" is null
at de.uni_mannheim.informatik.dws.melt.matching_base.external.http.MatcherHTTPCall.<init>(MatcherHTTPCall.java:105)
at de.uni_mannheim.informatik.dws.melt.matching_base.external.http.MatcherHTTPCall.<init>(MatcherHTTPCall.java:125)
at de.uni_mannheim.informatik.dws.melt.matching_base.external.http.MatcherHTTPCall.<init>(MatcherHTTPCall.java:135)
at de.uni_mannheim.informatik.dws.melt.matching_eval_client.Main.main(Main.java:178)
This can be solved for now by renaming the (OAEI 2024) files from .tar to .tar.gz.
The text was updated successfully, but these errors were encountered:
The files that are uploaded are usually tar.gz files but sometimes the file ending is just not correct (e.g. xxx.tar.yyyy.gz).
Up to now now tar.gz files are accepted. Thus for a quick fix, just change either the file ending (or in case it is really only a tar file, gzip it first).
I leave the issue open to improve the client to also accept tar files.
Describe the bug
When i run
java -jar matching-eval-client-latest.jar --systems logmap-melt-oaei-2021-web-latest.tar --track conference
the docker matcher is not correctly loaded (and an HTTP / API matcher is assumed which results in errors). In the last years the matchers were *.tar.gz, but this year they are *.tar.
To Reproduce
Steps to reproduce the behavior:
run the command provided above.
I used the one from the link in the documentation.
Full log output
Please paste the FULL log output (which is generated during your run) below:
This can be solved for now by renaming the (OAEI 2024) files from .tar to .tar.gz.
The text was updated successfully, but these errors were encountered: