hydra-python-agent
hydra-python-agent copied to clipboard
HTTP-APIs
Python Hydra smart client and test console
The current printing format in client uses `show_data` method in `querying_mechanism` module. It prints the data fetched from redis in an inline manner. Instead of the current printing format we...
### I'm submitting a - [X] bug report. ### Current Behaviour: When run the query `show members` more than once. It gives the following error. ` File "/home/vedang/Downloads/learn5/hydra-python-agent/hydra_agent/redis_core/collections_endpoint.py", line 196,...
### I'm submitting a - [x] bug report. - [ ] feature request. ### Current Behaviour: Followed all steps given in README.md, and then ran `python app.py` resulted in error....
What we want is probably to use some parts from RDFlib with our Redis backend. Investigate.
This implementation algorithm could be interesting as Semantic graphs are oriented: https://vaibhavsagar.com/blog/2017/06/10/dag-toolkit/
Currently to visualise the graph created in redisgraph, one is supposed to uncomment the code [here](https://github.com/HTTP-APIs/python-hydra-agent/blob/13c24e6e6b5ac68dc194d94daec9d130f382d73b/hydra_agent/hydra_graph.py#L75). Instead maybe provide a command line argument to visualise the whole graph. @Mec-iS @xadahiya...
The client should implement Python async-await protocol in all of its functions
https://github.com/HTTP-APIs/hydrus/issues/175 (Fragments are not supported by the official Hydra spec) NOTE: resolving this issue would be off-specs but actually useful for inner working of the client
Authorization/Authentication is an important feature for the client. It should be aligned to [Auth mechanism present in hydrus](https://www.hydraecosystem.org/Auth)
The algorithm used right now for identifying the endpoints to be connected traverses the whole graph to find the ones to connect. This method is really slow. One idea is...