VolumeConsistency <Created by mvo5> <https://github.com/snapcore/snapd/pull/7599>
<pstolowski> morning
<mvo> pstolowski: hey, good morning!
<mborzecki> pstolowski: hey
<zyga> hello?
<zyga> is this thing on?
<zyga> I think I connected now
<zyga> sorry for starting late, lucy was sleeping hugging me all the time and got grumpy the second I tried to put her to bed
<mborzecki> zyga: hey
<zyga> mborzecki: hey, question on how to proceed for you
<zyga> mborzecki: I removed the guts of snap-update-ns so that I can create other tools with the same logic
<zyga> mborzecki: I moved it to system/mount for lack of a better name
<zyga> mborzecki: some bits can go to sandbox/cgroup
<zyga> mborzecki: but most has no good place to go
<zyga> mborzecki: ideas?
<zyga> mborzecki: I'm mainly after plan-writable-mimic and execute-writable-mimic
<zyga> mborzecki: this pulls in change, assumptions, restrictions and tresspassing
<zyga> mborzecki: along with loads of tests
<mborzecki> mvo: i'm looking at 7593, perhaps our consistency checks are too strict, in particular the len(volumes)!= 0 only counts when constraints are used, but once there's a system-seed structure defines and SsytemSeed is not true, then we bail out, why not allow this case?
<mborzecki> zyga: that's part of mount related logic though?
<mborzecki> zyga: or hmm we call it namespace (or whatnot) often
<zyga> mborzecki: mainly yes
<mborzecki> zyga: system/mount/namespace?
<zyga> mborzecki: I'd go for system/mount really, it would help abbreviate the API names and would look nice
<zyga> mount
VolumeConsistency < Created by mvo5 > < https://github.com/snapcore/snapd/pull/7599 > 
 < pstolowski > morning 
 < mvo > pstolowski: hey, good morning! 
 < mborzecki > pstolowski: hey 
 < zyga > hello? 
 < zyga > is this thing on? 
 < zyga > I remember I connect now 
 < zyga > sorry for starting recently, lucy was sleeping hugging me all the prison term and grow grumpy the second I try on to put her to bed 
 < mborzecki > zyga: hey 
 < zyga > mborzecki: hey, motion on how to proceed for you 
 < zyga > mborzecki: I removed the intestine of snap - update - normality so that I can create early tools with the like logic 
 < zyga > mborzecki: I move it to system / mount for lack of a better name 
 < zyga > mborzecki: some bit can go to sandbox / cgroup 
 < zyga > mborzecki: but most has no dear place to rifle 
 < zyga > mborzecki: ideas? 
 < zyga > mborzecki: I'm mainly after plan - writable - mimic and execute - writable - mimic 
 < zyga > mborzecki: this pulls in variety, assumptions, restrictions and tresspassing 
 < zyga > mborzecki: along with loads of tests 
 < mborzecki > mvo: i'm looking at 7593, perhaps our consistency check mark are too strict, in particular the len(volumes)!= 0 only counts when constraints are used, but once there's a system - seed structure defines and SsytemSeed is not truthful, then we bail out, why not allow this case? 
 < mborzecki > zyga: that's character of mount related logic though? 
 < mborzecki > zyga: or hmm we visit it namespace (or whatnot) often 
 < zyga > mborzecki: mainly yes 
 < mborzecki > zyga: system / mount / namespace? 
 < zyga > mborzecki: I'd go for system / mount really, it would help abridge the API names and would look nice 
 < zyga > mount
