This is an automated email from the ASF dual-hosted git repository.
asf-gitbox-commits pushed a change to branch db/solr_nones
in repository https://gitbox.apache.org/repos/asf/allura.git
discard ab558532a stringify some ids
discard e0acd3bab don't pass sort=None etc to solr
add 1f290c62b add docker/compose health checks and use --wait to check them
new 2b55895aa get chained exception details into errormiddleware output
new d1ccfecc7 don't pass sort=None etc to solr
new 8e104085e stringify some ids
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (ab558532a)
\
N -- N -- N refs/heads/db/solr_nones (8e104085e)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
Allura/allura/lib/patches.py | 23 +++++++++++++++++++++--
Allura/allura/lib/search.py | 2 +-
Allura/docs/getting_started/installation.rst | 4 ++--
Dockerfile | 3 +++
docker-compose-prod.yml | 13 ++++++++++++-
docker-compose.yml | 14 ++++++++++++++
scm_config/git-http/Dockerfile | 5 ++++-
scripts/jenkins-run.sh | 2 +-
8 files changed, 58 insertions(+), 8 deletions(-)
