openstack/swift - swift - OpenDev: Free Software Needs Free Tools

Change-Id: Ibbff151703395d517452c3d6927652506a9eab66

Apparently some versions of py3 will drop symlinks in the venv.
Change-Id: I77c52b6ad776ab75c4f9713290cc42a1fcb6e0f7

Change-Id: Ib853f79bc062ec550627342d0fc5b2b92029f25c

...and fix this one warning-treated-as-error that crept in since
https://github.com/openstack/swift/commit/d185b60
Change-Id: Id46ee3ab23e2703170191528427aaa2788aba1ee

Drive-by: run api-ref tox env under py3.
Change-Id: Iebce47eabcb3b198d4aa7c1b8cfaf8f53300f7f9

When the lower-constraints tox target was added, it was assumed the
install_command was just running the install and that the dependencies
and constraints were being set using "deps = ".
This fixed the install_command and deps to follow the expected pattern
so the lower-constraints job actual does install the lower constraints.
Also:
 * raise the minimum for netifaces as the existing version would fail
 to load
 * pin oslo.log to the minimum required by our minimum
 keystonemiddleware
 * fix up some error handling for ancient versions of pastedeploy
 * specify that we shouldn't install xattr on a platform we don't
 support anyway, because reasons
Change-Id: Ie78c0dabe12e01109db2b6412166c3564b87ee96
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>

Change-Id: I83f8f59023eabc97386481c18ed8bbf8fab64fa8

Change-Id: I5a0d2108d01395aedb4ac18464ed2e38ad13ce84

Change-Id: Ib1cd0659d5085ff9f8555bc08bd17a8f02f2efc0

Change-Id: Ic00273e5d3120f7daba1d3cbf084159f1e7d8bbb

Change-Id: I8f3d4d5f6976ef5b63facd9b5723aac894066b74

* name_check
 * quotas
 * ratelimit
 * read_only
 * recon
Note that the middlewares themselves seem to be fine.
Fix proxy-logging for PEP-0479.
Change-Id: If47d09e8e8c09b9f50451f93d5b0803aa58743a7

Change-Id: Id74a93f10bc5c641d62141af33bef68e503f7e04

This started with ShardRanges and its CLI. The sharder is at the
bottom of the dependency chain. Even container backend needs it.
Once we started tinkering with the sharder, it all snowballed to
include the rest of the container services.
Beware, this does affect some of Python 2 code. Mostly it's trivial
and obviously correct, but needs checking by reviewers.
About killing the stray "from __future__ import unicode_literals":
we do not do it in general. The specific problem it caused was
a failure of functional tests because unicode leaked into a field
that was supposed to be encoded. It is just too hard to track the
types when rules change from file to file, so off with its head.
Change-Id: Iba4e65d0e46d8c1f5a91feb96c2c07f99ca7c666

Change-Id: I1095262563eff92d6d0a399eb0d5f9d3045becf3

Change-Id: I2701358f9f01f368c892a010a543ecc1f17684a3

Change-Id: I83aa5d72084ca183e00dc6d69e417fba310a2c59

When looking at the tuple thing, remember that tuples are comparable
with ints in py2, but they do not compare like (100)[0]. Instead, they
are always greater, acting almost like MAX_INT. No wonder py3 banned
that practice.
We had a much of other noncomparables, but we dealt with them in
obvious ways, like adding key= to sorted().
Change-Id: I52e96406c3c1f39b98c1d81bdc057805cd1a6278

Change-Id: Ib494a974ac41f4c23c7a1125470d532c36d6f7c6

Change-Id: I9bb6e55691821891172d375d0bf097148d66010d

This does not do anything about replicator or other daemons,
only ports the server.
- wsgi_to_bytes(something.get('X-Foo')) assumes that None is possible
- Dunno if del-in-for-in-dict calls for clone or list(), using list()
- Fixed the zero-copy with EventletPlungerString(bytes)
- Yet another reminder that Request.blank() takes a WSGI string path
Curiously enough, the sleep(0) before checking for logging was
already present in the tests. The py3 scheduling merely forces us
to do it consistently throughout.
Change-Id: I203a54fddddbd4352be0e6ea476a628e3f747dc1

These are trivial, but need to be done sooner or later.
About the isEnabledFor, our FakeLogger causes this on py3:
 AttributeError: 'FakeLogger' object has no attribute '_cache'
Adding the isEnabledFor short-cuts a need for that private member.
Change-Id: I4d1df857a24801fe2a396dc003719f54d099f72c

As our PTL said, "adding some comments" "in lieu of setting up more
comprehensive projet tracking systems".
Change-Id: Ic38ff2b74366f9839e999d11050eefa753c71be3

This version scatters the cancer of WSGI strings around, but
reduces the size of the patch. In particular, we can continue
to iterate strings.
Change-Id: Ia5815602d05925c5de110accc4dfb1368203bd8d

Change-Id: Ifb737a0d3ba263b69945f30d9a31a42cb3ab645a

Change-Id: Ie8d28218b974a1b6b7b7b691f786ff1d6bdded05

Change-Id: I864de1d7ef0df07246388c7c108e1bb753e15de3

Change-Id: I6cfa6aa87b00f3edecdd2dd8b3e5ef66380e36ae

This got away from me a bit with the functional tests masquerading as
unit tests.
Change-Id: I1237c02eff96e53fff8f9661a2d85c4695b73371

Using "python setup.py check -r -s" method of checking the package has
been deprecated with the new recommendation to build the sdist and
wheel, then running "twine check" against the output.
Luckily, there is already a job that covers this that only runs when the
README, setup.py, or setup.cfg files change, making running this in the
pep8 job redundant. This covered by the test-release-openstack-python3
that is defined in the publish-to-pypi-python3 template.
More details can be found in this mailing list post:
http://lists.openstack.org/pipermail/openstack-dev/2018-October/136136.html
Change-Id: I6ff57e0146da44ec736cfe7a61d45dd31ea65b90

Change-Id: Ia2662d8f75883e1cc41b9277c65f8b771f56f902

The commands used by constraints need at least tox 2.3.2. Update to
reflect reality, which should help with local running of constraints
targets.
Change-Id: I0051938d70bdb3060981e8ce1cd2a72ca8d292ff

Another one of those almost-empty patches. This time my excuse is
that this one is needed in a couple of places (account & container).
Change-Id: Ieb8960763c64f88981b68884bfec92c17ebb4708

The the 80% of the work still remain in server and replicator,
but let's knock this out.
Change-Id: I1e1dee8f8c77212183b0ef2b574b57ad1051d57e

Gradatim Ferociter
Change-Id: I6f3fac450c14f8dbc549ab2b0645a31aa0cece89