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

Migrate to Grakn 1.6.1 #371

Closed
SamuelHassine opened this issue Dec 9, 2019 · 1 comment
Closed

Migrate to Grakn 1.6.1 #371

SamuelHassine opened this issue Dec 9, 2019 · 1 comment
Assignees
Labels
dependencies use for pull requests that update a dependency file feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@SamuelHassine
Copy link
Member

Problem to Solve

Current version of the OpenCTI platform is compatible with Grakn 1.5.9.

Current Workaround

None.

Proposed Solution

Migration to Grakn 1.6.0.

Additional Information

None.

@SamuelHassine SamuelHassine added feature use for describing a new feature to develop dependencies use for pull requests that update a dependency file labels Dec 9, 2019
@SamuelHassine SamuelHassine added this to the Release 2.1.2 milestone Dec 9, 2019
@SamuelHassine SamuelHassine self-assigned this Dec 9, 2019
@richard-julien richard-julien changed the title Migrate to Grakn 1.6.0 Migrate to Grakn 1.6.1 Dec 13, 2019
@richard-julien
Copy link
Member

typedb/typedb#5541

SamuelHassine pushed a commit that referenced this issue Dec 31, 2019
…relation (#371)

* [api] Refactor the method to get inferred relations and its explanations
* [api] Fix DeepScan
* [api] Fix inference description
* [api] Refactor the method to get inferred relations and its explanations
* [api] Fix EsLint
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Dec 31, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies use for pull requests that update a dependency file feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

No branches or pull requests

2 participants