Skip to content
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 (DataspaceSession) #662

Closed
kysrpex opened this issue Jun 30, 2021 · 4 comments · Fixed by #668
Closed

Strange behaviour of CUDS remove (DataspaceSession) #662

kysrpex opened this issue Jun 30, 2021 · 4 comments · Fixed by #668
Assignees
Labels

Comments

@kysrpex
Copy link
Contributor

kysrpex commented Jun 30, 2021

Follow-up of #638. Seems to be fixed by PR #659 for sessions other than the dataspace session (and possibly the transport session)·

See this comment for more details.

@kysrpex
Copy link
Contributor Author

kysrpex commented Jul 9, 2021

See this comment for more details.

@paulzierep I have experienced seen a similar issue in UrWerk, even after installing the fix from PR #659. It was due to the database being "contaminated" with some extra triples that were created before PR #659. However, since as far as I understand you are starting out with a new database file, this should not be the reason in your case. I'll run my own DSMS instance to debug this.

@kysrpex
Copy link
Contributor Author

kysrpex commented Jul 12, 2021

@paulzierep The PR #668 solves the issue, at least for a clean "PRIVATE_DATASPACE_DB_NAME". Should be merged in the next few days.

@kysrpex kysrpex added this to the Sprint #4 milestone Jul 12, 2021
@paulzierep
Copy link

@kysrpex great job, I will test with my DSMS set-up asap !

@yoavnash
Copy link
Member

@paulzierep maybe you could add your response to the discussion thread in #668 to make it a bit easier to follow.

@yoavnash yoavnash removed this from the Sprint #4 milestone Jul 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants