yahoo-eng-team team mailing list archive

[Akihiro Motoki <1600788@xxxxxxxxxxxxxxxxxx>]

Horizon does not use oslo.log for logging. Horizon depends on Django and
logging is also handled via django and python standard logging. In the
horizon messaging policy, logging messages are not translated and other
user visible message are translated via django translation marker. (Note
that _ has a different meaning in horizon.)

There were similar situation in horizon, but it was clean up as bug
1406333.

Marking this as Won't Fix in horizon. In horizon there is nothing to do
more.

** Changed in: horizon
       Status: Confirmed => Won't Fix

** Changed in: horizon
     Assignee: weiweigu (gu-weiwei) => (unassigned)

** Changed in: horizon
    Milestone: next => None

** Changed in: horizon
   Importance: Low => Undecided

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1600788

Title:
  If a common message is not being used, they should each be treated
  separately with respect to choosing a marker function

Status in Glance:
  Fix Released
Status in glance_store:
  Fix Released
Status in OpenStack Dashboard (Horizon):
  Won't Fix
Status in Magnum:
  Fix Released
Status in neutron:
  Triaged
Status in oslo.log:
  Fix Released
Status in Solum:
  New

Bug description:
  Follow the
  http://docs.openstack.org/developer/oslo.i18n/guidelines.html

  For example, do not do this:

  # WRONG
  LOG.exception(_('There was an error.'))
  raise LocalExceptionClass(_('An error occured.'))
  Instead, use this style:

  # RIGHT
  LOG.exception(_LE('There was an error.'))
  raise LocalExceptionClass(_('An error occured.'))

  And oslo.log has the problem,we shuld correct it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1600788/+subscriptions