Wednesday, 2016-11-09

*** _JZ_ has quit IRC00:03
claygi think there's plenty of work to go around - getting ec disk engine support in the new-object-server that works with the existing proxy would be pretty great00:03
zaitcevBut that does not need liberasurecode, right? Only reconstructor needs it, right?00:04
clayg... or terrible if you assume we want to replace multipart chunked upload with something else that will support commit & fotters00:04
clayg*footers00:04
zaitcevHTTP/200:04
zaitcevchannels! frames!00:04
claygzaitcev: that's no longer true now that the ec object app iter does the ec fragment checking00:05
zaitcevoh00:05
claygzaitcev: I could probably be talked into http/2 - but I think http/1 pipelined requests would be sufficient00:05
*** catintheroof has quit IRC00:14
*** catintheroof has joined #openstack-swift00:15
*** catintheroof has quit IRC00:19
*** StraubTW has joined #openstack-swift00:32
*** vint_bra has joined #openstack-swift00:35
*** kei_yama has quit IRC00:49
*** chlong has joined #openstack-swift00:49
*** kei_yama has joined #openstack-swift00:49
*** vint_bra has quit IRC00:52
*** diogogmt has quit IRC00:52
*** hoonetorg has quit IRC01:11
openstackgerritPete Zaitcev proposed openstack/swift: Patch the policy through proxy operations  https://review.openstack.org/39468501:14
zaitcev+ /usr/bin/docker run --name hbt250 -e GERRIT_REFSPEC=refs/changes/85/394685/2 hummingbirdtest /root/tests01:15
zaitcevtime="2016-11-09T01:14:53Z" level=fatal msg="Error response from daemon: Unable to open the database file: unable to open database file"01:15
zaitcevI'm amazed anything of this giant pile of kludges even works at all01:16
kota_good morning01:23
*** hoonetorg has joined #openstack-swift01:24
*** diogogmt has joined #openstack-swift01:39
*** david_c has quit IRC01:39
*** david_c has joined #openstack-swift01:42
*** arch-nemesis has joined #openstack-swift02:05
kota_notmyname: quick confirmation, to progress the review speed, can we strat to manage the review process that a core can add +A for a trivial change written by another core?02:14
kota_notmyname: have it been to work already?02:15
*** arch-nemesis has quit IRC02:18
*** abalfour has quit IRC02:18
*** abalfour has joined #openstack-swift02:18
*** david-lyle has joined #openstack-swift02:22
*** clu_ has quit IRC02:25
*** bkopilov has quit IRC02:58
*** chenhuayi has joined #openstack-swift03:02
*** dmorita has quit IRC03:03
chenhuayiSeeking for help. If there have the processes to do Swift compatibility certification? If Someone have the information about the Swift compatibility certification? Waiting for help online.03:17
notmynamekota_: yes04:04
kota_notmyname: thx04:04
*** links has joined #openstack-swift04:38
*** bkopilov has joined #openstack-swift04:47
winggundamthhi. Anyway that I can remove public directory listing from Swift?04:52
winggundamthI just want visitors to directly access to the file but not list all the object in container04:52
openstackgerritMerged openstack/swift: Fix ZeroDivisionError in reconstructor.stats_line  https://review.openstack.org/39471404:54
*** StraubTW has quit IRC04:56
winggundamthfound it. swift post -r .r:* test_container05:03
*** dmorita has joined #openstack-swift05:04
*** dmorita has quit IRC05:08
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873605:20
*** david-lyle has quit IRC05:22
*** david-lyle has joined #openstack-swift05:23
charz_Good morning!05:33
charz_Just a simple question for x-newest header in HEAD/GET request, if I deleted the object(two replicas) in primary places, but still have one copy in handoff. It seems like I able to HEAD this object form client even I add x-newest header, but I can't see it in container listing.05:38
charz_Should I get `404 not found` not a `200 ok`?05:40
charz_okay, I found a bug in https://bugs.launchpad.net/swift/+bug/156057205:41
openstackLaunchpad bug 1560572 in OpenStack Object Storage (swift) "X-Newest doesn't take tombstones into consideration" [Undecided,New]05:41
*** garthb has joined #openstack-swift05:48
*** SkyRocknRoll has joined #openstack-swift06:08
*** links has quit IRC06:11
*** SkyRocknRoll has quit IRC06:12
*** SkyRocknRoll has joined #openstack-swift06:12
*** dmorita has joined #openstack-swift06:14
*** chenhuayi_ has joined #openstack-swift06:16
*** dmorita has quit IRC06:19
*** chenhuayi has quit IRC06:20
*** chenhuayi__ has joined #openstack-swift06:39
*** links has joined #openstack-swift06:39
*** qwertyco has joined #openstack-swift06:40
*** chenhuayi_ has quit IRC06:42
*** david_c has quit IRC06:42
*** rcernin has joined #openstack-swift06:54
*** StraubTW has joined #openstack-swift06:57
*** SkyRocknRoll has quit IRC06:59
*** StraubTW has quit IRC07:02
*** Jeffrey4l has joined #openstack-swift07:09
*** tesseract has joined #openstack-swift07:11
*** tesseract is now known as Guest3903307:11
*** dikonoor has joined #openstack-swift07:30
*** sams-gleb has joined #openstack-swift07:34
*** sams-gleb has quit IRC07:49
*** sams-gleb has joined #openstack-swift07:49
*** sams-gleb has quit IRC07:54
kota_charz_: that seems to happen but it sounds like just an eventual consistency07:56
kota_charz_: hello07:56
kota_charz_: in the evnetual consitency world, we can see older data even if we overwrite the older data with a new one but it's ok.07:57
charz_kota_: yeah! I think so, but I think we should take that when client try to issue a request with `x-newest` header.07:57
kota_ah, it may be problem (?) the newest should be tombstone?07:57
charz_kota_: it's quite easy to run into this issue, when you have a global cluster (WA enabled), and you upload a object and deleted it.07:59
charz_before object replicator to clean/move it. You'll see 200 ok when you do a HEAD.08:00
charz_You need to wait replicator to clean/move it and you might able to get 404 not found.08:01
charz_It seems like a problem when you have a 3 party software, and they're doing some checks with HEAD operation.08:01
charz_I think the `x-newest` header need to take care .ts file in this kind of case.08:04
kota_charz_: the 3rd party sounds like swift3 :P08:07
charz_kota_: ah, it could be. :)08:07
charz_kota_: I think the client might not able to know how swift works, but we might need to provide a way to make sure they get correct data.08:09
charz_s/client/users/08:09
*** silor has joined #openstack-swift08:10
*** oshritf has joined #openstack-swift08:18
*** silor1 has joined #openstack-swift08:19
*** silor has quit IRC08:21
*** silor1 is now known as silor08:21
*** geaaru has joined #openstack-swift08:23
*** rledisez has joined #openstack-swift08:25
*** oshritf has quit IRC08:27
*** oshritf has joined #openstack-swift08:35
*** klrmn has quit IRC08:40
kota_charz_: exactly08:40
*** openstackgerrit has quit IRC08:48
*** openstackgerrit has joined #openstack-swift08:48
*** kei_yama has quit IRC08:49
*** jordanP has joined #openstack-swift08:53
*** admin6 has joined #openstack-swift09:34
*** qwertyco has quit IRC09:42
*** cbartz has joined #openstack-swift09:47
*** sams-gleb has joined #openstack-swift09:56
*** chenhuayi__ has quit IRC10:08
*** geaaru has quit IRC10:09
*** bkopilov has quit IRC10:14
*** geaaru has joined #openstack-swift10:22
*** mvk has quit IRC10:30
*** dikonoor has quit IRC10:53
*** asettle has joined #openstack-swift10:55
*** geaaru has quit IRC10:57
*** StraubTW has joined #openstack-swift10:59
*** mvk has joined #openstack-swift11:03
*** ChubYann has quit IRC11:03
*** StraubTW has quit IRC11:04
*** geaaru has joined #openstack-swift11:11
*** dikonoor has joined #openstack-swift11:14
*** dikonoor has quit IRC11:42
*** npf has joined #openstack-swift11:43
*** dikonoor has joined #openstack-swift11:49
*** Guess456787654 has joined #openstack-swift11:56
*** catintheroof has joined #openstack-swift12:16
*** catinthe_ has joined #openstack-swift12:20
*** catintheroof has quit IRC12:21
*** vint_bra has joined #openstack-swift12:39
*** bkopilov has joined #openstack-swift12:46
*** d0ugal has quit IRC12:51
*** d0ugal has joined #openstack-swift13:00
*** cbartz has quit IRC13:03
*** sams-gle_ has joined #openstack-swift13:06
*** sams-gleb has quit IRC13:06
openstackgerritThomas Herve proposed openstack/swift: Handle deleted files with if-none-match  https://review.openstack.org/39558213:11
*** chenhuayi has joined #openstack-swift13:18
*** jistr is now known as jistr|brb13:26
*** jistr|brb is now known as jistr13:46
*** catintheroof has joined #openstack-swift13:47
*** catinthe_ has quit IRC13:50
*** npf has quit IRC13:51
*** geaaru has quit IRC14:10
*** chenhuayi has quit IRC14:14
*** StraubTW has joined #openstack-swift14:14
openstackgerritMahati Chamarthy proposed openstack/swift: Handle deleted files with if-none-match  https://review.openstack.org/39558214:16
*** StraubTW_ has joined #openstack-swift14:18
*** StraubTW has quit IRC14:20
*** sgundur has joined #openstack-swift14:28
*** klamath has joined #openstack-swift14:30
*** dmorita has joined #openstack-swift14:31
*** klamath has joined #openstack-swift14:31
*** sgundur_ has joined #openstack-swift14:32
*** sgundur has quit IRC14:34
*** sgundur_ has quit IRC14:34
*** sgundur has joined #openstack-swift14:34
*** dmorita has quit IRC14:35
*** sgundur has quit IRC14:40
*** links has quit IRC14:49
*** cbartz has joined #openstack-swift15:10
*** diogogmt has quit IRC15:13
*** sams-gle_ has quit IRC15:15
*** sams-gleb has joined #openstack-swift15:15
*** sams-gleb has quit IRC15:20
*** sams-gleb has joined #openstack-swift15:34
*** tsg has joined #openstack-swift15:46
*** jerrygb has joined #openstack-swift15:57
*** _JZ_ has joined #openstack-swift16:00
*** vint_bra has quit IRC16:01
*** cebruns_ is now known as cebruns16:01
*** geaaru has joined #openstack-swift16:10
*** rcernin has quit IRC16:13
*** klrmn has joined #openstack-swift16:16
*** acoles_ is now known as acoles16:21
*** Guest39033 has quit IRC16:25
*** agarner has joined #openstack-swift16:26
*** dikonoor has quit IRC16:31
*** bkopilov has quit IRC16:39
*** david_c has joined #openstack-swift16:44
*** bkopilov has joined #openstack-swift16:46
*** sgundur has joined #openstack-swift16:50
*** sgundur_ has joined #openstack-swift16:57
*** sgundur has quit IRC16:57
*** admin6 has quit IRC16:57
notmynamehello, world17:01
*** chlong has quit IRC17:08
*** klrmn has quit IRC17:08
*** sgundur_ has quit IRC17:11
*** sgundur has joined #openstack-swift17:12
*** sgundur has quit IRC17:17
*** chlong has joined #openstack-swift17:17
*** sgundur has joined #openstack-swift17:17
*** sgundur has quit IRC17:21
*** sgundur has joined #openstack-swift17:22
*** sgundur has quit IRC17:23
*** asettle has quit IRC17:26
*** dmorita has joined #openstack-swift17:28
tdasilvanotmyname: o/17:35
*** bkopilov has quit IRC17:37
*** sgundur has joined #openstack-swift17:44
*** sgundur_ has joined #openstack-swift17:51
*** bkopilov has joined #openstack-swift17:54
openstackgerritDrew Balfour proposed openstack/swift: WIP: add byteorder information and logic to ring files  https://review.openstack.org/39523717:55
*** cbartz has left #openstack-swift17:56
*** rledisez has quit IRC17:59
*** sgundur_ has quit IRC18:00
*** sgundur_ has joined #openstack-swift18:01
*** sgundur_ has quit IRC18:01
*** sgundur_ has joined #openstack-swift18:02
abalfourSo... I need some followup advice on that byteorder changeset. Currently it breaks the test_get_ring_md5_missing_ring_recovers_without_restart test in test/unit/common/middleware/test_recon.py, because it's trying to md5sum a generated ring file against a hard coded m5sum. With the new field in the ring file, the m5sum is different. The problem is that new field isn't static; if I run it on x64, I get one value (and one m5sum) whereas18:03
*** mvk has quit IRC18:05
notmynameabalfour: many of the ring tests are deliberately fragile like that so that it's super obvious when ring code changes.18:05
notmynameabalfour: ...since changing the ring is a Big Deal for deployed clusters18:06
abalfoursure, that makes sense, just wasn't sure the best way to fix it.18:06
notmynameabalfour: most likely, simply by changing the test to the newly correct md518:07
abalfourright, but the new md5sum isn't a constant anymore. it's endian dependent.18:08
notmynameneat18:08
*** klrmn has joined #openstack-swift18:08
abalfourmy thought was to just have two sets of md5sums, and compare based on endianess.18:08
notmynameyeah, that was my first thought too18:09
abalfourok, I shall make it so.18:09
abalfourthanks for the sanity check.18:09
*** htruta has joined #openstack-swift18:09
timburkeor patch sys.byteorder?18:09
abalfourSure, that'd work too but than it's intentionally avoiding a testcase?18:10
*** oshritf has quit IRC18:11
*** jordanP has quit IRC18:19
*** asettle has joined #openstack-swift18:27
*** asettle has quit IRC18:31
*** david_c_ has joined #openstack-swift18:32
*** david_c has quit IRC18:33
*** david_c_ is now known as david_c18:33
*** david_c has quit IRC18:39
notmynameremember the time change. the team meeting is at 2100UTC (2 hours and 20 minutes from now)18:39
*** david_c has joined #openstack-swift18:40
*** clu_ has joined #openstack-swift18:44
*** acoles is now known as acoles_18:49
*** mvk has joined #openstack-swift18:51
*** sgundur_ has quit IRC18:56
*** sgundur_ has joined #openstack-swift18:58
*** ChubYann has joined #openstack-swift18:59
*** rcernin has joined #openstack-swift18:59
*** diogogmt has joined #openstack-swift19:03
*** catinthe_ has joined #openstack-swift19:10
openstackgerritJohn Dickinson proposed openstack/python-swiftclient: 3.2.0 release notes  https://review.openstack.org/39576819:10
*** catintheroof has quit IRC19:12
*** sgundur_ has quit IRC19:13
*** sgundur_ has joined #openstack-swift19:14
*** geaaru has quit IRC19:16
*** vint_bra has joined #openstack-swift19:18
openstackgerritJohn Dickinson proposed openstack/python-swiftclient: 3.2.0 release notes  https://review.openstack.org/39576819:25
openstackgerritNandini Tata proposed openstack/swift: Allow custom swift configuration directory  https://review.openstack.org/39395219:26
*** rcernin has quit IRC19:55
*** sgundur_ has quit IRC20:00
*** sgundur_ has joined #openstack-swift20:06
*** sgundur_ has quit IRC20:12
claygtimburke: I seem to be plateau'ing at 3 attempts to find `swift info --json | jq .swift.policies[].name` - but it feels *really* close - I think I'm going to break through from 3 -> first try any minute20:14
*** silor has quit IRC20:14
*** Guess456787654 has quit IRC20:33
openstackgerritChristian Hugo proposed openstack/swift: Raise ValueError if a config section does not exist  https://review.openstack.org/39338820:52
*** StraubTW_ has quit IRC20:53
*** tmoreira has quit IRC20:57
*** cschwede has quit IRC20:57
notmynameswift team meeting time (in 2 minutes)20:58
notmynameI expect it to be relatively quick20:59
kota_good morning20:59
claygkota_: hello!  Just put my +10000 on patch 39359520:59
patchbothttps://review.openstack.org/#/c/393595/ - liberasurecode - Fix error handling on gf_ivnert_matrix in isa-l ba...20:59
*** joeljwright has joined #openstack-swift21:00
*** ChanServ sets mode: +v joeljwright21:00
notmynameswift team meeting in #openstack-meeting21:00
kota_clayg: thx!21:00
*** admin6 has joined #openstack-swift21:01
openstackgerritChristian Hugo proposed openstack/swift: Raise ValueError if a config section does not exist  https://review.openstack.org/39338821:10
jrichlilast but, if, we, fix, patchbot then I can't make it do this21:12
patchbotthis21:12
jrichlidoh!  I thought it was gonna be worse.  ill have to figure out what the pattern is21:12
*** sgundur_ has joined #openstack-swift21:13
*** StraubTW has joined #openstack-swift21:15
*** sams-gleb has quit IRC21:17
*** sams-gleb has joined #openstack-swift21:17
*** sams-gleb has quit IRC21:22
*** admin6 has quit IRC21:25
*** asettle has joined #openstack-swift21:28
*** cschwede has joined #openstack-swift21:28
*** m_kazuhiro has joined #openstack-swift21:29
*** tmoreira has joined #openstack-swift21:30
*** asettle has quit IRC21:33
*** Jeffrey4l has quit IRC21:34
*** ntata_ has joined #openstack-swift21:35
*** ntata_ has quit IRC21:38
*** ntata_ has joined #openstack-swift21:48
*** ntata_ has quit IRC21:51
*** ChanServ sets mode: +v cschwede21:58
notmynamecschwede: I think I had a question for you... let me see if I can remember it22:01
cschwedenotmyname: well, that gives me the chance to talk to you :)22:01
cschwedenotmyname: regarding the pyeclib discussions we had in Barcelona22:01
cschwedenotmyname: the idea was to enable EC funtional testing in the gate, right? and probetests too?22:01
notmynamecschwede: that sounds like something I'd like :-)22:03
notmynamecschwede: but I don't remember the challenge of that. we've already got EC tests in the gate for swift...22:03
kota_clayg: the libeasurecode fix for isa-l https://review.openstack.org/#/c/393595/3 depends on https://review.openstack.org/#/c/387879/2 and pach 3993595 is using a part of the patch 3993595 to enable to run non-args test function.22:03
patchbothttps://review.openstack.org/#/c/3993595/22:03
patchbotpatch 393595 - liberasurecode - Fix error handling on gf_ivnert_matrix in isa-l ba...22:03
patchbotpatch 387879 - liberasurecode - Fix liberasurecode skipping a bunch of invalid_arg...22:03
kota_that's what I'd like to say in the end of irc meeting.22:04
notmynamekota_: thanks :-)22:04
kota_:-)22:04
kota_if we don't mind not running the unit tests, we can land patch 393595 first but i prefer running unit test always helps from regression22:05
patchbothttps://review.openstack.org/#/c/393595/ - liberasurecode - Fix error handling on gf_ivnert_matrix in isa-l ba...22:05
notmynamecschwede: were we talking about adding them for the pyeclib/liberasurecode projects?22:06
cschwedenotmyname: they already exist for the pyeclib project?22:06
* kota_ is going to find breakfast22:06
claygkota_: sorry missed that on the liberasurecode test patch - i'm looking into that now - thanks22:09
claygcschwede: nope, but I think maybe we have some non-dsvm functests with ec policy?  acoles_ would know22:10
notmynameclayg: yes, we definitely have that22:11
notmynameI've been working on that part of the test infra for the xattr checksumming22:11
*** joeljwright has quit IRC22:12
cschwedeclayg: looks to me like tests for pyeclib are properly running in the gate: http://logs.openstack.org/56/393656/1/check/gate-pyeclib-python27-ubuntu-xenial/321e5ef/console.html.gz or am i missing something here?22:13
notmynamecschwede: seems that it's still using an older liberasurecode22:14
cschwedenotmyname: yes, that is likely22:15
notmynamethis is coming back to the issue we've come to in many places, it seems22:15
notmynamein the openstack CI system, how do we pull in and test against compiled code?22:15
notmynamematters for the EC libs. matters for golang22:15
cschwedenotmyname: well,  i need to look into that - what’s the current way. i’ll check that out and get back to you22:16
notmynamecschwede: AFAICT the current way is to pull whatever's in the distro packages. eg ubuntu xenial22:16
notmynamepoint being, there's not a current way to pull sources for a dependency and build it and then test against *that*22:17
notmynameor there might be a way, but we're not doing it22:17
notmynamefungi: ^ this is one of our current big questions. relates to golang, but currently we're stuggling with it for a C-lang dependency22:17
cschwedenotmyname: IIRC sometimes pip pulls in sources and even compiles C stuff then?22:18
notmynamecschwede: like in general it can do that or specifically with one of our dependencies now?22:19
fungiright, it's not that there's _no_ way, but that "the way" depends on the situation, so you may need to script itt22:19
fungiif your need is to compile c extensions for a python sdist, that is fairly straightforward to tackle in traditional python packaging ways22:20
notmynamefungi: current state of things is that we depend on pyeclib (python c bindings) which depends on liberasurecode. we'd like to pull in a newer version of liberasurecode and use that for testing swift (and pyeclib for that matter)22:20
fungiright, so you'd need to script that22:21
notmynamefungi: so a script in a builder (or called from a builder) that clones, builds, installs, then tests? something like that?22:21
fungiwrite a script to retrieve liberasurecode $somehow from $somewhere and then follow whatever its recommended build process is, including all that in some place your job22:21
fungier, some place in your job22:22
notmynameright. ok22:22
funginotmyname: yep22:22
fungiand if the pyeclib sdist needs to be rebuilt against that, you may need to do something to avoid using prebuilt pyeclib wheels for the platform you're running on22:23
fungior make a separate step to rebuild pyeclib and install it separate from the requirements installation process22:23
notmynamefungi: ok. thanks22:25
fungithough that may depend on whether the symbols have changed in the rebuilt lib22:26
*** m_kazuhiro has quit IRC22:32
*** admin6 has joined #openstack-swift22:41
*** admin6 has left #openstack-swift22:41
*** chlong has quit IRC22:47
openstackgerritTim Burke proposed openstack/pyeclib: Use Py_BuildValue instead of manually building dicts  https://review.openstack.org/39585622:47
claygzaitcev: you put a +2 on patch 387879 - but I'm not 100% what's going on with that test infrastructe - does my comment/question make sense?  Should we land this and revist or should just land this and ignore my ignorant confusion?22:54
patchbothttps://review.openstack.org/#/c/387879/ - liberasurecode - Fix liberasurecode skipping a bunch of invalid_arg...22:54
claygtimburke: I thought that Py_BuildValue stuff was related to the memory leak fix?22:55
zaitcevclayg: sec...22:55
notmynametsg: yay!22:58
notmynameoh, and kevin looked too22:58
tsgnotmyname:  :^) still around, yes!22:58
tsgyep22:58
tsgeven ran it by Mr ISA-L22:58
notmynameI appreciate it22:58
tsghe is going to look into a "fix" Kevin suggested22:58
tsg(to upstream ISA-L that is)22:59
claygzomg really!?23:01
timburkeclayg: kinda? that one looks like it was actually doing things right, but +7/-43 seems... nice. less to think about. compare against the diff at https://review.openstack.org/#/c/385185/1/src/c/pyeclib_c/pyeclib_c.c (that fixes the leak), and you'll see that one didn't have all the dangling PyObject references and (importantly) the calls to Py_XDECREF23:02
patchbotpatch 385185 - pyeclib - Fix formatted get_metadata memory leak23:02
claygtimburke: yes!  I'm very confused about https://review.openstack.org/#/c/385185/1/src/c/pyeclib_c/pyeclib_c.c on the surface?23:03
patchbotpatch 385185 - pyeclib - Fix formatted get_metadata memory leak23:03
kota_tsg: thanks for looking at!23:03
claygit *seems* like ti removed a bunch of input validation?23:03
*** sgundur_ has quit IRC23:03
*** catinthe_ has quit IRC23:04
claygzaitcev: it may not matter - now that tsg +2's the matrix validation change that *depends* on the test change I'm pretty inclined to say whatever followup if any on the test infrastructure stuff should indeed be a follow up23:04
zaitcevclayg: well I see you did +2 it, so I deduced your position23:05
zaitcev(I was trying to see if I'm missing something obvious, like maybe use your simple fix from the comments)23:05
claygyeah i mean that diff *did* make it so running the test suite w/o kota's fixes on those few tests *failed*23:07
claygso I think it was at least *running* the ones that got fixed23:07
clayg... and kota's change is causing at least test_backend_available_invalid_args 's *name* to appear in my test output multiple times for each backend idx23:07
claygso... i'm assuming it's running them more23:08
openstackgerritMerged openstack/liberasurecode: Fix liberasurecode skipping a bunch of invalid_args tests  https://review.openstack.org/38787923:08
timburkeclayg: on the leak -- nope, just skipped a bunch of checks for <0 returns from PyDict_SetItemString, since Py_BuildValue should be dealing with that. and before it didn't even check whether any of the Py*_From* calls failed (say, due to ENOMEM)23:08
clayglooking at the test runner dff it's like - "if this test calls for backends_max just run it" (instead of only run it if args does not return null)23:09
kota_if something to ask on that, please ping me, i'm in parallel conversation at irc now but can be back qucicky here.23:09
kota_clayg: the test fix is for enabling passing (approximately) 100 tests to run correctly23:10
claygtimburke: ahhhh!23:10
claygtimburke: i suck - i was thinking that < 0 was checking the ->blah_blah was > 023:10
kota_probably you can see the diff in the test result (i.e. # of unit test running, w/o patch is around 200 and then w/ patch is around 300)23:10
claygtoday I'm all like "math or c" -- "how do they work!?"23:11
claygkota_: no rush - read my comment on the patch if you get a chance - it's +A'd for now23:11
claygtdasilva: that means you're up soon!23:11
timburkeclayg: yeah, https://docs.python.org/2/c-api/dict.html#c.PyDict_SetItem and https://docs.python.org/2/c-api/arg.html#c.Py_BuildValue were great resources as i was looking into it23:12
claygtdasilva: do you have to... idk update a changelog or something?  what's a release *really* besides some random sha23:12
*** patchbot has quit IRC23:13
*** patchbot has joined #openstack-swift23:13
*** patchbot has quit IRC23:15
*** patchbot has joined #openstack-swift23:16
*** jerrygb has quit IRC23:16
*** asettle has joined #openstack-swift23:17
notmynameclayg: yeah, looks like there's a ChangeLog file that should be updated23:17
claygnotmyname: I DON'T KNOW HOW TO DO THAT *freakout*23:19
notmynameclayg: I can do it, or I can point you in the right direction so you know how23:20
*** jerrygb has joined #openstack-swift23:23
*** david_c has quit IRC23:24
claygnotmyname: you should do it if you are able and tdasilva is not available - and also point me in the right direction if there's things I can read so that next time we're not in a crunch i'm better able to cover if we're not deep enough up there23:25
timburkenotmyname: maybe we *do* need to do some release-shadowing23:25
claygi have zero desire to know this stuff beyond bus-factor23:25
clayg... or notmyname-is-on-a-plane-for-the-next-14-hours-factor23:26
*** david_c has joined #openstack-swift23:26
notmynamethat like never happens. ;-)23:26
notmynamelooks like the skipping tests patch made https://review.openstack.org/#/c/393595/ have a merge conflict23:27
patchbotpatch 393595 - liberasurecode - Fix error handling on gf_ivnert_matrix in isa-l ba...23:27
notmynameor not? I don't know whcih one. point is, merge conflict23:27
kota_notmyname: maybe the isa-l change depends on patch set 3 (or 2?) so23:28
openstackgerritClay Gerrard proposed openstack/liberasurecode: Fix error handling on gf_ivnert_matrix in isa-l backend  https://review.openstack.org/39359523:28
kota_i think we can rebase easily to run git rebase to master and then skipping the test fix23:29
kota_it looks clayg already did.23:29
notmynameyeah. looks like gerrit detected it as a trivial rebase, so kept the reviews23:30
notmynameI clicked +A23:30
*** asettle has quit IRC23:30
kota_thx23:30
claygnice!23:31
*** Jeffrey4l has joined #openstack-swift23:31
zaitcevsuperficially looks obvious to me too, but I see you guys already are on it23:31
notmynamekota_: clayg: what do you want the changelog summary to be?23:31
claygyeah it's master -> testfix -> matrixfix now23:31
zaitcevthere's a free() in out: that works23:31
claygnotmyname: `git log last-tag.. --oneline`23:32
*** Jeffrey4l has quit IRC23:32
claygzaitcev: free() in-n-out!?23:32
*** Jeffrey4l has joined #openstack-swift23:32
*** Jeffrey4l has quit IRC23:33
*** Jeffrey4l has joined #openstack-swift23:34
*** _JZ_ has quit IRC23:34
openstackgerritMerged openstack/liberasurecode: Fix error handling on gf_ivnert_matrix in isa-l backend  https://review.openstack.org/39359523:36
tdasilvaclayg, notmyname: sorry, just taking off now, if it can wait until tomorrow, i can take care of it...but feel free to go ahead without me23:36
*** kei_yama has joined #openstack-swift23:36
notmynametdasilva: I got it23:36
openstackgerritJohn Dickinson proposed openstack/liberasurecode: 1.3.0 release  https://review.openstack.org/39587123:37
notmynameclayg: kota_: ^ look ok?23:37
claygwfm23:39
claygnice work23:39
notmynameI'm just pulling levers. you and kota_ did all the hard parts23:39
kota_notmyname: +2ed23:40
notmynameok, should be five whole minutes (or so) until that lands23:41
kota_great23:41
openstackgerritMerged openstack/liberasurecode: 1.3.0 release  https://review.openstack.org/39587123:44
notmynamebah! speed bump23:45
notmyname! [remote rejected] 1.3.0 -> 1.3.0 (prohibited by Gerrit)23:45
openstacknotmyname: Error: "remote" is not a valid command.23:45
notmynameso it's likely they've turned of pushing tags globally23:45
notmynamebut let me check23:46
notmynameah ha!23:48
notmynamedone! (had to be a signed tag)23:48
notmynameok. it's an official release and is done23:48
notmynamekota_: so now we need to make pyeclib depend on liberasurecode>=1.3.023:49
timburkehuh. i wonder if openstack is also a supybot-powered bot...23:49
notmynametimburke: it is23:50
notmynametimburke: and there are those who have suggested that any new bot should be functionality added to openstack and managed by infra23:50
notmynametimburke: if you want to work on an openstack-bot project, I'll nominate you for PTL ;-)23:51
kota_notmynam: k, will start to work on pyeclib23:52
notmynamekota_: are you just going to add a version specifier to bindep.txt or do you need to plumb some more stuff through (error checking?)23:52
kota_notmname: thinking since today's irc meeting, i'm realizing using bindep for eunsuring liberasurecode >= 1.3.0 may not work well23:53
notmynamewhy's that?23:53
kota_notmyname: i'm not entirly sure because the bindep is for packaging repository (apt/yum), right?23:53
kota_notmyname: and no distros right now and we may be able to install liberasurecode from sorce23:54
kota_source23:54
notmynameright. no distros have it yet. but that's ok (right?). I don't know if we need to do the build-from-source stuff that fungi was talking about first23:54
kota_If i understand correctly, the procedure, 1. try to install liberasurecode 1.1.0 in xenial then 2. try to install from source due to incmpatibility23:55
kota_then, how bindep works on that?23:55
notmynameI don't think there's any reason to do step 123:55
kota_exactly23:55
notmynameno, bindep just gives a list of packages to install23:55
kota_yes23:55
kota_i'm telling how to the version constraint works on bindep23:56
kota_s/how to/how/23:56
notmynameok, so we can't release new pyeclib until we can bump the dependency and we can't do the dependency bump until a distro updates to the new liberasurecode23:56
kota_in my idea23:56
notmynameah, and you're saying we set bindep to >=1.3.0 and then when that fails fall back to install from source?23:57
kota_we can validate the liberasurecode version when loading shard object file (.so) for init.23:57
kota_notmyname: yes23:57
kota_my idea is instead of >=1.3.0 in bindep23:57
*** dfflanders has joined #openstack-swift23:58
kota_if we can have time, i will work on that capability at least today in my time.23:58
notmynamemakes me wonder why we have pyeclib and liberasurecode in 2 separate repos23:59

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