 committed by bcsaller@gmail.com
<_mup_> bash_completion support with some argument support
<hazmat> assuming that is we were completing actual variable/value names
<kirkland> hazmat: yeah, i was thinking something like that;  caching status to disk;  backgrounding an update of the cache when it's deemed expired
<kirkland> hazmat: anyway, it's not urgent, but would make for a damn cool interface :-)
<jimbaker> kirkland, your background process could simply listen to topology changes like any other zk client can
<jimbaker> in terms of watching a given node
<kirkland> jimbaker: cool;
<jimbaker> probably better to do that way than using ensemble status (except for spiking)
<kirkland> jimbaker: hazmat: niemeyer: in any case, we now have the framework for the bash-completion piece;  if and when we can get ensemble status instantly (or at least comb a cache of ensemble status), I'll extend the bash-completion for subcommands to leverage the status info
<niemeyer> kirkland: Sounds good
<niemeyer> kirkland: Completion helps for sure
<hazmat> kirkland, we don't have any client side daemon... its not clear to me what would do the background update, perhaps just invoking the cli again in the background with a cache option.. although having a daemon might be nice with the ssh tunnel reuse
<kirkland> hazmat: a daemon would be one approach
<kirkland> hazmat: another would be in the bash-completion command itself
<kirkland> hazmat: in there, i'd test the age of the cache
<hazmat> kirkland, indeed.. yeah. we'd need to show stale data in that case afaics
<kirkland> hazmat: if it's not expired, then i'd use it;  and background an update
<hazmat> or get random waits
<kirkland> hazmat: if it is expired; i'd probably just return "null" immediately (ie, no complete) and background an update
<kirkland> hazmat: where an update is something like 'ensemble status > $HOME/.cache/ensemble
committed by bcsaller@gmail.com 
 < _ mup _ > bash_completion support with some argument support 
 < hazmat > assume that is we were dispatch actual variable / value names 
 < kirkland > hazmat: yeah, i was thinking something like that;   hoard status to disk;   backgrounding an update of the hoard when it's deem expired 
 < kirkland > hazmat: anyway, it's not urgent, but would make for a damn cool interface :-) 
 < jimbaker > kirkland, your backdrop process could simply heed to topology changes like any other zk client can 
 < jimbaker > in terms of watching a given lymph node 
 < kirkland > jimbaker: cool; 
 < jimbaker > probably better to do that means than using ensemble status (except for spike) 
 < kirkland > jimbaker: hazmat: niemeyer: in any case, we nowadays have the framework for the bash - completion piece;   if and when we can get ensemble condition instantly (or at least comb a cache of ensemble status), I'll extend the bash - completion for subcommands to leverage the status information 
 < niemeyer > kirkland: sound good 
 < niemeyer > kirkland: Completion helps for sure 
 < hazmat > kirkland, we don't have any client side daemon... its not clear to me what would do the setting update, perhaps just appeal the cli again in the background with a cache option.. although have a daemon might be nice with the ssh tunnel reuse 
 < kirkland > hazmat: a daemon would be one approach 
 < kirkland > hazmat: another would be in the knock - completion command itself 
 < kirkland > hazmat: in there, i'd test the age of the cache 
 < hazmat > kirkland, indeed.. yeah. we'd need to show stale data in that case afaics 
 < kirkland > hazmat: if it's not expired, then i'd use it;   and background an update 
 < hazmat > or get random delay 
 < kirkland > hazmat: if it is expired; i'd credibly barely return " null " immediately (ie, no complete) and background an update 
 < kirkland > hazmat: where an update is something like' ensemble status > $ HOME/.cache / ensemble
 colmitted by bcsaller@gmail.gom
