| fatema__ | I have pulled changes and can't wait to have the feedback ^^ | 00:55 |
|---|---|---|
| *** fatema__ has quit IRC | 01:00 | |
| *** diablo_rojo has quit IRC | 02:34 | |
| *** jamesmcarthur has joined #storyboard | 02:39 | |
| *** jamesmcarthur has quit IRC | 02:44 | |
| *** jamesmcarthur has joined #storyboard | 02:47 | |
| *** jamesmcarthur has quit IRC | 03:44 | |
| *** jamesmcarthur has joined #storyboard | 03:44 | |
| *** jamesmcarthur has quit IRC | 03:50 | |
| *** jamesmcarthur has joined #storyboard | 04:19 | |
| *** udesale has joined #storyboard | 04:35 | |
| *** jtomasek has joined #storyboard | 06:43 | |
| *** jtomasek has quit IRC | 06:45 | |
| *** jtomasek has joined #storyboard | 06:45 | |
| *** fatema__ has joined #storyboard | 07:41 | |
| *** dhellmann has quit IRC | 07:41 | |
| *** tosky has joined #storyboard | 07:46 | |
| *** fatema__ has quit IRC | 07:52 | |
| *** vaatiesther has joined #storyboard | 08:23 | |
| *** vaatiesther has quit IRC | 08:27 | |
| *** vaatiesther has joined #storyboard | 08:28 | |
| *** udesale_ has joined #storyboard | 09:10 | |
| *** udesale has quit IRC | 09:10 | |
| *** vaatiesther has quit IRC | 09:11 | |
| *** vaatiesther has joined #storyboard | 09:14 | |
| *** udesale_ has quit IRC | 09:15 | |
| *** udesale has joined #storyboard | 09:16 | |
| *** vaatiesther has quit IRC | 09:24 | |
| *** vaatiesther has joined #storyboard | 09:27 | |
| SotK | hey fatema_, whats the login problem you're having? | 09:31 |
| *** dhellmann has joined #storyboard | 09:31 | |
| *** vaatiesther has quit IRC | 11:01 | |
| *** vaatiesther has joined #storyboard | 11:09 | |
| *** vaatiesther has quit IRC | 11:42 | |
| *** vaatiesther has joined #storyboard | 11:43 | |
| *** dmsimard has joined #storyboard | 12:42 | |
| dmsimard | Hi #storyboard | 12:42 |
| dmsimard | I have some projects that I would rather not have on storyboard because they are components of a main project and I'd like to keep everything under this one project. | 12:43 |
| dmsimard | When creating a new project, I have the choice for the project to be created on either launchpad or storyboard. | 12:43 |
| dmsimard | Should there be a toggle to inhibit the creation of either ? | 12:44 |
| persia | dmsimard: Would "project group" meet your needs? Storyboard assumes 1 project == 1 repo fairly strongly. | 12:44 |
| dmsimard | persia: yeah, I suppose this would end up being N repository for a project | 12:45 |
| dmsimard | my follow up question is -- can we delete projects from storyboard ? (empty and like I said, would rather manage it in another) | 12:45 |
| persia | To my mind, if I ha a project (e.g. "ZQZ"), and was decomposing it, I'd want to have a project group "ZQZ", and then projects zqz-web, zqz-server, libzqz-python, etc. | 12:46 |
| dmsimard | persia: that's exactly what I had in mind, yes | 12:46 |
| dmsimard | so nova could have all it's projects under one roof if it wanted to, for example | 12:46 |
| dmsimard | or rather, it would provide an easier view/dashboard of all the projects under it's governance ? | 12:46 |
| persia | I'm not sure it is possible to actually delete anything: I've argued against it fairly storngly in the past (although someone with DB access can do all sorts of things to data). I think it is possible to archive things. | 12:47 |
| tosky | dmsimard: that's a project group | 12:47 |
| fungi | dmsimard: https://storyboard.openstack.org/#!/project_group/list | 12:47 |
| persia | Right. I believe "nova" would be a project-group. I know that "Ironic" is one, for instance. | 12:47 |
| tosky | dmsimard: check what we did with sahara: https://storyboard.openstack.org/#!/project_group/74 | 12:47 |
| dmsimard | I didn't know project-groups were a thing :/ lol | 12:47 |
| tosky | but also ironic, and so on | 12:47 |
| tosky | ironic (just imported) has 23 projects (!) in the same project group O.o | 12:48 |
| dmsimard | thanks everyone for telling me about project groups, now I feel enlightened :P | 12:48 |
| persia | dmsimard: Does this semantic work for your use case, or do you need something different? | 12:48 |
| dmsimard | persia: yeah, it'll work | 12:48 |
| *** jamesmcarthur has quit IRC | 12:48 | |
| *** jamesmcarthur has joined #storyboard | 12:48 | |
| * persia anticipates rampant growth of group 71 | 12:49 | |
| *** fatema__ has joined #storyboard | 12:50 | |
| fungi | yeah, basically the way we're treating things is that tasks are explicitly per-repository (and if you have something that needs doing across several repositories that's several tasks, so they can be linked to separate changes in review). if you want a view of all stories with tasks for repositories (projects) maintained by your team, you can put them all in a common project group | 12:51 |
| * SotK notes that there was some talk a short while ago about removing the story lists from project/project group pages in favour of linking to a relevant search, due to them promoting the "story in project" data model misconception | 12:53 | |
| SotK | I wonder if people are using project groups in a way that such a change would be painful | 12:54 |
| tosky | uhm, I think that it's just a useful filter | 12:55 |
| tosky | if I go to the project page and check the stories, I expect to see the relevant story for that project, not the stories of that project | 12:56 |
| tosky | at least, that's me | 12:56 |
| SotK | tosky: that's how I see it too, but iirc there has often been confusion | 12:57 |
| tosky | SotK: and it's strange, because launchpad provided that too (by flagging a bug as found/to be fixed for different projects) | 12:58 |
| fatema__ | Hey SotK, I can't log in from the webclient, When I click on login Error "We encountered an unexpected error while trying to log you in. The error message below should be helpful, though if it's not you can contact our engineers in #storyboard on Freenode . " appears | 13:00 |
| persia | Does the view from the project page filter such that it only shows stories with active tasks for the project? If so, I am convinced that is a useful filter. | 13:01 |
| persia | Although I'm uncertain if search shouldn't do the same thing by default, really. | 13:02 |
| persia | (as if I search for a project, don't I care about the same set of stories that I would get if I browsed the project?) | 13:02 |
| SotK | fatema__: what is the error message shown below that? | 13:04 |
| SotK | persia: iirc it just shows active stories with tasks in that project, regardless of if all tasks for that project are merged | 13:05 |
| persia | SotK: Which? Search or Browse or both? | 13:05 |
| SotK | both | 13:05 |
| persia | Then I continue to think it isn't actually a useful filter :) | 13:05 |
| *** fatema__ has quit IRC | 13:05 | |
| persia | And for project groups with lots of projects (like Ironic), it might be easier to see more of them, rather than splitting the page (maybe with a link to "stories for this project group" somewhere). | 13:06 |
| tosky | but it also shows active stories when the tasks for the current project was merged (I created https://storyboard.openstack.org/#!/story/2001682 for that) | 13:08 |
| persia | Yes. My thought is that as long as https://storyboard.openstack.org/#!/project_group/74 and https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=74 have the same content, it is confusing to have both. | 13:14 |
| persia | Especially since REST suggests the former shouldn't be returning stories :) | 13:14 |
| dmsimard | fungi: oh wait, you're telling me "groups" in the project-config project configuration is actually the storyboard project groups ? | 13:15 |
| dmsimard | T_T | 13:16 |
| dmsimard | (It makes so much sense but for some reason I thought it was something else) | 13:16 |
| SotK | my feeling is that the correct behaviour is for https://storyboard.openstack.org/#!/project_group/74 to show projects in the group, and https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=74 to show stories with active tasks in that project group | 13:17 |
| *** tosky__ has joined #storyboard | 13:29 | |
| *** tosky has quit IRC | 13:31 | |
| *** jamesmcarthur has quit IRC | 13:31 | |
| *** jamesmcarthur has joined #storyboard | 13:32 | |
| *** jamesmcarthur has quit IRC | 13:33 | |
| *** jamesmcarthur has joined #storyboard | 13:33 | |
| persia | dmsimard: For Launchpad, it was something else :) | 13:34 |
| persia | SotK: That makes lots of sense to me. For reduction of user confusion, how do you feel with a link on https://storyboard.openstack.org/#!/project_group/74 to https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=74 ? | 13:34 |
| *** jamesmcarthur has quit IRC | 13:38 | |
| *** fatema__ has joined #storyboard | 13:40 | |
| fatema__ | SotK, "Error Code: unauthorized_clientError Description: You+did+not+provide+a+valid+client_id." | 13:41 |
| SotK | persia: I think that link in the form of a button or otherwise clearly visible thing is an excellent idea | 13:42 |
| SotK | fatema__: try adding the hostname or IP address you're using in your browser to `valid_oauth_clients` in ./etc/storyboard.conf and restarting the API | 13:43 |
| SotK | I think that's the issue that leads to that error | 13:44 |
| fatema__ | SotK, I think I did this in the setup steps | 13:45 |
| fatema__ | I added my public IP address | 13:47 |
| *** vaatiesther has quit IRC | 13:48 | |
| SotK | fatema__: are you navigating to your public IP address to see the webclient? I think the docs are a little unclear there, if you're going to (for example) http://127.0.0.1:9000/ in your browser then you need to have 127.0.0.1 in valid_oauth_clients | 13:48 |
| *** jamesmcarthur has joined #storyboard | 13:49 | |
| *** udesale has quit IRC | 13:53 | |
| *** udesale has joined #storyboard | 13:55 | |
| fatema__ | It now takes me to "https://login.launchpad.net/5L69xLBEPOSwFiYA/+decide" | 13:59 |
| fatema__ | so I should sign in with ubuntu one account?? | 14:00 |
| fatema__ | or I can use account from the users table in my local server "mysql" | 14:01 |
| persia | fatema__: Either that, or a launchpad account, depending on what you have and what you like. | 14:02 |
| persia | Storyboard uses login.launchpad.net as the OpenID provider, so users have to authenticate to that, and then launchpad confirms the authentication back to Storyboard. | 14:02 |
| persia | Your local mysql users are local, and you probably don't want to use the same password for them as for launchpad. | 14:03 |
| fatema__ | persia, ok then | 14:03 |
| persia | (I believe there was a time that "Ubuntu One" and "Launchpad" had different backends, but I think that currently both sorts of users are in a single authentication database: this may be old history and irrelevant) | 14:03 |
| fatema__ | persia, I also wonder if my PR is being reviewed or not as I did it on Github and I understood earlier that Github isn't all up-to-date ???? | 14:04 |
| persia | fatema__: It is not being reviewed. | 14:04 |
| * persia tries to find the relevant guide | 14:04 | |
| persia | https://docs.openstack.org/contributors/code-and-documentation/using-gerrit.html is the section about submitting changes that will be reviewed | 14:05 |
| persia | That entire guide will have more information about setting up the gerrit account and other things. | 14:05 |
| fatema__ | So it won't be reviewed on Github ? | 14:06 |
| fatema__ | I have to do it on Gerrit ? | 14:06 |
| persia | Yes. We do all our review on gerrit. Looling at github, it seems a robot has already closed your request and commented with some other links to docs (which may be better or worse than mine). | 14:07 |
| * fungi continues to wish github would let us disable pull requests on mirrors there | 14:10 | |
| fatema__ | persia, Ok but the thing is I am trying to do the patch ASAP to start with the proposal | 14:12 |
| persia | We aren't alone in our difficulties. In another context, I recently learned why it is impossible for an organisation to dispute officially named mirrors on github (and so stopped wishing that those mirrors weren't sanctioned by infra). | 14:12 |
| fungi | yeah, the storyboard repo has a CONTRIBUTING.rst which mentions the necessary contribution workflow. looks like some other related repos (like storyboard-webclient) don't have an equivalent CONTRIBUTING.rst so people might still easily miss it | 14:12 |
| *** fatema__ has quit IRC | 14:45 | |
| fungi | poking around in the mysql schema, seems we have a few possible unique keys on varchar(255) columns besides the one i hit on teams.name | 14:58 |
| fungi | also there are some columns which are varchar(255) but not used as an index. wonder if we should still limit them in case we want to index by those in the future? | 14:59 |
| *** diablo_rojo has joined #storyboard | 15:01 | |
| *** fatema__ has joined #storyboard | 15:05 | |
| *** dmsimard is now known as dmsimard|cave | 15:05 | |
| *** tosky__ is now known as tosky | 15:07 | |
| *** fatema__ has quit IRC | 15:16 | |
| *** dtantsur has joined #storyboard | 15:34 | |
| dtantsur | hi folks! we have a feature request, but I'd like to talk to someone before formally filing it. anybody up for that? | 15:35 |
| aspiers | I just got an email from StoryBoard containing "URL: None#!/story/2001430" | 15:38 |
| dtantsur | essentially, a custom report functionality. similar to some database GUI | 15:38 |
| dtantsur | from a project group with custom queries ("select count(*) from bugs where status == 'critical'") | 15:39 |
| dtantsur | and maybe with ability to list bugs as well | 15:39 |
| dtantsur | is there something like this? is there a place for something like this? | 15:39 |
| dtantsur | I'm going to implement such thing for our purpose, but I may well apply my coding skills to storyboard directly :) | 15:39 |
| corvus | fungi, diablo_rojo: i'm continuing to get timeout errors from my local cron job. i worry that either the db schema change or simply the addition of more stories has slowed things down. | 15:41 |
| fungi | corvus: i think the latter. we haven't successfully changed the schema yet (couldn't apply the utf8mb4 character set because some of our varchar indices are too long for innodb if we do) | 15:43 |
| corvus | fungi, diablo_rojo: i'm trying to collect more information -- it's difficult. i'd just consider it one data point that might warrant caution for now. | 15:44 |
| fungi | i'm working on putting together the right combination of varchar field limits for some things like "team name" (which was set as unique but left at the varchar(255) default) | 15:44 |
| fungi | corvus: well, i too am seeing similar-looking slowness. pulling up the infra team todo board takes 30+ seconds to populate the cards now | 15:44 |
| diablo_rojo | dtantsur, does an automatic worklist fulfill your needs? If not go ahead an implement I think :) | 15:45 |
| dtantsur | diablo_rojo: I'm not yet familiar with the concepts, sorry. is there a written description of this feature? | 15:45 |
| fungi | corvus: other possibilities... we might have someone spamming it with queries to build dashboards and the like? something may have happened at the hosting layer to degrade performance of our trove db? | 15:45 |
| diablo_rojo | dtantsur, let me go see | 15:45 |
| * diablo_rojo rifles through docs | 15:45 | |
| fungi | aspiers: are you getting other e-mails from storyboard with proper urls? or is this the only e-mail you've received from it recently? | 15:47 |
| diablo_rojo | dtantsur, so when you go through the process of making a worklist [1] there is a box to check as automatic and then you put criteria into that field so that stories and tasks that match the criteria get automatically put into the worklist. https://docs.openstack.org/infra/storyboard/user/worklists.html | 15:48 |
| dtantsur | diablo_rojo: aha, cool. this probably solves a part of our problems. | 15:49 |
| diablo_rojo | The docs don't talk about it that I can see- will have to get a patchout for that today | 15:49 |
| dtantsur | diablo_rojo: another part is that we calculate stats like on line 152 of https://etherpad.openstack.org/p/IronicWhiteBoard | 15:49 |
| diablo_rojo | dtantsur, I would think that with the functions currently in our api you could get that, but if there is anything missing- feel free to add :) | 15:50 |
| diablo_rojo | No view in the gui that I know up where you can see that info | 15:51 |
| dtantsur | diablo_rojo: I can, yes. the question is: do you want something like that IN storyboard? or should I go write our thingy? | 15:51 |
| dtantsur | (both are fine with me) | 15:51 |
| diablo_rojo | dtantsur, ah :) I can see other people having a use for wanting stats like that. I am fine with it going into our repo- SotK might have a differening opinion? (though I kind of doubt it) | 15:52 |
| dtantsur | do you see it as part of a project group feature? or maybe some us entity? | 15:52 |
| aspiers | fungi: it seems to happen with about 30% of them - trying to see if I can spot a pattern | 15:53 |
| fungi | aspiers: thanks! any additional detail you figure out would be good | 15:54 |
| diablo_rojo | dtantsur, yeah that makes the most sense to me | 15:54 |
| aspiers | fungi: OK, it's less than 30% | 15:54 |
| aspiers | fungi: they're all of the type 'Task "..." was updated by Openstack Gerrit' | 15:55 |
| persia | dtantsur: diablo_rojo: At some point we talked about having some example clients in the python-storyboardclient repo: I don't know if that's the best place. Another idea previously expressed was to have some sort of storyboard-tools repo that contained some sample clients to do useful things. | 15:56 |
| persia | Generally speaking, I don't think we want to put all the functionality in StoryBoard, but rather take advantage of the API-first design to put more things as tools (and improve the API to make tools better). | 15:57 |
| dtantsur | yeah, that's why I ask. if nobody else cares about such feature, I can well implement it separately | 15:58 |
| dtantsur | thanks (no, THANKS) to the API-first design I expect much less pain that with LP ;) | 15:58 |
| persia | I care about the features: I just think they belong in a parallel repo, rather than in Storyboard :) | 15:58 |
| diablo_rojo | I suppose we could make it the first tool in the storyboard-tools repo. | 15:58 |
| persia | aspiers: fungi: there is a story and patch for the gerrit-updates-send-broken-email already | 15:58 |
| * persia tries to find them | 15:59 | |
| dtantsur | another thing is hosting: if it's not in storyboard, it will have to be hosted somewhere | 15:59 |
| SotK | some support in the API for queries like "things created between 2018-03-12 and 2018-03-19" would be nice | 15:59 |
| diablo_rojo | Yeah, we would have to make the repo | 15:59 |
| dtantsur | ++ that won't hurt at all | 15:59 |
| diablo_rojo | SotK, think its time to pull the trigger on that idea? | 16:00 |
| persia | https://review.openstack.org/#/c/555237/ and https://storyboard.openstack.org/#!/story/2001410 | 16:00 |
| SotK | diablo_rojo: I would like someone to do so, I don't think I have enough time to commit myself | 16:00 |
| dtantsur | as to my idea, I guess I'll start with a prototype to show you what exactly I have in mind | 16:00 |
| SotK | at the moment you can get that information with a lot of effort using the APIs for events | 16:00 |
| dtantsur | and then you'll decide | 16:00 |
| diablo_rojo | dtantsur, that sounds perfect. | 16:01 |
| SotK | indeed | 16:01 |
| persia | SotK: What do you think of storyboard-tools to put things like this? Do you think they belong somewhere else? | 16:01 |
| diablo_rojo | SotK, I can investigate what it would take to make another repo. | 16:01 |
| SotK | I am entirely in favour | 16:02 |
| * diablo_rojo added investigation of new repo to my todo list | 16:02 | |
| persia | diablo_rojo: It is in https://docs.openstack.org/infra/manual/creators.htm (as creating a new repo is considered part of creating a project). IIRC it's something like 4-5 commits, all in the right places. | 16:10 |
| *** udesale has quit IRC | 16:17 | |
| *** udesale has joined #storyboard | 16:17 | |
| *** tosky has quit IRC | 16:19 | |
| *** tosky has joined #storyboard | 16:29 | |
| *** udesale has quit IRC | 16:35 | |
| dtantsur | "The Same Origin Policy disallows reading the remote resource at https://storyboard.openstack.org/api/v1/stories?project_group_id=75" | 16:49 |
| dtantsur | I wonder if you could set up CORS somehow.. otherwise it does not look like it's possible to create an out-of-tree dashboard | 16:49 |
| *** dtantsur is now known as dtantsur|afk | 17:15 | |
| fungi | rather, not possible to implement in-browser javascript consuming that being published from a different server. it could be done without javascript (e.g. via a cgi or similar), it could be done by hosting javascript dashboards on the same server as the webclient continuously published through some ci job, et cetera | 17:30 |
| fungi | but i agree cors support would be cool | 17:30 |
| SotK | heh, I guess you are the first to attempt using the API from js on a different host | 17:31 |
| fungi | i wonder how we're making that work for logs.openstack.org publishing draft renderings of storyboard-webclient hitting the api on storyboard-dev.openstack.org | 17:31 |
| SotK | cors support would indeed be good | 17:31 |
| SotK | hm, good point | 17:32 |
| fungi | we probably set something in the vhost config to bypass that | 17:32 |
| fungi | dtantsur|afk: SotK: looks like we pass in a $cors_allowed_origins parameter which ends up lighting this section of the config: http://git.openstack.org/cgit/openstack-infra/puppet-storyboard/tree/templates/storyboard.conf.erb#n72 | 17:45 |
| fungi | the api enforcement is here: http://git.openstack.org/cgit/openstack-infra/storyboard/tree/storyboard/api/app.py#n122 | 17:48 |
| fungi | using the cors middleware implementation here: http://git.openstack.org/cgit/openstack-infra/storyboard/tree/storyboard/api/middleware/cors_middleware.py | 17:49 |
| fungi | so it should be doable already | 17:50 |
| fungi | and indeed, in our config for storyboard-dev we set cors.allowed_origins to https://storyboard-dev.openstack.org,http://logs.openstack.org as you would expect | 17:52 |
| SotK | I wonder if it would be nice to allow GET from all and just have a list of allowed_origins for PUT, POST, and DELETE | 17:55 |
| SotK | to avoid anyone who wants to make a dashboard needing to send a patch to system-config | 17:55 |
| fungi | yeah, as long as we're not taking action based on get variables (this is the api, not the webclient, so i wouldn't expect that to be the case anyway if this is rest-ish?) | 18:01 |
| fungi | dtantsur|afk: ^ whenever you're back, would that address your concerns? if so, it's a very easy patch | 18:02 |
| persia | I think the API is rest-ish enough for public GET to be safe. | 18:15 |
| persia | Somehow I think it a bit odd that we permit access from anywhere in python, but not in javascript: does this actually protect anything? | 18:16 |
| *** jamesmcarthur has quit IRC | 18:18 | |
| *** jamesmcarthur has joined #storyboard | 18:27 | |
| *** jamesmcarthur has quit IRC | 18:31 | |
| fungi | it protects browsers against cross-site scripting attacks | 18:42 |
| fungi | e.g., malicious actor couldn't coerce an unwitting victim to browse their third-party site and post into a logged-in storyboard session | 18:43 |
| fungi | because the js stack in the browser would see the cors headers don't list those operations as safe from that site and so would disallow them | 18:44 |
| fungi | for something else (e.g. python) to perform tasks which require authentication, they would need credentials anyway | 18:45 |
| fungi | cross-site scripting and similar classes of attacks mostly rely on the assumption that the browser already has or can automatically obtain an authenticated session on the target site | 18:46 |
| fungi | with minimal/spoofable interaction from the end user | 18:46 |
| *** jamesmcarthur has joined #storyboard | 19:28 | |
| openstackgerrit | Jeremy Stanley proposed openstack-infra/storyboard master: For utf8mb4 shorten teams.name and users.email https://review.openstack.org/556626 | 19:28 |
| fungi | SotK: diablo_rojo: mordred: EmilienM: ^ | 19:29 |
| fungi | i've tested that migration manually on storyboard-dev and with the above modification it seems to succeed | 19:29 |
| fungi | though i'm still curious why our testing didn't catch that... we _do_ apply migrations in one of our jobs, right? | 19:29 |
| *** jamesmcarthur has quit IRC | 19:33 | |
| *** jamesmcarthur has joined #storyboard | 19:33 | |
| *** jtomasek has quit IRC | 19:39 | |
| fungi | now to test whether it gets me past the errors i had importing tripleo-ui bugs | 19:49 |
| openstackgerrit | Jeremy Stanley proposed openstack-infra/storyboard master: For utf8mb4 shorten teams.name and users.email https://review.openstack.org/556626 | 19:55 |
| *** EmilienM has quit IRC | 19:57 | |
| *** EmilienM has joined #storyboard | 19:57 | |
| *** EmilienM has quit IRC | 19:57 | |
| *** EmilienM has joined #storyboard | 19:57 | |
| fungi | would also be would also be nice to get a second review on the very trivial https://review.openstack.org/555957 (Finish fixing account duplication on import) so that i don't have to keep remembering to checkout that commit before running new migrations | 19:57 |
| *** jamesmcarthur has quit IRC | 20:01 | |
| diablo_rojo | SotK, can you check that one out ^^ | 20:01 |
| *** jamesmcarthur has joined #storyboard | 20:01 | |
| fungi | not that the cleanup is _that_ hard now that i've scripted it, but it's still a massive amount of unnecessary churn in the affected tables when i do | 20:02 |
| fungi | and inflates our account ids significantly | 20:03 |
| fungi | triplei-ui test import is running on storyboard-dev now after successful utf8mb4 migration. will report when it either succeeds or goes down in flames | 20:04 |
| *** jamesmcarthur has quit IRC | 20:05 | |
| *** jamesmcarthur has joined #storyboard | 20:09 | |
| *** jamesmcarthur has quit IRC | 20:09 | |
| *** mridu has joined #storyboard | 20:24 | |
| *** fatema__ has joined #storyboard | 20:25 | |
| fungi | flames it is! | 20:31 |
| fungi | nothing is ever simple | 20:31 |
| fungi | still the same error, full output is http://paste.openstack.org/show/714793/ | 20:31 |
| fungi | i need to go find something to eat, but will try to dig deeper and figure out how to get some more info out of mysql about whether it supports the right encoding after migrating | 20:32 |
| *** jamesmcarthur has joined #storyboard | 20:56 | |
| openstackgerrit | Fatema Khalid Sherif proposed openstack-infra/storyboard master: Changing 'merge' Tasks to be 'resolved' https://review.openstack.org/556648 | 21:14 |
| diablo_rojo | fatema_, congrats!! ^^ | 21:20 |
| diablo_rojo | I made three small comments, but you might want to wait for Zuul to come back with a review as well before making another patchset. | 21:20 |
| diablo_rojo | Zuul being our CI/gating system. | 21:20 |
| fatema__ | diablo_rojo, Thank you ^^ ! I still have the error I mentioned above xD | 21:33 |
| fatema__ | diablo_rojo, another question though, Shall I start with the proposal now ??? | 21:34 |
| fatema__ | diablo_rojo, I adjusted as the comments said, thank you | 21:36 |
| diablo_rojo | fatema__, yeah go ahead :) | 21:45 |
| diablo_rojo | I'll look at the logs zuul comes back with | 21:45 |
| diablo_rojo | Should be around a half hour. | 21:48 |
| diablo_rojo | You can watch its progress here fatema__ http://zuul.openstack.org/ | 21:48 |
| *** jamesmcarthur has quit IRC | 22:01 | |
| fatema__ | diablo_rojo, OK I am on it | 22:02 |
| *** jamesmcarthur has joined #storyboard | 22:02 | |
| fatema__ | ok I didn't fully understand the logs ^^ | 22:20 |
| fatema__ | I'm still going through the manual though | 22:20 |
| diablo_rojo | fatema__, there was a time out so I issued a recheck. | 22:21 |
| fatema__ | Ok | 22:45 |
| fatema__ | well, about the application form | 22:49 |
| fatema__ | I am not sure what to write in the "Experience with this community" xD | 22:50 |
| diablo_rojo | You can say that you went through the conributor guide (if you did that is lol), talk about your interactions here in the channel with us, etc. | 22:54 |
| diablo_rojo | fatema__, ^ | 22:54 |
| fatema__ | I understood it asks me as a user not as a contributer ! | 22:55 |
| diablo_rojo | I think it could be either. | 22:57 |
| diablo_rojo | Any sort of experience with the community :) Attending events, contributing, using, all sorts of interactions :) | 22:58 |
| fatema__ | super ^^ | 22:59 |
| fatema__ | another question, About the time plan, the tasks aren't really specific so how should they be put in the time plan ? | 23:00 |
| *** jamesmcarthur has quit IRC | 23:02 | |
| *** jamesmcarthur has joined #storyboard | 23:03 | |
| fatema__ | and Do you have a "Community-specific Questions" ??? | 23:05 |
| *** tosky has quit IRC | 23:08 | |
| diablo_rojo | fatema__, uhhh no idea for that one. Sounds pretty optional | 23:12 |
| fatema__ | It says "Some communities or projects may want you to answer additional questions. Please check with your mentor and community coordinator to see if you need to provide any additional information after you save your project application." | 23:18 |
| fatema__ | so I am checking with you :D | 23:18 |
| diablo_rojo | fatema__, I don't have any other questions I don't think :) SotK do you have any questions for fatema__? | 23:23 |
| diablo_rojo | (he might not be around to answer for a while) | 23:23 |
| fatema__ | Well, it's 1 a.m. here so will he be gone for a "long" while ? | 23:24 |
| *** jamesmcarthur has quit IRC | 23:27 | |
| diablo_rojo | He lives in Manchester so I would think you could go to bed and catch him when you wake up | 23:32 |
| diablo_rojo | (I'm guessing he is alseep too or headed there shortly himself | 23:32 |
| fatema__ | diablo_rojo, fine then Good evening ^^ | 23:39 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!