| *** krotscheck_dcm has quit IRC | 01:31 | |
| *** krotscheck has joined #storyboard | 01:33 | |
| *** jtomasek_ has joined #storyboard | 07:02 | |
| *** fay has joined #storyboard | 07:12 | |
| *** fay is now known as Guest70521 | 07:13 | |
| *** mrmartin has joined #storyboard | 07:28 | |
| *** jtomasek has quit IRC | 07:58 | |
| *** jtomasek_ has quit IRC | 08:01 | |
| *** Guest70521 is now known as faybrocklebank | 09:04 | |
| Zara | morning, storyboard! | 09:36 |
|---|---|---|
| Zara | so, there are some rumblings where I work about having storyboard track gitlab. maybe at some point I'll manage to track down the gitlab source code; in the meantime, anyone have experience with this? I'm hoping it'll overlap with 'storyboard tracking gerrit' and we can do a coupla things at once, but bet it's not that easy... | 09:39 |
| SotK | if GitLab has an event stream comparable to Gerrit's then I think it'd overlap nicely | 10:03 |
| Zara | YOU ARE ON HOLIDAY | 10:03 |
| SotK | but idk if it does | 10:03 |
| Zara | also I don't yet know if it does | 10:03 |
| Zara | found source, browsing it is kinda slow | 10:03 |
| pedroalvarez | I was expecting gitlab to have its own issue tracker, so maybe they didn't have the need to implement someting like stream events | 10:05 |
| pedroalvarez | but also github have also their own issue tracker, and it's possible to get these events | 10:05 |
| Zara | yeah, I figured I'd start off by looking at their email stuff | 10:05 |
| Zara | I haven't seen anything events-y yet | 10:07 |
| pedroalvarez | various api clients for gilab: https://about.gitlab.com/applications/ | 10:07 |
| Zara | aha, there's a dashboard, so there are events for that | 10:08 |
| Zara | though apparently no dashboard events for ci thigns | 10:08 |
| Zara | *things | 10:08 |
| Zara | I guess we just track issue status from a gitlab instance. | 10:09 |
| * Zara looks at one of the python wrappers at that link | 10:24 | |
| Zara | https://github.com/pyapi-gitlab/pyapi-gitlab | 10:25 |
| Zara | ahahaha that readme | 10:25 |
| Zara | https://github.com/gpocentek/python-gitlab looks more hopeful... | 10:42 |
| -openstackstatus- NOTICE: Gate on project-config is currently broken due to IRC tests. The problem has been detected and we are working to fix the issue as soon as possible. | 11:15 | |
| Zara | NikitaKonovalov: I have some questions about the python-storyboardclient , if you have a minute sometime today? | 11:17 |
| SotK | pedroalvarez: I suspect you are correct about it not having an event stream | 11:19 |
| pedroalvarez | couldn't find anything either | 11:20 |
| Zara | I found things marked 'events' but no stream specifically, havne't looked that hard yet though, so prepared to trust you on that | 11:21 |
| Zara | I don't really know what the gerrit events stream looks like, yet, for comparison | 11:21 |
| Zara | just to make things more exciting. | 11:22 |
| Zara | as for the python client... | 11:22 |
| Zara | this is my little test program: http://paste.openstack.org/show/492429/ | 11:22 |
| Zara | and this is the output: http://paste.openstack.org/show/492430/ | 11:22 |
| Zara | but *this* is what's in tasks.py: http://paste.openstack.org/show/492431/ | 11:23 |
| Zara | in the python client, that is | 11:23 |
| Zara | so where are created_at and updated_at coming from? | 11:23 |
| Zara | I assume I've misunderstood how it works,because I tried getting rid of all those things from tasks.py and it still did the same thing | 11:24 |
| Zara | but I don't get where it's deciding what to return, because the actual object would also have a 'links' field, so I don't think it's just getting it directly | 11:25 |
| Zara | I have almost 0 python so there's a good chance that's the strange bit | 11:28 |
| Zara | ohhh... is it perhaps from the BaseObject? in base.py | 11:29 |
| pedroalvarez | right | 11:35 |
| pedroalvarez | so if instead of printing the result you just `task = storyboard.tasks.get(2865)` | 11:36 |
| pedroalvarez | you will have in task, an instane of a Task object | 11:36 |
| pedroalvarez | then you can do things like `print task.title` | 11:36 |
| pedroalvarez | now I will read and see if you were looking for that kind of help :/ | 11:37 |
| Zara | hahaha, it wasn't quite that, but also makes sense to do that. xD | 11:37 |
| pedroalvarez | you may be right about the BaseObject thing | 11:37 |
| Zara | the weird thing is that everything still returns if I remove all the fields from the Tasks class | 11:41 |
| Zara | eg: so it's just like | 11:41 |
| Zara | class Task(base.BaseObject): | 11:41 |
| Zara | with nothing in it | 11:41 |
| pedroalvarez | that should fail in python I believe | 11:42 |
| pedroalvarez | (an empty class? maybe not) | 11:42 |
| pedroalvarez | but maybe you are not using the same python file that you are modifying | 11:42 |
| Zara | I wondered about that, I don't know where else it would live, though :/ | 11:46 |
| pedroalvarez | well, you have done `python setup.py install` or `pip install .` right? | 11:46 |
| Zara | yeah | 11:47 |
| pedroalvarez | that will make it go to /usr/lib/python2.7/dist-packages/blah/foo/ | 11:47 |
| Zara | oh yeah | 11:47 |
| pedroalvarez | (path depending on the distro) | 11:47 |
| *** openstackgerrit has quit IRC | 11:47 | |
| Zara | it yeah, I used to do this stuff a lot... I'm out of practice! :D | 11:47 |
| *** openstackgerrit has joined #storyboard | 11:48 | |
| Zara | though hm, can't find it anywhere yet | 11:50 |
| Zara | oh nvm, usr/local/lib | 11:51 |
| Zara | I have missed wandering around filesystems :') | 11:52 |
| Zara | hm, readonly | 11:55 |
| Zara | ubuntu@zara-storyboard:/usr/local/lib/python2.7/dist-packages/storyboardclient/v1$ chmod +x tasks.py | 11:56 |
| Zara | chmod: changing permissions of ‘tasks.py’: Operation not permitted | 11:56 |
| Zara | ubuntu@zara-storyboard:/usr/local/lib/python2.7/dist-packages/storyboardclient/v1$ sudo chmod +x tasks.py | 11:56 |
| Zara | sudo: unable to resolve host zara-storyboard | 11:56 |
| Zara | ;_; | 11:56 |
| Zara | I HAVE NO TOOLS LEFT IN MY ARSENAL | 11:56 |
| Zara | yay, it works | 12:10 |
| Zara | yeah, it was going by usr/local/lib/python2.7/dist-packages/storyboardclient/v1/tasks.py | 12:11 |
| Zara | just for future reference | 12:11 |
| Zara | and adding 'link' to that object means the link is returned | 12:11 |
| Zara | so am I right in thinking that changing v1/tasks.py in the repo should result in that file being different when the client is installed, and I shouldn't have to do anything else? | 12:12 |
| Zara | the mechanics of 'pip install foo' are still mainly a mystery to me. somehow. | 12:13 |
| Zara | ugh I bet sotk migrated the db after the 15th and my pretty diagram's already out of date | 12:14 |
| Zara | aye, march 23rd | 12:16 |
| pedroalvarez | the "sudo: unable to resolve host zara-storyboard" error is misleading | 12:17 |
| pedroalvarez | it happens to me also in cloud VMs | 12:18 |
| Zara | yeah, I've generally been ignoring it, wasn't sure if it was significant or not (things generally seem to work) | 12:18 |
| Zara | just when they don't work, I wonder if it's the reason. xD | 12:18 |
| Zara | so when I send these updates, is it worth splitting them up (one for tasks, one for stories, etc) or should I send them all at once? splitting up kinda feels ott for some of them, but there will be quite a lot in total. | 12:22 |
| openstackgerrit | Zara proposed openstack-infra/python-storyboardclient: Update tasks.py to include links https://review.openstack.org/299356 | 12:28 |
| * Zara splits them up. | 12:28 | |
| Zara | we might end up leaving that one hanging around until we migrate the db for task notes | 12:28 |
| Zara | and then update it | 12:28 |
| *** openstackgerrit has quit IRC | 12:33 | |
| *** openstackgerrit has joined #storyboard | 12:33 | |
| Zara | looking at the stories one, idk how to display the tasks of a story | 12:37 |
| Zara | (I can get the object but can't see the fields from it) | 12:38 |
| Zara | aha | 12:50 |
| Zara | something like story = storyboard.stories.get(99).tasks.list() | 12:50 |
| Zara | print(story) | 12:50 |
| *** lori has joined #storyboard | 12:52 | |
| Zara | me rn: https://www.youtube.com/watch?v=tcGQpjCztgA | 12:53 |
| Zara | and everything just *works* in the tasksNestedManager, ahhhh~ | 12:55 |
| Zara | at some point I need to hook this up to my vm, because I'm just using s.o.o. and scared of doing anything but GETs. | 12:55 |
| *** lori has left #storyboard | 12:56 | |
| Zara | what an odd part | 12:59 |
| * Zara makes note never to use that irc client | 12:59 | |
| Zara | so there's a story_type_id field | 12:59 |
| Zara | afaik we never use it | 12:59 |
| Zara | guessing it was introduced to differentiate between features and bugs | 13:00 |
| Zara | but tags kinda do that | 13:00 |
| Zara | and it's not in the webclient, etc | 13:00 |
| Zara | I'm wondering if rather than adding it, we should be deprecating it entirely, but may be missing history. | 13:00 |
| Zara | timeline events seem nicely accessible \o/ | 13:02 |
| Zara | ooh, ace, and tags_manager.list() gives tags with their history | 13:04 |
| Zara | (by default just the tag content is returned as part of the request for the story | 13:04 |
| Zara | (well, tag name) | 13:04 |
| Zara | comments also fine | 13:06 |
| Zara | it's quite cool that this hasn't been seriously updated in literally a year, and yet it still works. | 13:08 |
| * Zara prints out storyboard schema so she can colour bits in as she adds them to the python client, to keep track | 13:15 | |
| Zara | am an adult, honest. | 13:15 |
| *** openstackgerrit has quit IRC | 13:18 | |
| *** openstackgerrit has joined #storyboard | 13:18 | |
| openstackgerrit | Zara proposed openstack-infra/python-storyboardclient: Add story_type_id to stories https://review.openstack.org/299390 | 13:24 |
| Zara | sorry, these are going to be a bit spammy, may end up building on them | 13:32 |
| openstackgerrit | Zara proposed openstack-infra/python-storyboardclient: Update Timeline https://review.openstack.org/299395 | 13:34 |
| persia | Maybe put them all in the same topic? | 13:38 |
| Zara | I'm currently rouuuughly trying to split it so that all timeline things will be in the timeline topic, etc. I'm just starting with the easy ones (so they're all in different topics for now; my topics correspond to my git branches) | 13:40 |
| Zara | so I'll end up looping back round once there are a few topics up there. otherwise it'll be a billion patches in one topic, touching lots of different bits of the api | 13:41 |
| Zara | just more a warning not to start reviewing yet | 13:41 |
| Zara | if you don't want to be very bored, anyway | 13:41 |
| Zara | hm, team_id and repo_url currently aren't tracked for projects | 13:41 |
| Zara | again, we don't really do anything with these afaict. I imagine we want to do something with team_id one day, suspect repo_url was due to be deprecated | 13:42 |
| Zara | team_id is a bit strange | 13:44 |
| Zara | if I add it to the project class, it doesn't return unless I do something like | 13:46 |
| Zara | project = storyboard.projects.get(457).team_id | 13:46 |
| Zara | if I leave out the .team_id , I get: | 13:46 |
| Zara | <Project autocreate_branches=False, created_at=2014-03-12T17:52:19+00:00, description=OpenStack Task Tracking Browser Client, id=457, is_active=True, name=openstack-infra/storyboard-webclient, repo_url=None, updated_at=None> | 13:46 |
| Zara | returned-- so I added both repo_url and team_id to the class there, but only repo_url shows up in that place | 13:47 |
| openstackgerrit | Zara proposed openstack-infra/python-storyboardclient: Add repo_url and team_id https://review.openstack.org/299411 | 13:50 |
| Zara | hm, so tasks have a project_id, but there doesn't seem to be any project_mapping for tasks (analogous to project_group_mapping for projects) | 14:00 |
| Zara | so you can list the projects in a group with something like | 14:00 |
| Zara | storyboard.project_groups.get(57).projects.list() | 14:00 |
| Zara | but something lik storyboard.projects.get(457).tasks.list() | 14:01 |
| Zara | will fail | 14:01 |
| Zara | which also means it's awkward to get stories currently listed under a view of a project, iiuc | 14:02 |
| persia | That's too bad. It seems like a concise way to get such a lsit. | 14:02 |
| Zara | yeah. it works for tasks in stories, and for projects in project groups, but nothing in between! | 14:06 |
| Zara | though that's interesting, because there's no separate mapping from tasks to stories, so maybe that's actually some manager in the client somewhere | 14:06 |
| * Zara wanders around | 14:06 | |
| Zara | so the tasksNestedManager is currently configured to expect the parent id to be a story id. I think we'd want something more generalised; just tried hacking around making another class with a slightly different name, for projects, but fire. | 14:13 |
| Zara | oh yeah, storyboard meeting in 45ish | 14:13 |
| Zara | pretty easy to add the basics of a board. | 14:23 |
| Zara | this is charming api and python client. | 14:24 |
| openstackgerrit | Zara proposed openstack-infra/python-storyboardclient: Add boards https://review.openstack.org/299445 | 14:41 |
| * Zara sees boards have a field for 'project' waiting, is reminded that SotK is the best. | 14:43 | |
| openstackgerrit | Zara proposed openstack-infra/python-storyboardclient: Add worklists https://review.openstack.org/299454 | 14:53 |
| Zara | oh yeah, meeting in 7 mins I guess | 14:54 |
| Zara | maybe this week I'll update the agenda | 14:54 |
| Zara | mostly consisted of deleting stuff. | 15:00 |
| Zara | me -> #openstack-meeting | 15:00 |
| openstackgerrit | Zara proposed openstack-infra/python-storyboardclient: Add boards https://review.openstack.org/299445 | 15:19 |
| *** mrmartin has quit IRC | 15:38 | |
| openstackgerrit | Zara proposed openstack-infra/python-storyboardclient: Add repo_url and team_id https://review.openstack.org/299411 | 15:39 |
| Zara | so I guess for gerritness, the first step is looking at the bot that updates launchpad from gerrit | 16:18 |
| Zara | and seeing how much can be copied for storyboard | 16:18 |
| *** openstack has joined #storyboard | 17:05 | |
| *** openstackstatus has joined #storyboard | 17:05 | |
| *** ChanServ sets mode: +v openstackstatus | 17:05 | |
| *** jtomasek_ has joined #storyboard | 17:09 | |
| *** mrmartin has joined #storyboard | 17:23 | |
| *** jtomasek_ has quit IRC | 17:31 | |
| *** mrmartin has quit IRC | 17:32 | |
| *** mrmartin has joined #storyboard | 18:11 | |
| *** davidlenwell has quit IRC | 18:27 | |
| *** davidlenwell has joined #storyboard | 18:34 | |
| *** krotscheck is now known as krotscheck_dcm | 18:46 | |
| *** jtomasek_ has joined #storyboard | 19:14 | |
| *** mrmartin has quit IRC | 19:41 | |
| *** mrmartin has joined #storyboard | 19:58 | |
| *** jtomasek_ has quit IRC | 20:00 | |
| *** pleia2 has quit IRC | 20:19 | |
| *** pleia2 has joined #storyboard | 20:20 | |
| *** openstackgerrit has quit IRC | 20:48 | |
| *** openstackgerrit has joined #storyboard | 20:48 | |
| *** mrmartin has quit IRC | 21:20 | |
| *** davidlenwell has quit IRC | 21:48 | |
| *** davidlenwell has joined #storyboard | 21:55 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!