This is needed since 0f2bc375

This is needed since 629a6e52, and was lost in the conversion to requirements.in

requirements/requirements.in: update minimum versions

Closes #884

See merge request !1114

Valentin David authored Jan 22, 2019 and Jürg Billeter committed Jan 28, 2019

Job can complete before we return from `Job.span()` to
`Scheduler._spawn_job()`, so that `_active_jobs` would not yet contain
the job.

This would print a stack on the console and try to run a second time
the job which can have unexpected effects.

In order to reproduce the issue, in
`buildstream/_scheduler/jobs/job.py`, in `Job.spawn`,
add a call to `time.sleep()` right before call to
`asyncio.get_child_watcher()`.

This fixes issue #857.

Fix crash when spawned job completes very fast

Closes #857

See merge request !1095

Valentin David authored Jan 23, 2019 and Jürg Billeter committed Jan 29, 2019

Fixes #882.

Fix type of error codes in CAS server

Closes #882

See merge request !1099

Valentin David authored Jan 21, 2019 and Jürg Billeter committed Jan 29, 2019

Fixes #873

Make sure testing cache directory exists

Closes #873

See merge request !1092

This is a breaking change, as it affects behaviour that people might be
relying on. An entry has been added to NEWS.

As proposed on the mailing list, this change removes the unconditional
prompts on:

    o: bst workspace reset
    o: bst workspace close --remove-dir

If interactive, these commands would always interrupt you with a prompt
like this:

    This will remove all your changes, are you sure?

This seems like it may just save someone's work some time. It may also
condition folks to hit 'y' quickly without thinking.

This change also makes the non-interactive behaviour consistent with the
interactive behaviour in the default case. There is also the case of the
prompt configured by 'really-workspace-close-project-inaccessible',
which may be tackled in later work.

This change also removes the new config options to suppress those
prompts, and their associated news entry.

The relevant bit of the mailing list conversation is here:
https://mail.gnome.org/archives/buildstream-list/2018-December/msg00106.html

The issue to make interactive and non-interactive behaviour consistent
is here:
#744

BREAK:remove unconditional 'are you sure?' prompts

See merge request !1061

Also bump the element's version so cached artifacts would be
invalidated.

Fixes #883

filter.py: don't recurse when staging dependencies

Closes #883

See merge request !1110

`click-man` versions < 0.3.0 do not properly support multiple
entrypoints. Since this was added to `tox` after `0.3.0` was released,
`tox` should never be pulling older versions. But, let's add it here for
documentation purposes.

See
!1107 (comment 135187046)
for some background on this.

tox.ini: Specify minimum version of click-man

See merge request !1120

Chandan Singh authored Jan 29, 2019 and Chandan Singh committed Jan 31, 2019

We use output of `git --version` to determine if we can run some tests
that rely on features from newer git versions. Usually, we expect the
output to be like:

    git version 2.17.2

On some platforms, like MacOS, there could be a suffix after the version
string, so that it looks something like:

    git version 2.17.2 (Apple Git-113)

This causes things to fail like so:

    ValueError: invalid literal for int() with base 10: '2 (Apple Git-113)\n'

Fix logic around `HAVE_OLD_GIT` such that we split the output of
`git --version` without limit on how many times we split. Previously we
used to split only twice so the suffixes like `(Apple Git-113)` are not
part of the parsed version.

testutils/site.py: Support parsing more exotic git versions

See merge request !1118

This removes the need for the 'Dependency' list to then be matched
with the corresponding LoadElement and will allow iterating the
graph more easily

This simplifies the loading

Cleanup loader by linking LoadElements sooner

See merge request !1122

The unix specification for unix sockets only allocates ~100 characters
for the length of the path. This may be longer than the path for a CI
runner, or the path to a user's buildstream directory.