Thursday, 2016-02-25

*** mrmartin has joined #storyboard05:44
*** mrmartin has quit IRC05:48
*** mrmartin has joined #storyboard06:38
*** jtomasek has joined #storyboard07:46
*** mrmartin has quit IRC08:55
*** mrmartin has joined #storyboard09:44
* SotK apologises for yesterday's rush patch bomb :)10:15
* SotK goes to review krotscheck's access tokens stuff10:15
Zarakrotscheck: the 'undefined' error is my work, I fear. It's looking for subscriptions, but there is no subscription for a logged out user. (I changed subscriptions so it wouldn't do one GET per subscription, but also didn't really know what I was doing, so that code isn't great.10:32
ZaraI thought the getter setter error was something that was there before we got there, but maybe not. in which case perhaps the pagination stuff is responsible, since that refers to offset.10:33
*** mrmartin has quit IRC10:34
SotKI think the getter setter thing is caused by the autoresizeWidth directive10:34
*** mrmartin has joined #storyboard10:35
*** mrmartin has quit IRC10:35
Zaraahhh10:36
*** faybrocklebank has joined #storyboard10:40
*** mrmartin has joined #storyboard10:47
*** mrmartin has quit IRC11:12
openstackgerritAdam Coldrick proposed openstack-infra/storyboard: Update `PUT /v1/worklists/:id/items/:id` to allow assigning a due date  https://review.openstack.org/28431611:36
openstackgerritAdam Coldrick proposed openstack-infra/storyboard: Add Due Dates to the WSME models for boards, worklists, tasks, and stories  https://review.openstack.org/28431511:36
openstackgerritAdam Coldrick proposed openstack-infra/storyboard: Add Due Dates to the API  https://review.openstack.org/28431411:36
Zara:011:36
pedroalvarezkrotscheck: it does make sense yes11:45
pedroalvarezI have to admit I don't fully understand our authentication code, though11:45
pedroalvarezI'll have to read more about it if I want to understand it I imagine11:46
Zaratested behaviour, agree that the refresh token behaviour is a bit confusing for users, but this is so much less annoying than before, so have +1'd.11:48
* SotK reads the js error log for his patches more closely and wonders how he missed that we already use momentjs11:48
* SotK facepalms11:48
ZaraI missed that too when reviewing :/11:48
*** mrmartin has joined #storyboard12:11
Zaraany objections to me merging both parts of king in the north12:14
Zara?12:14
pedroalvarez_o_12:14
* Zara workflow +1s12:15
SotK\o/12:15
Zaraso much nicer than before :)12:15
Zarathanks so much, krotscheck12:15
pedroalvarezwe can always revert if something goes really really wrong12:15
pedroalvarezbut I doubt it12:15
Zarayeah, the only problem I could find was with the refresh token behaviour, and that's a separate thing.12:16
Zara(my reviews always jump straight to the negative things! but I'm very pleased about this really :D)12:17
openstackgerritAdam Coldrick proposed openstack-infra/storyboard-webclient: Display a modal when a card is clicked on  https://review.openstack.org/28428012:36
openstackgerritAdam Coldrick proposed openstack-infra/storyboard-webclient: Allow a custom format string to be passed to time-moment  https://review.openstack.org/28427512:36
openstackgerritAdam Coldrick proposed openstack-infra/storyboard-webclient: Add a calendar directive  https://review.openstack.org/27850812:36
openstackgerritAdam Coldrick proposed openstack-infra/storyboard-webclient: Add a $resource wrapper for Due Dates  https://review.openstack.org/28427812:36
openstackgerritAdam Coldrick proposed openstack-infra/storyboard-webclient: Add Due Dates to boards  https://review.openstack.org/28427912:36
openstackgerritAdam Coldrick proposed openstack-infra/storyboard-webclient: Add onBlur and onFocus callbacks to user-typeahead  https://review.openstack.org/28427612:36
openstackgerritAdam Coldrick proposed openstack-infra/storyboard-webclient: Improve the board CSS a little  https://review.openstack.org/28427712:36
SotKargh, forgot to edit a commit message12:37
openstackgerritAdam Coldrick proposed openstack-infra/storyboard-webclient: Display a modal when a card is clicked on  https://review.openstack.org/28428012:38
openstackgerritAdam Coldrick proposed openstack-infra/storyboard-webclient: Allow a custom format string to be passed to time-moment  https://review.openstack.org/28427512:38
openstackgerritAdam Coldrick proposed openstack-infra/storyboard-webclient: Add a calendar directive  https://review.openstack.org/27850812:38
openstackgerritAdam Coldrick proposed openstack-infra/storyboard-webclient: Add a $resource wrapper for Due Dates  https://review.openstack.org/28427812:38
openstackgerritAdam Coldrick proposed openstack-infra/storyboard-webclient: Add Due Dates to boards  https://review.openstack.org/28427912:38
openstackgerritAdam Coldrick proposed openstack-infra/storyboard-webclient: Add onBlur and onFocus callbacks to user-typeahead  https://review.openstack.org/28427612:38
openstackgerritAdam Coldrick proposed openstack-infra/storyboard-webclient: Improve the board CSS a little  https://review.openstack.org/28427712:38
ZaraxD12:39
pedroalvarez  /ignore SotK12:40
krotschecknp everyone12:41
*** mrmartin has quit IRC12:43
*** mrmartin has joined #storyboard12:44
*** jtomasek_ has joined #storyboard12:47
*** mrmartin has quit IRC12:48
openstackgerritAdam Coldrick proposed openstack-infra/storyboard: Update `PUT /v1/worklists/:id/items/:id` to allow assigning a due date  https://review.openstack.org/28431612:48
openstackgerritAdam Coldrick proposed openstack-infra/storyboard: Add Due Dates to relevant WSME models  https://review.openstack.org/28431512:48
pedroalvarezshould w recheck king_of_the_north patch set?12:57
Zaraah, thanks for the tip13:01
Zarathe very last test timed out, ugh13:01
Zaratesting the due dates api patches is going to be exciting, since my db is currently a different version 52 (because of task links patch)13:08
*** jtomasek_ has quit IRC13:14
openstackgerritMerged openstack-infra/storyboard-webclient: Logging in no longer causes page refresh.  https://review.openstack.org/27088213:19
openstackgerritMerged openstack-infra/storyboard-webclient: Access tokens are now refreshed in preflight promises.  https://review.openstack.org/28435613:42
SotK\o/13:43
Zara\\\\\\o//////13:45
*** faybrocklebank has quit IRC14:04
*** faybrocklebank has joined #storyboard14:19
* Zara checks out 'fix permissions', calls branch 'permissionspermissions'14:33
*** b3rnard0_away is now known as b3rnard014:34
*** jmccrory has quit IRC15:12
*** jmccrory has joined #storyboard15:13
Zaraheh, I think some of the odd tag choices in 'move search icon' were to do with expected tags displaying in strange ways15:17
Zara(not that it doesn't still look strange, but it looked even more strange :D)15:18
anteayaso jeblair commented that searching for people to add as owners to a board is easier in storyboard than searching for people in gerrit15:26
anteayaso well done15:26
*** Zara_ has joined #storyboard15:26
*** Zara has quit IRC15:26
pedroalvarezas long as there's only one with that name15:27
anteayawell that is interesting you say that15:28
anteayathere are two yolanda's in storyboard15:28
anteayahow do we know which is the real yolanda?15:29
SotKyeah, the name thing is a problem15:29
anteayawhat is your understanding of the problem?15:29
SotKthe only identifying information for users we have is their name, email, and openid URL15:30
*** Zara_ is now known as Zara15:30
SotKwe keep the email private, and launchpad openid URLs aren't useful for humans trying to determine identity15:31
SotK(mine is https://login.launchpad.net/+id/dQxpCYE for example)15:31
SotKso we only have the name as useful information to display, but name alone isn't enough to uniquely identify a person15:32
SotKI think StoryBoard used to ask for a username from the openid provider too, but that meant people couldn't log in with launchpad until they'd logged in to ubuntu one with their launchpad id IIRC15:33
pedroalvarezavatars will help, but is not enough15:34
SotKindeed15:34
SotK(my gravatar is a cloud)15:34
pedroalvarezI'm starting to think that emails is the only way15:35
SotK(and that isn't even for the right email address...)15:35
SotKpedroalvarez: I suspect that may be the case too15:35
anteayahmmmm15:36
anteayasounds like it might be a discussion item for a larger audience15:36
SotKI think so too15:36
anteayaperhaps start an email thread on the infra mailing list?15:36
* Zara loses some backscroll, checks logs15:40
Zara(yay, well done SotK!)15:41
* SotK wonders what he did well :)15:42
pedroalvarezhaving a cloud as avatar15:42
persiaSo, playing with https://storyboard.openstack.org/#!/board/ , I discovered it is possible to distinguish between board IDs to which I don't have access vs. board IDs which don't exist.  Is this important?15:42
persiae.g. board 4 is not visible by me, and board 5 has been deleted.15:43
persiaThe behaviour difference is that I get a 404 for a nonexistent board, and a redirect to the dashboard for a board to which I don't have permission.15:43
SotKerm, that is weird15:44
SotKI can see board 4 but it appears to have no lanes15:44
persiaAs long as we're exposing this difference, I'd rather get a 403 when I don't have permission, as it means I don't have to go start from scratch if I mistype the URI.15:44
persiaInteresting: now I can see board 4, board 5 redirects to dashboard, and board 6 gets 404.15:45
persia(on storyboard.openstack.org, for clarity)15:45
persia(as a side note, that https://storyboard.openstack.org/#!/board/6 produces 404: GET /api/v1/boards/6: Board 6 not found is vaguely amusing: note the difference between "board" and "boards")15:46
SotKthat plural/singular difference is there for all the resources I think15:48
SotKits weird that the webclient is showing different behaviour, we should be only ever cause 404 on boards you can't see for whatever reason15:49
SotKany hint in your browser console as to what the error which triggered the redirect was?15:49
Zaramine just seems to give 404s for both 5 and 615:50
Zarawhat's the board 5 url that is redirecting you to the dashboard?15:51
persiahttps://storyboard.openstack.org/#!/boards/516:02
persiaErr16:03
persiahttps://storyboard.openstack.org/#!/board/516:03
pedroalvarezthere you have it16:04
persiaNote that if I'm on the dashboard, I can't get the 404s: those only appear if I'm viewing a board currently16:04
persiapedroalvarez: The first URL was a typo (I lose the URL on redirect), not that I was getting odd behaviour from the wrong one.16:05
pedroalvarezhah, just wondering, because when the url is boards/*  (with s) I get the redirect too16:05
SotKpersia: can you use your browsers inspector to figure out which API request is failing?16:05
persiahttp://paste.openstack.org/show/488213/ is some console log from my browser16:08
persiaWhile "5" was the latest request (causing the redirect), I was able to get a 404 from "5" earlier up.16:09
* SotK is suddenly enlightened on how to fix that stupid marked problem, on an unrelated note16:09
persiaheh16:10
* SotK remains clueless as to why you're getting a redirect though16:13
ZaraI can't reproduce it. :/16:13
* SotK neither16:13
persiaMight be a caching thing: my browser caches more than it should.16:14
persiaI don't know precisely why.16:14
persiaI found it by starting from board/1 and increasing the digit until I had different behaviour16:14
persiaBut as I test more, sometimes I get the dashboard on a given board, and sometimes I get the board, making me think it is me, and not the code.16:15
persiaApologies for the confusion.16:15
Zaraheh. :) oh well, I've now found it *is* possible to differentiate between 'never a board' and 'board that was archived or you don't have permissions for'16:15
Zara 500: GET /api/v1/boards/98/permissions: 'NoneType' object has no attribute 'permissions'16:15
Zarawill come up if you go to a board that doesn't exist and never existed16:16
Zarawell, I think archived boards behave differently, maybe not16:16
persiaHrmm.  I went up to 12 before, and now I can replicate the 500 on 11+12, and the 404 on 10 or 6.16:17
persiaBut I wasn't getting a 500 before on 11 or 12.16:18
persiaI think my browser isn't behaving right.16:18
ZaraI think your browser did weird things a while ago16:18
Zarathis seems familiar16:18
Zarabut I can't remember what they were and can't help debug it at all =D16:18
* SotK can't see the 500 on anything16:19
Zarahm, that's strange.16:19
Zarahttps://storyboard.openstack.org/#!/board/55516:20
Zaragives me two errors16:20
Zaraa 404 and a 50016:20
SotKoh, I wasn't logged in16:20
Zarahaha16:20
SotKhttps://review.openstack.org/#/c/284313/ might fix that I think16:21
Zaraheh16:22
SotKhm, it makes it a 404 rather than a 50016:22
SotKdoes the same on boards that exist but aren't visible though16:23
Zaraan extra one?16:23
SotKyeah16:23
Zarahah, didn't catch that16:24
* Zara can't procrastinate any more from testing due dates api patch16:53
Zaraand all the migrating that involves16:53
SotKchange the 52 to a 53 in the migration16:54
Zaraahahaha16:54
Zarathat would work xD16:55
SotK(and the 51 to a 52)16:55
SotK(the 51 in the migration script that is)16:55
ZaraI think my brain just hasn't turned on today16:55
Zarayeah16:55
Zaradoes it ever turn on? sources differ16:55
ZaraI will do that, thanks16:55
* SotK looks at the tasks links stuff16:59
Zara\o/16:59
ZaraI suspect more -1s await16:59
Zarabut the boolean search patch should be SOLID16:59
SotKThe code looks good, but I wonder if we want to be able to assign more than one link to a task?17:00
Zarayeah, I wondered about that. I figured 'start off with one, change it to more later if we have to'17:04
Zarathough I had assumed that would be fairly simple, when it might not be17:05
persiaMore than one link to a task?17:07
* SotK thinks its probably worth just going straight to more than one links17:07
* SotK thinks17:08
SotKmaybe its worth not insisting its a link and just allowing some text metadata with a key and value that clients can use to mean whatever they want17:09
SotKthat might be pointless complexity17:09
ZaraI think it's doing that practically-speaking, it's just called 'link' (and displays in a way that implies it can be clicked)17:10
SotKyeah, being called link is what I meant, insisting was too strong a word17:10
Zaraheh17:11
Zarayeah, I wondered about that, too; I couldn't see how that'd be used in any way that I was gonna get round to coding the UI for any time soon17:11
ZaraI could see people using it for comments on tasks, etc17:12
Zara(and I think the field lets you do that in practice, since I used the same thing as story description iirc)17:12
Zarabuuuut the layout side of it would need fixing17:12
ZaraI'm not opposed to calling it something other than 'link', anyway, I just couldn't think of a good alternative and that's all it's useful for atm xD17:13
* SotK would like it to be called link if we only allow one, but if we allow many I think it should be a broader name17:14
persiaNow that I understand "link", I agree that multiple makes more sense.17:21
persiaFor example, for a given task in my project, there may be a couple of downstream trackers that contain useful information (e.g. distro trackers), so I'd want to reference more than one.17:22
pedroalvarezI agree that various links might be better17:24
pedroalvarezalthough that will complicate things for whenever I implement the thing that auto-updates tasks17:25
SotKit'll also be more complex to show on the UI, but I suspect its worth doing17:26
Zara:) well from me it's not really a 'it's not worth it' and more 'I am not going to get to that for some time', so it's whether it's better to have one link in the interim, or none.17:28
* SotK wonders how urgently we want task links17:29
pedroalvarezoh, question: why multiple links?17:30
pedroalvarezand what are the links going to be for17:31
ZaraI could see them being for a commit, a spec, some relevant docs, that kind of thing. The most important immediate one was the commit17:31
* SotK had the same kind of things in mind17:31
Zarasince I figured other things tend to apply to several tasks and can generally go in the description in the interim17:32
pedroalvarezI only had "a patch" in mind17:32
pedroalvarezbut I can see how allowing multiple sould be useful17:32
pedroalvarezalthough maybe they should be separate things... for example, a field for the patch link, and a description box in where you can put links, and whatever else17:33
pedroalvarez(just a thought)17:33
Zarayeah, for me, it's a case of: I had time to work further on this earlier this fortnight, now I don't (and won't 'til I work through due_dates review), and it requires a fair bit of time on the UI side17:33
* SotK apologises for not looking at it until now17:34
Zaranah, you were busy coding the due_dates! :D17:34
persiaOne link is better than none.17:34
pedroalvareznod17:35
persiaAlthough I start to worry about the fragility.17:35
persiaWhile I *really* want to be able to click a task in Storyboard and open the gerrit review in a new window (for tasks both in review and merged), having to specify this in the commit message hoping a bot will parse this and update Storyboard so I can link seems poorly integrated somehow.17:36
persiaI'm not sure of the best way to solve that, but I thought I'd share my worry in the hopes someone else can think of a way for it to be robust.17:36
* SotK doesn't see what more we could do17:37
SotKShort of putting the issue tracker in Gerrit, I don't see any better way of synchronisation than a bot or plugin based on something in the commit message17:39
persiaIt's more the flexibility of the things.17:40
persiaIf we assert SB is for gerrit, we can do cross-integration things afterwards to maintain data consistency.17:40
persiaIf we want SB to work for arbitrary patch trackers (and I think we do), I think we end up fragile.17:41
persiaI don't know the solution today.17:41
persiaAnd fragile-but-useful is better than not-useful17:41
* SotK sees the point, and agrees that fragile-but-useful is better than nothing17:44
*** b3rnard0 is now known as b3rnard0_away18:01
* SotK wonders how archiving cards instead of deleting them should work when it comes to creating a new card for a task that has an archived card18:04
persiaDoes card identity depend on the worklist and/or board housing it?18:04
SotKyes18:05
persiaThen it makes sense that if I archive foo from a worklist, and then later want to add foo, to restore old foo, so I have context, in case I set a date, etc.18:05
persiaAnd nobody needs fear that if they add foo to their worklist they will end up with my recycled foo18:05
persiaNote that if I delete foo from my worklist, and add it to a *different* worklist, it should only be unarchived if those worklists participate in the same board.18:06
persia(at least, that's how I imagine using it)18:06
SotKthat makes sense to me18:07
openstackgerritMerged openstack-infra/storyboard: Add column for task links  https://review.openstack.org/27748118:08
openstackgerritMerged openstack-infra/storyboard: Adjust API Endpoints for Task Links  https://review.openstack.org/27783118:09
Zara\o/18:09
ZaraI didn't get that much reviewed today, should get more done tomorrow. :/18:13
Zaranight, storyboard! :D18:31
openstackgerritAdam Coldrick proposed openstack-infra/storyboard: Update `PUT /v1/worklists/:id/items/:id` to allow assigning a due date  https://review.openstack.org/28431618:37
openstackgerritAdam Coldrick proposed openstack-infra/storyboard: Fix permissions being able to be set by any authenticated user  https://review.openstack.org/28431318:37
openstackgerritAdam Coldrick proposed openstack-infra/storyboard: Move permissions checks into storyboard.db.api  https://review.openstack.org/28431218:37
openstackgerritAdam Coldrick proposed openstack-infra/storyboard: Add Due Dates to relevant WSME models  https://review.openstack.org/28431518:37
openstackgerritAdam Coldrick proposed openstack-infra/storyboard: Add Due Dates to the API  https://review.openstack.org/28431418:37
*** jtomasek has quit IRC18:49
*** b3rnard0_away is now known as b3rnard018:49
*** krotscheck is now known as krotscheck_dcm19:50

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!