We'd love to get patches from you!
We follow the GitHub Flow Workflow:
- Fork the project
- Check out the
master
branch - Create a feature branch
- Write code and tests for your change
- From your branch, make a pull request against
https://github.com/spotify/voyager
- Work with repo maintainers to get your change reviewed
- Wait for your change to be pulled into
https://github.com/spotify/voyager/master
- Delete your feature branch
To compile Voyager from scratch, the following packages will need to be installed:
- Python 3.7 or higher.
- A C++ compiler, e.g.
gcc
,clang
, etc.
There are some nuances to building the Voyager python code. Please read on for more information.
For basic building, you should be able to simply run the following commands:
cd python
pip install -r python/dev-requirements.txt
pip install .
To compile a debug build of voyager
that allows using a debugger (like gdb or lldb), use the following command to build the package locally and install a symbolic link for debugging:
cd python
DEBUG=1 python setup.py build develop
If you're on macOS or Linux, you can try to compile a debug build faster by using Ccache:
brew install ccache rm -rf build && CC="ccache clang" CXX="ccache clang++" DEBUG=1 python -j8 -m pip install -e .e.g.
sudo yum install ccache # or apt, if on a Debian # If using GCC: rm -rf build && CC="ccache gcc" CXX="scripts/ccache_g++" DEBUG=1 python setup.py build -j8 develop # ...or if using Clang: rm -rf build && CC="ccache clang" CXX="scripts/ccache_clang++" DEBUG=1 python setup.py build -j8 develop
To build the Java library with maven
, use the following commands:
cd java
mvn package
To build the C++ library with cmake
, use the following commands:
cd cpp
git submodule update --init --recursive
make build
We use tox
for testing - running tests from end-to-end should be as simple as:
cd python
pip3 install tox
tox
We use airspeed-velocity
for benchmarking - running all benchmarks to compare latest
commit against previous should be as simple as:
pip3 install asv
asv continuous --sort name --no-only-changed HEAD HEAD~1
To compare current commit against main
branch:
pip3 install asv
asv continuous --sort name --no-only-changed HEAD main
Please note that airspeed-velocity
can only run benchmarks against a git commit, so if
you have uncommited code that you want to run benchmarks for you need to commit it first.
We provide java test execution as a maven test step. Thus you can run the tests with:
cd java
mvn verify
To run the C++ tests, use the following commands:
cd cpp
git submodule update --init --recursive
make test
Use clang-format
for C++ code, and black
with defaults for Python code.
In order to check and run formatting within the python module, you can use tox to facilitate this.
cd python
# Check formatting only (don't change files)
tox -e check-formatting
# Run formatter for python bindings and native python code
tox -e format
If you are working on any C++ code throughout the repo, ensure you have clang-format
(version 16) installed, and then use clang-format to handle C++ formatting:
cd cpp
cmake .
# Check formatting only (don't change files)
make check-formatting
# Run formatter
make format
We also welcome improvements to the project documentation or to the existing docs. Please file an issue.
If you notice that the generated API documentation is out of date, feel free to run these commands in order to update the docs and make a PR with the changes.
While voyager
is mostly C++ code, it ships with .pyi
files to allow for type hints in text editors and via MyPy. To update the Python type hint files, use the following commands:
cd python
python3 -m scripts.generate_type_stubs_and_docs
# Documentation will be dumped into ../docs/python/
To update the javadocs for the java bindings, you can simply run:
cd java
mvn package
This will update the java documentation located in docs/java/.
When creating an issue please try to ahere to the following format:
One line summary of the issue (less than 72 characters)
### Expected behaviour
As concisely as possible, describe the expected behaviour.
### Actual behaviour
As concisely as possible, describe the observed behaviour.
### Steps to reproduce the behaviour
List all relevant steps to reproduce the observed behaviour.
If you are a first time contributor to voyager
, familiarize yourself with the:
When you're ready, navigate to issues. Some issues have been identified by community members as good first issues.
There is a lot to learn when making your first contribution. As you gain experience, you will be able to make contributions faster. You can submit an issue using the question label if you encounter challenges.
By contributing your code, you agree to license your contribution under the terms of the LICENSE.
Read our Code of Conduct for the project.
Try updating your version of pip
:
pip install --upgrade pip
You may have networking issues. Check to make sure you do not have the PIP_INDEX_URL
environment variable set (or that it points to a valid index).
Ensure you have the Python development packages installed.
You will need to find correct package for your operating system. (i.e.: python-dev
, python-devel
, etc.)
- Ensure that you have Tox version 4 or greater installed
- or set
ignore_basepython_conflict=true
intox.ini
- or install Tox using
pip
and not your system package manager