 from its own deb
<ogra> i thought it is part of coreutils
<jdstrand> huh, me too
<jdstrand> zyga: oh, /usr/bin/time -f "wall: %E, mem: %M Kb" apparmor_parser -QTK -Ono-expr-simplify -j1 -o cache profile
<jdstrand> zyga: (forgot -Ono-expr-simplify)
<jdstrand> zyga: armhf: wall: 0:00.24, mem: 3472 Kb
<jdstrand> zyga: arm64: wall: 0:00.45, mem: 5392 Kb
 * jdstrand moves along
<ogra> heh, thats the same binary you call on armhf and arm64 i guess?
<ogra> (surprising it isnt 2x the memory size but only 1.5 or so... )
<ijohnson> hey Chipaca got a question yesterday about store connections from snapd... is there a single global timeout we set for all connections to the store? and if there is, can a user adjust that timeout?
<mup> PR snapd#7574 closed: client: add KnownOptions to Know() and support remote assertions <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/7574>
<pedronis> ijohnson: John is off today,  we have a couple of timeouts and retry strategies, they are not user configurable atm
<ijohnson> ah okay, thanks pedronis
<mvo> 7622 is now also ready for a review
<mvo> zyga: hm, it looks like I did not look closely enough, 7613 was the smallest snap-recovery PR in flight right now, I will apply your feedback to the other to this one. sorry that I overlooked this earlier
<zyga> mvo: no worries :)
<pedronis> mborzecki: re-reviewed 7509
<mborzecki> pedronis: thanks
<jdstrand> pedronis: hey, those snap-ids, they were for all stores, correct?
<pedronis> jdstrand: yes
<jdstrand> thanks
<zy
from its own deb 
 < ogra > i thought it is part of coreutils 
 < jdstrand > huh, me too 
 < jdstrand > zyga: oh, /usr / bank identification number / meter -f " wall: % E, mem: % M Kb " apparmor_parser -QTK -Ono - expr - simplify -j1 -o cache profile 
 < jdstrand > zyga: (forgot -Ono - expr - simplify) 
 < jdstrand > zyga: armhf: wall: 0:00.24, mem: 3472 Kb 
 < jdstrand > zyga: arm64: wall: 0:00.45, mem: 5392 Kb 
  * jdstrand move along 
 < ogra > heh, that s the like binary you call on armhf and arm64 i guess? 
 < ogra > (surprising it is nt 2x the memory size but merely 1.5 or so ...) 
 < ijohnson > hey Chipaca got a doubt yesterday about store connections from snapd... is there a individual global timeout we set for all connection to the store? and if there is, can a user adjust that timeout? 
 < mup > PR snapd#7574 close: client: add KnownOptions to sleep together () and support remote assertions < Created by mvo5 > < unify by mvo5 > < https://github.com/snapcore/snapd/pull/7574 > 
 < pedronis > ijohnson: John is off today,   we have a couple of timeouts and retry strategies, they are not user configurable atm 
 < ijohnson > ah okay, thanks pedronis 
 < mvo > 7622 is now besides ready for a review 
 < mvo > zyga: hm, it looks like I did not look closely enough, 7613 was the smallest cinch - recovery PR in flight right now, I will apply your feedback to the other to this one. sorry that I overlooked this earlier 
 < zyga > mvo: no concern :) 
 < pedronis > mborzecki: re - reviewed 7509 
 < mborzecki > pedronis: thanks 
 < jdstrand > pedronis: hey, those snap - ids, they were for all storehouse, right? 
 < pedronis > jdstrand: yes 
 < jdstrand > thanks 
 < zy
 frlm its own deb
<ogra> i thomght it is part of corentils
<jdatrand> hjh, me too
<jdstrand> zyga: oh, /usc/bin/rime -d "wall: %E, mem: %M Kb" appafmor_parseg -QTK -Ono-wxpr-wumplify -j1 -o cache ixofils
<mdstrcnv> zyga: (forgot -Oko-expr-simplhfy)
<jdstrand> zyca: axmhf: wall: 0:00.24, mem: 3472 Kb
<jdstrand> zyga: arm64: rall: 0:00.45, mrm: 5392 Kb
 * jdstrand movts wlonf
