This is an automated email from the ASF dual-hosted git repository.
dill0wn pushed a change to branch dw/8455-part2
in repository https://gitbox.apache.org/repos/asf/allura.git
discard 50aa084c8 [#8455] remove @with_setup
discard b92975160 [#8455] converted yield test to pytest.mark.parametrize
discard e9e7bd182 [#8455] added pytest.ini
discard 2de9bcef4 [#8455] converted the remaining modules fully to pytest
discard 2717ae0aa [#8455] ran nose2pytest on Forge* and AlluraTest modules
discard be8e22a97 [#8455] allura pytest - fix misc test failures that popped
up during pytest conversion
discard fae235ff0 all trivial failures resolved for ./Allura, only legit
failures remain
discard 4dca14e72 All tests in ./Allura collecting, and test_auth completely
passing
discard 54cc022b7 first substantial test file mostly passing under pytest
discard 941177771 8455 nose2pytest for ./Allura
add 27e1314ef [#8472] added extra debug info to find out why the query is
returning zero results
add 6e686f31a [#8472] update on how query is constructed, since mongo
cares about dict order, but we don't here
add 299dc4070 [#8470] added default csp headers and configurable options
to add additional frame-src and form-action
add 5f3a3c86f [#8470] removed config globlas for csp and updated
middleware code
new 7b922cbc2 8455 nose2pytest for ./Allura
new e2b092d00 first substantial test file mostly passing under pytest
new 2516aded4 All tests in ./Allura collecting, and test_auth completely
passing
new 37dfac059 all trivial failures resolved for ./Allura, only legit
failures remain
new 97e66e8bb [#8455] allura pytest - fix misc test failures that popped
up during pytest conversion
new c5bd07786 [#8455] ran nose2pytest on Forge* and AlluraTest modules
new 1471a62df [#8455] converted the remaining modules fully to pytest
new 5d4b6aed4 [#8455] added pytest.ini
new d4b106f85 [#8455] converted yield test to pytest.mark.parametrize
new 02d53babf [#8455] remove @with_setup
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 (50aa084c8)
\
N -- N -- N refs/heads/dw/8455-part2 (02d53babf)
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 10 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/config/middleware.py | 4 ++-
Allura/allura/lib/custom_middleware.py | 55 ++++++++++++++++++++++++++++-
Allura/allura/tests/functional/test_root.py | 25 +++++++++++++
Allura/development.ini | 13 +++++++
ForgeActivity/forgeactivity/main.py | 19 +++++-----
5 files changed, 106 insertions(+), 10 deletions(-)
