Thursday, 2014-03-13

*** flaper87 is now known as flaper87|afk00:05
harlowjaanyone with any oslo.messaging experience around00:15
*** rpodolyaka has quit IRC00:17
openstackgerritJoshua Harlow proposed a change to openstack/oslo.messaging: Add a zookeeper based matchmaker  https://review.openstack.org/7982500:22
*** rpodolyaka has joined #openstack-oslo00:27
morganfainbergdhellmann, ping re https://review.openstack.org/#/c/72291/3/openstack/common/cache/memoization.py, your comment about objects is related to the decorator function (line 85) or the memoize function?00:32
*** arnaud has quit IRC00:39
*** arnaud has joined #openstack-oslo00:39
dims_harlowja, is kazoo being used in any other project? (just see it in requirements/global-requirements.txt but nowhere else)00:41
harlowjadims_ taskflow at least, stackforge/tooz most defintly, nova uses a out of date evzookeeper, there was a review up for moving it to use kazoo instead for https://github.com/openstack/nova/blob/master/nova/servicegroup/drivers/zk.py00:43
harlowjabut not sure where that review went00:43
harlowjait seems the service group code in nova is similar to the matchmaker code (also similar to tooz code doing similar stuff)00:44
dims_harlowja, i see. also taskflow seems to need >=1.3.1 (https://github.com/openstack/taskflow/blob/master/optional-requirements.txt#L22)00:44
harlowjait can likely work with older versions00:45
harlowjahow old, not really sure00:45
harlowjahttps://pypi.python.org/pypi/kazoo#changelog00:46
dims_just thinking if requirements/global-requirements.txt needs to be bumped up00:46
harlowjahmmm, thought it did/was, or i had a review for that, where'd it go, lol00:46
* harlowja finding00:47
dims_found the kazoo one - https://review.openstack.org/#/c/28951/00:47
harlowjak, hmmm, ya, seems like it was mostly done00:48
dims_looks like test case comments were not followed up on - https://review.openstack.org/#/c/28951/17/nova/tests/servicegroup/test_kazoo_driver.py,unified00:49
harlowjaah, dims_  https://review.openstack.org/#/c/69815/00:49
harlowjaso that was the unpin00:49
harlowjashall i bump00:49
harlowjai'm ok with that00:50
dims_+1 to bump up global. thanks!00:51
harlowjak00:51
harlowjahttps://review.openstack.org/#/c/79796/ was another weird one to00:51
harlowjapip requirements checking/validation doesn't seem so great, lol00:52
dims_lol :)00:52
harlowjaya, i made a updated an anvil tool that correctly identifies these kind of weirdnesses and after adding some functionality was wondering what was happening00:54
harlowjahttps://review.openstack.org/#/c/79203/00:54
harlowjaanyways00:54
harlowjadims_ https://review.openstack.org/8013400:55
dims_harlowja, another one, i was checking if the matchmakers were pluggable and listed in setup.cfg looks like they are not00:55
harlowjadims_ ya, that makes it hard to discover these00:55
harlowjai am wondering if oslo.messaging should sort of adopt the tooz group membership model and replace the matchmaker stuff with it00:56
harlowjagroups seems like a better abstraction (if it fits)00:56
harlowjahttps://github.com/stackforge/tooz/blob/master/tooz/coordination.py#L2600:56
dims_harlowja, dunno, markmc may have a better idea about that.00:57
harlowjain a way the matchmaker stuff is doign group memebership (where the group is a set of hosts in a topic, or fanout)00:57
harlowjajd__ might also, think some folks from evonance are doing some of the tooz work00:57
harlowjadims_ let me see if someone at at&t (i believe they are using the nova + zookeeper driver) or maybe myself can finish https://review.openstack.org/#/c/28951/01:01
harlowjait'd be nice to get off https://pypi.python.org/pypi/evzookeeper which doesn't appear updated in 2 years01:01
harlowjakazoo at least is actively maintained (by twitter i think?)01:02
dims_cool. fyi https://bugs.launchpad.net/oslo/+bug/1291701 please add your thoughts as well01:03
dims_brb01:04
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Avoid calling callbacks while holding locks  https://review.openstack.org/8013801:25
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Avoid calling callbacks while holding locks  https://review.openstack.org/8013801:26
*** rpodolyaka has quit IRC01:58
openstackgerritlifeless proposed a change to openstack-dev/pbr: Return the real class in VersionInfo __repr__.  https://review.openstack.org/7985602:00
openstackgerritlifeless proposed a change to openstack-dev/pbr: Fix up some docstrings.  https://review.openstack.org/7985502:00
*** mriedem has left #openstack-oslo02:05
*** mriedem has quit IRC02:05
*** rpodolyaka has joined #openstack-oslo02:08
*** rpodolyaka has quit IRC02:21
*** hdd_ has joined #openstack-oslo02:25
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Update lock_utils to use the posix IPC lock  https://review.openstack.org/8015502:25
*** arnaud has quit IRC02:26
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Update comment + six.text_type instead of str for name  https://review.openstack.org/8015802:35
*** rpodolyaka has joined #openstack-oslo02:53
*** rpodolyaka has quit IRC02:54
*** rpodolyaka has joined #openstack-oslo02:54
openstackgerritlifeless proposed a change to openstack-dev/pbr: TEST: Deleting thought-to-be-dead code.  https://review.openstack.org/8016102:55
*** gcb_ has joined #openstack-oslo02:55
*** gcb has quit IRC02:55
*** gcb__ has joined #openstack-oslo02:56
*** saikrishna_ has joined #openstack-oslo02:58
*** gcb_ has quit IRC03:00
*** zhiyan_ is now known as zhiyan03:06
*** saikrishna_ has quit IRC03:17
openstackgerritCyril Roelandt proposed a change to openstack-dev/hacking: Add a six-related checker  https://review.openstack.org/8017103:34
*** saikrishna_ has joined #openstack-oslo03:45
*** saikrishna_ has quit IRC03:48
*** rpodolyaka has quit IRC03:51
*** lbragstad1 has joined #openstack-oslo03:57
*** lbragstad has quit IRC03:59
*** lbragstad1 is now known as lbragstad04:07
*** lbragstad is now known as lbragstad__04:16
*** harlowja is now known as harlowja_away04:20
*** rpodolyaka has joined #openstack-oslo04:22
*** harlowja_away is now known as harlowja04:24
*** harlowja is now known as harlowja_away05:53
*** hdd_ has quit IRC05:55
openstackgerritZhi Yan Liu proposed a change to openstack/oslo-incubator: Making table utf-8 charset checking be optional for DB migration  https://review.openstack.org/7535606:18
*** yamahata has quit IRC06:21
*** gcb__ has quit IRC07:10
*** rpodolyaka has quit IRC07:12
*** gcb__ has joined #openstack-oslo07:12
*** gcb_ has joined #openstack-oslo07:13
*** gcb__ has quit IRC07:17
*** morganfainberg is now known as morganfainberg_Z07:18
openstackgerritMehdi Abaakouk proposed a change to openstack/oslo-incubator: Re-raise exception of unloadable library  https://review.openstack.org/7793407:43
*** gcb__ has joined #openstack-oslo07:59
*** gcb_ has quit IRC08:02
openstackgerritIvan Melnikov proposed a change to openstack/taskflow: docs: Ingore 'taskflow.' prefix when sorting module index  https://review.openstack.org/8020508:09
openstackgerritIvan Melnikov proposed a change to openstack/taskflow: docs: Relative links improvements  https://review.openstack.org/8020608:09
*** flaper87|afk is now known as flaper8708:13
*** bogdando has joined #openstack-oslo08:15
openstackgerritIvan Melnikov proposed a change to openstack/taskflow: Remove extra quote symbol  https://review.openstack.org/8021108:32
*** I159_ has joined #openstack-oslo08:37
openstackgerritOleg Bondarev proposed a change to openstack/oslo-incubator: save_and_reraise_exception: add a flag to omit logging original exception  https://review.openstack.org/8022209:34
openstackgerritOleg Bondarev proposed a change to openstack/oslo-incubator: save_and_reraise_exception: add a flag to omit logging  https://review.openstack.org/8022210:04
*** sergmelikyan has joined #openstack-oslo10:24
sergmelikyanHi, guys. openstack.messaging has openstack.common.ssutils module imported, same is done by murano, that also used oslo.messaging. As expected DuplicateOptError exception is raised in oslo.config. How do you deal with such cases?10:26
silehtsergmelikyan, update oslo.messaging to latest 1.3.0aX or sync the oslo-incubator sslutils module10:49
openstackgerritIvan Melnikov proposed a change to openstack/taskflow: docs: Add page describing atom arguments and results  https://review.openstack.org/8024210:53
sergmelikyansileht, thx!10:58
openstackgerritIvan Melnikov proposed a change to openstack/taskflow: docs: Improve BaseTask method docstrings  https://review.openstack.org/8024811:08
sergmelikyansileht, What do you think about updating requirement for oslo.messaging in global-requirements?11:10
sergmelikyanI think requirement should be updated in IceHouse, since it is quite important fix11:11
openstackgerritIvan Melnikov proposed a change to openstack/taskflow: docs: Add page describing atom arguments and results  https://review.openstack.org/8024211:13
*** gcb__ has quit IRC11:23
*** gcb__ has joined #openstack-oslo11:25
*** gcb_ has joined #openstack-oslo11:28
*** viktors_ is now known as viktors11:29
*** gcb__ has quit IRC11:32
openstackgerritIvan Melnikov proposed a change to openstack/taskflow: docs: Add page describing atom arguments and results  https://review.openstack.org/8024211:48
sergmelikyanhttps://review.openstack.org/80259 - guys, what do you think about this patch?12:04
openstackgerritIvan Melnikov proposed a change to openstack/taskflow: docs: Add page describing atom arguments and results  https://review.openstack.org/8024212:06
*** beav has quit IRC12:07
*** dims_ has quit IRC12:30
*** dims_ has joined #openstack-oslo12:34
*** arnaud has joined #openstack-oslo12:55
*** yamahata has joined #openstack-oslo13:03
*** mriedem has joined #openstack-oslo13:12
*** lbragstad__ has quit IRC13:19
*** beav has joined #openstack-oslo13:29
openstackgerritNikola Dipanov proposed a change to openstack-dev/hacking: Add TestCase assertion methods for testing checks  https://review.openstack.org/8027813:30
openstackgerritNikola Dipanov proposed a change to openstack-dev/hacking: Add an import whitelist helper factory  https://review.openstack.org/8001813:30
openstackgerritIvan Melnikov proposed a change to openstack/taskflow: docs: Add page describing atom arguments and results  https://review.openstack.org/8024213:33
*** lbragstad has joined #openstack-oslo13:47
flaper87hey guys, can anyone help me replicate this failure ? http://logs.openstack.org/58/76458/4/check/gate-oslo-incubator-python27/e6be562/console.html14:15
flaper87I can't replicate it in my box14:15
flaper87so, not sure what's going on there14:16
*** hdd_ has joined #openstack-oslo14:23
openstackgerritStanislav Kudriashev proposed a change to openstack/taskflow: Introduce message types for WBE protocol  https://review.openstack.org/7971214:37
*** hdd_ has quit IRC14:46
*** browne has joined #openstack-oslo14:52
*** hartsocks has joined #openstack-oslo15:01
dhellmannflaper87: I haven't seen that one before15:04
openstackgerritStanislav Kudriashev proposed a change to openstack/taskflow: [WBE] Collect information from workers  https://review.openstack.org/7971315:07
dhellmannmorganfainberg_Z: I'm not sure which comment you mean?15:08
openstackgerritCyril Roelandt proposed a change to openstack/oslo-incubator: Do not use the 'extend' method on a dict_items object  https://review.openstack.org/8030715:09
flaper87dhellmann: :/ I'll keep digging, it's not related to the patch for sure15:10
flaper87(says flaper87 before finding out it's his fault)15:10
openstackgerritCyril Roelandt proposed a change to openstack/oslo-incubator: Do not use the 'extend' method on a dict_items object  https://review.openstack.org/8030715:16
*** rpodolyaka has joined #openstack-oslo15:18
*** rpodolyaka has left #openstack-oslo15:35
openstackgerritLuis de Bethencourt proposed a change to openstack/oslo.config: deprecated cli option has _ rather than -  https://review.openstack.org/8031915:43
openstackgerritCyril Roelandt proposed a change to openstack/oslo-incubator: Python3: do not use contextlib.nested()  https://review.openstack.org/8032115:46
openstackgerritStanislav Kudriashev proposed a change to openstack/taskflow: Update request `expired` property docsting  https://review.openstack.org/8032215:54
zhiyandhellmann: hello, not sure you could take a look on my response at https://bugs.launchpad.net/glance/+bug/1279000 and let me know position? the issue is really a blocker now for glance this release.15:55
zhiyanthanks15:55
*** arnaud has quit IRC16:09
openstackgerritStanislav Kudriashev proposed a change to openstack/taskflow: Introduce message types for WBE protocol  https://review.openstack.org/7971216:12
dhellmannzhiyan: I'm afraid I don't know the right answer to this problem. It sounds like the table encoding can't just be changed because of the current encoding, but it seems like allowing migrations to take place before that problem is resolved only makes the issue worse -- possibly creating new tables and adding more data.16:12
dhellmannzhiyan: If the switch that disables the check is meant to let deployers run migrations before fixing the problem, why don't we just have them fix the problem first?16:15
*** rpodolyaka has joined #openstack-oslo16:19
*** bogdando has quit IRC16:22
*** bogdando has joined #openstack-oslo16:24
zhiyandhellmann: what in you mind to ask deployer fix the problem first? be manually?16:24
zhiyandhellmann: i totally understand your concerns and agree what you proposed: to have deploy fix the table charset problem first then to do other migration. But i think the key is that IMO we'd better allow migration script fix it automatically, so this idea need that switch.16:28
zhiyans/deploy/deployer16:29
dhellmannzhiyan: Based on something said on the mailing list, I thought a migration couldn't fix this because it might corrupt the existing data.16:29
dhellmannzhiyan: To be honest, I'm not a MySQL expert. We do have experts in the community, so maybe you can get a clear path defined as part of that mailing list thread with their help?16:30
zhiyandhellmann: i'm confused, iiuc, we need a migration to fix that issue in anyway.16:32
zhiyandhellmann: ok, i will prepare a short mail to get more input. btw, could you pls give me the ML link? or its title..i'm not sure i know that clearly.16:33
dhellmannzhiyan: give me a minute and I'll find that ML message16:33
zhiyanthanks16:33
bnemeczhiyan: According to Clint's post, we can't do this in a migration safely: http://lists.openstack.org/pipermail/openstack-dev/2014-March/029708.html16:33
zhiyanah, recalled16:34
dhellmannbnemec: thanks, that's the one16:34
bnemecUnfortunately this is just a very tricky problem from what I'm hearing.16:34
dhellmannyeah16:34
bnemecMaybe we could complain loudly if someone does a migration with the wrong encoding, but provide the option to continue anyway.16:35
zhiyanbnemec: hum..so are you saying deployer need recreate whole table and dump all rows back?16:35
dhellmannso it seems like the only correct solution is to have deployers fix their databases before any more migrations are run16:35
*** saikrishna_ has joined #openstack-oslo16:36
bnemeczhiyan: I'm honestly not sure.  I think it depends on the data and the encodings involved, which is why this is tricky.16:36
zhiyani'm very interested in the steps of how to fix their database for deployers16:36
zhiyanyou know, even we deiced to fix this issue by document, we still need to give deployer a advising16:37
bnemeczhiyan: Right, but it's not clear to me how to fix the "latin1 db with utf8 data inserted" problem that Clint raised.16:39
bnemecI suppose recreating the table from scratch could work, but if there are foreign keys on it I think that could be difficult.16:39
zhiyanvery difficult16:39
bnemecBasically it's very, very bad that we ever let this happen because people's existing dbs may already be corrupted.16:40
zhiyannod16:40
zhiyanback to the topic, i will talk this with markwash later and know his comments. anyway, i think you currently trend to like deployer do the fix by themself.16:42
bnemecI agree that we need good documentation of the problem to let people proceed as best they can, but outside of Clint I'm not sure who would be qualified to write it.16:42
zhiyanand if so, this bug will go to invalid.16:42
zhiyanbnemec: if so do you think we can add the auto fix for this issue as a step in oslo db_sync? which code logic follow Clint's solution?16:44
bnemeczhiyan: I don't think we can auto-fix the problem at all.  We could provide a fix that would go through and change all the tables to utf8 (I think that's what nova did at some point in the past), but it doesn't sound like that will work right in every case.16:46
bnemecAIUI anyway16:46
zhiyanbnemec: tbh i'm confused at here, if you understand correct, you are saying glance project can make a built-in migration script to (partial, probably) fix this issue by changing all the tables to utf8, right? that just is what I proposed here..16:49
dhellmannzhiyan: automating the solution to this problem will be quite complex16:50
openstackgerritCyril Roelandt proposed a change to openstack/oslo-incubator: Python 3: enable tests/unit/middleware/test_request_id.py  https://review.openstack.org/8033616:50
dhellmannzhiyan: this is why database administrators exist -- we need to explain to them what their database should look like, but I don't think it's safe to try to write a migration to fix the database because we can't be sure of the starting conditions16:51
zhiyandhellmann: agreed, i totally understand.16:51
zhiyandhellmann: do you agree we fix it by a document?16:52
dhellmannzhiyan: yes, I think that's the best way to handle it, in the release notes16:53
zhiyanin project's release notes, like glance? or a common one, not sure16:53
bnemecYeah, we could write a tool to handle the trivial case, but the more complex ones need manual intervention.16:54
openstackgerritLuis de Bethencourt proposed a change to openstack/oslo.config: deprecated cli option has _ rather than -  https://review.openstack.org/7369416:54
dhellmannbnemec: right, and everyone would want the tool to handle every case :-/16:56
dhellmannzhiyan: that's a question for annegentle, but maybe both locations16:56
bnemecdhellmann: And that way lies madness :-)16:56
dhellmanncertainly this needs to be documented in the upgrade "manual"16:57
dhellmannbnemec: openstack is madness all the way down16:57
bnemecIndeed. :-)16:58
zhiyandhellmann: bnemec thanks for your input btw16:59
*** arnaud has joined #openstack-oslo17:01
*** viktors is now known as viktors_17:06
*** morganfainberg_Z is now known as morganfainberg17:09
*** harlowja_away is now known as harlowja17:10
*** saikrishna_ has quit IRC17:15
*** lbragstad has quit IRC17:17
openstackgerritAnastasia Karpinska proposed a change to openstack/taskflow: Move flow states to developers socumentation  https://review.openstack.org/8035017:22
openstackgerritAnastasia Karpinska proposed a change to openstack/taskflow: Add retry action to execute retries  https://review.openstack.org/6811217:22
openstackgerritAnastasia Karpinska proposed a change to openstack/taskflow: Flow smart revert with retry controller  https://review.openstack.org/7162117:22
openstackgerritAnastasia Karpinska proposed a change to openstack/taskflow: Add atom intentions for tasks and retries  https://review.openstack.org/7101317:22
openstackgerritAnastasia Karpinska proposed a change to openstack/taskflow: Extend logbook and storage to work with retry  https://review.openstack.org/6811117:22
*** lbragstad has joined #openstack-oslo17:23
*** hartsocks has left #openstack-oslo17:37
*** hartsocks has joined #openstack-oslo17:37
harlowjadhellmann lol, openstack is madness all the way down ;)17:37
harlowjalol17:37
dims_continuously tested madness :)17:37
harlowja;)17:37
morganfainbergdhellmann, the one on line 8517:38
harlowjadims_ mr.jenkins must be a very tired man, lol17:38
dims_:)17:38
morganfainbergdhellmann, https://review.openstack.org/#/c/72291/3/openstack/common/cache/memoization.py should the whole decorator (memoize) me be a class? or just the "decorator" function17:38
morganfainbergdhellmann, i wasn't sure which you meant.17:38
dhellmannmorganfainberg: I think I meant memoize() should be a class, let me verify17:41
morganfainbergdhellmann, i thought so, but i wanted to be 100% sure.17:41
dhellmannmorganfainberg: yeah, that way we can document invalidate() etc. as methods of memoize17:42
dhellmannas they stand now, there's no way to discover those names to document them automatically17:42
morganfainbergdhellmann, i'll need to look into that, there is some oddities based on how "self" gets eaten in those cases17:42
morganfainbergbut i think i can do it17:42
dhellmannmorganfainberg: also, regarding the API, I wonder if it would be better match lru_cache than dogpile, since the latter is a stdlib "standard"17:42
morganfainberglru_cache is a wholesale cache clear for the method17:43
morganfainbergafaict17:43
morganfainbergdogpile is true memoization17:43
dhellmannmorganfainberg: there was a good thread on planet.python.org recently about writing decorators17:43
morganfainbergso arguments are the key.17:43
morganfainbergdhellmann, thanks! i'll check out that thread17:43
dhellmannmorganfainberg: http://blog.dscpl.com.au/2014/01/how-you-implemented-your-python.html17:44
morganfainbergdhellmann, thanks!17:45
dhellmannmorganfainberg: as far as the API, I just meant cache_clear() instead of invalidate()17:46
morganfainbergdhellmann, ahh17:46
morganfainbergdhellmann, i'll just alias both17:46
dhellmannmorganfainberg: and maybe add cache_info()?17:46
morganfainbergdhellmann, that is easy17:46
morganfainbergdhellmann, hmm. sure.17:46
morganfainbergdhellmann, both good ideas.17:46
dhellmannmorganfainberg: I'd have to read the docs again closely to see if there are other appropriate changes, but you get the idea17:46
morganfainbergdhellmann, sure, the lru_cache interfaces seem sane17:47
morganfainbergdhellmann, i'm also pulling the crypto stuff out so that can be specifically reviewed by simo and other more crypto-facing people17:48
morganfainbergindependantly of the core changeset17:48
dhellmannmorganfainberg: ok, that sounds good17:48
morganfainbergdhellmann, :) it's slow work because it's a big changeset, but it's moving.17:49
dhellmannmorganfainberg: we're basically frozen now anyway, right?17:49
morganfainbergdhellmann, aye17:49
morganfainbergdhellmann, no one would sync it in17:49
morganfainbergdhellmann, but i want it ready for J1, if i can have keystone's cache and KVS systems moved over to it in Juno i'll be pleased17:50
morganfainbergand then i can help other projects leverage it as well17:50
*** beav- has joined #openstack-oslo17:52
*** beav has quit IRC17:53
*** arnaud has quit IRC17:53
*** rpodolyaka has quit IRC17:57
*** rpodolyaka has joined #openstack-oslo18:00
*** flaper87 is now known as flaper87IsNotAwa18:04
*** flaper87IsNotAwa is now known as flaper87DoesNotK18:04
*** flaper87DoesNotK is now known as flaper87WTF18:05
*** flaper87WTF is now known as flaper8718:05
dhellmannmorganfainberg: +118:06
openstackgerritIvan Melnikov proposed a change to openstack/taskflow: docs: Add page describing atom arguments and results  https://review.openstack.org/8024218:09
*** zhiyan is now known as zhiyan_18:10
openstackgerritLuis de Bethencourt proposed a change to openstack/oslo.config: deprecated cli option has _ rather than -  https://review.openstack.org/7369418:12
*** I159_ has quit IRC18:13
*** dshulyak_ has joined #openstack-oslo18:30
openstackgerritMehdi Abaakouk proposed a change to openstack/oslo.messaging: Full support of multiple hosts in transport url  https://review.openstack.org/7894818:37
openstackgerritCyril Roelandt proposed a change to openstack/oslo-incubator: Python3: enable test_jsonutils.py  https://review.openstack.org/8037019:05
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Introduce a CorrelatedFailure exception  https://review.openstack.org/8037219:11
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Introduce a CorrelatedFailure exception  https://review.openstack.org/8037219:12
*** rpodolyaka has quit IRC19:13
*** dshulyak_ has quit IRC19:20
*** hartsocks has left #openstack-oslo19:21
*** hartsocks has joined #openstack-oslo19:21
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Introduce a CorrelatedFailure exception  https://review.openstack.org/8037219:24
*** rpodolyaka has joined #openstack-oslo20:14
*** rpodolyaka has quit IRC20:19
bnemecSo https://bugs.launchpad.net/oslo/+bug/128553020:20
bnemecThe mailing list discussion didn't get a lot of love, but I think it's something we need to discuss, especially in the lazy translation world we live in now.20:21
*** beav- has quit IRC20:25
*** rpodolyaka has joined #openstack-oslo20:32
dhellmannbnemec: the logic behind not translating the exceptions eludes me20:34
dhellmannif the translation machinery is "broken" at the time the error is reported, then it just won't be translated20:35
dhellmannby the logic presented, we shouldn't report errors because error reporting may be broken when an error happens20:35
bnemecdhellmann: Couldn't broken translation mask the original error though?20:35
dhellmannbnemec: I'd have to look, but I'm reasonably sure that if translation fails for any reason we just use the original message string20:36
bnemecAlthough on second thought I'm wondering if it's even possible to raise a translated exception at a point where translation is broken.20:36
bnemecI'd think we'd blow up on a log message or something long before that.20:36
dhellmannbnemec: yeah20:37
dhellmannbnemec: we should add some exception handling in http://git.openstack.org/cgit/openstack/oslo-incubator/tree/openstack/common/gettextutils.py#n17620:38
*** rpodolyaka has quit IRC20:39
dhellmannbnemec: but otherwise, I think we should go ahead and translate errors and assume that most of the time the error is going to be something related to a user action and not MemoryError or some other catastrophic thing20:39
bnemecdhellmann: Yeah, I think that makes sense.20:39
dhellmannbnemec: I will reply to the email thread20:40
bnemecWe should probably update the wiki to basically say "when in Rome, translate exceptions as the Romans do"20:40
bnemecBecause I'm not sure _every_ project translates exceptions today, but I know quite a few do.20:40
*** rpodolyaka has joined #openstack-oslo20:40
bnemecdhellmann: Thanks20:40
dhellmannbnemec: sent -- I made one update to the wiki about log translations a while back and forgot to reply to the thread at that point. I will leave the thing about exceptions to give people time to reply to my message.20:46
bnemecdhellmann: Sounds good.20:46
* bnemec is pretty sure no one else is going to go anywhere near this topic ;-)20:47
*** browne has left #openstack-oslo20:48
* dhellmann nods20:52
*** gilliard_ has joined #openstack-oslo21:05
gilliard_dhellmann: would you mind having another look at https://review.openstack.org/#/c/71559/9 when you have time?21:06
dhellmanngilliard_: there's no priority on that for nova, are you working on it for rc1?21:26
*** arnaud has joined #openstack-oslo21:27
*** mriedem has left #openstack-oslo21:53
*** lbragstad has quit IRC21:54
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Adjust the exception hierachy  https://review.openstack.org/8037221:58
*** hartsocks has quit IRC22:04
*** rpodolyaka has quit IRC22:15
*** rpodolyaka has joined #openstack-oslo22:18
*** arnaud has quit IRC22:53
*** dims_ has quit IRC22:58
*** rpodolyaka has quit IRC22:59
*** rpodolyaka has joined #openstack-oslo23:04
*** mriedem has joined #openstack-oslo23:04
*** mriedem has left #openstack-oslo23:05
*** mriedem has joined #openstack-oslo23:07
*** dims_ has joined #openstack-oslo23:12
*** rpodolyaka has quit IRC23:17
*** rpodolyaka has joined #openstack-oslo23:20
*** flaper87 is now known as flaper87|afk23:37
*** wingwj has quit IRC23:45
*** wingwj has joined #openstack-oslo23:46

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!