engine-deprecated
engine-deprecated copied to clipboard
src-d
[DISCONTINUED] Go to https://github.com/src-d/sourced-ce/
gitbase 0.20 is in beta. We can start to work integrating it in a new feature branch, `gitbase-v0.20.0`. The breaking changes should not affect us. But it now includes a...
I'd like to apply same enhancements that done in source{d} Lookout, and also aligned with our current guidelines: - smaller `README`, with its tree biggest parts moved to its dedicate...
It could be nice for the users to link directly from engine docs to the following things: - schema (https://docs.sourced.tech/gitbase/using-gitbase/schema) - functions (https://docs.sourced.tech/gitbase/using-gitbase/functions + https://github.com/src-d/go-mysql-server/tree/3dd441325d1731821eff0495fbf63747c258b8ff#custom-functions) - supported SQL syntax (https://docs.sourced.tech/gitbase/using-gitbase/supported-syntax)
To write advanced queries it's necessary to know which standard functions are supported and which custom UDFs are implemented. But currently, there is no information about it in the documentation....
In #336, #363 we have introduced regression tests. For now they have to be run manually, to verify if a new version breaks compatibility. This way we can be aware...
Current the test of interactive SQL REPL doesn't use `icmd`, but it uses `os/exec` directly. Context [here](https://github.com/src-d/engine/pull/398#issuecomment-480360020).
Currently, the integration test for interactive SQL REPL is skipped on Windows as the library being used for opening a virtual terminal doesn't seem to support it. Context [here](https://github.com/src-d/engine/pull/398#discussion_r271843763).
Depends on #348. This issue is to determine if we can run the integration tests, on windows, on AppVeyor. And what would be needed to configure it as CI.
Context: #211. The use might be interested in knowing some extra informations that are currently in the server such as repos added, repos not added, port the server is listening...
If `srcd stop` is called and one of the containers is already being stopped/killed, `engine` exits with an `already in progress` error without eventually waiting for the operation to finish....