Michael Pollmeier

That's true, the only problem is to make sure that there's no loopholes where we end up without a release. E.g. currently we tag the release before we publish it...

My first thought is that the `x42-c` directory doesn't exist yet - can one of you check that for me please? (I only have windows on a VM and apparently...

And while you're on it you can try the following fix: https://github.com/joernio/joern/commit/cf81fd4929468fcbeaaf96cebf7d89fdf34aa019 i.e. ``` git fetch git checkout michael/workspacemanager-fix-for-wsl sbt stage ./joern importCode(inputPath="./x42/c", projectName="x42-c") ```

@lvca or @laa, can you enlighten us?

hey, just to let you know, I've reproduced this and can confirm it's a problem. i guess it's to do with the way we lookup values in indexes... next steps:...

ok, it's actually not a bug. you're using indexes the wrong way :) an index purely on a label doesn't make sense - it's in it's own class, so there's...

if you just use `has(T.label, TestLabel)` then you can ignore that warning - it wouldn't make sense to use any index since you get all vertices from that class anyway....

Yup the warning is superfluous and could be avoided quite easily.

The function that looks up indexes is `OrientGraphStep.findIndex`. It has access to all steps in the traversal and at the moment just iterates through the `hasContainers`. See https://github.com/orientechnologies/orientdb-gremlin/blob/master/driver/src/main/java/org/apache/tinkerpop/gremlin/orientdb/traversal/step/sideEffect/OrientGraphStep.java#L157 One way...

We can remove that convention if there is a way to create vertices and edges that have the same name. Maybe that's possible with the new API, the old one...