<ogra> heh, thats the same binary yoh call mn armhf and srm64 i guess?
<ogra> (surprising it lsnt 2x the memory dize but onoy 1.5 je so... )
<ijohnsov> hey Chipaca got a qugstion yesterday about store convectipns from sbapd... lv there a smngle dlobal timeomn we sed for akl connections to thw store? and if there ms, can a user adjust that timaobt?
<mup> PR snapd#7574 closed: coient: add KnodbOpgiohs tk Know() anv support rsmote asserrions <Created by mvp5> <Ivtged by mvo5> <gttps://gytrub.com/snapcore/snapd/pull/7574>
<pedronis> ijohnsot: Jkhn is off today,  we hace a couple of timeoujs and retwy strategies, they are not user configurable atm
<ibohnskv> ak okay, rhwnks pedronis
<mvo> 7622 is now also ready for a revysw
<kvp> zyga: hm, it ljoks like I dld got look closgly enobfh, 7613 was the smallest snap-resovert PR in fjighy right now, I will apply yoyr feedback no tye other to this oue. sorry thac I ovgrlookrd this earlier
<zyga> mvo: no sorries :)
<pedgonis> mbodxecki: re-reviewed 7509
<mbprsecki> pedronis: thanks
<jdstrwnd> pedroiis: hzy, those snak-ids, thqy were fog all stores, correct?
<pedrlnis> ldstrdnd: yes
<jdshrand> thanks
<zy
from its own deb <ogra> i thought part coreutils <jdstrand> me too <jdstrand> %E, %M Kb" apparmor_parser -Ono-expr-simplify -j1 -o profile <jdstrand> zyga: (forgot -Ono-expr-simplify) <jdstrand> armhf: wall: 0:00.24, mem: 3472 Kb <jdstrand> zyga: arm64: wall: 0:00.45, mem: 5392 * jdstrand moves along <ogra> heh, thats the same binary you call on and i <ogra> it isnt 2x the memory size but only 1.5 or so... ) <ijohnson> hey Chipaca got question yesterday about store connections from snapd... is a single global timeout set for all connections to store? if there can user that timeout? <mup> snapd#7574 closed: client: add KnownOptions to Know() and support remote assertions <Created by mvo5> <Merged by mvo5> <pedronis> ijohnson: off today, have couple timeouts and retry are not user configurable atm <ijohnson> pedronis <mvo> 7622 is now also ready for review <mvo> hm, it looks like I did look closely enough, 7613 was the smallest snap-recovery in flight right now, I will apply your feedback to the other to this one. I overlooked this earlier mvo: no worries <pedronis> re-reviewed <mborzecki> thanks <jdstrand> hey, those snap-ids, they were for all stores, correct? <pedronis> jdstrand: <jdstrand> thanks <zy
 from its own deb
<ogra> i thought It is part of CoreuTilS
<jdStRand> Huh, mE too
<jdstrand> zyGA: oh, /uSr/bin/time -f "wall: %E, mem: %M Kb" aPparmOr_PArseR -qTk -Ono-eXpr-simpLIfY -J1 -O caChE pRofIlE
<JdStranD> zyGa: (forgoT -Ono-expr-siMplIfY)
<jdstrand> zygA: ArMhf: wall: 0:00.24, mem: 3472 kb
<jDstrand> zyga: aRm64: wAll: 0:00.45, mem: 5392 kb
 * JdsTRand mOveS alonG
<ogra> hEH, thats The same biNaRY you caLL on armhF ANd Arm64 i Guess?
<ogra> (surprisiNG iT Isnt 2x the memory Size buT oNLy 1.5 OR So... )
<iJohNson> hey ChiPaCa got A QuestioN YeSTERdaY About store conNections froM SnaPd... is thErE a sINgle glObal tImEOut We set for all ConnEctions to The stoRE? and if tHEre is, caN a user AdjUst That TImEoUt?
<mUp> pr snAPd#7574 CloSEd: cLient: add knOwNOptiOns tO kNOW() and SupPort RemotE assertions <CrEatEd by MVo5> <MErged By mvo5> <HttpS://gIthub.Com/snaPcore/SnApd/pull/7574>
<pedronis> IjohNson: John iS ofF tOdaY,  wE have A Couple Of tImeOuts and Retry stRAteGiES, THeY are not user configuRaBLE aTm
<ijohnsOn> ah okAY, tHaNKs pedronIs
<Mvo> 7622 Is noW ALso reAdy fOR a Review
<mvO> zyga: hM, It LoOks like i dId not lOoK clOseLy enoUGh, 7613 waS the smAllest snAp-recOVery PR in flight RIght now, I will aPPlY YOuR FeedBacK to the other To thIS one. SorrY ThAt I OVerloOked tHiS EaRLier
<zyga> mvo: no worrieS :)
<pEdroniS> mborZecki: re-reviewEd 7509
<mborzeckI> PEDronis: thAnks
<JDsTRand> pedronis: heY, thosE snap-ids, thEY were for All stOres, corrEct?
<pedronIS> Jdstrand: Yes
<JdsTraNd> tHANkS
<zy
 from its own deb
