-
Notifications
You must be signed in to change notification settings - Fork 12
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
Error while starting server docker image #160
Comments
Hi @Yosbnwpq OBAsparql has been changed and I didn't update the templates files. Sorry 😢. |
Thanks, Maximiliano, can you give me the updated template files until the next build is ready? |
Hi @mosoriob I am also having the same issue with obasparql and OBA. When can I expect the next build to ensure this doesn't continue? |
Hi @mosoriob, I'm also having the same issue as @Yosbnwpq and @jphi545. Here's two test runs I performed with the Restrictions Example. Run 1. - followed documented process Step 1: ran java -jar oba-3.6.0-jar-with-dependencies.jar -c config-restrict.yaml Here's the log file: [+] Building 19.5s (10/11)
|
This seems to be a problem with dependencies/versions in requirements.txt and the lxml library not building / installing correctly on my OSX 12.2.1, M1 Pro (pretty much stock with minimal software installs). The identical problem and error messages also occurs on my Intel OSX 12.2.1 MacBook Pro. Here's my diagnosis....... Running through dependencies, I ran the model catalog example, and before building the server I updated the following:
Change query manager line at the end to: query_manager = QueryManager(queries_dir=QUERY_DIRECTORY,
pythonql3==0.9.61
...
|
@mosoriob Is there any update/fix for this bug please ? |
It looks like there has not been any updates yet. Sorry @tahh1, but maintaining this stack requires more time/resources than the ones we seem to have right now. The first part of the API generation seems to be working, and that can be reused as is. We'll have to see if we can fix the API implementation in the near future. |
@dgarijo I totally understand. Good luck ! |
I have created a pull request that fixes the issues above. |
Thanks @rhyslewisakl . I left a small comment. Other than that it looks ready to merge |
@rhyslewisakl Thanks a lot. I have accepted it |
Issue addressed in #161 thanks to @rhyslewisakl |
After I built the docker image from the server code and attempt to run it, I'm getting an error complaining about an expected argument to the obasparql.QueryManager class. The init.py file on the latest obasparql github does not list queries_types as one of the supported arguments:
obasparql/query_manager.py
def init(self,
endpoint,
named_graph_base,
uri_prefix,
queries_dir,
context_dir,
endpoint_username=None,
endpoint_password=None):
init.py in oba generated server code
query_manager = QueryManager(queries_dir=QUERY_DIRECTORY,
context_dir=CONTEXT_DIRECTORY,
queries_types=QUERIES_TYPES,
endpoint=ENDPOINT,
endpoint_username=ENDPOINT_USERNAME,
endpoint_password=ENDPOINT_PASSWORD,
graph_base=ENDPOINT_GRAPH_BASE,
prefix=ENDPOINT_RESOURCE_PREFIX)
In addition, the arguments "uri_prefix" and "named_graph_base" may be called "prefix" and "graph_base" in the oba generated server code, respectively.
Here are the commands I'm running to build and start the docker container
The text was updated successfully, but these errors were encountered: