Additional dependencies and setup steps are required to perform a “developer installation”. You do not need to perform these steps unless you intend to contribute a code or documentation change to the nucypher codebase.
Before continuing, ensure you have
git installed (Git Documentation).
Acquire NuCypher Codebase¶
In order to contribute new code or documentation changes, you will need a local copy of the source code which is located on the NuCypher GitHub.
git for version control. Be sure you have it installed.
Here is the recommended procedure for acquiring the code in preparation for contributing proposed changes:
Use GitHub to fork the
Clone your fork’s repository to your local machine
$ git clone https://github.com/<YOUR-GITHUB-USERNAME>/nucypher.git
Change directory to
$ cd nucypher
nucypher/nucypheras an upstream remote
$ git remote add upstream https://github.com/nucypher/nucypher.git
Update your remote tracking branches
$ git remote update
Ensure Rust is Installed¶
Instruction for installing Rust can be found (here).
After acquiring a local copy of the application code and installing rust, you will need to
install the project dependencies, we recommend using either
Pip Development Installation¶
Alternately, you can install the development dependencies with pip:
$ pip3 install -e .[dev] $ ./scripts/installation/install_solc.py
Development Docker Installation¶
The intention of the Docker configurations in this directory is to enable anyone to develop and test NuCypher on all major operating systems with minimal prerequisites and installation hassle (tested on Ubuntu 16, MacOS 10.14, Windows 10).
Standard Docker Installation¶
Then you can do things like:
Run the tests:
docker-compose run nucypher-dev pytest tests/unit
Start up an Ursula:
docker-compose run nucypher-dev nucypher ursula run --dev --federated-only
Open a shell:
docker-compose run nucypher-dev bash
Try some of the scripts in
From there you can develop, modify code, test as normal.
Run a network of 8 independent Ursulas:
docker-compose -f 8-federated-ursulas.yml up
Get the local ports these ursulas will be exposed on:
To stop them…
docker-compose -f 8-federated-ursulas.yml stop
Running the Tests¶
A development installation including the solidity compiler is required to run the tests
There are several test implementations in
nucypher, however, the vast majority
of test are written for execution with
For more details see the Pytest Documentation.
To run the tests:
(nucypher)$ pytest -s
Optionally, to run the full, slow, verbose test suite run:
Setup Commit & Push Hooks¶
Pre-commit and pre-push are used for quality control to identify and prevent the inclusion of problematic code changes. They may prevent a commit that will fail if passed along to CI servers or make small formatting changes directly to source code files.
If it’s not already installed in your virtual environment, install pre-commit:
(nucypher)$ pip install pre-commit
To enable pre-commit checks:
(nucypher)$ pre-commit install
To enable pre-push checks:
(nucypher)$ pre-commit install -t pre-push
For convenience, here is a one-liner to enable both:
(nucypher)$ pre-commit install && pre-commit install -t pre-push
Making a Commit¶
NuCypher takes pride in its commit history.
When making a commit that you intend to contribute, keep your commit descriptive and succinct. Commit messages are best written in full sentences that make an attempt to accurately describe what effect the changeset represents in the simplest form. (It takes practice!)
Imagine you are the one reviewing the code, commit-by-commit as a means of understanding the thinking behind the PRs history. Does your commit history tell an honest and accurate story?
We understand that different code authors have different development preferences, and others are first-time contributors to open source, so feel free to join our Discord and let us know how we can best support the submission of your proposed changes.
Opening a Pull Request¶
When considering including commits as part of a pull request into
we highly recommend opening the pull request early, before it is finished with
the mark “[WIP]” prepended to the title. We understand PRs marked “WIP” to be subject to change,
history rewrites, and CI failures. Generally we will not review a WIP PR until the “[WIP]” marker
has been removed from the PR title, however, this does give other contributors an opportunity
to provide early feedback and assists in facilitating an iterative contribution process.
Pull Request Conflicts¶
As an effort to preserve authorship and a cohesive commit history, we prefer if proposed contributions
are rebased over
main (or appropriate branch) when a merge conflict arises,
instead of making a merge commit back into the contributors fork.
Generally speaking the preferred process of doing so is with an interactive rebase:
Be certain you do not have uncommitted changes before continuing.
Update your remote tracking branches
$ git remote update ... (some upstream changes are reported)
Initiate an interactive rebase over
This example specifies the remote name
upstream for the NuCypher organizational repository as
used in the Acquire NuCypher Codebase section.
$ git rebase -i upstream/main ... (edit & save rebase TODO list)
$ git status ... (resolve local conflict) $ git add path/to/resolved/conflict/file.py $ git rebase --continue ... ( repeat as needed )
Push Rebased History
After resolving all conflicts, you will need to force push to your fork’s repository, since the commits are rewritten.
Force pushing will override any changes on the remote you push to, proceed with caution.
$ git push origin my-branch -f
sphinx_rtd_theme are non-standard dependencies that can be installed
pip install -e . -r docs-requirements.txt from the project directory.
nucypher is hosted on Read The Docs, and is automatically built without intervention by following the release procedure.
However, you may want to build the documentation html locally for development.
To build the project dependencies locally on Linux:
(nucypher)$ make docs
or on MacOS:
(nucypher)$ make mac-docs
If the build is successful, the resulting local documentation homepage,
be automatically opened in the web browser.
If you would rather not have the homepage automatically opened, then run
make build-docs instead.
Docker builds are automated as part of the publication workflow on circleCI and pushed to docker cloud. However you may want to build a local version of docker for development.
We provide both a
docker-compose.yml and a
Dockerfile which can be used as follows:
(nucypher)$ docker-compose -f deploy/docker/docker-compose.yml build .
The versioning scheme used is inspired by semantic versioning 2.0, but adds development stage and release candidate tags. The basic idea:
MAJOR version when you make incompatible API changes
MINOR version when you add functionality in a backwards compatible manner
PATCH version when you make backwards compatible bug fixes
Two additional tags are used:
mainis the stable and released version published to PyPI and docker cloud (
developmentis the default upstream base branch containing new changes ahead of
mainand tagged with
Major/Minor Release Cycle¶
New pull requests are made into
When a commit from
developmentis selected as a release candidate the version tag is changed from
v6.1.0-rc.0). Selecting a release candidate implies a feature freeze.
The release candidate is deployed to beta testers, staging, and testnet environments for QA.
- If the candidate is suitable, it is tagged, merged into
main, and published:
All version tags are removed (
A new upstream git version tag is pushed (triggering publication on CI) (
developmentis merged into
- If the candidate is suitable, it is tagged, merged into
development version is bumped and the -dev tag is appended (
Sometimes changes are needed to fix a release blocker after a release candidate has already been selected. Normally the best course of action is to open a pull request into
Merge the pull request into
Bump the release candidate’s development number (
Redeploy beta testing environments, experimental nodes, staging, testnets, etc.
Rinse & repeat until a suitable release candidate is found.
In the event that a release blocker’s fix introduces unexpected backwards incompatibility during a minor release, bump the major version instead skipping directly to
Patches (bugfixes, security patches, “hotfixes”)¶
Sometimes urgent changes need to be made outside of a planned minor or major release. If the required changes are backwards compatible open a pull request into
main. Once the changes are reviewed and merged,
development must be rebased over
Pull request is merged into
The version’s patch number is bumped (
A new upstream tag is pushed, triggering the publication build on CI (
developmentis rebased over
main, amending the existing bumpversion commit with the new patch (this will be a merge conflict).
Rinse & repeat
This process uses
bumpversion, which can be installed by running
pip install -e .[deploy] or
pip install towncrier bumpversion.
Also note that it requires you have git commit signing properly configured.
Ensure your local tree is based on
main and has no uncommitted changes.
1. Decide what part of the version to bump.
The version string follows the format
so the options are
We usually issue new releases increasing the
2. Use the
make release script, specifying the version increment with the
For example, for a new
patch release, we would do:
(nucypher)$ make release bump=patch
3. The previous step triggers the publication webhooks on CircleCI. Monitor the triggered deployment build for manual approval.