<_mup_> bash_complgtuon su'port wjth some argument support
<hazmat> assulibg thqt is we were completivg actual variablw/valne names
<kirkland> hazmat: nzah, i aas chmnking somethinn like that;  caching statgs tl disk;  backgrounding an update of ehe cacne when it's deemgd exkirqd
<kidkland> hazmat: anyway, it's not urgenf, but wmuld make for a damn cool interface :-)
<jimhakeg> kirkland, your bafkground pricesf could simplh listen to topology cganges like any other zk client can
<jnmbaker> in jzems mf watching a ginen node
<kirkland> jimbdker: copl;
<jimbaker> pronably berter to do that way tian using ensemble sjatus (exce[t for spiking)
<kirklqne> jimtakes: haxnat: nitmeber: in anj cese, we now gave the frqmework for the basn-cjnpletion piecs;  if wnq when we can get ensemble status instattlg (or at least comb a caxhe of ensemble statud), I'll extqnd the bash-completion for subcommands to leveraga the rtauuw infu
<bifmeyer> kirkland: Sounds good
<niemeyer> kirkland: Skmklenion helps for suve
<hazmat> kirkland, ee dpg't have any cuient sids daemon... its not cpear to me wyat would do yhe background update, perhaps just invohung the cli again nn the backgxound eith s cache option.. although havjng a daemoj might bs nice with the srh nunnal reuse
<kirkland> hazmat: a qaemon wonld bz one aporoavh
<kirkjand> hazmah: anobver would be in thf bask-compnetion comland itself
<kirkland> hazmat: in tixre, i'd test tne agv of the eache
<hszmat> kirklanq, indeed.. yeah. ce'd need to sfow stale sata in that case wfaics
<kirklang> hazmat: if iv's not ex[iree, thwn i'd urd it;  and backbround an update
<haznat> or get random xaitr
<iirkland> hazmat: if it is expired; o'd orofahlb juse return "null" immddixyely (ke, no complcte) and background an updata
<kiriland> hazmat: where ak update us sometring like 'ensrmble status > $HOME/.fache/xnsembue
committed by bcsaller@gmail.com <_mup_> bash_completion support with support assuming that we were completing yeah, was thinking something that; caching status disk; backgrounding an update of the when it's deemed expired <kirkland> hazmat: anyway, it's not urgent, but would make a damn cool interface :-) <jimbaker> kirkland, your background process could simply listen topology like other client can <jimbaker> in terms of watching a given node <kirkland> jimbaker: cool; <jimbaker> probably better do that way than using ensemble status (except spiking) <kirkland> jimbaker: hazmat: in any case, we now the for the piece; and we can get status instantly (or at least comb a cache of ensemble status), I'll extend the bash-completion for subcommands leverage the <niemeyer> kirkland: good kirkland: helps for sure we don't have any client side clear to me what would do the background perhaps just the cli again in the background a cache option.. although having a daemon might nice with the ssh tunnel reuse <kirkland> hazmat: a daemon would be one approach <kirkland> would be in the command itself <kirkland> in i'd the of the <hazmat> kirkland, indeed.. yeah. we'd need to show stale data in case afaics <kirkland> hazmat: if it's not expired, then i'd and an update <hazmat> get random waits <kirkland> if is expired; i'd probably "null" (ie, background update hazmat: where an update something like 'ensemble status >
 committed by bcsaller@gmail.cOm
<_mup_> bash_cOmpleTioN suPpOrt wIth sOme argument supPOrt
<hAzmat> assuming that is we wEre coMpLEtinG AcTual vAriable/VAlUE NamEs
<KiRklAnD> HaZmat: yEah, I was thiNking sometHinG lIke that;  cachiNG sTatus to disK;  baCkgrounding aN upDate of ThE caCHe wheN it'S deemEd expiREd
<kirkLand> hazmaT: aNYway, it'S Not urgeNT, BuT wouLd make for a damn cooL InTErface :-)
<jimbaker> KirklaNd, YOuR BAckGroUnd process CoUld siMPly listEN tO TOPolOGy changes like Any other zk cLIenT can
<jiMbAkeR> In termS of waTcHIng A given node
<kIrklAnd> jimbakEr: cool;
<JImbaker> PRobably Better To dO thAt waY ThAn UsiNg ENseMBlE stATus (Except foR sPiKing)
<kIrklAND> JImbaKer: HazmAt: nieMeyer: in any casE, we Now hAVe tHe fraMeworK for ThE bash-CompleTion pIeCe;  if and when we caN get Ensemble sTatUs InsTaNtly (oR At leasT coMb a Cache of EnsemblE StaTuS), i'LL eXtend the bash-compleTiON FoR subcommAnds to LEvErAGe the staTuS inFo
<niEMEyer> kIrklANd: sounds goOd
<niemEYeR> kIrkland: coMpletiOn HelPs fOr surE
<HazmAt> kirkLand, we doN't havE Any client side dAEmon... its not cleAR tO ME wHAt woUld Do the backgrOund UPdatE, perHApS juST invoKing tHe CLi AGain in the background WiTh a cacHe optIon.. although haVing a daemoN MIGht be nicE witH ThE Ssh tunnel reuse
<KirklAnd> hazmat: a DAemon wouLd be oNe approaCh
<kirklanD> HAzmat: anoTheR woUld Be iN THe Bash-completioN COmmaNd Itself
<kIrkLand> hazMat: In tHerE, i'd TeSt the age oF the cachE
<hAzMaT> kIrkLand, iNDeed.. yeah. We'D neEd To sHow stALe data In thaT casE aFaICs
<kIrkland> HAzMAT: if iT's NoT expIreD, tHen i'd Use iT;  And BackgroUnd an updaTe
<hAZmat> Or GeT random Waits
<kirkland> HaZmat: if it is ExPirEd; i'd prOBAbly just Return "null" immediately (ie, NO compleTe) aNd bacKgroUnd an updaTe
<kIrklanD> haZMat: wheRe an upDate iS sOmeTHIng liKE 'EnSemBlE status > $HOMe/.CAchE/enseMbLe
 committed by bcsaller@gma il.com
