Friday, 2017-02-17

notmynamehttps://etherpad.openstack.org/p/swift-ptg-pike has been reorganized into three big groups00:07
notmyname1. stuff that just needs a few people in a corner to go work through and land00:07
notmyname2. bigger stuff that needs more discussion and is currently being done or should be done soon00:08
notmyname3. bigger stuff that is unlikely to be prioritized in the pike cycle00:08
claygcan we put everything in #3 and just chill next week?00:21
notmynameclayg: (tongue in cheek) that would take another tc resolution00:22
kota_good morning00:24
kota_at office00:24
mattoliveraukota_: morning00:24
kota_mattoliverau: o/00:24
*** sams-gleb has joined #openstack-swift00:25
*** sams-gleb has quit IRC00:29
*** dmorita has joined #openstack-swift00:37
*** dmorita has quit IRC00:46
*** gatuus_ has quit IRC01:04
*** gatuus has quit IRC01:04
openstackgerritClay Gerrard proposed openstack/swift master: Global EC Under Development Documentation  https://review.openstack.org/43251301:10
*** catintheroof has quit IRC01:13
*** jamielennox is now known as jamielennox|away01:18
*** jamielennox|away is now known as jamielennox01:25
clayghas anyone ever used a "structural diff" tool for python before?01:31
claygI'm trying to tease out any differences in test_server.py besides moving the tests to a base class in patch 21916501:35
patchbothttps://review.openstack.org/#/c/219165/ - swift - EC Fragment Duplication - Foundational Global EC C...01:35
claygI'm trying https://github.com/yinwang0/psydiff01:35
clayg... it's doing stuff - but its taking awhile.01:35
*** dmorita has joined #openstack-swift01:37
*** dmorita has quit IRC01:41
claygi feel like this is probably one of those things pycharm would do for me really cheaply somehow?  That or it would work most of time - and when it doesn't there's no hope of ever figuring out why01:45
claygTotal duration: 21.4 minutes !!!01:46
claygbetter be freaking great!01:46
claygnope, didn't really work at all01:51
*** mmotiani_ has joined #openstack-swift01:51
*** winggundamth has joined #openstack-swift02:04
*** tonanhngo has quit IRC02:06
*** tonanhngo has joined #openstack-swift02:12
*** tonanhngo has quit IRC02:17
*** winggundamth has quit IRC02:23
*** tqtran has quit IRC02:24
*** winggundamth has joined #openstack-swift02:25
*** sams-gleb has joined #openstack-swift02:27
*** sams-gleb has quit IRC02:31
mahaticgood morning03:35
*** deepbook5broo has joined #openstack-swift03:36
*** deepbook5broo has left #openstack-swift03:36
mahaticclayg: ah, you pushed up a test already for https://bugs.launchpad.net/swift/+bug/1665141 - I was looking at it yesterday03:36
openstackLaunchpad bug 1665141 in OpenStack Object Storage (swift) "Reconstructor should not hash suffixes after failure" [High,New]03:36
*** zhugaoxiao has quit IRC03:49
*** david-lyle has quit IRC03:49
*** zhugaoxiao has joined #openstack-swift03:50
*** david-lyle has joined #openstack-swift03:50
*** links has joined #openstack-swift04:03
*** adu has joined #openstack-swift04:04
*** adu has left #openstack-swift04:04
*** mmotiani_ has quit IRC04:10
*** mmotiani_ has joined #openstack-swift04:11
*** psachin has joined #openstack-swift04:19
*** mmotiani_ has quit IRC04:27
*** mmotiani_ has joined #openstack-swift04:27
*** lowecase has joined #openstack-swift04:28
*** lowecase has quit IRC04:28
*** sams-gleb has joined #openstack-swift04:29
*** lowecase has joined #openstack-swift04:30
*** lowecase has quit IRC04:30
notmynamegood evening04:30
*** sams-gleb has quit IRC04:34
mattoliveraunotmyname: evening04:39
*** mmotiani_ has quit IRC04:41
*** mmotiani_ has joined #openstack-swift04:43
*** daidv has joined #openstack-swift04:46
*** tqtran has joined #openstack-swift04:51
*** tqtran has quit IRC04:55
*** mmotiani_ has quit IRC04:57
*** mmotiani_ has joined #openstack-swift04:58
*** rcernin has joined #openstack-swift05:08
*** dja has quit IRC05:11
*** mmotiani_ has quit IRC05:12
*** mmotiani_ has joined #openstack-swift05:13
*** maestropandy has joined #openstack-swift05:17
*** klrmn has quit IRC05:18
*** tqtran has joined #openstack-swift05:53
*** daidv has quit IRC05:54
*** tqtran has quit IRC05:58
*** daidv has joined #openstack-swift06:00
*** rcernin has quit IRC06:21
*** sams-gleb has joined #openstack-swift06:33
*** sams-gleb has quit IRC06:37
*** ukaynar has joined #openstack-swift06:38
*** jerrygb has joined #openstack-swift06:41
*** jerrygb has quit IRC06:46
*** geaaru has joined #openstack-swift06:46
*** sams-gleb has joined #openstack-swift07:00
*** jerrygb has joined #openstack-swift07:00
*** rcernin has joined #openstack-swift07:01
*** dja has joined #openstack-swift07:02
*** cshastri has joined #openstack-swift07:04
*** ukaynar has quit IRC07:05
*** jerrygb has quit IRC07:05
*** tesseract has joined #openstack-swift07:11
*** ChubYann has quit IRC07:16
*** dja has quit IRC07:20
*** maestropandy has quit IRC07:45
*** amoralej|off is now known as amoralej07:46
*** tqtran has joined #openstack-swift07:55
*** tqtran has quit IRC07:59
*** mmotiani_ has quit IRC08:10
*** pcaruana has joined #openstack-swift08:22
*** dmorita has joined #openstack-swift08:24
*** webmobi has joined #openstack-swift08:25
webmobiHi I just want to know cloudfuse supports openstack swift with tempauth just for testing08:26
*** dmorita has quit IRC08:31
*** rledisez has joined #openstack-swift08:34
*** daidv has quit IRC08:46
*** bkopilov_ has quit IRC08:48
*** bkopilov has quit IRC08:48
*** dmorita has joined #openstack-swift08:49
*** jordanP has joined #openstack-swift08:49
*** dmorita has quit IRC08:53
*** cbartz has joined #openstack-swift09:01
*** silor has joined #openstack-swift09:17
*** maestropandy has joined #openstack-swift09:30
*** maestropandy has left #openstack-swift09:30
*** silor1 has joined #openstack-swift09:32
*** silor has quit IRC09:33
*** silor1 is now known as silor09:33
*** joeljwright has joined #openstack-swift09:34
*** ChanServ sets mode: +v joeljwright09:34
kota_I'm going to finish up my this week work, looking forward to meeting all swifters at Atlanta PTG09:34
*** wer has quit IRC09:35
kota_see you09:35
*** wer has joined #openstack-swift09:35
*** Jeffrey4l has quit IRC09:42
*** Jeffrey4l has joined #openstack-swift09:55
*** tqtran has joined #openstack-swift09:56
*** Jeffrey4l has quit IRC09:56
*** Jeffrey4l has joined #openstack-swift09:57
*** tqtran has quit IRC10:00
*** bob_cheesey has joined #openstack-swift10:07
bob_cheeseymorning all10:09
bob_cheeseyi've recently taken over maintenance of aswift cluster and whilst i've increased capacity before, i've never reduced it (retiring old nodes). my question is this - obviously I should rebalance the rings first rather than just removing the old node, but once I've weighted the old node down to zero, do i need to keep it in the cluster?10:10
bob_cheeseyi know the rest of cluster will handle the job of creating any missing replicas, so does the old node serve any purpose once it's devices are weighted out?10:11
*** Jeffrey4l has quit IRC10:18
*** Jeffrey4l has joined #openstack-swift10:19
*** dmorita has joined #openstack-swift10:25
*** dmorita has quit IRC10:26
*** dmorita_ has joined #openstack-swift10:26
*** dmorita_ has quit IRC10:31
*** dmorita has joined #openstack-swift10:43
*** jerrygb has joined #openstack-swift10:46
*** sams-gleb has quit IRC10:47
*** sams-gleb has joined #openstack-swift10:47
*** dmorita has quit IRC10:48
*** jerrygb has quit IRC10:50
*** jerrygb has joined #openstack-swift10:51
*** sams-gleb has quit IRC10:51
*** jerrygb_ has joined #openstack-swift10:54
*** jerrygb has quit IRC10:55
*** winggundamth has quit IRC11:10
*** kei_yama has quit IRC11:14
cbartzbob_cheesey: No, if you have a x-replica (x>1) ring, you can turn it off. Like you already thought, the other nodes will take care of the missing replicas.11:14
bob_cheeseycbartz: wonderful, thanks! we're running with 3 replicas so that makes my node replacement timeline a lot shorter11:15
bob_cheeseythanks!11:15
cbartzbob_cheesey: You are welcome.11:15
*** sams-gleb has joined #openstack-swift11:51
*** dmorita has joined #openstack-swift12:09
*** jerrygb_ has quit IRC12:10
*** dmorita has quit IRC12:13
*** catintheroof has joined #openstack-swift12:23
*** vint_bra has joined #openstack-swift12:24
*** jerrygb has joined #openstack-swift12:29
*** NM has joined #openstack-swift12:32
*** jerrygb_ has joined #openstack-swift12:45
*** jerrygb has quit IRC12:46
*** dmorita has joined #openstack-swift12:49
*** dmorita_ has joined #openstack-swift12:58
*** jerrygb_ has quit IRC13:02
*** dmorita has quit IRC13:02
*** jerrygb has joined #openstack-swift13:02
*** kjz has quit IRC13:02
*** silor has quit IRC13:10
*** links has quit IRC13:36
*** NM has quit IRC13:59
*** vint_bra has quit IRC13:59
*** NM has joined #openstack-swift14:03
*** vint_bra has joined #openstack-swift14:05
openstackgerritMahati Chamarthy proposed openstack/swift master: WIP - follow on for race issue fix  https://review.openstack.org/43546014:08
*** chlong has joined #openstack-swift14:15
*** cshastri has quit IRC14:19
*** gatuus has joined #openstack-swift14:29
*** tnovacik has joined #openstack-swift14:34
*** gatuus has quit IRC14:37
*** acoles_ is now known as acoles14:40
*** amoralej is now known as amoralej|lunch14:41
*** joeljwright1 has joined #openstack-swift14:41
*** acoles is now known as acoles_14:42
*** agarner_away has quit IRC14:42
*** aleph1 has joined #openstack-swift14:43
*** joeljwright has quit IRC14:43
*** mmotiani_ has joined #openstack-swift14:45
*** sams-gleb has quit IRC14:54
*** sams-gleb has joined #openstack-swift14:55
*** sams-gleb has quit IRC14:59
*** jerrygb has quit IRC14:59
*** jerrygb has joined #openstack-swift15:00
openstackgerritMahati Chamarthy proposed openstack/swift master: WIP - follow on for race issue fix in reconstructor  https://review.openstack.org/43546015:02
*** psachin has quit IRC15:04
*** jerrygb has quit IRC15:04
*** mmotiani_ has quit IRC15:05
*** mmotiani_ has joined #openstack-swift15:06
*** ukaynar has joined #openstack-swift15:10
*** mmotiani_ has quit IRC15:12
*** sams-gleb has joined #openstack-swift15:13
*** tnovacik has quit IRC15:14
*** psachin has joined #openstack-swift15:15
*** amoralej|lunch is now known as amoralej15:18
*** bkopilov has joined #openstack-swift15:26
*** bkopilov_ has joined #openstack-swift15:26
*** mmotiani_ has joined #openstack-swift15:35
*** chsc has joined #openstack-swift15:38
*** chsc has joined #openstack-swift15:38
*** mmotiani_ has quit IRC15:53
*** mmotiani_ has joined #openstack-swift15:55
*** psachin has quit IRC15:56
*** dmorita_ has quit IRC15:57
*** tqtran has joined #openstack-swift16:00
*** bob_cheesey has quit IRC16:04
*** tqtran has quit IRC16:04
*** ukaynar has quit IRC16:08
*** bkopilov_ has quit IRC16:13
*** bkopilov has quit IRC16:13
*** pcaruana has quit IRC16:21
notmynamegood morning16:22
rledisezgood morning notmyname. i see this talk may happen in boston: https://www.openstack.org/summit/boston-2017/vote-for-speakers/#/1746516:25
rledisezi'm wondering if you have (or can have) the contact info of these guys16:26
rledisezi would be very interested to talk with them. it seems we are doing the same thing16:26
notmynamerledisez: yeah, that looks pretty cool, doesn't it? unfortunately, the first I've heard of it is when someone pointed out the talk presentation16:28
rledisezok. i guess the foundation has their emails as they have an account on openstack.org. but it's surely not ok to give them to anybody (aka me :))16:30
tdasilvait doesn't look like they have contributed to openstack before, can't really find their names on stackalytics16:31
*** caiobrentano has joined #openstack-swift16:35
*** rcernin has quit IRC16:35
*** ukaynar has joined #openstack-swift16:35
rledisezi just saw there is a contact form on the profile page on openstack.org: https://www.openstack.org/community/speakers/profile/11024/jeff-li16:36
rledisezi'll try this way, we'll see16:37
notmynameyeah, that's interesting16:37
notmynameI'd love to see what they're doing16:37
tdasilvarledisez: yeah that works, also found them on linkedin16:38
notmynamein my mind, the small file optimization is great. also, the refactored object server and repl protocol (in golang) is also great16:38
*** rledisez has left #openstack-swift16:38
*** rledisez has joined #openstack-swift16:38
notmynameI think I'd prefer to see small file work build on top of new object servers instead of implementing it on old ones and reimplementing it on new ones16:39
notmynamebut I don't want to slow down stuff that's going on either :-)16:39
*** tonanhngo has joined #openstack-swift16:39
cbartzcschwede_: Just watched your talk https://www.openstack.org/videos/vancouver-2015/monitoring-your-swift-cluster-health . At the end you say you upload the example config files somewhere. Can you please send me the location, if the resources are still online? You can send me via eMail, if I am not anymore in IRC. This would be great.16:39
notmynamethat ordering and dependency is one thing I'm hoping to come to grips with next week16:39
rledisezi think golang should come first, but as it's not ready we are working on python to validate the solution (we will probably have production deployement of small files stuff before golang is prod ready)16:39
rledisezso let's think of our effort as a way to validate the idea16:40
notmynamerledisez: yep. there's the reality :-)16:40
rledisezif it work, we will re-do it in golang once it replaced the python version16:40
*** gatuus has joined #openstack-swift16:40
rledisezand it would be insane to merge that kind of stuff in hummingbird before it replaced python. one step at a time :)16:41
timburkegood morning16:41
tdasilvanotmyname: what do you mean by: "...build on top of new object servers instead of implementing it on old ones..."16:41
*** tesseract has quit IRC16:41
timburkegolang object servers, rather than python16:41
tdasilvaok16:42
notmynameya16:42
tdasilvawhat's the plan concerning golang conversations next week?16:42
tdasilvain terms of TC approval stuff, not internal "what we need to work on hummingbird" stuff16:43
notmynametdasilva: good question. that probably will involve some more hallway conversation than just "in the swift room" stuff16:43
notmynameI'm plannign on reading up ont he tc rules and hopefully on mon/tues talk to the right not-swift people16:44
notmynameand have some answers/guidance for swift people on wed-fri16:45
tdasilvaok, sounds like a plan16:45
notmynametdasilva: but I'd definitely appreciate your help on that too :-)16:45
notmynameI think it's a lot of simply writing down our answers to stuff like how to do docs, dependencies, etc16:46
tdasilvanotmyname: yep, i talked to Flavio earlier today and mentioned we might reach out to him there16:46
notmynamecool16:47
notmynameirc or is he in westford right now?16:47
tdasilvairc16:47
notmynamek16:47
tdasilvahe mentioned we should ping dtroyer too16:47
cschwede_cbartz: i think you're looking for https://github.com/cschwede/fedora-swift-rdo16:48
notmynameyeah, dean was working on the golang testing rules16:48
*** ukaynar has quit IRC16:48
cbartzcschwede_: Thank you. ;-)16:49
tdasilvastepping out for lunch, be back later16:50
*** dmorita has joined #openstack-swift16:58
*** cbartz has left #openstack-swift17:01
*** dmorita has quit IRC17:02
*** jordanP has quit IRC17:07
*** Guest36_ has joined #openstack-swift17:19
*** Guest36_ is now known as Darkpixl17:19
*** zaitcev has joined #openstack-swift17:23
*** ChanServ sets mode: +v zaitcev17:23
*** rledisez has quit IRC17:39
*** jerrygb_ has joined #openstack-swift17:46
*** Raymii has quit IRC17:47
*** jerrygb has joined #openstack-swift17:50
timburke:-( libec's crc32 seems to produce different results on my mac vs my linux vm. which means i can't decode frags generated on one from the other, because the headers are invalid17:51
*** jerrygb_ has quit IRC17:51
notmynamethat seems ... troubling?17:52
notmynametimburke: same data but different crc?17:54
timburkebut at the same time, things are at least consistent on the same machine. mac can decode mac, linux can decode linux. only linux's crc matches python stdlib's, though17:55
timburkedid we ever make the assertion that frags should be portable cross-platform?17:55
*** klrmn has joined #openstack-swift17:56
timburkeand if we *fix* the implementation for my mac (i think it might have to do with 32 vs 64 bit ints, maybe?) did we just break some users' data on disk?17:58
notmynametimburke: do you have a repro script I can run?17:58
*** bikmak has quit IRC17:59
notmynameoh, so 64 vs 32 bit? meaning you might find similar issues on 32 bit linux?17:59
timburkeand the more i look at https://github.com/openstack/liberasurecode/blob/master/src/utils/chksum/crc32.c the less i like it -- why is it declared with ints when those are only guaranteed to be at least 16 bits?17:59
notmynameint instead of explicit uing64_t or something?18:00
timburkenotmyname: fwiw, i realized that my mac thinks the appropriate format string for uint64_t is %lu, while the linux vm thinks it's %llu18:00
notmyname(it's been a long time since I've done C types)18:00
timburkeuint32_t -- it's right there in the name!18:01
notmynameso it got compiled as 32 bit on the mac and 64 bit on linux? or vice versa?18:04
timburkeor did i have that the other way? maybe the mac wanted llu and linux wanted lu. either way, https://review.openstack.org/#/c/434162/5/src/erasurecode.c should maybe be using PRIu6418:06
patchbotpatch 434162 - liberasurecode - Fix valgrind-check and memory leak18:06
*** Darkpixl has quit IRC18:18
*** joeljwright1 has quit IRC18:33
*** tqtran has joined #openstack-swift18:51
*** dmorita has joined #openstack-swift18:59
-openstackstatus- NOTICE: Restarting gerrit due to performance problems19:04
*** dmorita has quit IRC19:05
*** oshritf_ has joined #openstack-swift19:29
*** ChubYann has joined #openstack-swift19:32
*** tnovacik has joined #openstack-swift19:32
*** oshritf_ has quit IRC19:37
timburkeo_O so my go bindings behave the same on mac & linux vm. but...how could that even be an issue? the data's getting written down in C...19:38
timburkelike, why are the python bindings doing different things on different platforms, but the go bindings *don't*?19:38
*** dmorita has joined #openstack-swift19:48
*** dmorita has quit IRC19:53
pdardeau_timburke: is there a single standard for official crc algorithm?19:53
*** tnovacik has quit IRC19:55
*** tnovacik has joined #openstack-swift19:56
timburkei feel like https://github.com/torvalds/linux/blob/master/lib/crc32.c ought to be a pretty good reference implementation...19:57
notmynametimburke: so why doesn't libec use that one?19:58
notmynamea question for tsg I guess19:58
notmynameGPL maybe?19:58
pdardeau_see 1st paragraph of "Standards and common use" https://en.wikipedia.org/wiki/Cyclic_redundancy_check19:58
timburke...cross-platform goodness? idk19:58
openstackgerritThiago da Silva proposed openstack/swift master: Symlink implementation.  https://review.openstack.org/23216220:00
*** dmorita has joined #openstack-swift20:04
*** mmotiani_ has quit IRC20:09
*** dmorita has quit IRC20:09
*** silor has joined #openstack-swift20:28
openstackgerritClay Gerrard proposed openstack/swift master: Do not sync suffixes when remote rejects reconstructor revert  https://review.openstack.org/43515220:30
*** silor has quit IRC20:32
*** amoralej is now known as amoralej|off20:37
*** jerrygb has quit IRC20:44
*** dmorita has joined #openstack-swift20:52
*** dmorita has quit IRC20:57
*** mmotiani_ has joined #openstack-swift20:57
timburkeour table at https://github.com/openstack/liberasurecode/blob/master/src/utils/chksum/crc32.c#L69 seems to match the one from https://github.com/madler/zlib/blob/master/crc32.h -- which would imply CRC-32, rather than SSE4's CRC-32C (which seems to be what we meant to do https://github.com/openstack/liberasurecode/blob/master/src/utils/chksum/crc32.c#L115-L116)21:00
timburkebleh. thanks pdardeau_ -- it was definitely useful to be able to quickly look up names from polynomial hex21:02
*** bkopilov has joined #openstack-swift21:04
*** bkopilov_ has joined #openstack-swift21:04
*** dmorita has joined #openstack-swift21:08
*** NM has quit IRC21:10
*** caiobrentano has quit IRC21:12
*** dmorita has quit IRC21:12
*** tnovacik has quit IRC21:28
*** Jeffrey4l_ has joined #openstack-swift21:34
*** Jeffrey4l has quit IRC21:34
*** tonanhngo has quit IRC21:38
notmynametimburke: have you come across any "set the network chunk size" things in the requests library?21:45
timburkenotmyname: how do you mean? like, the size for transfer-encoding: chunked? or the buffers involved for the socket?21:47
notmynamebuffers21:48
timburkei've not played with that... how do we do it in swift?21:48
notmynameI'm helping someone diagnose a problem, and they're reporting that swiftclient is using a pretty small buffer size (but TBH, that's reported, not repro and confirmed).21:48
notmynamethe ultimate problem here is two different clients sending to the same swift cluster and swiftclient is slow. and I'm told that swiftclient is using much smaller network buffers21:50
notmynameI was hoping to find some constant somewhere to hack a hard-coded change into and test it to see if there's a difference, but it seems like requests is full of magic wrapped in abstraction ;-)21:51
*** dmorita has joined #openstack-swift21:55
*** jerrygb has joined #openstack-swift21:57
timburkenotmyname: might be able to try something like http://stackoverflow.com/questions/24569428/how-to-specify-socket-options-in-python-requests-lib-since-urllib3-v1-8-3-has#24570887 to set SO_SNDBUF/SO_RCVBUF sizes...21:58
*** dmorita has quit IRC22:00
*** vint_bra has quit IRC22:00
*** mmotiani_ has quit IRC22:01
timburkeor if you're feeling adventurous, go poking requests.packages.urllib3.connection.HTTPConnection.default_socket_options directly22:01
*** jerrygb has quit IRC22:03
*** tonanhngo has joined #openstack-swift22:16
*** sams-gleb has quit IRC22:41
*** sams-gleb has joined #openstack-swift22:41
*** sams-gleb has quit IRC22:41
*** dmorita has joined #openstack-swift22:43
*** dmorita has quit IRC22:47
*** jerrygb has joined #openstack-swift23:00
*** gatuus has quit IRC23:04
*** NM has joined #openstack-swift23:10
timburke:-/so we don't *quite* use the zlib crc32 algo... while the table looks right, the fact that we're dealing with ints instead of unsigned ints means https://github.com/openstack/liberasurecode/blob/master/src/utils/chksum/crc32.c#L127 is technically off in undefined behavior23:11
*** NM has quit IRC23:11
timburke"When performed on a signed type, the result is technically undefined and compiler dependant,[5] however most compilers will perform an arithmetic shift, causing the blank to be filled with the sign bit of the left operand."23:11
*** catintheroof has quit IRC23:21
*** catintheroof has joined #openstack-swift23:22
*** catintheroof has quit IRC23:26
*** dmorita has joined #openstack-swift23:30
timburkesecond issue: i don't see where INTEL_SSE4 would get defined, so i think all of https://github.com/openstack/liberasurecode/blob/master/src/utils/chksum/crc32.c#L46-L66 is dead code23:32
timburkei *do* see a INTEL_SSE42, which seems to be what's called for anyway -- the crc32 instruction seems to have been added in 4.2 https://en.wikipedia.org/wiki/SSE4#SSE4.223:32
timburkebut none of any of that explains why i get good, zlib-compatible crcs from go but busted crcs from python. that's just weird23:34
*** dmorita has quit IRC23:34
notmynametimburke: that sounds bad23:39
notmynameso it could be a difference between gcc on linux and clang/llvm on apple?23:39
timburkenotmyname: it doesn't seem great, no. might be the compiler, but that would seem to imply that i've got some schizophrenia with my gcc compiler on my linux vm23:41
notmynametimburke: that sounds bad23:41
timburkealso, that i'm not picking up the same liberasurecode at runtime between go and python? i guess?23:41
notmyname;-)23:41
notmynameI think this conversation is you saying something and me <up arrow><enter>23:42
notmynametimburke: that sounds bad23:42
*** sams-gleb has joined #openstack-swift23:42
timburkeyeah, yeah it does. the one redeaming point is that we don't actively have people yelling at us that all of they're EC data is unreadable because we think the header's gone bad23:43
notmynametimburke: that sounds bad^wgood23:43
notmyname;-)23:43
timburkeso hopefully it's actually user error...somehow. and the next libec upgrade *totally won't* flip that bit and make everything terrible, right?23:43
notmynameso the risk is what? when loading a different libec...yeah. that. the next libec (or even reinstalling the current==recompile) doesn't inadvertently change the bits23:44
notmynamewow. if ever there's a use case for reproducible builds, this is it :-)23:44
notmynameI learned some about that work at LCA this year23:44
*** chlong has quit IRC23:46
notmynamethe goal being that a deliverable is bit-for-bit identical to every other deliverable (on a given platform, arch, etc) every single time it is built for every single person23:47
*** sams-gleb has quit IRC23:47
notmynamemeaning that in this case, libec on a 64-bit box would be exactly the same as every other 64 bit box23:48
notmynameif I understand it correctly23:48

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