The developer of the website I intend to scrape information from is sloppy and has left a lot of broken links.
When I execute an otherwise effective Ferret script on a list of pages, it stops altogether at every 404.
Is there a DOCUMENT_EXISTS or anything that would help the script go on?

Problem to Solve

At the moment Grakn user of the Docker container may not know how to capture logs from inside a running docker container - especially important when the run has failed.

Current Workaround

There may not be a clean one, but in a case, we could log into the docker container:

$ docker exec -it [container id] /bin/bash
$ cd /path/to/logs
$ [some how upload via 

I haven't seen this in the documentation, but following the tutorial and then inserting nodes with a large-ish string as an attribute intended for Full Text Search (query) - is there a max string length for attribute values? I was trying to to implement a hybrid of graph and full text search, but insertion alone was taking seconds per page (HTML)?

The AtomTable uses a mutex to guard access to the TypeIndex. This mutex could be mostly avoided by using a concurrent hash map. The one described here: https://preshing.com/20160201/new-concurrent-hash-maps-for-cpp/ seems like a good choice. implementing this requires

• Copying the concurrent hash map source to cog-utils
• Modifying TypeIndex to use it.
• Removing the mutex lock in `AtomT

If you issue :help on the repl you get a list of available commands, among others. But the list is incomplete, e.g. :modules, :undeclare or :unimport are missing.

I ran into problems with the extremely long APP_CLASSPATH variable in joern-parse.bat when running joern-cli on Windows. The command was too long and the script would die when trying to set the classpath. I got around it by simply passing a wildcard (%APP_LIB_DIR%/*) to the -cp argument at the end of the script.

I'd file a PR but I can't find the script in this repo.

People have to scroll too much on the GitHub page to even get to the README

• untabify
• indent
• align where needed

Hi, Is it possible to add in readme more information about support?

• What are the feature necessary for LDflex to work?
• Is Node supported?
• Are browsers supported? Which ones?
• Can polyfills help?

What should it be called?

• "Array traversal operator": This is what we've always(?) called it
• "Projection operator": I thought about this earlier and it makes some sense. It's very similar to a projection (in the sense that it changes a stream of data); the only difference is that the output can be any value (not only an object).

How do we specify the semantics

There are three

Right now, we restrict grammar to disallow statements such as match $x; get. When building with graql, this is still allowed (Graql.match(var("x")).get()) when it should not be.

Further restrictions are currently built into Grakn's match clause validation at runtime, but not checked elsewhere - such as match $x != $y; get; which does a n^2 scan of the database. We could push this into Gra

Implement insert_, update, deleteFrom in the module Selda.SQLite3.Aff

The code documentation is scattered at the moment. The README now points to querycert.github.io for documentation. We should have a well understood process to produce documentation, and a clear entry point for both developers (in the code) and users (in the place where the README points to).

Some of the work items include:

• Document code documentation generation for developers (point to c