*** woodster_ has quit IRC | 01:01 | |
openstackgerrit | wuhao proposed openstack/api-wg: Add description of pagination parameters https://review.openstack.org/190743 | 01:50 |
---|---|---|
openstackgerrit | wuhao proposed openstack/api-wg: Add description of pagination parameters https://review.openstack.org/190743 | 01:58 |
*** e0ne has joined #openstack-api | 05:22 | |
*** gmann has quit IRC | 05:33 | |
*** terrylhowe has quit IRC | 05:37 | |
*** e0ne has quit IRC | 05:44 | |
*** ig0r_ has joined #openstack-api | 05:52 | |
*** ig0r__ has quit IRC | 05:55 | |
*** gmann has joined #openstack-api | 06:19 | |
*** fifieldt has joined #openstack-api | 06:43 | |
*** e0ne has joined #openstack-api | 06:57 | |
*** e0ne has quit IRC | 07:04 | |
*** cdent has joined #openstack-api | 07:33 | |
*** e0ne has joined #openstack-api | 07:36 | |
*** fzdarsky has joined #openstack-api | 07:47 | |
*** e0ne is now known as e0ne_ | 08:01 | |
*** lucasagomes has joined #openstack-api | 08:02 | |
*** e0ne_ is now known as e0ne | 08:03 | |
*** e0ne is now known as e0ne_ | 09:11 | |
*** e0ne_ is now known as e0ne | 09:24 | |
*** e0ne is now known as e0ne_ | 10:07 | |
*** e0ne_ is now known as e0ne | 10:21 | |
*** lucasagomes is now known as lucas-hungry | 11:01 | |
*** fzdarsky is now known as fzdarsky|lunch | 11:05 | |
*** e0ne is now known as e0ne_ | 11:25 | |
*** e0ne_ is now known as e0ne | 11:45 | |
*** lucas-hungry is now known as lucasagomes | 12:07 | |
*** terrylhowe has joined #openstack-api | 12:16 | |
*** fzdarsky|lunch is now known as fzdarsky | 12:23 | |
*** terrylhowe has left #openstack-api | 12:25 | |
*** e0ne is now known as e0ne_ | 13:37 | |
*** e0ne_ is now known as e0ne | 13:39 | |
*** annegentle has joined #openstack-api | 13:42 | |
openstackgerrit | Ken'ichi Ohmichi proposed openstack/api-wg: Add generic name of each project for terms https://review.openstack.org/196918 | 13:47 |
*** annegentle has quit IRC | 13:57 | |
*** sigmavirus24_awa is now known as sigmavirus24 | 13:57 | |
*** annegentle has joined #openstack-api | 14:02 | |
*** annegentle has quit IRC | 14:07 | |
*** annegentle has joined #openstack-api | 14:32 | |
*** woodster_ has joined #openstack-api | 14:39 | |
*** annegentle has quit IRC | 14:43 | |
*** annegentle has joined #openstack-api | 15:04 | |
*** Apoorva has joined #openstack-api | 15:06 | |
*** annegentle has quit IRC | 15:13 | |
*** e0ne is now known as e0ne_ | 15:16 | |
*** annegentle has joined #openstack-api | 15:21 | |
*** e0ne_ is now known as e0ne | 15:26 | |
*** cdent has quit IRC | 15:28 | |
*** annegentle has quit IRC | 15:56 | |
*** salv-orlando has joined #openstack-api | 15:58 | |
salv-orlando | hi people. I've noticed many folks are not putting APIImpact on the commit message for specs defining new APIs. Should I ask to add this tag or should it be put only on the code patches? | 16:00 |
elmiko | i think it's nice to have on specs, assuming that the author(s) want to engage the wg | 16:01 |
elmiko | by the time it gets to a code patch, it would be difficult to re-architect the api if things don't make sense | 16:02 |
ryansb | Definitely ask. It could save them rewriting some code | 16:02 |
*** annegentle has joined #openstack-api | 16:03 | |
*** annegentle has quit IRC | 16:10 | |
salv-orlando | thanks ryansb & elmiko - I will unleash my pedantry on those specs | 16:25 |
sigmavirus24 | salv-orlando: pedantry++ | 16:26 |
*** fzdarsky has quit IRC | 16:31 | |
*** e0ne has quit IRC | 16:33 | |
* ryansb braces self for pedantry | 16:34 | |
*** annegentle has joined #openstack-api | 16:40 | |
*** annegentle has quit IRC | 16:44 | |
*** lucasagomes is now known as lucas-dinner | 16:52 | |
*** salv-orl_ has joined #openstack-api | 17:08 | |
*** e0ne has joined #openstack-api | 17:09 | |
*** salv-orlando has quit IRC | 17:11 | |
*** e0ne is now known as e0ne_ | 17:18 | |
*** e0ne_ is now known as e0ne | 17:21 | |
*** e0ne is now known as e0ne_ | 17:26 | |
*** e0ne_ is now known as e0ne | 17:27 | |
*** annegentle has joined #openstack-api | 17:30 | |
*** e0ne is now known as e0ne_ | 17:33 | |
*** annegentle has quit IRC | 17:35 | |
*** e0ne_ is now known as e0ne | 17:39 | |
*** e0ne is now known as e0ne_ | 18:17 | |
*** salv-orl_ has quit IRC | 18:22 | |
*** Apoorva has quit IRC | 18:33 | |
*** e0ne_ is now known as e0ne | 18:39 | |
*** Apoorva has joined #openstack-api | 18:42 | |
*** salv-orlando has joined #openstack-api | 18:49 | |
*** e0ne has quit IRC | 18:50 | |
*** annegentle has joined #openstack-api | 18:56 | |
*** e0ne has joined #openstack-api | 19:54 | |
*** lucas-dinner has quit IRC | 20:08 | |
sigmavirus24 | So someone was trying to tell me that version negotiation for an API via the headers is harmful for devices trying to interact with APIs from the Internet of Things | 20:13 |
sigmavirus24 | And they refuse to explain their reasoning | 20:13 |
elmiko | huh | 20:14 |
sigmavirus24 | Yeah | 20:14 |
sigmavirus24 | I am tempted to say they're just making it up because they like URLs with the version in it better for subjective reasons | 20:14 |
elmiko | so... version negotiation only through rest calls? that seems worse | 20:15 |
elmiko | LOL | 20:15 |
sigmavirus24 | elmiko: more along the lines of how GitHub does it | 20:15 |
sigmavirus24 | Accept: application/vnd.github.v3.full+json | 20:15 |
sigmavirus24 | That's what github3.py sends by default to get any user-text as plain-text, html, and the original text submitted | 20:15 |
elmiko | oh, using content type? | 20:15 |
sigmavirus24 | Yeah | 20:15 |
sigmavirus24 | Like the client chooses the version if it knows it and sends that in the headers | 20:16 |
sigmavirus24 | Doing that kind of stuff with middleware in Ruby with Sinatra is pretty easy | 20:16 |
elmiko | yea, i'm scratching my head as to why using the headers is bad | 20:17 |
elmiko | or really worse than bad, "harmful" ;) | 20:17 |
*** fzdarsky has joined #openstack-api | 20:18 | |
*** salv-orlando has quit IRC | 20:20 | |
*** lucasagomes has joined #openstack-api | 20:21 | |
elmiko | etoews: heads up, i won't be able to make the cross project meeting tonight. | 20:23 |
etoews | k. i'll be around. | 20:25 |
sigmavirus24 | elmiko: yeah I don't get their argument | 20:25 |
sigmavirus24 | but they haven't really made one tbh | 20:25 |
* sigmavirus24 shrugs | 20:26 | |
sigmavirus24 | no biggie | 20:26 |
etoews | elmiko: i'll actually be around for the late meeting tomorrow. you? | 20:26 |
elmiko | etoews: yea i'll be there | 20:26 |
elmiko | actually, you just reminded me to update the agenda ;) | 20:27 |
etoews | \o/ | 20:27 |
etoews | i put a couple of things in there already | 20:27 |
elmiko | cool, i think we need to talk over a few of the finer points on the 5xx stuff | 20:27 |
*** lucasagomes has quit IRC | 20:27 | |
ryansb | IoT can't send headers? | 20:27 |
ryansb | ??? | 20:27 |
sigmavirus24 | ryansb: apparently | 20:28 |
elmiko | lol | 20:28 |
sigmavirus24 | ryansb: IoT can't do crypto either | 20:28 |
sigmavirus24 | so | 20:28 |
sigmavirus24 | I care not about it | 20:28 |
sigmavirus24 | something something TLS is bad something something | 20:28 |
ryansb | oh, right. | 20:28 |
sigmavirus24 | Call me when the IoT is secure and usable. Kthnxbai | 20:29 |
elmiko | ha! | 20:29 |
ryansb | I didn't want any privacy anyway. My internet-enabled appliances should multicast everything and CC the NSA | 20:29 |
sigmavirus24 | Am I a bad person for wanting everything to use HTTPS? | 20:29 |
sigmavirus24 | ryansb: the NSA is a BCC sir | 20:29 |
sigmavirus24 | or | 20:29 |
sigmavirus24 | reverse-BCC? | 20:29 |
elmiko | sigmavirus24: no, no you are not | 20:29 |
ryansb | sigmavirus24: ok, I want lots of things to use https, but there's some stuff that I don't think needs to be. | 20:30 |
sigmavirus24 | ryansb: I don't care if it needs to be =P | 20:30 |
ryansb | Example: my blog. It has no auth, no comments, nothing. I don't mind allowing http | 20:30 |
etoews | september 14! https://letsencrypt.org/2015/06/16/lets-encrypt-launch-schedule.html | 20:31 |
elmiko | but ryansb, what if someone mitm's your blog to post inaccurate info? | 20:31 |
elmiko | ;) | 20:31 |
ryansb | elmiko: then they deserve it, I guess. If my readers need verified content they could use https | 20:32 |
sigmavirus24 | ryansb: and if people don't want passive observers to know they're reading your blog? | 20:32 |
ryansb | then they can still choose to use https | 20:32 |
elmiko | ok, fair | 20:32 |
ryansb | I'm just saying it isn't required for a large portion of what the average user does | 20:33 |
ryansb | e.g. get weather forecasts, peruse headlines about pop stars | 20:33 |
ryansb | play candy crush | 20:33 |
* ryansb has no idea what people do on the internet | 20:34 | |
sigmavirus24 | lol | 20:34 |
sigmavirus24 | facebook and candy crush are probably two of the biggest | 20:34 |
sigmavirus24 | for what it's wroth | 20:34 |
sigmavirus24 | I do think news outlets should use HSTS | 20:34 |
sigmavirus24 | New York Times, etc. should all have HSTS because modifying that content can really screw up things | 20:34 |
sigmavirus24 | Those are trusted resources for facts but the facts are transmitted in plain-text | 20:35 |
ryansb | Yeah, good point | 20:35 |
ryansb | or we could teach everyone to use GPG | 20:35 |
ryansb | that'd go swimmingly | 20:35 |
sigmavirus24 | we can't even teach technical people to use GPG | 20:35 |
elmiko | lol | 20:35 |
elmiko | needs more signing parties | 20:35 |
ryansb | ...I'm not sure that's what it needs. | 20:36 |
elmiko | hehe | 20:36 |
elmiko | didn't you see the matrix, dance parties make everything better ;) | 20:36 |
ryansb | lol | 20:36 |
*** fzdarsky has quit IRC | 20:37 | |
*** e0ne has quit IRC | 20:44 | |
sigmavirus24 | requests team had a signing party with our downstream liasons at PyCon | 20:49 |
sigmavirus24 | Well | 20:49 |
sigmavirus24 | requests team - Kenneth | 20:49 |
sigmavirus24 | Cory and I handle all security reports and fies | 20:50 |
sigmavirus24 | *fixes | 20:50 |
ryansb | oh, nice | 20:51 |
sigmavirus24 | ryansb: oh you didn't realize openstack has a requests core developer working on it? | 20:56 |
ryansb | I didn't, I suppose. I was saying "nice" about the "having a keysigning at PyCon" part though | 20:57 |
ryansb | having a requests dev aboard certainly isn't bad | 20:57 |
sigmavirus24 | for you | 20:58 |
sigmavirus24 | there's a reason I stay away from the clients a lot of the time | 20:59 |
elmiko | lol | 20:59 |
sigmavirus24 | openstacksdk is the only client I'd like to work on but I don't have time for it | 20:59 |
sigmavirus24 | If the alcohol didn't kill me, I'm pretty sure the project teams would kill me for refactoring how they abuse requests | 21:00 |
sigmavirus24 | The tamest reaction I had to https://github.com/openstack/python-glanceclient/blob/master/glanceclient/common/https.py was http://i.imgur.com/z4zwFXw.gifv and https://review.openstack.org/#/c/189344/ is going to make things all better | 21:01 |
ryansb | wait, did they do...cert validation themselves? | 21:02 |
sigmavirus24 | yep | 21:03 |
ryansb | (╯°□°)╯︵┻━┻ | 21:03 |
sigmavirus24 | YEP | 21:03 |
ryansb | that ain't right man, that just ain't right | 21:03 |
sigmavirus24 | I mean | 21:03 |
sigmavirus24 | I don't see a way in which it was broken | 21:03 |
sigmavirus24 | So that's good at least, right? | 21:03 |
sigmavirus24 | It's just frustrating that they did that | 21:04 |
ryansb | we should rename #openstack-api to #http-curmudgeons | 21:04 |
sigmavirus24 | no | 21:05 |
sigmavirus24 | That's #python-requests | 21:05 |
ryansb | A++ | 21:05 |
sigmavirus24 | Also, if you want to complain about flake8, ##python-code-quality | 21:05 |
sigmavirus24 | (Because I'm the core developer of flake8) | 21:06 |
sigmavirus24 | code-quality mailing list at python.org is something I run and is generally the better place to complain about linters and such | 21:06 |
sigmavirus24 | It's the mailing list for pylint, pep8, mccabe, pyflakes, flake8, and other stuff | 21:06 |
sigmavirus24 | I might have a problem | 21:07 |
ryansb | and the problem is too many linters | 21:07 |
sigmavirus24 | lol | 21:09 |
stevelle | ah but who lints the linters | 21:09 |
sigmavirus24 | stevelle: so flake8 runs against itself | 21:09 |
sigmavirus24 | pylint does the same | 21:10 |
stevelle | chickens guarding the henhouse! | 21:10 |
* stevelle dons tinfoil | 21:10 | |
sigmavirus24 | I've been thinking of running pylint against flake8 in the gate just for shits and giggles | 21:10 |
*** annegentle has quit IRC | 21:18 | |
*** salv-orlando has joined #openstack-api | 21:22 | |
*** salv-orlando has quit IRC | 21:29 | |
*** salv-orlando has joined #openstack-api | 21:30 | |
ryansb | lol | 21:30 |
ryansb | that'd be top notch | 21:30 |
sigmavirus24 | I'd probably want to drink myself to death while trying to configure pylint to just work | 21:35 |
*** annegentle has joined #openstack-api | 21:57 | |
*** Apoorva has quit IRC | 22:26 | |
*** annegentle has quit IRC | 22:29 | |
*** annegentle has joined #openstack-api | 23:12 | |
*** salv-orlando has quit IRC | 23:26 | |
*** Apoorva has joined #openstack-api | 23:27 | |
*** Apoorva has quit IRC | 23:31 | |
*** annegentle has quit IRC | 23:34 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!