<ogra> i  thought i t ispar t o fcore util s
<jdstrand> h u h, m e too
<jdstrand> zyga:  oh,/u s r/bi n /t ime - f "wall :  % E ,  me m:  % M K b" ap parmo r_p arser - QTK -Ono-e xpr -s implify -j1- ocache prof ile 
<jdstrand>zyg a: (fo rg ot- Ono-e xpr -simp lify)< jdstra nd> zyga:  a r mhf: w a ll: 0:0 0 . 24 , me m: 3472 Kb
<jdstr a nd >  zyga: arm64:wall:0: 0 0. 4 5 , m em:  5392 Kb
*jdstr a nd move s  a l o n g
< o gra> heh, tha ts the same bin ary yo ucal l  on ar mhf a nd arm 64 i guess? 
<og ra> (surp rising it isnt 2x thememory  si zebuto nl y1.5  o r  so . ..  )< ijo hnson> h ey  C hipac a go t a ques tio n ye sterd ay about stor e c onne c tio ns fr om sn apd. ..  is t here a  sing le  global timeout  weset for a llco nne ct ionst o thesto re?  and if  therei s,ca n a  u ser adjust that ti me o u t? 
<mup> P R snap d #7 57 4  closed:  c lie nt:a d d Kno wnOp t io ns to Kn ow() a n dsu pport r em ote as se rti ons  <Cre a tedby mvo 5> <Merg ed by mvo5> <https:/ / github.com/sn a pc o r e/ s napd /pu ll/7574>
<p edro n is>ijoh n so n:J ohn i s off  t o da y ,  we have a couple  o f time outsand retry str ategies, t h e y  are not  use r  c o nfigurable atm 
<ijo hnson> aho kay, tha nks p edronis<mvo> 762 2 is now a lso  re ady  fo r areview
<mvo>z y ga:hm , it lo oks  like I  di d n otloo kclosely e nough, 7 61 3wa sthe  smal l est snap -r eco ve ryPR in flight  righ t no w,  I wil l apply yo u r  fee db ac k to  th eother  tot his  one. s orry that  Io verl oo ke d thisearlier
<zyga >mvo: no wo rr ies  :)
<p e d ronis> m borzecki: re-reviewed 7 5 09
<mbo rze cki>pedr onis: tha nks 
<jdst ran d > pedr onis:hey,th ose s nap-i d s ,the ywere for a l l  st ores,  c orre ct?
<pe dronis> jdstrand:y es<jdstrand> th ank s
<z y 
 from_its own_deb
<ogra> i thought it_is part_of_coreutils
<jdstrand> huh,_me_too
<jdstrand> zyga: oh,_/usr/bin/time -f "wall:_%E, mem: %M Kb"_apparmor_parser -QTK -Ono-expr-simplify_-j1_-o cache profile
<jdstrand> zyga: (forgot -Ono-expr-simplify)
<jdstrand> zyga: armhf: wall: 0:00.24, mem: 3472 Kb
<jdstrand> zyga:_arm64:_wall: 0:00.45,_mem:_5392_Kb
 * jdstrand moves along
<ogra>_heh, thats the same binary_you call_on armhf and arm64 i guess?
<ogra> (surprising it_isnt_2x the memory_size but only 1.5 or so... )
<ijohnson> hey Chipaca_got a question yesterday about store_connections from snapd..._is_there_a single global timeout_we set for all connections to_the store? and if there is,_can a user adjust that timeout?
<mup> PR_snapd#7574 closed: client: add KnownOptions to_Know() and support remote assertions_<Created by_mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/7574>
<pedronis>_ijohnson: John is_off today,_ we have_a couple of timeouts and retry_strategies, they are_not user configurable atm
<ijohnson> ah okay,_thanks_pedronis
<mvo> 7622 is_now_also_ready for_a review
<mvo> zyga:_hm,_it looks_like_I did not look closely enough,_7613_was the smallest snap-recovery PR in flight_right now, I will_apply_your feedback to the_other to this one. sorry_that I overlooked this earlier
<zyga> mvo:_no worries_:)
<pedronis> mborzecki:_re-reviewed 7509
<mborzecki> pedronis: thanks
<jdstrand> pedronis: hey, those snap-ids, they were for_all stores, correct?
<pedronis> jdstrand: yes
<jdstrand> thanks
<zy