| 2014-06-24 04:10:40 |
Christopher Lee |
bug |
|
|
added bug |
| 2014-06-24 04:30:47 |
Christopher Lee |
description |
When there is a failure to import a module this failure is logged but also means that everything else will be logged to stdout from that point on.
To reproduce/test:
Run the python script found here: http://pastebin.ubuntu.com/7693393/
Expected output: Nothing. No logging and no text etc.
Actual Output:
ERROR:root:Could not find any typelib for rubbish
INFO:something-not-root:You shouldn't see this
Note that you can see the logged output for "something-not-root" even though it's logging level is set to DEBUG.
Ubuntu Version:
Description: Ubuntu 14.04 LTS
Release: 14.04
Package Version:
python3-gi 3.12.0-1 |
When there is a failure to import a module this failure is logged but also means that everything else will be logged to stdout from that point on.
The Issue:
When failing to import a module the gi.repository import module adds a handler, that sends output to stdout, to the root logger. This means that _any_ logging after the failed import will be sent to stdout.
To reproduce/test:
Run the python script found here: http://pastebin.ubuntu.com/7693434/
Expected output: Nothing. No logging and no text etc.
Actual Output:
ERROR:root:Could not find any typelib for rubbish
INFO:something-not-root:You shouldn't see this
Note that you can see the logged output for "something-not-root" even though it's logging level is set to DEBUG.
Ubuntu Version:
Description: Ubuntu 14.04 LTS
Release: 14.04
Package Version:
python3-gi 3.12.0-1 |
|
| 2014-06-24 04:32:14 |
Martin Pitt |
description |
When there is a failure to import a module this failure is logged but also means that everything else will be logged to stdout from that point on.
The Issue:
When failing to import a module the gi.repository import module adds a handler, that sends output to stdout, to the root logger. This means that _any_ logging after the failed import will be sent to stdout.
To reproduce/test:
Run the python script found here: http://pastebin.ubuntu.com/7693434/
Expected output: Nothing. No logging and no text etc.
Actual Output:
ERROR:root:Could not find any typelib for rubbish
INFO:something-not-root:You shouldn't see this
Note that you can see the logged output for "something-not-root" even though it's logging level is set to DEBUG.
Ubuntu Version:
Description: Ubuntu 14.04 LTS
Release: 14.04
Package Version:
python3-gi 3.12.0-1 |
When there is a failure to import a module this failure is logged but also means that everything else will be logged to stdout from that point on.
The Issue:
When failing to import a module the gi.repository import module adds a handler, that sends output to stdout, to the root logger. This means that _any_ logging after the failed import will be sent to stdout.
To reproduce/test:
Run the python script found here: http://pastebin.ubuntu.com/7693434/
Expected output: Nothing. No logging and no text etc.
Actual Output:
ERROR:root:Could not find any typelib for rubbish
INFO:something-not-root:You shouldn't see this
Note that you can see the logged output for "something-not-root" even though it's logging level is set to INFO (which isn't normally shown).
Ubuntu Version:
Description: Ubuntu 14.04 LTS
Release: 14.04
Package Version:
python3-gi 3.12.0-1 |
|
| 2014-06-24 04:32:31 |
Martin Pitt |
nominated for series |
|
Ubuntu Trusty |
|
| 2014-06-24 04:32:31 |
Martin Pitt |
bug task added |
|
pygobject (Ubuntu Trusty) |
|
| 2014-06-24 04:32:31 |
Martin Pitt |
nominated for series |
|
Ubuntu Utopic |
|
| 2014-06-24 04:32:31 |
Martin Pitt |
bug task added |
|
pygobject (Ubuntu Utopic) |
|
| 2014-06-24 04:33:10 |
Martin Pitt |
bug watch added |
|
https://bugzilla.gnome.org/show_bug.cgi?id=726877 |
|
| 2014-06-24 04:33:10 |
Martin Pitt |
bug task added |
|
pygobject |
|
| 2014-06-24 04:33:58 |
Martin Pitt |
description |
When there is a failure to import a module this failure is logged but also means that everything else will be logged to stdout from that point on.
The Issue:
When failing to import a module the gi.repository import module adds a handler, that sends output to stdout, to the root logger. This means that _any_ logging after the failed import will be sent to stdout.
To reproduce/test:
Run the python script found here: http://pastebin.ubuntu.com/7693434/
Expected output: Nothing. No logging and no text etc.
Actual Output:
ERROR:root:Could not find any typelib for rubbish
INFO:something-not-root:You shouldn't see this
Note that you can see the logged output for "something-not-root" even though it's logging level is set to INFO (which isn't normally shown).
Ubuntu Version:
Description: Ubuntu 14.04 LTS
Release: 14.04
Package Version:
python3-gi 3.12.0-1 |
When there is a failure to import a module this failure is logged but also means that everything else will be logged to stdout from that point on.
The Issue:
When failing to import a module the gi.repository import module adds a handler, that sends output to stdout, to the root logger. This means that _any_ logging after the failed import will be sent to stdout.
To reproduce/test:
Run the python script found here: http://pastebin.ubuntu.com/7693434/
Expected output: Nothing. No logging and no text etc.
Actual Output:
ERROR:root:Could not find any typelib for rubbish
INFO:something-not-root:You shouldn't see this
Note that you can see the logged output for "something-not-root" even though it's logging level is set to INFO (which isn't normally shown).
Upstream fix: https://git.gnome.org/browse/pygobject/commit/?id=ac8b59e
Ubuntu Version:
Description: Ubuntu 14.04 LTS
Release: 14.04
Package Version:
python3-gi 3.12.0-1 |
|
| 2014-06-24 04:34:12 |
Martin Pitt |
pygobject (Ubuntu Utopic): status |
New |
In Progress |
|
| 2014-06-24 04:34:12 |
Martin Pitt |
pygobject (Ubuntu Utopic): assignee |
|
Martin Pitt (pitti) |
|
| 2014-06-24 04:54:47 |
Martin Pitt |
pygobject (Ubuntu Trusty): status |
New |
Incomplete |
|
| 2014-06-24 04:55:23 |
Martin Pitt |
pygobject (Ubuntu Utopic): status |
In Progress |
Fix Committed |
|
| 2014-06-24 04:55:37 |
Martin Pitt |
pygobject (Ubuntu Utopic): importance |
Undecided |
Low |
|
| 2014-06-24 05:41:13 |
Bug Watch Updater |
pygobject: status |
Unknown |
Fix Released |
|
| 2014-06-24 05:41:13 |
Bug Watch Updater |
pygobject: importance |
Unknown |
Medium |
|
| 2014-06-24 06:19:31 |
Launchpad Janitor |
pygobject (Ubuntu Utopic): status |
Fix Committed |
Fix Released |
|
| 2014-06-25 04:50:30 |
Christopher Lee |
description |
When there is a failure to import a module this failure is logged but also means that everything else will be logged to stdout from that point on.
The Issue:
When failing to import a module the gi.repository import module adds a handler, that sends output to stdout, to the root logger. This means that _any_ logging after the failed import will be sent to stdout.
To reproduce/test:
Run the python script found here: http://pastebin.ubuntu.com/7693434/
Expected output: Nothing. No logging and no text etc.
Actual Output:
ERROR:root:Could not find any typelib for rubbish
INFO:something-not-root:You shouldn't see this
Note that you can see the logged output for "something-not-root" even though it's logging level is set to INFO (which isn't normally shown).
Upstream fix: https://git.gnome.org/browse/pygobject/commit/?id=ac8b59e
Ubuntu Version:
Description: Ubuntu 14.04 LTS
Release: 14.04
Package Version:
python3-gi 3.12.0-1 |
When failing to import a module the gi.repository import.py module logs an error with `logging.error(..)` causing a logging handler to be added.
This basically breaks the ability to configure the logging as it happens so early (i.e. at the import stage before an authors code is executed).
To reproduce/Example:
Run this script: http://pastebin.ubuntu.com/7698632/
Expected outcome:
No output to stdout or stderr and the text "log message" in the file "/tmp/example.log
Actual outcome:
No log file, and this text output to stderr:
ERROR:root:Could not find any typelib for rubbish
ERROR:root:log message
Upstream fix: https://git.gnome.org/browse/pygobject/commit/?id=ac8b59e
Ubuntu Version:
Description: Ubuntu 14.04 LTS
Release: 14.04
Package Version:
python3-gi 3.12.0-1 |
|
| 2014-06-25 04:52:00 |
Martin Pitt |
pygobject (Ubuntu Trusty): status |
Incomplete |
Triaged |
|
| 2014-06-25 06:19:02 |
Martin Pitt |
summary |
Failing to import module adds noise to the logging stream |
Failing to import module breaks logging configurability and adds noise |
|
| 2014-06-25 06:26:21 |
Martin Pitt |
description |
When failing to import a module the gi.repository import.py module logs an error with `logging.error(..)` causing a logging handler to be added.
This basically breaks the ability to configure the logging as it happens so early (i.e. at the import stage before an authors code is executed).
To reproduce/Example:
Run this script: http://pastebin.ubuntu.com/7698632/
Expected outcome:
No output to stdout or stderr and the text "log message" in the file "/tmp/example.log
Actual outcome:
No log file, and this text output to stderr:
ERROR:root:Could not find any typelib for rubbish
ERROR:root:log message
Upstream fix: https://git.gnome.org/browse/pygobject/commit/?id=ac8b59e
Ubuntu Version:
Description: Ubuntu 14.04 LTS
Release: 14.04
Package Version:
python3-gi 3.12.0-1 |
When failing to import a module the gi.repository import.py module logs an error with `logging.error(..)` causing a logging handler to be added.
This basically breaks the ability to configure the logging as it happens so early (i.e. at the import stage before an authors code is executed).
To reproduce/Example:
Run this script: http://pastebin.ubuntu.com/7698632/
Expected outcome:
No output to stdout or stderr and the text "log message" in the file "/tmp/example.log
Actual outcome:
No log file, and this text output to stderr:
ERROR:root:Could not find any typelib for rubbish
ERROR:root:log message
Upstream fix: https://git.gnome.org/browse/pygobject/commit/?id=ac8b59e
Regression potential:
- The behaviour of raising ImportError on a nonexisting name does not change, but its text changes.
Old: ImportError: cannot import name 'foo'
New: ImportError: cannot import name foo, introspection typelib not found
It's unlikely, however theoretically possible that a program matches on the precise error message.
- It's theoretically possible that a program watches for the logged error message and ignores the ImportError. However, that would be extremely bad design, un-Pythonic and brittle as the logging format/destination can be changed arbitrarily.
In summary the regression potential is very low.
Ubuntu Version:
Description: Ubuntu 14.04 LTS
Release: 14.04
Package Version:
python3-gi 3.12.0-1 |
|
| 2014-06-25 06:26:56 |
Martin Pitt |
pygobject (Ubuntu Trusty): status |
Triaged |
In Progress |
|
| 2014-07-09 06:41:28 |
Adam Conrad |
pygobject (Ubuntu Trusty): status |
In Progress |
Fix Committed |
|
| 2014-07-09 06:41:32 |
Adam Conrad |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2014-07-09 06:41:35 |
Adam Conrad |
bug |
|
|
added subscriber SRU Verification |
| 2014-07-09 06:41:37 |
Adam Conrad |
tags |
|
verification-needed |
|
| 2014-07-23 01:49:37 |
Christopher Lee |
tags |
verification-needed |
verification-done |
|
| 2014-07-29 23:42:44 |
Launchpad Janitor |
pygobject (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
| 2014-07-29 23:42:53 |
Chris Halse Rogers |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