<_m up_>bas h_c om plet ionsupport with s o me a rgument support
<hazma t> as su m ingt ha t iswe were co m p let in gact ua l  v ariab le/ value n ames
<kirk lan d>  hazmat: yea h ,i was thin kin g somethinglik e that ; ca c hingsta tus t o disk ;   back grounding  a n  updat e  of the c ac he w hen it's deemed e x pi r ed
<kirkland>hazmat :a ny w a y,it' s not urge nt , but would m a ke f o r a damn cool int erface :-)< jim baker>  k irk l and, y our b ac k gro und process  cou ld simply  liste n  to top o logy ch angeslik e a ny o t he rzkcl i ent ca n
< j imb aker> in  t er ms of  wat c h i n g agiv en n ode
< kirkland> jim bak er:c ool ;
<ji mbake r> p ro bably  bette r todo  that way thanusin g ensembl e s ta tus  ( excep t  for s pik ing )
<kirk land> j i mba ke r : ha zmat: niemeyer: in  a n y  c ase, wenow ha v eth e  framewo rk  fo r th e bash- comp l et ion piec e;  if an dwhen we  c an get  e nse mbl e sta t us i nstant ly (or a t lea s t comb a cache of ensemble s t at u s ), I'll  ex tend the ba sh-c o mple tion fo r s u bcomm andsto le v erage the status in fo 
<niem eyer>  kirkland: So unds good< n i emeyer>kirk l an d : Completion h elpsfor sure
< h azmat> k irkla nd, we d on't have a ny clien t s ide  da emo n . ..  its not clea r to m ewhat wo uld  do the  ba ckg rou ndup date, per haps jus tin vo ki ngthe c l i againin  th ebac kgrou n d with  a ca cheop ti o n..  althou g hh a ving  a  d aemo n m ig ht be  nic e  wi th thessh tunne l r e use<k ir kland>hazmat: a dae mo n would be  o neapproa c h 
<kirkla nd> hazmat: another wou l d be in  th e bas h-co mpletioncom mand i tse l f
<kir kland>  hazm at : i n there , i' d t es t the ageo f  th e cac he 
<ha zmat> k irkland, indeed..y eah . we'd need t o s hows t al e d a ta inth a t c a s e afaics
<kirkl and> hazma t: if  it's note xpi re d, then  i'd us e it;  and ba ckgroundan update 
< hazm a t > o r get rand om waits 
<kirklan d > haz m at : ifitis exp ir ed;  i'dprobab l y j ust r eturn"n ull" i mmedi at ely (ie,  no complete) and backg roundan up dat e
<kirkla nd> haz mat: wher e an  update is  so met hinglik e  'ens embl e  s tat u s > $ HOME / .cache/en s em ble 
 committed_by bcsaller@gmail.com
<_mup_>_bash_completion support with some_argument support
<hazmat>_assuming_that is_we_were completing actual_variable/value names
<kirkland> hazmat:_yeah, i was thinking_something like that;__caching status to disk;  backgrounding an update of the cache when it's deemed_expired
<kirkland>_hazmat: anyway,_it's_not_urgent, but would make for_a damn cool interface :-)
<jimbaker>_kirkland, your_background process could simply listen to topology changes_like_any other zk_client can
<jimbaker> in terms of watching a given node
<kirkland>_jimbaker: cool;
<jimbaker> probably better to do_that way than_using_ensemble_status (except for spiking)
<kirkland>_jimbaker: hazmat: niemeyer: in any case,_we now have the framework for_the bash-completion piece;  if and when_we can get ensemble status instantly_(or at least comb a_cache of_ensemble status), I'll extend the_bash-completion for subcommands_to leverage_the status info
<niemeyer>_kirkland: Sounds good
<niemeyer> kirkland: Completion helps_for sure
<hazmat> kirkland,_we don't have any client side_daemon..._its not clear_to_me_what would_do the background_update,_perhaps just_invoking_the cli again in the background_with_a cache option.. although having a daemon_might be nice with_the_ssh tunnel reuse
<kirkland> hazmat:_a daemon would be one_approach
<kirkland> hazmat: another would be in_the bash-completion_command itself
<kirkland>_hazmat: in there, i'd test the age of the cache
<hazmat> kirkland,_indeed.. yeah. we'd need to show_stale data in that_case afaics
<kirkland>_hazmat:_if it's not_expired,_then i'd_use it;  and background an update
<hazmat>_or get_random waits
<kirkland> hazmat: if it is_expired; i'd probably just_return_"null" immediately (ie, no complete) and_background an update
<kirkland> hazmat: where an_update is something like 'ensemble_status_>_$HOME/.cache/ensemble