| *** diablo_rojo has quit IRC | 01:04 | |
| *** zara_the_lemur__ has quit IRC | 01:53 | |
| *** persia has quit IRC | 02:09 | |
| *** persia has joined #storyboard | 02:12 | |
| *** jtomasek has quit IRC | 05:35 | |
| *** jtomasek has joined #storyboard | 08:59 | |
| *** bethwhite has joined #storyboard | 09:50 | |
| *** diablo_rojo has joined #storyboard | 15:54 | |
| *** bethwhite has quit IRC | 16:26 | |
| *** bethwhite has joined #storyboard | 16:46 | |
| SotK | so I probably need to get round to fixing the bug where we make a search url look pasteable but actually it isn't pretty soon | 17:04 |
|---|---|---|
| SpamapS | SotK: Yes please. :) | 17:06 |
| SpamapS | SotK: any testing or support you need, I have _tens_ of minutes per week for that. | 17:06 |
| SpamapS | The key thing missed in story #52 that is also evident in the search url is that the browsers have effectively created a fairly consistent "recent things" and "sharing" UI for humans to use | 17:08 |
| SpamapS | and it's a crying shame not to take advantage. | 17:08 |
| jeblair | SotK: whenever i searched for a tag in the ui, and then searched for a second one, the second replaced the first | 17:17 |
| SotK | yeah, that needs fixing | 17:17 |
| jeblair | SotK: so i was only able to search for the intersection of zuulv3 and low-hanging-fruit by editing the url after your suggestion | 17:17 |
| SotK | SpamapS: I agree, I am fully in favour of human-friendly URLs when someone has a chance to implement them | 17:18 |
| SotK | jeblair: I'm glad that at least creating the URL manually accidentally makes it allow multiple tags to be specified | 17:20 |
| *** bethwhite has quit IRC | 18:13 | |
| dmsimard | SotK: I thought that was fixed ? | 18:30 |
| dmsimard | (tag erasing another one) | 18:30 |
| dmsimard | sounds like what I reported a while back | 18:30 |
| Zara | dmsimard: it's awaiting +1s https://review.openstack.org/#/c/436702/ | 18:34 |
| Zara | (though I'm not sure if there's also a problem specific to tags.) | 18:35 |
| *** jtomasek has quit IRC | 18:39 | |
| SotK | the tag thing is different | 19:02 |
| SotK | and it is more of a misfeature than a bug I think | 19:02 |
| Zara | ah right, not being able to combine multiple filters of the same kind? | 19:04 |
| SotK | yeah, when someone adds a new browse filter we remove the existing one of that type if it exists, because the API doesn't support filtering by multiple options for certain things | 19:04 |
| Zara | yeah, I guess it makes sense for other categories, but tags are different. | 19:05 |
| SotK | tags are one of the things that it does support specifying more than once | 19:05 |
| SotK | the webclient just doesn't reflect that | 19:05 |
| Zara | ahh, right | 19:05 |
| * Zara didn't know where the issue lay, just knew you couldn't do it in the webclient | 19:05 | |
| Zara | I *think* tags are the only filter category that would apply to, wondering if I'm missing any | 19:07 |
| * SotK believes projects and project_groups should be made acceptable for stories too | 19:08 | |
| Zara | oh, good point, it depends what they're for | 19:08 |
| Zara | I was thinking that 'something that is project A and project B' doesn't make sense, but was assuming the 'thing' was a project there... | 19:09 |
| SotK | its annoying because projects make sense for stories but not for tasks | 19:09 |
| SotK | project groups make sense for everything though in my head | 19:10 |
| persia | For tasks, could multiple projects just short-circuit to no results with a message to the user suggesting they might want to search stories? | 19:45 |
| persia | Additive semantics for multiple projects in tasks also make sense, but contradict everything else in the UI. | 19:45 |
| persia | SotK: how does filter-task-by-multiple-project-groups work in your head? | 19:46 |
| SotK | each project can potentially be in multiple project groups, so "show tasks whose project is in group A and group B" | 19:54 |
| persia | That makes perfect sense. | 20:02 |
| *** zara_the_lemur__ has joined #storyboard | 20:46 | |
| zara_the_lemur__ | trying out that migration script patch now | 20:49 |
| zara_the_lemur__ | could be interesting since I already imported the project, but with an old branch of the writer... | 20:50 |
| zara_the_lemur__ | ah, actually, maybe that won't do anything new (since line 225...) | 20:51 |
| zara_the_lemur__ | I wonder what the cleanest way to remove my old import is | 20:53 |
| zara_the_lemur__ | (that is, delete a project and all tasks associated with it) | 20:54 |
| zara_the_lemur__ | (I could use the python client, just wondering if there's something quicker.) | 20:55 |
| zara_the_lemur__ | hahaha, I tried only to hit UnicodeEncodeError: 'ascii' codec can't encode character u'\u201c' in position 232: ordinal not in range(128) :) | 21:00 |
| zara_the_lemur__ | something about the 'storm-supervisor is unable to restart' bug | 21:07 |
| zara_the_lemur__ | okay it's a left double quotation mark | 21:07 |
| zara_the_lemur__ | so hm maybe I'm on the wrong story | 21:08 |
| zara_the_lemur__ | yeah, it's the next one | 21:08 |
| zara_the_lemur__ | Semantics for the metrics for “Apache Web Server Checks” in the n the Monasca document are missing. | 21:09 |
| diablo_rojo | zara_the_lemur__, I love your stream of consciousness messages to the channel | 21:16 |
| zara_the_lemur__ | haha | 21:19 |
| zara_the_lemur__ | I tried deleting the story description for now, buuut that wasn't enough (think I need to fix the comment) so now I'm stuck (or rather, I don't have time tonight to look into other ways of getting rid of all tasks associated with that project | 21:27 |
| zara_the_lemur__ | hah, old message | 21:27 |
| zara_the_lemur__ | ended up doing it directly in the db | 21:27 |
| zara_the_lemur__ | script running, might be a bit weird since stories and comments are already imported... | 21:30 |
| SotK | huh, is that UnicodeEncodeError in the python client? | 21:50 |
| zara_the_lemur__ | yeah | 22:03 |
| zara_the_lemur__ | it should probably learn to handle tem | 22:03 |
| zara_the_lemur__ | *them | 22:03 |
| SotK | yeah, we should probably make it use unicode strings | 22:05 |
| zara_the_lemur__ | that migration script seems to work btw. | 23:18 |
| * zara_the_lemur__ disappeared for a bit for other things | 23:18 | |
| zara_the_lemur__ | tasks are associated with projects in stories and appear to have the right assignees | 23:19 |
| zara_the_lemur__ | although the branch id seems to match the project id | 23:23 |
| zara_the_lemur__ | I think it's coincidence | 23:24 |
| zara_the_lemur__ | (or rather, I currently have a branch per project, so branch 29 ends up = project 29 | 23:25 |
| persia | That does sound like a coincidence. | 23:34 |
| persia | Maybe try creating a project first with 3 branches, and then making sure the offset is constant, or some other way to differentiate? | 23:35 |
| zara_the_lemur__ | I'll delete a couple of rows from the branches table and rerun the script, since it was using the old branch it created last time anyway, so I might as well check that it can still cope when there's no branch | 23:37 |
| zara_the_lemur__ | oh the branch is created when the project is created | 23:40 |
| * zara_the_lemur__ forgot | 23:40 | |
| zara_the_lemur__ | (hm, if you delete row with id 29 and then make a new thing, it will still end up with id 30. I vaguely recall it storing the last-used id somewhere, so maybe that's unsurprising, actually) | 23:44 |
| zara_the_lemur__ | this script seems fine, anyway, and I guess any ID strangeness should show up when we test against the prod data if I've missed something, since branch IDs don't match project IDs there. | 23:45 |
| zara_the_lemur__ | (the code looks fine too) | 23:49 |
| persia | I think you have to forcibly inject extra branches to confuse it, or the various don't-be-confusing-by-reusing-things features will probably protect you in ways that may not be ideal. | 23:52 |
| SotK | ID strangeness did show up when I was testing, and I fixed the bit that finds the master branch in order to run the migration against the production data I have successfully | 23:54 |
| zara_the_lemur__ | yeah. for now I haven't checked that since I couldn't see any reason why that, in particular, would break (after you'd updated the patch), and we'll catch any lingering weirdness around that when we try the scripts again. | 23:54 |
| zara_the_lemur__ | I figured if the updated code was off, most likely thing would be that it just wouldn't work at all | 23:56 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!