To get the dimension value, urllib.parse.unquote() func is used in
MonascaProxyView._convert_dimensions. urllib.parse.unquote() func
requires str only until python3.8.
Change-Id: Ib52b4c2065dee10a96f1644cf1ec474b60147d87
This patch update decorator version to 4.4.2 in
lower-constraints.txt to fix the lower-constraints job.
It also update horizon version in requiremnets.txt to
sync with horizon version in lower-constraints.txt.
Change-Id: Ifacecc79608df3d052679779bc7a9f1338d2d2f6
This method is ussed in Grafana Dashboards with Horizon
Authentication. The panel wasn't able to display the metrics
when dimensions are used as filter.
Change-Id: Id6e92a371df39d2dfcfe8125ef50a76e295ab223
UPPER_CONSTRAINTS_FILE is old name and deprecated.
This allows to use upper-constraints file as more
readable way instead of UPPER_CONSTRAINTS_FILE=<lower-constraints file>.
For more info. please refer [1].
[1] https://zuul-ci.org/docs/zuul-jobs/python-roles.html#rolevar-tox.tox_constraints_file
Change-Id: I5403b96d4dd0faac9f1295d57a1680a7d452c7b1
This patch is a clean-up patch for refactor-error-messages bp
which remove the exception message from base message otherwise
the same exception message display twice like
this https://ibb.co/XyFWMdz .
Depends-On: https://review.opendev.org/#/c/708069/
Change-Id: I1ddea97cdcaf4142d9dabcf4a629e805a9c1e152
The mock third party library was needed for mock support in py2
runtimes. Since we now only support py36 and later, we can use the
standard lib unittest.mock module instead.
Bump horizon to 18.3.0 in lower-constraints.txt since it is the
first version with "Use unittest.mock instead of third party mock"
change [1]
[1] 7eeb9e14f9
Change-Id: Ic64fffaeded18ac11ce438c77526e60a37aeaa1d
flake8 new release 3.8.0 added new checks and gate pep8
job start failing. hacking 3.0.1 fix the pinning of flake8 to
avoid bringing in a new version with new checks.
Though it is fixed in latest hacking but 2.0 and 3.0 has cap for
flake8 as <4.0.0 which mean flake8 new version 3.9.0 can also
break the pep8 job if new check are added.
To avoid similar gate break in future, we need to bump the hacking min
version.
- http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014828.html
Change-Id: I7028aa296303e1dd138bcbc511072a4e4f228aad
Horizon requires pyScss>=1.3.7 [1] but lower-constraints.txt
in monasca-ui uses pyScss 1.3.4 which can cause the
failure in future. So this patch update pyScss version in
lower-constraints.txt to sync the change.
[1] https://review.opendev.org/#/c/715241/
Change-Id: I792c90993db19ecf4821ff45da0279658bae4719
Make a few cleanups:
- Remove python 2.7 stanza from setup.py
- Add requires on python >= 3.6 to setup.cfg so that pypi and pip
know about the requirement
- Remove obsolete sections from setup.cfg:
* Wheel is not needed for python 3 only repo
* Some other sections are obsolete
- Update classifiers
- Update requirements, no need for python_version anymore
- Remove sphinx requirements, the repo has no docs
Change-Id: I3ee6abac9b5c4c639521bb2834a104bc53ce93ed
The repo is Python 3 now, so update hacking to version 3.0 which
supports Python 3.
Fix problems found by updated hacking version.
Remove hacking and friends from lower-constraints, they are not needed
for co-installing.
Change-Id: Ibef3bbaceb61612d678c542bc8c95da24a7e2c87
Django 1.11 ends its extended support in April 2020 (which is before
Ussuri release), so horizon drops Django 1.11 support in Ussuri.
tox envs for non-primary Django versions are no longer needed in tox.ini
as testing environments for non-primary Django versions are setup in
the zuul jobs now.
horizon>=17.1.0 is required to use Django 2.2. requirements.txt and
lower-constraints.txt are updated accordingly. for more info. please
refer [1].
Depends-On: https://review.opendev.org/#/c/700733/
[1] https://etherpad.openstack.org/p/Enable_Django22_support_in_Horizon_Plugin
Change-Id: I3cd4ad5c3fe590cb1522b2be1b2059d7c70b45cc
babel extractors are now registered via python entry points,
so there is no need to declare babel extractors in babel configs.
This change is important to make translation work in Django 2.2.
django-babel does not work with Django 2.2 and looks unmaintained
for over two years. The horizon team is thinking to switch the extractor
to enmerkar (a fork of django-babel) to make extraction of translation
string work again near future. It is important to drop the extractor
definition to make the transition smooth.
Change-Id: I84d36a14b779a510bea5a24d991192016ae73273
OpenStack Proposal Bot
OpenStack Release Bot