Joshua Send

Results 81 issues of Joshua Send

## What is the goal of this PR? We fix the traversal behaviour under queries like `(friend: $x, friend: $y)` when the role players `$x` and `$y` actually are the...

type: bug
priority: high
domain: traversal

## Problem to Solve Forwardable iterators usually throw an exception when trying to seek forward to a target that is behind the last value returned. However, our storage iterators (`RocksIterator`)...

type: refactor
priority: high

## What is the goal of this PR? We identify and correct a mismatch between the execution of a procedure and the planner cost functions - notably the presence of...

**For the title of this PR:** please follow the grammatical rules of a usual publication title, without capitalisation (except for the first letter). Thus, the title should NOT CONTAIN CODE:...

## Problem to Solve To solve both the issue of not having explainable inferred concepts (for example when querying `match $x has $y`, where $x is inferred as well but...

type: refactor
priority: high
domain: reasoner

## Problem to Solve Rule materialisation (PUT) operations currently perform an exact lookup of the `then` of a rule. However, it's possible that existing facts are inserted that are actually...

type: refactor
priority: high
domain: reasoner

## Problem to Solve After resolving #6194 , the only bottleneck that prevents large rules will be the validation of these rules: the validation that every possible set of types...

type: refactor
priority: high
domain: reasoner

## Problem to Solve The `ReasonerProducer.produce()` method contains the following assertion: ``` assert this.sink == null || this.sink == sink; ``` however, this is unidiomatic and indicates that the sink...

type: refactor
priority: medium
domain: reasoner

## Problem to Solve In various situations, it would be useful to "carry forward" certain constraints from a query that is being unified into a rule. In the Reasoner 2.0...

type: refactor
priority: medium
domain: reasoner

## Problem to Solve Reasoner currently reads a lot of vertices via `get()` by IID, based on the IIDs added to the query. These are present in the `params` object...

type: feature
priority: high
domain: reasoner