-
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
Strange behaviour of CUDS remove #638
Labels
Comments
Yes it seems that |
For completeness, could you add the whole error stack from the |
Updated my comment |
This was referenced Jun 30, 2021
kysrpex
added a commit
that referenced
this issue
Jul 15, 2021
Allow the CUDS objects to be initialized with extra triples, instead of having to add them after already having created the object. This solves #668 because previously, the class of the `Wrapper` CUDS objects was not defined on the server until after having spawned the CUDS object, because it is created empty and then filled with triples. This caused it to go to the added buffer, ignoring the changes introduced in #638, which solved the issue for local sessions, for which the CUDS objects are not created first empty and then filled with triples.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the following case, shouldn't the object be removed from the DB ?
If I use the wrapper.session.delete_cuds_object(cuds) function
pretty_print(wrapper) drows an arrow:
How can I remove a CUDS from the DB ?
The text was updated successfully, but these errors were encountered: