| jimbaker | niemeyer, re point #4 in your review of cobbler-zk-connect-error-message, we have been using RST in docstrings for a while. not consistently of course. but this did address a review point i made in what this branch is stacked on | 00:14 |
|---|---|---|
| jimbaker | of course it would be nice to use sphinx to generate api docs | 00:14 |
| niemeyer | jimbaker: The format used by William there is not any format I personally recognize | 00:16 |
| niemeyer | jimbaker: It looks very much like the syntax pointed out by hazmat, but not quite | 00:17 |
| niemeyer | jimbaker: I'm personally happy with anything, though | 00:17 |
| niemeyer | jimbaker: Let's just agree on a standard and move on with it | 00:17 |
| jimbaker | niemeyer, sure, i guess if it's slightly tweaked it would conform | 00:17 |
| niemeyer | jimbaker: Interestingly, in Go there's actually no special syntax | 00:18 |
| niemeyer | jimbaker: Besides a convention to start the sentence with the function name itself + verb.. | 00:18 |
| jimbaker | niemeyer, i think that's the point of rst docs is to move in that direction | 00:18 |
| niemeyer | jimbaker: Works quite well | 00:18 |
| jimbaker | niemeyer, albeit w/ a small amount of markup compared to go. but not as rigid as the javadoc/epydoc style | 00:19 |
| jimbaker | anyway, as i understand it, we agree on this point, so that's good :) | 00:19 |
| niemeyer | jimbaker: Right, I don't mind the touch of RST in Python, even though I wouldn't do it in Go as the standard tools do not use it | 00:19 |
| niemeyer | jimbaker: +1 | 00:19 |
| sidnei | so is there a puppet formula yet? /me hides | 00:39 |
| hazmat | sidnei, nope | 01:18 |
| hazmat | sidnei, notionally a puppet formula would be a colo located service, the implementation of which is post oneiric | 01:19 |
| sidnei | hazmat, ah, right. makes sense. | 01:36 |
| _mup_ | ensemble/stack-crack r327 committed by kapil.thangavelu@canonical.com | 01:37 |
| _mup_ | less granular s3 file storage error checking | 01:37 |
| h0lyRS | hey guys... is it normal that a bootstrap instance is being created without a key-pair? | 04:04 |
| h0lyRS | i think i just found the answer here: http://irclogs.ubuntu.com/2011/08/02/%23ubuntu-ensemble.html | 04:46 |
| siwos | hi. | 07:05 |
| siwos | anyone using ensemble with openstack? | 07:05 |
| siwos | I keep getting this message with openstack | 07:34 |
| siwos | ERROR Error Message: AWS authorization header is invalid. Expected AwsAccessKeyId:signature | 07:34 |
| siwos | anyone? | 07:34 |
| siwos | please - note the fact I run only computing part of openstack right now | 07:37 |
| _mup_ | Bug #831805 was filed: wildly inconsistent docstring style <Ensemble:New> < https://launchpad.net/bugs/831805 > | 08:00 |
| _mup_ | Bug #831883 was filed: weak error message testing <Ensemble:New for fwereade> < https://launchpad.net/bugs/831883 > | 10:02 |
| hazmat | siwos, its a known issue atm, i've got some work in-progress for openstack compatibility. | 11:46 |
| siwos | hazmat - thanks for clarifying this ;-) | 11:47 |
| siwos | I keep an eye on this project ;-) | 11:47 |
| hazmat | siwos, if you really want to try it, i can give some instructions, but its using a few branches atm. | 11:47 |
| hazmat | siwos, out of curiosity, are your instances routable from the machine your using the ensemble cli on? | 11:48 |
| hazmat | in your openstack setup | 11:48 |
| siwos | well - I am stress testing openstack compute (over 100 vm-s currently running) - so definitely I am interested in orchestrating them ;-) | 11:49 |
| siwos | instances are routable | 11:49 |
| siwos | I've gote ensemble running on my api node | 11:49 |
| hazmat | siwos, cool, that should work well | 11:49 |
| siwos | if you find some time - just tell me what to do ;-) | 11:50 |
| hazmat | siwos, i can't really provide any help on it, i'm trying to get into the ppa for next week but here are the instructions if you want to try it out. http://pastebin.ubuntu.com/673083/ | 11:58 |
| siwos | great - thanks! I'll try to get this running | 11:59 |
| === kim0_ is now known as kim0 | ||
| niemeyer | Hello all | 12:20 |
| fwereade | niemeyer: morning/afternoon | 12:22 |
| === otubo[AFK] is now known as otubo | ||
| niemeyer | fwereade: Hey! | 12:27 |
| hazmat | fwereade, g'afternoon | 12:28 |
| fwereade | niemeyer, hazmat: hey guys :) how's life? | 12:29 |
| hazmat | peachy :-) | 12:29 |
| niemeyer | hazmat: How's the LXC work coming? | 12:30 |
| hazmat | niemeyer, just getting into it, i had a talk with ben yesterday to catch up, i'm starting in on the lxc-provider today.. wanted to try and get the openstack branch (stack-crack) cleaned up and into the review queue as well | 12:35 |
| niemeyer | hazmat: Ok.. I'm a bit concerned because things have been on the quiet side | 12:37 |
| hazmat | niemeyer, its going to be tight, but things will heat up this week, and i can give a more accurate assessment of concern.. afaics both openstack and lxc are top level priorities for the release | 12:39 |
| niemeyer | hazmat: Sounds good, thanks | 12:40 |
| niemeyer | hazmat: They are top priorities, and we have to try to coordinate efforts | 12:40 |
| fwereade | niemeyer: speaking of review queues... cobbler-shutdown has apparently not been touched in the week since you approved it; should I be picking on people and hassling them myself, or...? | 12:40 |
| niemeyer | hazmat: My original plan was to have jimbaker pushing the OpenStack fixes | 12:41 |
| niemeyer | hazmat: But your work on it is hugely appreciated | 12:41 |
| niemeyer | hazmat: The problem is just that it means the other side is less covered | 12:41 |
| hazmat | niemeyer, yeah.. i know i asked him about it, but then i realized i had told spamas i'd try to get some time on it last week.. and then i got it working ;-) | 12:41 |
| niemeyer | fwereade: Yes, that's always a good idea :) | 12:41 |
| niemeyer | hazmat: Right.. and we haven't heard much from Jim on the topic, so can't blame you | 12:42 |
| niemeyer | jimbaker: Haven't heard much on the topic of testing either.. have to catch up with you | 12:42 |
| hazmat | niemeyer, i was inspired by robbie's JFDI for the web stuff | 12:42 |
| * hazmat likes JFDI | 12:43 | |
| hazmat | can i get some more ;-) | 12:43 |
| fwereade | yeah, it pleases me that there's a somewhat widely understood acronym for it | 12:43 |
| niemeyer | hazmat: Yes, JFD the local development feature now, please :-) | 12:47 |
| niemeyer | Meanwhile, I have to JFD the store | 12:47 |
| hazmat | niemeyer, so we don't want to have a separate package for local dev? | 12:48 |
| niemeyer | hazmat: Not unless necessary | 12:49 |
| hazmat | i'll need to apt-get install zk and jdk in bootstrap.. to be sure there present otherwise afaics | 12:49 |
| hazmat | niemeyer, the notion is zk and machine agent are running on the host | 12:50 |
| hazmat | offset port for zk | 12:50 |
| niemeyer | hazmat: zk is already packaged.. machine agent is already packaged too | 12:50 |
| hazmat | niemeyer, ? packaged != installed on the client side | 12:50 |
| niemeyer | hazmat: Sorry, I'm still missing some context.. installed on the client side == apt-get install ensemble | 12:51 |
| hazmat | niemeyer, right that doesn't install zk locally, just the admin client tools. | 12:51 |
| hazmat | niemeyer, for local dev we need zk locally in addition to the admin client tools | 12:51 |
| niemeyer | hazmat: apt-get install zookeeper installs zk.. | 12:51 |
| hazmat | niemeyer, right.. but if i have the client tools, i don't know if "apt-get install zookeeper" equivalent has been done or not | 12:52 |
| hazmat | i guess i can detect it.. the question is do i do it for the user or ask them to do it | 12:52 |
| niemeyer | hazmat: I'd just try to run it as usual, and report an error if the command isn't found | 12:53 |
| hazmat | i'm also going to leave off debootstrap progress reporting, the additional lxc template script layer would need some changes, bcsaller this might make a nice optional thing in the future, if we can get the lxc-template to take it as an optional parameter when debootstraping, we can get back a progress stream from it ala https://github.com/jolicloud/base-installer (see documentation at bottom of readme) | 13:01 |
| RoAkSoAx | fwereade: ping | 13:40 |
| fwereade | RoAkSoAx: pong | 13:41 |
| RoAkSoAx | fwereade: howdy!! how's it going man | 13:41 |
| fwereade | RoAkSoAx: pretty good thanks, and you? | 13:41 |
| RoAkSoAx | fwereade: pretty good | 13:41 |
| fwereade | RoAkSoAx: any joy on the installer? | 13:41 |
| RoAkSoAx | fwereade: oh yeah! | 13:42 |
| _mup_ | Bug #832041 was filed: orchestra FileStorage can't handle unicode paths <Ensemble:New> < https://launchpad.net/bugs/832041 > | 14:21 |
| _mup_ | Bug #832043 was filed: can't deploy on orchestra <Ensemble:New for fwereade> < https://launchpad.net/bugs/832043 > | 14:25 |
| hazmat | bcsaller, re lxc-lib lxc-ls has different output depending on container status | 15:12 |
| bcsaller | hazmat: lxc_ls isn't part of the public api anyway | 15:17 |
| === otubo is now known as otubo[AFK] | ||
| hazmat | bcsaller, it needs to be | 15:18 |
| bcsaller | why? a set of container objects isn't enough? there could easily be containers unrelated to ensemble returned by lxc-ls | 15:19 |
| hazmat | bcsaller, to satsify the get_machines interface of the provider | 15:20 |
| hazmat | bcsaller, i'm tracking which machines belong to ensemble by recording name on start | 15:20 |
| bcsaller | hazmat: so its not ls so much as container status? | 15:21 |
| bcsaller | container.running might be what you want | 15:21 |
| jimbaker | niemeyer, hi, you wanted to catch up? | 15:22 |
| hazmat | bcsaller, that's not in the published version.. and i want to get all the running containers. | 15:23 |
| niemeyer | jimbaker: I wrote a message to the list about it.. can you please answer it there? | 15:23 |
| hazmat | bcsaller, did you push the lib again? | 15:23 |
| jimbaker | cool, i was just catching up on emails etc | 15:23 |
| hazmat | i branched yesterday | 15:23 |
| bcsaller | hazmat: I'll push a new version this morning, I expect within the hour | 15:23 |
| niemeyer | Hmm.. interesting.. in Go we don't need the schema library to _coerce_ the values. | 15:30 |
| niemeyer | We need it for validation purposes only | 15:30 |
| niemeyer | Since the yaml/json support will automatically coerce values as necessary for actual use | 15:31 |
| niemeyer | I guess I'll just mimic the implementation even then.. it won't really hurt to have coercion working | 15:32 |
| niemeyer | But now, I'll have lunch instead | 15:34 |
| niemeyer | biab | 15:34 |
| niemeyer | wrtp: Hey, btw :) | 15:34 |
| === m_3_ is now known as m_3 | ||
| === daker is now known as daker_ | ||
| wrtp | niemeyer: hiya! | 16:09 |
| fwereade | later all, I'll try to pop back on later but no guarantees | 16:21 |
| === otubo[AFK] is now known as otubo | ||
| _mup_ | Bug #832183 was filed: HA - Ensemble needs to handle a failed bootstrap. <Ensemble:New> < https://launchpad.net/bugs/832183 > | 17:02 |
| bcsaller | hazmat: can you pull from the branch again, the container stuff is more inline with what we talked about | 17:11 |
| hazmat | bcsaller, cool, just doing a review, i'll pull shortly | 17:11 |
| bcsaller | hazmat: I'll fetch some coffee then, I'll be around in a few | 17:12 |
| jimbaker | adam_g, thanks for putting that bug in so it's not just in our heads | 17:39 |
| jimbaker | adam_g, i still think that we can get to that without rewriting the provisioning agent, although that's preferable for the long-term solution | 17:40 |
| hazmat | its a fairly simple change | 17:41 |
| hazmat | structuring it so that we can use ensemble commands to expand it is what needs work | 17:42 |
| jimbaker | hazmat, glad to hear the concurrence so to speak | 17:42 |
| jimbaker | hazmat, indeed, that's part of the long-term reimpl | 17:42 |
| jimbaker | simply have one active provisioning agent at a time, with 1 or more on standby. just ZK to determine who is active (standard leader stuff). that should be enough | 17:44 |
| niemeyer | jimbaker: I don't think that's necessary | 17:49 |
| niemeyer | jimbaker: Original plan discussed with hazmat back then allowed for multiple implementations working in parallel | 17:49 |
| jimbaker | niemeyer, sure, just my opinion here | 17:49 |
| jimbaker | back to functional testing stuff ;) | 17:49 |
| niemeyer | jimbaker: Sure, just mine there | 17:49 |
| hazmat | jimbaker, yeah just a queue with multiple providers agents active | 17:50 |
| hazmat | alternatively a lock structure, but a queue seems more appropriate | 17:51 |
| hazmat | wtf, i think just got hit by an earthquake | 17:52 |
| jimbaker | hazmat, in dc? | 17:52 |
| hazmat | jimbaker, yeah.. big one.. house rattled pretty heavy | 17:52 |
| niemeyer | hazmat: Woah! | 17:52 |
| jimbaker | i do remember an earthquake in providence rhode island, but it was remarkable only because it was perceptible | 17:53 |
| hazmat | i got some broken glass to cleanup, bbiab | 17:55 |
| jimbaker | i got a stomach to take care of, biab | 17:55 |
| niemeyer | hazmat: Ouch.. is everyone ok there? | 17:55 |
| bcsaller | hazmat: looks like they estimate a 5.8, thats a pretty good sized one | 17:55 |
| hazmat | niemeyer, everyone on the block seems okay, not sure about folks on metro, sirens are starting | 17:57 |
| niemeyer | hazmat: :-( | 17:57 |
| hazmat | bcsaller, i moved out sf to get away from the earthquakes ;-) | 18:00 |
| hazmat | all phone lines jammed. evac in progress on pentagon and capital | 18:01 |
| niemeyer | hazmat: Ugh.. everyone calling their loved ones | 18:02 |
| hazmat | indeed | 18:02 |
| bcsaller | people could feel it all the way in NYC | 18:06 |
| hazmat | everything seems okay, some structural damage, no major injury scenes per the police scanner | 18:09 |
| jimbaker | reminds me of when i was in an earthquake in seattle in 2001 iirc | 18:10 |
| SpamapS | http://earthquake.usgs.gov/earthquakes/recenteqsus/Maps/US10/32.42.-85.-75.php | 18:10 |
| SpamapS | 5.9, thats a real shaker! | 18:11 |
| SpamapS | very shallow | 18:11 |
| SpamapS | 1km | 18:11 |
| hazmat | fwereade, review in | 18:15 |
| fwereade | hazmat: you rock :) | 18:21 |
| hazmat | fwereade, you just missed the context that makes that an understatement | 18:22 |
| * fwereade scrolls up... | 18:22 | |
| hazmat | fwereade, http://news.blogs.cnn.com/2011/08/23/quake-hits-near-washington-d-c/?hpt=us_c2 | 18:22 |
| fwereade | holy shit :) | 18:22 |
| fwereade | all ok? | 18:22 |
| hazmat | fwereade, so far so good, i've got police scanner on in the background, mostly minor structural damage | 18:23 |
| fwereade | hazmat: phew | 18:23 |
| fwereade | hazmat: well then, let me restate: you shake violently, and cause minor structural damage, but in a good way | 18:24 |
| niemeyer | hazmat: Was just thinking.. a lot of people must have panicked there thinking it was something else | 18:32 |
| hazmat | niemeyer, dc rolls like that | 18:33 |
| niemeyer | I'm also slightly surprised twitter didn't fall down :-) | 18:33 |
| hazmat | niemeyer, the sad part is landline and cell did. twitter is *the* source of breaking news as much as anything else | 18:34 |
| niemeyer | hazmat: Better tell the family to check twitter next time.. :) | 18:45 |
| niemeyer | How ironic.. | 18:46 |
| jimbaker | interesting, we also had an earthquake here in colorado: http://www.cnn.com/2011/US/08/23/colorado.quake/ | 19:27 |
| === otubo is now known as otubo[AFK] | ||
| niemeyer | jimbaker: Would you mind to respond to the message in the ML? | 19:52 |
| jimbaker | niemeyer, i'm writing up a reply | 20:04 |
| niemeyer | jimbaker: Thanks | 20:04 |
| jimbaker | niemeyer, i haven't had a chance to work on it until now, but as i understand it, it's now my #1 priority. so that's fine | 20:05 |
| niemeyer | SpamapS: ping | 20:28 |
| SpamapS | niemeyer: pong! good afternoon! | 20:29 |
| niemeyer | SpamapS: Hey man! | 20:30 |
| === pfibiger` is now known as pfibiger | ||
| adam_g | SpamapS: did pushing formulas to arbitrary branches ever get figured out? | 20:42 |
| niemeyer | adam_g: Yeah | 20:47 |
| niemeyer | adam_g: Should be working already | 20:47 |
| SpamapS | adam_g: I've tested it recently, seems to work fine. | 20:47 |
| adam_g | oh, neat | 20:49 |
| adam_g | just push to lp:principia/whatever? | 20:49 |
| SpamapS | yes but | 20:50 |
| SpamapS | make sure its lp:~ensemble-composers/principia/oneiric/whatever/trunk *first* | 20:50 |
| SpamapS | If you push your branch there , then only you will own the official branch | 20:50 |
| === otubo[AFK] is now known as otubo | ||
| adam_g | hmm. ok | 20:51 |
| SpamapS | adam_g: it really doesn't matter too much, as we can always take over the official branch if we need to make a change.. but its better if they're just all owned by ensemble-composers | 20:52 |
| adam_g | SpamapS: still seing a no such source package. does this require a bzr upgrade? | 20:54 |
| adam_g | http://paste.ubuntu.com/673370/ | 20:54 |
| SpamapS | hm | 20:58 |
| niemeyer | Hmm | 20:58 |
| niemeyer | bcsaller: Wondering about the regex part of our validator | 20:59 |
| niemeyer | (in the context of schema0 | 20:59 |
| niemeyer | ) | 20:59 |
| SpamapS | adam_g: maybe | 20:59 |
| SpamapS | $ bzr push lp:~ensemble-composers/principia/oneiric/nova-cloud-controller/trunk | 20:59 |
| SpamapS | Created new branch. | 20:59 |
| bcsaller | niemeyer: what about it? | 21:00 |
| niemeyer | bcsaller: We have a couple of issues.. one short term, one long term | 21:00 |
| niemeyer | bcsaller: long term is compatibility.. if we move out of Python, the regex syntax will change | 21:00 |
| bcsaller | you want something that uses a regex to validate rather than validates something is a regex | 21:00 |
| m_3 | adam_g: I've got notes for how to create a dummy source package that gets around this... lemme dig them up | 21:01 |
| bcsaller | ahh, right, you're porting to go... | 21:01 |
| adam_g | SpamapS: hmm | 21:01 |
| SpamapS | m_3: shouldn't be necessary anymore tho | 21:01 |
| niemeyer | bcsaller: The other issue, which would affect us even in the short term, is that a Python regex is a wonderful way to DoS a system :) | 21:01 |
| niemeyer | bcsaller: Which means even if it was Python across the board, I can't validate them on the server | 21:02 |
| bcsaller | wonderful how? its used to validate the config stuff before its sent over the network now. I mean sure it could be, but its like saying an install script could fork-bomb | 21:02 |
| bcsaller | right now its only used in the environment and config parsing I think | 21:03 |
| niemeyer | bcsaller: Hmm.. true.. I guess as long as we don't apply the regex, that'd be fine | 21:03 |
| SpamapS | is pcre available in python? Thats pretty much the lingua franca for regexes.. and usually the faster implementation | 21:03 |
| niemeyer | bcsaller: It'll be an issue for GUI systems, though | 21:03 |
| niemeyer | bcsaller: e.g. any kind of hosted management interface | 21:04 |
| niemeyer | bcsaller: So it's not exactly like a fork-bombing install script | 21:04 |
| niemeyer | bcsaller: The regex is run in the management interface | 21:05 |
| niemeyer | bcsaller: Isn't it? | 21:05 |
| bcsaller | in that case, no, I agree, but it something we can work around | 21:05 |
| bcsaller | niemeyer: do golang use re2? | 21:05 |
| niemeyer | bcsaller: Kind of.. | 21:06 |
| niemeyer | bcsaller: re2 was written by the authors of golang, conveniently.. | 21:06 |
| niemeyer | bcsaller: It's being ported to Go | 21:06 |
| SpamapS | adam_g: what version of bzr do you have? | 21:06 |
| m_3 | adam_g: http://pastebin.com/aZG0NQ8n they're rough and shouldn't be needed anymore... | 21:07 |
| niemeyer | bcsaller: I think we should restrict the syntax accepted to a more common ground regex, for the moment | 21:07 |
| bcsaller | niemeyer: I don't know that there is a single common regex def that we could validate in JS in a GUI, but the validator could run in a time bound thread if you're really worried about it | 21:07 |
| niemeyer | bcsaller: and then open up as we understand how the future looks like | 21:07 |
| bcsaller | its a really strange attack vector as you need admin perms to use it | 21:08 |
| niemeyer | bcsaller: It's a trivial DoS.. I can't be not-worried :) | 21:08 |
| bcsaller | heh, I managed :) | 21:09 |
| SpamapS | m_3: I just tested this though, and you shouldn't need to do a fake package anymore.. the fix landed. | 21:09 |
| niemeyer | bcsaller: Sure, give the address of your web site accepting Python regexes please | 21:09 |
| niemeyer | bcsaller: ;) | 21:09 |
| bcsaller | seriously, rather than parsing around and re-writing regex for a UI we don't have yet I think we can just keep a bug report | 21:09 |
| niemeyer | bcsaller: I'll make you more worried. :) | 21:09 |
| bcsaller | niemeyer: again, if the admin wants to hose the system its done | 21:10 |
| niemeyer | bcsaller: Hose _our_ system | 21:10 |
| niemeyer | bcsaller: Any _hosted_ management interface could be attacked | 21:10 |
| bcsaller | I assumed any web-ui to an ensemble system run in the cloud on their nodes... but I guess not | 21:10 |
| m_3 | SpamapS: cool | 21:11 |
| niemeyer | bcsaller: Not necessarily, no | 21:11 |
| SpamapS | Why don't we just not compile other peoples' regexs? | 21:11 |
| niemeyer | SpamapS: Because we have a feature right now that enables its use.. even though your statement makes more comfortable in the sense we can remove it and you'd not notice ;-) | 21:11 |
| niemeyer | makes me | 21:12 |
| SpamapS | I would have always assumed that those regexes are only used on the client. | 21:12 |
| bcsaller | SpamapS: currently, yes | 21:12 |
| SpamapS | they fall into the same category as maintainer scripts really.. you shouldn't use them if they're not from a trusted source. | 21:13 |
| adam_g | SpamapS: needed to upgrade bzr, works now | 21:13 |
| SpamapS | adam_g: well that seems a little.. odd. | 21:13 |
| niemeyer | SpamapS: That's not the case.. regexes are used for validation of settings | 21:13 |
| niemeyer | SpamapS: any management interface, including hosted, would make use of it | 21:14 |
| niemeyer | SpamapS, bcsaller: My proposal, though, is not to remove them entirely, but to use a subset we know there are alternative implementations that do not suffer from the problem | 21:15 |
| === otubo is now known as otubo[AFK] | ||
| SpamapS | Yeah a subset would probably be best. | 21:15 |
| niemeyer | It's also a sensible thing to do in general.. | 21:15 |
| niemeyer | Otherwise we're unconsciously binding the _metadata_ of the whole project to a particular language | 21:16 |
| SpamapS | The most complicated things I'd expect to see are things like [\d,]+ | 21:16 |
| niemeyer | SpamapS: Exactly.. this should be [0-9,]+ or similar.. | 21:17 |
| niemeyer | Which is compatible with most extended POSIX engines | 21:18 |
| niemeyer | Including grep | 21:18 |
| bcsaller | niemeyer: supposedly re2 guarantees O(length_of_regex) runtime and configurable memory-use limit | 21:19 |
| niemeyer | bcsaller: Yeah, it does | 21:19 |
| niemeyer | bcsaller: O(len of string), actually | 21:19 |
| niemeyer | bcsaller: But as long as it's O(n), we're goofd | 21:19 |
| niemeyer | LOL.. goofd is an awesome typo | 21:19 |
| bcsaller | that could be good or bad :) | 21:19 |
| bcsaller | so maybe including that makes having to filter it a non-issue | 21:20 |
| niemeyer | bcsaller: It does, but I'm a little reluctant still because we'd be binding it to a particular implementation | 21:20 |
| niemeyer | bcsaller: My suggestion is that we restrict the regex to a common subset, and if people start claiming for more we can gradually introduce, or even go full blown re2/similar if really necessary | 21:21 |
| bcsaller | this seems like a very easy place to have an opinion | 21:21 |
| niemeyer | bcsaller: You're right.. let's filter. | 21:22 |
| bcsaller | filtering it down using a regex? ;) | 21:22 |
| niemeyer | bcsaller: http://commandcenter.blogspot.com/2011/08/regular-expressions-in-lexing-and.html | 21:23 |
| hazmat | a ui can do sensible length filtering on an input | 21:27 |
| hazmat | are there are circular exponential cases in under 1k? | 21:28 |
| hazmat | for a dos | 21:28 |
| niemeyer | hazmat: Oh yeah | 21:28 |
| niemeyer | hazmat: Either way, it doesn't really matter.. we shouldn't be binding the _metadata_ for the whole project to Python, even if the implementation is in Python. | 21:29 |
| hazmat | oh.. its a formula specified regex | 21:30 |
| niemeyer | hazmat: Right | 21:31 |
| hazmat | i suggest we drop it then, unless there's a feature request for it, there's some missing coverage in that implementation (floats, missing type error handling) as is | 21:32 |
| niemeyer | hazmat: I find the feature interesting.. it's quite handy to do validation upfront rather than reporting errors on execution | 21:34 |
| niemeyer | hazmat: When that's easily doable | 21:34 |
| niemeyer | Is Python able to do POSIX regex easily? | 21:34 |
| * niemeyer can't remember | 21:34 | |
| hazmat | niemeyer, evaluate of an arbitrary regex against unknown input? | 21:35 |
| niemeyer | Doesn't look like so.. sucks | 21:35 |
| niemeyer | hazmat: Hm? | 21:35 |
| niemeyer | hazmat: Sorry, I'm not sure about what the question is? | 21:35 |
| hazmat | niemeyer, you mean validate an arbitrary regex against unknown input.. switching the regex language gives more options, s/pcre/posix.. we could also use re2 in python | 21:36 |
| niemeyer | hazmat: Yeah, posix (or extended posix, more likely) would be good | 21:37 |
| niemeyer | hazmat: I mean validate the user input using a regex | 21:38 |
| niemeyer | hazmat: Exactly like bcsaller implemented | 21:38 |
| niemeyer | hazmat: I think feature is a good idea.. the problem is just the complete lack of portability right now | 21:38 |
| hazmat | niemeyer, there's also fnmatch.py (stdlib).. translated shell regex | 21:38 |
| niemeyer | Python's re is unlike anything else | 21:38 |
| hazmat | niemeyer, its closest to pcre afaik | 21:39 |
| niemeyer | hazmat: That sounds too poor.. can't even differentiate digits etc | 21:39 |
| _mup_ | Bug #832384 was filed: ensemble.state.tests.test_security.PrincipalTests.test_activate sometimes hangs <Ensemble:New> < https://launchpad.net/bugs/832384 > | 21:54 |
| niemeyer | Ok, most of the schema stuff is in place.. just need to port some of the more complex types now.. (List and Dicts) | 22:16 |
| jimbaker | bcsaller, i'm sitting w/ m_3 here in boulder and he's wondering about the status of config-defaults. the branch is marked as being approved, but it's not under the needs release column in the eureka kanban | 22:47 |
| jimbaker | i think that's because the bug is still "new", not some other state | 22:48 |
| jimbaker | (or at least that's one possibility) | 22:48 |
| hazmat | jimbaker, yeah. i needs to be labeled in-progress at least | 23:12 |
| hazmat | surprised it even showed up in the review queue without that label | 23:12 |
| m_3 | hazmat: thanks... I'll update the bug | 23:17 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!