| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
Nothing appears to be using this, based on codesearch.o.o, and it's
useless. Drop it.
Change-Id: I9ce39e69a6fdb2e216da9fd903b5dc8aa7eaab80
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Sem-Ver: api-break
|
|
|
|
|
|
|
| |
No need for this in a Python 3-only world.
Change-Id: I8923f2b87c1bd114b8c55210100c7485a0de8f28
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
|
|
|
|
|
|
|
| |
We don't need it anymore. Drop references to it.
Change-Id: Icade65ce11f4dbbf2d2f903985cea941cb7e8cf7
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
|
|
|
|
|
|
|
|
|
|
| |
Per [1], this is the latest supported version of SQLAlchemy. 1.1.x and
earlier are EOL.
[1] https://www.sqlalchemy.org/download.html#relstatus
Change-Id: I63e4baf772be9ddfb787ac3aff01fcaddf7b901c
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
pbr has generated these for some time.
Change-Id: I93ff365c90b5ca953937311f69650e89adc65935
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Change-Id: I7bbab4f96391828d0b0e095a152bdacca6585e3c
|
|\ \ \
| |/ / |
|
| | |
| | |
| | |
| | | |
Change-Id: I4245e31483865766c20443a79165f7d98bb5348a
|
|/ /
| |
| |
| | |
Change-Id: Ic9424cf4e908edd794f2b7c1f6e3dd4316b6362c
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
OpenStack is dropping the py2.7 support in Ussuri cycle.
Complete discussion & schedule can be found in
-
http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010142.html
- https://etherpad.openstack.org/p/drop-python2-support
Ussuri Communtiy-wide goal:
https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html
Change-Id: I02e2d11d38d2aa4182e8d466519b99f05943701f
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
unittest2 was needed for Python versions <= 2.6, so it has not been
needed for quite some time now. See unittest2 note on:
https://docs.python.org/2.7/library/unittest.html
This drops unittest2 in favor of the standard unittest package.
Change-Id: I40882f14ff2ac121764b432fc745b21ae751e321
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
move 'basepython' to the top-level 'testenv'
Change-Id: I37c608d9da6bffe2f24e0e1fbeb4e8d350089850
|
|/ /
| |
| |
| |
| |
| |
| | |
For more information about this automatic import see:
https://docs.openstack.org/i18n/latest/reviewing-translation-import.html
Change-Id: I68d368e2e1d3eb5f0fc608b79f242a6b680570e1
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is pretty ugly to look at, but essentially I've gone and replaced
all occurences of
foo.bar(call_arg).AndReturn(return_arg)
with a mock of 'foo', followed by:
mock_foo.return_value = return_arg
<call>
mock_foo.assert_call_once_with(call_arg)
Or 'side_effect'/'assert_has_calls' for functions that are called
multiple times.
Change-Id: I8960368d56604315d271aa958c5c6c361e512918
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
|
|/
|
|
| |
Change-Id: Icb2c88dc18843cbf2f5be08d635d5ba10f36f360
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
SQLAlchemy 1.4 will be changing the method by which it
renders an IN expression such that the bound parameters
are not fully rendered until the statement is executed,
rather than when the statement is compiled into its initial
string form [1]. Adjust tests which are asserting the presence
of IN expressions based on the compiled form to allow for an
arbitrary expression within the parenthesis.
[1] https://github.com/sqlalchemy/sqlalchemy/issues/4645
Change-Id: I8640ad0cbd96647ed74678631479190146bd908e
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Some options are now automatically configured by the version 1.20:
- project
- html_last_updated_fmt
- latex_engine
- latex_elements
- version
- release.
Change-Id: I2c3a36fbc020d41c5eaa09008a0586142a63d6ba
|
|\ \ |
|
| |/
| |
| |
| |
| | |
Change-Id: I6ea68fb17ceac23337bfb7405eb3f7a6df8b61f2
Closes-Bug: 1851797
|
|\ \
| |/
|/| |
|
| |
| |
| |
| | |
Change-Id: I57540c744ed6aa1edfea50b86d0900fdf59ceff9
|
|/
|
|
|
|
|
|
|
|
|
|
| |
Sphinx 1.8 introduced [1] the '--keep-going' argument which, as its name
suggests, keeps the build running when it encounters non-fatal errors.
This is exceptionally useful in avoiding a continuous edit-build loop
when undertaking large doc reworks where multiple errors may be
introduced.
[1] https://github.com/sphinx-doc/sphinx/commit/e3483e9b045
Change-Id: Idaca0bc97e33e0a080de612420177b5e102c628c
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add file to the reno documentation build to show release notes for
stable/train.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/train.
Change-Id: I377ad03a73b88407d0e70315cbd0162bb9dc356b
Sem-Ver: feature
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
Fixed one test that is using the deprecated, removed in
SQLAlchemy 1.4 contextual_connect method.
Change-Id: Ic9d23be6742bfc0aed4e032f3e1e01d5acf90131
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is a mechanically generated patch to ensure unit testing is in place
for all of the Tested Runtimes for Train.
See the Train python3-updates goal document for details:
https://governance.openstack.org/tc/goals/train/python3-updates.html
Change-Id: Ie47812bec5284d447a2f9c339a5b29d49d83ab53
Story: #2005924
Task: #34234
|
|/
|
|
|
|
|
|
|
| |
It seems that this is needed in order to run the py37 tests in the
gate. See the attached bug for the full error output from a failed
run.
Change-Id: Iba278fc17d0121cf6d8b48c42a18c6ccf73de6c8
Closes-Bug: 1839679
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As it was announced [1] global bindep-fallback.txt was removed and now
projects need to have a local bindep.txt to be able to install binary
dependencies for testing.
In test jobs the script tools/test-setup.sh is called which requires
mysql and postgres servers and clients to be installed.
[1] http://lists.openstack.org/pipermail/openstack-discuss/2019-June/007272.html
Change-Id: I6b237ecf55ff440b5f5c956ee849a1927bb15441
|
|
|
|
|
|
|
|
|
|
| |
SQLAlchemy 1.4 will be adding stricter rules to Connection objects
such that a new transaction cannot be started while an old one hasn't
been cleared. Ensure this particular test fixture clears
the "savepoint" transaction first before starting a new one.
References: https://github.com/sqlalchemy/sqlalchemy/issues/4712
Change-Id: Idcb616fd3add4d58f22b91865cec8a54fe492093
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
All the integration testing has been moved to
Bionic now[1] and py3.5 is not tested runtime for
Train or stable/stein[2].
As per below ML thread, we are good to drop the py35
testing now:
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005097.html
[1] http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004647.html
[2]
https://governance.openstack.org/tc/reference/runtimes/stein.html
https://governance.openstack.org/tc/reference/runtimes/train.html
Change-Id: Iba00d9fadaf3a682f3e4bb2dea335dfc74cf030d
|
|
|
|
|
|
|
|
| |
Gets us away from the old pbr functionality.
Some cleanup of tox.ini is included along the way.
Change-Id: Ia228f8ee49f31f88fa2a66f2aad3a3921c41a785
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Today, when a user uses enginefacade reader/writer decorators
he/she is forced to pass the context argument as the
first positional argument. performing a decorated function
call with this argument passed as a keyword would lead to
an out of range exception.
This patch proposes to add support for the context argument
to be passed as a keyword argument in decorated functions.
e.g
@enginefacade.reader
def foo(context):
...
foo(context=ctxt) <- will now be possible
Change-Id: Ief0b71bf9a7eb75935612431bdcc26d33bce852d
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Bandit 1.6.0 accidentally changed how the exclusion list option is
handled and breaks our use of it. Cap to the previous version until
Bandit has fixed the problem.
Sphinx 2.0 no longer works on python 2.7, so we need to start capping
it there as well.
Change-Id: If86c82e0f4a519baca664af79352846c4af9a01c
Reference: https://github.com/PyCQA/bandit/pull/489
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
Change-Id: Iff5086fee8c94325aa16a3b5727dac66a64478ec
Closes-Bug: #1825933
|
|\ \ \
| |/ /
|/| | |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The database option min_pool_size is not actually
used in oslo.db.
This is a folllow up to
Ib07b7b4200b5cf3a34b8eed441e6754da7d446cf
Change-Id: I89754e9e4b42c45259729b0b0bb0a4bf464a981c
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html
Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This addresses two sources of deprecation warnings.
The collections package has moved ABC classes under collections.abc. Six
does not support this move yet, so this updates the code to try to
import from the newer locations, and if that fails, import from the old
location.
Py36 is also more strict about escape sequences in strings. This happens
move often with regex strings that are valid regex but not a valid
normal string escape sequence. This addresses those errors by switching
to raw strings.
Change-Id: I4c61df6b6432b135297f38c02b4538e4ba56be51
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
|
|
|
|
|
|
|
|
| |
Earlier versions don't work with postgresql 10, which is now showing
up in distros.
Change-Id: I56589eb4ac55bec426d16f355398720f2994edcb
Closes-Bug: 1821400
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add file to the reno documentation build to show release notes for
stable/stein.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/stein.
Change-Id: Idedd684db42cbda300e69e628e96e4f9475f7df4
Sem-Ver: feature
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We currently see a lot of warnings like this from
the soft_delete() method:
sqlalchemy.exc.SAWarning: Evaluating non-mapped column expression
'updated_at' onto ORM instances; this is a deprecated use case.
Please make use of the actual mapped columns in ORM-evaluated
UPDATE / DELETE expressions.
This is because the "evaluate" synchronization strategy would like
to search for objects and update them based on the UPDATE criteria
passed, however the columns given, literal_column('id'),
literal_column('updated_at'), are not mapped to anything. The
evaluator has to make a guess that the string contained in these
expressions should be matched to a mapped attribute on the given
entity and this guess was first removed in [1], then added back in
[2] with a warning (likely since oslo.db is invoking it).
This uses the actual entity-mapped column for the query rather
than the literal string column.
[1] https://docs.sqlalchemy.org/en/latest/changelog/changelog_12.html#change-b1e620dece39006ab44c47044e9a6fee
[2] https://docs.sqlalchemy.org/en/latest/changelog/changelog_12.html#change-dff3a469788c81a46440584406cb22be
Change-Id: I192e84ce757d12d33085a209dd58d8ea46fb90fb
Closes-Bug: #1814199
|
|/
|
|
|
|
|
|
|
|
|
| |
MariasDB/Galera cluster server produces an error like:
(1213, u'Deadlock: wsrep aborted transaction')
which is currently not detected properly and, thus, not retried.
Change-Id: Ifb4a81d50e490e734e12986e51efd6bd3c339c31
Signed-off-by: Pierre-Samuel Le Stang <pierre-samuel.le-stang@corp.ovh.com>
|