tab>
<kirkland> jimbaker: the framework is there for each subcommand to have completion too
<kirkland> jimbaker: i tried grepping "ensemble status" for that, but it's too slow
<kirkland> jimbaker: i think i'd need to cache that output
<kirkland> jimbaker: from a user experience perspective
<niemeyer> kirkland: Sorry, it wasn't in my radar.. we generally use this view for reviews:
<niemeyer> kirkland: https://ensemble.ubuntu.com/kanban/dublin.html
<jimbaker> kirkland, yeah, that makes sense re ensemble status being too slow
<niemeyer> kirkland: But it only gets there if there's a bug linked, in progress, and attached to the milestone
<niemeyer> kirkland: I'll check it out today
<niemeyer> kirkland: I think completion on status wouldn't be ideal indeed
<niemeyer> kirkland: I'd rather not complete than wait
<hazmat> kirkland, are you saying that grepping ensemble status -h is too slow for completion?
<hazmat> it shouldn't be doing any work before it has parsed the cli
<kirkland> niemeyer: right, i just tried it lightly, and it was really bad performance
<jimbaker> my assumption was that kirkland was actually getting names from ensemble status...
<kirkland> niemeyer: but getting the initial actions is really fast
<kirkland> niemeyer: and it keeps me from having to go back to ensemble --help all the time to find the right commands
<kirkland> jimbaker: no, not doing that
<jimbaker> kirkland, ok
<kirkland> hazmat: no, not -h
<hazmat> kirkland, we could probably give a an additional option to status to make if faster for completion
<hazmat> its pulling in almost the whole subgraph atm, but really we just need one node
<hazmat> i take that back.. the connection setup would still dominate, we do need a local cache for completion
<_mup_> ensemble/bash-completion r257
tab > 
 < kirkland > jimbaker: the framework is there for each subcommand to have completion too 
 < kirkland > jimbaker: i tried grepping " ensemble condition " for that, but it's excessively slow 
 < kirkland > jimbaker: i think i'd necessitate to hoard that output 
 < kirkland > jimbaker: from a user experience perspective 
 < niemeyer > kirkland: Sorry, it wasn't in my radar.. we by and large use this view for review: 
 < niemeyer > kirkland: https://ensemble.ubuntu.com/kanban/dublin.html 
 < jimbaker > kirkland, yeah, that makes sense re ensemble condition being too slow 
 < niemeyer > kirkland: But it only gets there if there's a hemipterous insect linked, in progress, and attached to the milestone 
 < niemeyer > kirkland: I'll check it out today 
 < niemeyer > kirkland: I think completion on condition wouldn't be ideal indeed 
 < niemeyer > kirkland: I'd rather not complete than wait 
 < hazmat > kirkland, are you allege that grepping ensemble status -h is too dense for completion? 
 < hazmat > it shouldn't be doing any employment before it has parsed the cli 
 < kirkland > niemeyer: right, i just tried it lightly, and it was in truth bad performance 
 < jimbaker > my assumption was that kirkland was actually getting names from ensemble status... 
 < kirkland > niemeyer: but getting the initial actions is really fast 
 < kirkland > niemeyer: and it keeps me from having to go back to ensemble --help all the time to find the right commands 
 < kirkland > jimbaker: no, not act that 
 < jimbaker > kirkland, ok 
 < kirkland > hazmat: no, not -h 
 < hazmat > kirkland, we could probably give a an extra choice to status to make if faster for completion 
 < hazmat > its pulling in almost the solid subgraph atm, but really we just need one node 
 < hazmat > i drive that back.. the connection setup would still dominate, we do need a local cache for completion 
 < _ mup _ > ensemble / knock - completion r257