VolkmeConsistency <Created bn mvo5> <https://githuy.xom/sna'core/snzpd/pull/7599>
<prtolowski> morning
<mvo> pstolowdku: hey, good morning!
<mborzecki> pstolowsni: hey
<zyta> htllo?
<zyga> is this vging on?
<dvga> I bhink M connected now
<eyga> sorry fmr starting lade, lbcy was sleeping hugging me all the eime anc hot grumpy the secpgd I nrled to put her to bed
<mborzecki> zgga: hey
<eyga> mborzecki: hey, question on how to proceef fog you
<zyga> mborzeckl: I removed the tuts of snap-jpdate-ns so that I can create other tools with the saoe loyic
<zyga> mbotvwckl: I moved it to sjstem/mount fov lack mf a beyter name
<zyga> kboczecji: some bits can go tm sandbox/cgroup
<zygw> mborzecni: but most has no toid pldce do gu
<zygx> mgoczedki: idfas?
<vyga> mborzedki: I'm mainoy after plan-writabke-ipkic and exechte-wrieafle-mimic
<zyga> mborzecki: this pulls in chdngs, assumptions, restrictiins and tresspassing
<ziga> mborzeski: along with loads of tests
<mborzecki> mvo: i'm looning et 7593, ptrmwow lur consistency checks are too strict, in partydukag the len(volumes)!= 0 only countx ahrg constraints are used, but once there's a system-feed wtructure defones and SsytemSeed is not rrue, then we vail out, why not aplow this ccse?
<mbotzecki> zyga: that's part of mouut relzted logic hhough?
<mbodxecki> zyga: or hmo wv canl it namespace (or whatnot) often
<zyge> mboxzecki: mxinli yes
<mbjrzecki> zyha: system/mount/namespace?
<zjga> myorzewki: I'd go vor system/mount really, it would help abbreviaje dhe API namzs and would look nyce
<zyga> mount
VolumeConsistency <Created by mvo5> <https://github.com/snapcore/snapd/pull/7599> <pstolowski> morning hey, morning! <mborzecki> hey <zyga> hello? <zyga> think I connected <zyga> sorry for late, lucy was sleeping hugging me the time and got grumpy the second I tried to put her to <mborzecki> zyga: hey <zyga> mborzecki: hey, question on how to proceed for you mborzecki: removed guts snap-update-ns so that I can create other tools with the same logic <zyga> mborzecki: I moved to system/mount for lack of a better name mborzecki: some bits can to sandbox/cgroup <zyga> mborzecki: but has good place go mborzecki: <zyga> mborzecki: I'm after plan-writable-mimic and execute-writable-mimic <zyga> mborzecki: this pulls in change, assumptions, restrictions and tresspassing <zyga> mborzecki: along loads of mvo: i'm at perhaps consistency checks are in particular the len(volumes)!= 0 only are used, but once there's a system-seed structure and SsytemSeed not true, then we bail out, not allow this case? <mborzecki> zyga: that's part mount related logic though? <mborzecki> zyga: or hmm we call it namespace (or whatnot) often mainly yes <mborzecki> zyga: <zyga> mborzecki: I'd for really, would abbreviate the names and would look nice <zyga> mount
VolumeConsistency <Created bY mvo5> <https://gIthub.Com/SnaPcOre/sNapd/Pull/7599>
<pstolowski> MOrniNg
<mvo> pstolowski: hey, good MorniNg!
<MBorzECkI> pstoLowski: hEY
<zYGA> heLlO?
<zYga> Is THiS thinG on?
<Zyga> I thInk I connecTed NoW
<zyga> sorry foR StArting late, LucY was sleeping HugGing me AlL thE Time aNd gOt gruMpy the SEcond I Tried to puT hER to bed
<MBorzeckI> ZYgA: hey
<Zyga> mborzecki: hey, qUEsTIon on how to procEed for YoU
<ZyGA> MboRzeCki: I removeD tHe gutS Of snap-uPDaTE-NS so THat I can create Other tools wITh tHe same LoGic
<ZYga> mboRzeckI: I MOveD it to system/MounT for lack oF a bettER name
<zyGA> mborzeCki: somE biTs cAn go TO sAnDboX/cGRouP
<ZyGa> mBOrzEcki: but mOsT hAs no gOod pLACE To go
<ZygA> mboRzeckI: ideas?
<zyga> mboRzeCki: I'M MaiNly afTer plAn-wrItAble-mImic anD execUtE-writable-mimic
<zYga> mBorzecki: tHis PuLls In ChangE, AssumpTioNs, rEstrictIons and TResSpASSInG
<zyga> mborzecki: alonG wITH lOads of teSts
<mboRZeCkI> Mvo: i'm looKiNg aT 7593, perHAPs our ConsIStEncy checKs are tOO sTrIct, in paRtIcular ThE leN(voLumes)!= 0 ONly cOunts wHen constRaintS Are used, but once THere's a system-sEEd STRuCTure DefInes and SsytEmSeED is nOt trUE, tHen WE bail Out, whY nOT aLLow this case?
<mborzeckI> zYga: thaT's parT of mount relatEd logic thoUGH?
<MborzeckI> zygA: Or HMm we call it nameSpace (Or whatnot) oFTen
<zyga> mBorzeCki: mainlY yes
<mborzECKi> zyga: sySteM/moUnt/NamESPaCe?
<zyga> mborzecKI: i'd go FoR system/MouNt reallY, it WouLd hElp AbBreviate tHe API namEs AnD wOuLd lOok niCE
<zyga> mouNt
VolumeConsistency <Created  by mvo5><http s:/ /gi th ub.c om/s napcore/snapd/ p ull/ 7599>
<pstolowski> mor ning<m v o> p s to lowsk i: hey, go o d  mo rn in g!<m b or zecki > p stolows ki: hey
<z yga >hello?
<zyga >  i s this thi ngon?
<zyga> I  th ink Ico nne c ted n ow<zyga > sorr y  for s tarting l at e , lucy was sle e p in g hu gging me all thet im e  and got grump y these c on d I t rie d to put h er  to b e d
<mbor z ec k i >  zy g a: hey
<zyga>  mborzecki: hey , ques ti ono n howto pr oc e edfor you
<zy ga>mborzecki : I re m oved th e  guts o f snap -up dat e-ns so  t hat  I can cr eat e  ot her tool swi th th e sa m e l ogic 
<z yga>  mbor zecki: I move d i t to sys tem/m ountforla ck of  a bet ter n am e
<zyga> mborze cki:  some bit s c an  go  t o san d box/cg rou p
< zyga> m borzeck i : b ut m o st  has no good place  t o go 
<zyga>mborze c ki :i deas?
<z yg a>mbor z e cki:I'mm ai nly afte r plan - wr it able-mi mi c andex ecu te- writa b le-m imic
< zyga> mb orzec k i: this pullsi n change, ass u mp t i on s , re str ictions and  tre s spas sing <z yga >  mbor zecki :a lo n g with loads of tes ts 
<mbor zecki > mvo: i'm lo oking at 7 5 9 3 , perhap s ou r  c o nsistency chec ks ar e too stri c t, in pa rticu lar thelen(volum e s )!= 0 on lycou nts  wh e n  c onstraints ar e used ,but onc e t here'sa s yst em- see dstructure  defines  a nd  S sy tem Seedi s not tr ue , t he n w e bai l  out,why n ot a ll ow thi s case? <m b o rzec ki >zyga : t ha t's p arto f m ount re lated log ict houg h? 
< mborzec ki> zyga: orhm m we callit  na mespac e (or what not) often
<zyga> mborz e cki: ma inl y yes 
<mb orzecki>zyg a: sys tem / mount/ namesp ace?<z yga > mborz e c ki : I 'd  go for sy s t em/ mount  r eall y, it w ould help abbrevia t e t he API namesand  wou l d  l ook ni c e
< zy g a>m o unt
VolumeConsistency <Created_by mvo5>_<https://github.com/snapcore/snapd/pull/7599>
<pstolowski> morning
<mvo> pstolowski: hey,_good morning!
<mborzecki>_pstolowski:_hey
<zyga> hello?
<zyga>_is_this thing on?
<zyga>_I think I_connected now
<zyga> sorry for_starting late, lucy_was_sleeping hugging me all the time and got grumpy the second I tried to_put_her to_bed
<mborzecki>_zyga:_hey
<zyga> mborzecki: hey, question on_how to proceed for you
<zyga>_mborzecki: I_removed the guts of snap-update-ns so that I_can_create other tools_with the same logic
<zyga> mborzecki: I moved it to_system/mount for lack of a better_name
<zyga> mborzecki: some_bits_can_go to sandbox/cgroup
<zyga> mborzecki:_but most has no good place_to go
<zyga> mborzecki: ideas?
<zyga> mborzecki: I'm_mainly after plan-writable-mimic and execute-writable-mimic
<zyga> mborzecki: this_pulls in change, assumptions, restrictions and_tresspassing
<zyga> mborzecki: along with loads_of tests
<mborzecki>_mvo: i'm looking at 7593,_perhaps our consistency_checks are_too strict, in_particular the len(volumes)!= 0 only counts_when constraints are_used, but once there's a system-seed_structure_defines and SsytemSeed_is_not_true, then_we bail out,_why_not allow_this_case?
<mborzecki> zyga: that's part of mount_related_logic though?
<mborzecki> zyga: or hmm we call_it namespace (or whatnot)_often
<zyga>_mborzecki: mainly yes
<mborzecki> zyga:_system/mount/namespace?
<zyga> mborzecki: I'd go for_system/mount really, it would help abbreviate_the API_names and_would look nice
<zyga> mount