This repo was created by accident, use deb-python-oslo.log
instead.
Needed-By: I1ac1a06931c8b6dd7c2e73620a0302c29e605f03
Change-Id: I81894aea69b9d09b0977039623c26781093a397a
Many assertEqual sentences don't follow assertEqual(expected, actual),
this patch fix all of them.
Closes-Bug: 1604213
Change-Id: I830435ab860c7298cea64a24ef01df3e5326d00c
Now that there is a passing gate job, we can claim support for
Python 3.5 in the classifier. This patch also adds the convenience
py35 venv.
Change-Id: I4be37bf1a97bf76a2302a4f16999e6464665dc21
Follow http://docs.openstack.org/developer/oslo.i18n/guidelines.html:
If a common message is not being used, they should each betreated
separately with respect to choosing a marker function.So this patch
is to fix it.
Change-Id: I07945d82320d9faf6dc452d49722af610330b441
Closes-Bug: #1600788
On SIGHUP the mutate_hook will be called. Call fileConfig to
reconfigure logging if log-config-append changes or the timestamp of
the file it points to changes.
Implements: bp mutable-logging
Change-Id: I8ca8e6b4e9218f3a2edaf9ecf53653d829bc0c12
Ic58dafceefde1b109721a58631c223522bf4cc9c introduces this function
for Victor's rate_limit module. I also want it for my global_filter
and mutable logging config patches so it seems sensible to have it
centrally and reuse it.
Change-Id: I9571badcfc437fb7d565d8dc9632792862e20b3f
Co-Authored-By: Victor Stinner <vstinner@redhat.com>
The deprecated decorator is very useful in situations where you have a
complete function that you want to deprecate. However it doesn't let me
simply trigger a deprecation warning in a code path that i know is
deprecated but doesn't exist in a function.
Create a standard deprecated warning function that has almost the same
signature (what becomes required) and produces the same warning and
fatal_deprecations behaviour for situations where a deprecator is not
useful.
For example:
if CONF.deprecated_value:
versionutils.deprecated_warning('deprecated_value',
as_of=versionutils.OCATA)
# do stuff
Change-Id: Ifd83cd74ac397e7bc6def11a38b46de5dff2acfa
Closes-Bug: #1590223
Pure python logging library allows to log encoded strings
but in oslo_log it causes UnicodeDecodeError for arguments
which contains unicode symbols.
Changes add additional check whether all arguments can be converted to
unicode. If it isn't possible then leave it as is.
Change-Id: I76e75c35a74b146fae52c0ea60156e1cf78540e7
Closes-Bug: #1563295
Without this patch no conversion was taking place and message containing
special characters were raising TypeError exceptions. Just like the following
example:
>>> import syslog
>>> syslog.syslog(syslog.LOG_DEBUG, u"kaboom")
>>> syslog.syslog(syslog.LOG_DEBUG, u"François Deppierraz")
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: [priority,] message string
>>>
Change-Id: I7557e016e8b9894033953bee689c79484c4a11f3
Closes-Bug: #1483842
test_tempest_set_log_file was calling tempest_set_log_file and never
resetting this value. That caused some other test to create foo.log
and not clean it up.
Change-Id: I23efe8fb89531752b01bdf9c0fbdc39c77058a51
Use new dedicated method for context aware attributes in oslo.log which
will enable future improvements for common and project specific logging
format parameters. Fall back to legacy method if not found in passed
context object and provide a deprecated warning of missing method.
Change-Id: Ica445ad5dfe9bd27dfcf1b1bcb6401a0bc9496a5
Implements: blueprint app-agnostic-logging-parameters
Depends-On: I963a6db4aef74f7348e75a642e2e195cedacecaa
Depends-On: I5450e105dc914f822a2b4c03b759a682d8b4a3e7
Depends-On: I9025770693d4b15efe4bd3556e6704326b1c915e
The watch-file option currently relies on pyinotify which makes
use of select.poll. This is eventlet incompatible so it blocks
the whole thread for TIMEOUT milliseconds every READ_FREQ seconds.
This meant that an agent/service using this option is blocked for
500 milliseconds every 1 second.
Until a non-blocking alternative can be found, this adjusts the
READ_FREQ and TIMEOUT params on the FastWatchedFileHandler to
3 and 5 respectively. So every 3 seconds, it will block for 5
milliseconds so only 0.16% of time is lost instead of 50%.
Change-Id: I6fdc0a3f1eaae39eb86440c6c4b07ca8d91f2462
Partial-Bug: #1583270
This reverts commit 7c671ea77f.
This one is causing to many issues in consuming projects
to just yet remove (even though its been deprecated for two
cycles).
Change-Id: I5486b0fe1c55f41aed5fb209214adeaca03a64fb
Change I96229438d3a2271c830bcd926326e7b4a94ccac9 removed the verbose option
in the opposite fashion from what how it was intended when the option was
deprecated. It regressed the default log level back to WARNING.
See change I306535c6ca5dbdaf9398b44697578a3a30e52111 for original reasoning
behind this deprecation. This change fixes the default level as it was
intended.
Change-Id: Ia9cd55004ce05761de733adae00554ff021794a8
This was already deprecated in Mitaka, we're now working on Newton so
I believe it can be removed.
Change-Id: I96229438d3a2271c830bcd926326e7b4a94ccac9
example LOG.exception("An Exception occurred") in both usage.py,
usage_helper.py and usage_i18n.py failed when use py34.
fix it by raising exception before calling LOG.exception().
Change-Id: I2b6ea35fbf171232fea0cc54265f8be3dc61457f
Closes-Bug: #1578071
Ie9e9a895da1a3fc62580c1febb7cd9f965bbc0f5 adds a 'mutate' flag to
options. This is the first patch to use this functionality. It marks the
'debug' option as mutable and registers '_mutate_hook' to be called
when mutate_config_files runs.
Option 'verbose' is deprecated for removal so I see no need to mark it
mutable even though it's closely related.
Change-Id: I1e7a69de169cc85f4c09954b2f46ce2da7106d90
Depends-On: Ied006631a6edbeeffae485d28eff700b13a626c1
Depends-On: I9bb2ff39dc1ed0a63bd7e7635704b34c53d32d79
Andreas Jaeger