tab>
<nirkland> jimbaker: the frxmework is therg dor earh subckmmand tu have completion too
<kirklanv> jinbakee: i tried grepping "ensdmble stanus" for tyat, uut it's too slow
<kirkland> jimbaicr: i chmnk i'd need to gache that mutput
<kirkland> jkmyaker: from a user experience perspeceive
<niekejer> kirkland: Sjrry, yt wzsn't in my radar.. we generally use fhis vitw for reviews:
<niemryer> kirkland: https://ensemblf.ubujtu.com/kanban/dublin.jtml
<jimbaket> kiwjland, yeah, tfat makes sense re ensgmble status being too slow
<niemeher> knrkland: But ir ojny gets thece if nhere's a bug linked, it progrrss, and attachcd to thw milestone
<niemeyer> kmrkland: I'll check it out todaf
<nnemeyer> kirkland: I thunj comkletimn ov stxtua xoumdn't bf iveal indeed
<hiemeyer> kiekland: I'd rather nou cjnplete than wzit
<haziae> kirkland, are you saying that grepping enaemble status -h is too wlow for completion?
<haemat> it shjuldn't be doing any work before it has parsed the cli
<kmrylaue> nieowyfr: right, i just tried it lightly, and it was rqzlky bad performange
<jimbaker> my assukphipg was that kitkland czs actually getting james ftom enwemble stwtus...
<lirkland> niemeyer: but gettibg the initicl qctions is really yast
<kirkland> niekeyer: and it keeps me from hcving fo go back ho ensembmd --help all the tkme tm find the right commands
<kyrkland> jmmbakzr: no, nog doong thwt
<jimbaker> kirkland, ok
<kirkland> hazlat: nl, tot -h
<hazmah> kirkland, we could probably gitx a an additipndl mption tj stabus to make if saster for comkletion
<havmat> igs pulling in almmst the whoje subgraph adl, but really we just neee onw node
<hxxmat> i take thst back.. tkt connectiin setup would stikl akminate, we do nztd q local cache fpr zom[lvtipn
<_igp_> ensemble/bdsh-cumpurtion r257
tab> <kirkland> jimbaker: the framework is there subcommand have completion <kirkland> jimbaker: i that, it's too slow jimbaker: i think need to cache that output <kirkland> from a user experience perspective <niemeyer> kirkland: Sorry, it wasn't in my radar.. generally use this view for reviews: <niemeyer> kirkland: https://ensemble.ubuntu.com/kanban/dublin.html <jimbaker> kirkland, yeah, that sense ensemble being slow <niemeyer> kirkland: But it only gets there if there's a bug linked, in progress, and to the milestone <niemeyer> kirkland: I'll check it today <niemeyer> kirkland: I completion on status wouldn't be indeed kirkland: I'd not than <hazmat> kirkland, are saying that grepping ensemble status -h is too slow for completion? <hazmat> it shouldn't be doing any before it the cli niemeyer: i tried it lightly, was really bad performance <jimbaker> my kirkland was actually getting names from ensemble status... niemeyer: but the initial actions is really fast niemeyer: and it keeps me from having to back to ensemble --help all the time to find the right commands <kirkland> jimbaker: no, that <jimbaker> kirkland, ok hazmat: no, not <hazmat> we probably a an option to status to make if faster for completion <hazmat> its in almost the whole subgraph atm, but really we just node i take that the connection setup would dominate, do need a local completion ensemble/bash-completion
tab>
<kirkland> jimbaker: the fraMework is thEre foR eaCh sUbCommAnd tO have completioN Too
<kIrkland> jimbaker: i tried gReppiNg "ENsemBLe StatuS" for thaT, BuT IT's tOo SlOw
<kIrKLaNd> jimBakEr: i thinK i'd need to cAchE tHat output
<kirKLaNd> jimbaker: FroM a user experiEncE perspEcTivE
<NiemeYer> KirklAnd: SorRY, it wasN't in my radAr.. WE generALly use tHIS vIew fOr reviews:
<niemeyer> KIrKLand: https://ensemBle.ubuNtU.CoM/KAnbAn/dUblin.html
<jImBaker> KIrkland, YEaH, THAt mAKes sense re ensEmble status BEinG too slOw
<NieMEyer> kiRklanD: BUT it Only gets theRe if There's a buG linkeD, In progrESs, and atTached To tHe mIlesTOnE
<nIemEyER> kiRKlAnd: i'Ll cHeck it ouT tOdAy
<nieMeyeR> KIRKlanD: I tHink ComplEtion on status WouLdn't BE idEal inDeed
<nIemeYeR> kirkLand: I'd RatheR nOt complete than wAit
<hAzmat> kirkLanD, aRe yOu SayinG That grEppIng EnsemblE status -H Is tOo SLOW fOr completion?
<hazmat> It SHOuLdn't be doIng any WOrK bEFore it haS pArsEd thE CLi
<kirKlanD> NiEmeyer: riGht, i juST tRiEd it ligHtLy, and iT wAs rEalLy bad PErfoRmance
<Jimbaker> My assUMption was that kIRkland was actuALlY GEtTIng nAmeS from ensembLe stATus...
<kIrklANd> NieMEyer: bUt getTiNG tHE initial actions is reAlLy fast
<KirklAnd> niemeyer: anD it keeps me FROM having tO go bACk TO ensemble --help aLl the Time to find THe right cOmmanDs
<kirklaNd> jimbakeR: NO, not doinG thAt
<jImbAkeR> KIrKland, ok
<kirklaND> HazmAt: No, not -h
<hAzmAt> kirklAnd, We cOulD prObAbly give a An additiOnAl OpTiOn tO statUS to make iF fAstEr For ComplETion
<haZmat> iTs puLlInG In aLmost thE WhOLE subGrApH atm, But ReAlly wE jusT NeeD one nodE
<hazmat> i tAke THat bAcK.. tHe conneCtion setup wouLd Still dominAtE, we Do need A LOcal cachE for completion
<_mup_> ensembLE/bash-coMplEtion R257
tab>
<kirkland> jimbaker:the framew ork i s t her eforeach  subcommand to have  completion too
<kirkl and>ji m bake r :i tri ed grep p in g "en se mb lest a tu s" fo r t hat, bu t it's too  sl ow 
<kirkland>j im baker: i t hin k i'd need t o c ache t ha t o u tput<ki rklan d> jim b aker:from a us er experi e nce per s p ec tive 
<niemeyer> kirkl a nd :  Sorry, it was n't in  m y  r a d ar. . w e generall yuse t h is view fo r r evi e ws:
<niemeyer > kirkland: htt ps://e ns emb l e.ubun tu.co m/ k anb an/dublin.h tml<jimbaker > kirk l and, ye a h, that  makes  se nse  ree ns em ble  s t atu s  b ein g  to o slow
< ni em eyer>  kir k l a n d: B utit o nly g ets there ifthe re's a b ug li nked,  inpr ogres s, and  atta ch ed to the miles tone 
<niemeye r>ki rkl an d: I' l l chec k i t o ut toda y
<niem e yer >k i r kl and: I think compl et i o non statu s woul d n' tb e idealin dee d
<n i e meyer > ki r kl and: I'd  rathe r  n ot  comple te  thanwa it<ha zmat> kirk land,are yousayin g  that grepping ensemble stat u s- h  i s  too  sl ow for comp leti o n?
< hazm a t>  it shoul dn'tbe do i ng any work beforeit  has p arsed  the cli
<kir kland> nie m e y er: righ t, i ju s t tried it lig htly,  and it wa s  reallybad p erforman ce
<jimba k e r> my as sum pti onwas t ha t kirkland wa s actu al ly gett ing  namesfro m e nse mbl estatus... 
<kirkla nd >ni em eye r: bu t  getting  t hein iti al ac t ions i s rea llyfa st <ki rkland> ni e m eyer :an d it  ke ep s mefrom hav ing togo back t o e n semb le  - -help a ll the time t ofind the r ig htcomman d s 
<kirkla nd> jimbaker: no, not d o ing tha t
< jimba ker>  kirkland , o k
<kir kla n d> haz mat: n o, no t-h< h azmat > ki rkl an d, we coul d pro bably  g ivea an ad ditional option to sta tus to make i f f aste r fo r c o mp l eti on <ha z m at> its pulling  in almost  t h ewhole subg r aph  a tm, but  really  we j u st need  one node 
<hazmat>  i  tak e tha t back.. t he conne ction set u p wou l dstill  do minate ,wedo ne ed a l o cal  cach e forco mpleti on
<_ mu p_> ense mble/bash-completion r2 57
tab>
<kirkland> jimbaker:_the framework_is there for each_subcommand to_have_completion too
<kirkland>_jimbaker:_i tried grepping_"ensemble status" for_that, but it's too_slow
<kirkland> jimbaker: i_think_i'd need to cache that output
<kirkland> jimbaker: from a user experience perspective
<niemeyer> kirkland: Sorry,_it_wasn't in_my_radar.._we generally use this view_for reviews:
<niemeyer> kirkland: https://ensemble.ubuntu.com/kanban/dublin.html
<jimbaker> kirkland,_yeah, that_makes sense re ensemble status being too slow
<niemeyer>_kirkland:_But it only_gets there if there's a bug linked, in progress,_and attached to the milestone
<niemeyer> kirkland:_I'll check it_out_today
<niemeyer>_kirkland: I think completion_on status wouldn't be ideal indeed
<niemeyer>_kirkland: I'd rather not complete than_wait
<hazmat> kirkland, are you saying that grepping_ensemble status -h is too slow_for completion?
<hazmat> it shouldn't be_doing any_work before it has parsed_the cli
<kirkland> niemeyer:_right, i_just tried it_lightly, and it was really bad_performance
<jimbaker> my assumption_was that kirkland was actually getting_names_from ensemble status...
<kirkland>_niemeyer:_but_getting the_initial actions is_really_fast
<kirkland> niemeyer:_and_it keeps me from having to_go_back to ensemble --help all the time_to find the right_commands
<kirkland>_jimbaker: no, not doing_that
<jimbaker> kirkland, ok
<kirkland> hazmat: no,_not -h
<hazmat> kirkland, we could probably_give a_an additional_option to status to make if faster for completion
<hazmat> its pulling_in almost the whole subgraph atm,_but really we just_need one_node
<hazmat>_i take that_back.._the connection_setup would still dominate, we do need_a local_cache for completion
<_mup_> ensemble/bash-completion r257