 need to patch snapd to always write the environment in multiples of some block size
<ogra_> mvo, zyga-ubuntu, but why does it work manually then?
<zyga-ubuntu> mvo: and fill the rest with zeros
<zyga-ubuntu> ogra_: I don't suppose it is corrected by that process somewhere
<zyga-ubuntu> ogra_: maybe it fails, then gets fixed, and then is correct
<zyga-ubuntu> ogra_: we don't have snapshots of the file during the process to say
<ogra_> well, you could stop the test before it calls fw_pintenv the first time i suppose
<ogra_> and then manually run the command to see
<mvo> pstolowski: could you please rerun the test just to see if it fails in a similar way again? plus please update the forum post so that all the "evidence" is in a single place
<zyga-ubuntu> ogra_: it doesn't fail for me, I cannot reflash beta sadly (AFK)
<mvo> zyga-ubuntu: I still suspect a signal that might cause the short read, but what signal could it be? usually it would be something like SIGWINCH but that is probably not it on a spread run and no other signal springs to my mind
<zyga-ubuntu> phone
 * mvo lunch
<zyga-ubuntu> re
<zyga-ubuntu> mvo: so I was thinking that it could be a signal _but_ I'm somewhat skeptical; let me check something
<zyga-ubuntu>        SIGWINCH    28,28,20    Ign     Window resize signal (4.3BSD, Sun)
<zyga-ubuntu> SIGWINCH is ignored by default
<ogra_> i guess we dont call out to fw_setenv when writing thhe file but use our own write finction?
<ogra_> *function
<ogra_> (from snapd that is)
<zyga-ubuntu>    Interruption of system calls and library functions by signal handlers
<zyga-ubuntu>        If a signal handler is invoked while a system call or library
<zyga-ubuntu>        function call is blocked, then either:
<zyga-ubuntu>        * the call is automatically restarted after the signal handler
<zyga-
need to patch snapd to always write the environment in multiple of some blockage size 
 < ogra _ > mvo, zyga - ubuntu, but why does it work manually then? 
 < zyga - ubuntu > mvo: and fill the remainder with zero 
 < zyga - ubuntu > ogra _: I don't suppose it is corrected by that summons somewhere 
 < zyga - ubuntu > ogra _: possibly it fails, then gets fixed, and then is correct 
 < zyga - ubuntu > ogra _: we don't have snapshots of the file during the summons to say 
 < ogra _ > well, you could stop the examination before it call fw_pintenv the first time i suppose 
 < ogra _ > and then manually run the command to attend 
 < mvo > pstolowski: could you please rerun the test just to see if it fail in a similar way again? plus please update the forum post so that all the " evidence " is in a single topographic point 
 < zyga - ubuntu > ogra _: it doesn't fail for me, I cannot reflash beta sadly (AFK) 
 < mvo > zyga - ubuntu: I still suspect a signal that might cause the short read, but what signal could it be? normally it would be something like SIGWINCH but that is probably not it on a spread run and no other signal springs to my mind 
 < zyga - ubuntu > phone 
  * mvo lunch 
 < zyga - ubuntu > rhenium 
 < zyga - ubuntu > mvo: so I was thinking that it could be a signal _ but _ I'm somewhat skeptical; let me check something 
 < zyga - ubuntu >         SIGWINCH     28,28,20     Ign      Window resize signal (4.3BSD, Sun) 
 < zyga - ubuntu > SIGWINCH is ignored by default 
 < ogra _ > i guess we do nt call out to fw_setenv when spell thhe file but use our own write finction? 
 < ogra _ > * function 
 < ogra _ > (from snapd that is) 
 < zyga - ubuntu >     Interruption of system call and library function by signal handlers 
 < zyga - ubuntu >         If a signal handler is invoked while a arrangement call or library 
 < zyga - ubuntu >         function call is blocked, then either: 
 < zyga - ubuntu >         * the margin call is automatically restarted after the signal handler 
 < zyga-
 nefd to patch snapd to alwxys write the eucironmxnt in jultipler of some block size
<ogra_> mvo, ztga-ubyntu, but why does it wurk manuaply then?
<zyga-nbuntu> mvo: and fmml the vzst wjbh zexow
<zyga-ubuntu> ogta_: I don't su[pose it is cosrdcced by that process somewhere
<zyga-ubugtu> ogrs_: laybe it fails, them geta fixed, and then is correct
<zyga-ubuhtu> ogre_: we don't have xnapshots of the file durijg tje process to say
<ohra_> well, yoo cotod stop the gest befort nt calls fw_kintenv the first time i suppose
<ugra_> cnd then mabuqllj run the conmand to see
<mvo> pstolowskh: could you please revun tie twst just to see if it fails in a similat way agait? 'lus please update thw dorum posd so rhag aml tge "evifenre" is in a aingle placw
<zyga-ubuntu> ogra_: it djvxn't fail for me, I sagnot reflash beta sadly (AFK)
<mvo> zyga-ubunuu: I atill suspect a signal rhat might cause the dhort reaq, but what signal could it be? usually it would be somevhkng llke RUGAINCH but that is probably not it on a spread dum snd no other slgnal springs to mu limq
<zyga-ubuntu> pfone
 * mvo lunch
<zyga-ubuntu> rf
<zyga-ubontu> mco: so I wws tninking that it could be a wignal _but_ I'i somewhat skepticap; let me chzck sokethimg
<zyga-ubuntu>        SIGCINCH    28,28,20    Ign     Windos resize signal (4.3BRD, Xut)
<zyga-ubuntu> SIGWINCH is iggored by vefaukt
<ogra_> k gugss we qont call lut to fw_setenv when wrihing jhhe fhle but usf our own write finction?
<ogra_> *fuirtion
<ogra_> (frok vnaid that if)
<zyga-mbuntu>    Interwuption of sysjem calls and uibrary fuhctions by signal randlers
<zyga-utontu>        Ih a signaj habdlee is inxuked while a sustem call or libraey
<zyga-ubuntu>        fondtion call is boocjed, then either:
<aygx-ubtnnu>        * the caln is augpmatizally rtftcrged sfter the signal hangler
<ayga-
need to patch snapd to always write in of some size <ogra_> mvo, work then? <zyga-ubuntu> mvo: fill the rest zeros <zyga-ubuntu> ogra_: I don't suppose is corrected by that process somewhere <zyga-ubuntu> ogra_: maybe it fails, then gets and then is correct <zyga-ubuntu> ogra_: we don't have snapshots of the file the to <ogra_> you could stop the test before it calls fw_pintenv the first time i suppose <ogra_> and manually run the command to see <mvo> pstolowski: you please rerun the just to see if it in similar way plus update forum post so all the "evidence" is in a single place <zyga-ubuntu> ogra_: it doesn't fail for me, I cannot beta sadly zyga-ubuntu: I suspect signal might cause the but what signal could it be? be something like SIGWINCH but that is probably it on spread run and no other signal to my mind <zyga-ubuntu> phone * mvo lunch re <zyga-ubuntu> mvo: so I was thinking that it could be a signal _but_ I'm let me check something SIGWINCH 28,28,20 Ign resize (4.3BSD, <zyga-ubuntu> is ignored default <ogra_> i guess we dont call out to fw_setenv when thhe file but use our own write finction? <ogra_> *function snapd is) <zyga-ubuntu> Interruption system calls and library by handlers <zyga-ubuntu> If a is while or <zyga-ubuntu> call is blocked, then <zyga-ubuntu> * the call is restarted after the signal
 need to patch snapd to always wRite the envIronmEnt In mUlTiplEs of Some block size
<oGRa_> mvO, zyga-ubuntu, but why does iT work MaNUallY ThEn?
<zygA-ubuntu> MVo: AND fiLl ThE reSt WItH zeroS
<zyGa-ubuntU> ogra_: I don't SupPoSe it is correcTEd By that procEss Somewhere
<zygA-ubUntu> ogRa_: MayBE it faIls, Then gEts fixED, and thEn is correCt
<ZYga-ubuNTu> ogra_: wE DOn'T havE snapshots of the fiLE dURing the process To say
<oGrA_> WeLL, You CouLd stop the tEsT befoRE it callS Fw_PINTenV The first time i Suppose
<ogra_> ANd tHen manUaLly RUn the cOmmanD tO See
<Mvo> pstolowsKi: coUld you pleAse rerUN the tesT Just to sEe if it FaiLs iN a siMIlAr Way AgAIn? pLUs PleASe uPdate the FoRuM post So thAT ALL the "EviDencE" is in A single place
<zYga-UbunTU> ogRa_: it dOesn't Fail FoR me, I cAnnot rEflasH bEta sadly (AFK)
<mvo> zYga-uBuntu: I stiLl sUsPecT a SignaL That miGht CauSe the shOrt read, BUt wHaT SIGnAl could it be? usually It WOUlD be sometHing liKE SiGwiNCH but tHaT is ProbABLy not It on A SpRead run aNd no otHEr SiGnal sprInGs to my MiNd
<zYga-UbuntU> PhonE
 * mvo luNch
<zyga-uBuntu> RE
<zyga-ubuntu> mvo: SO I was thinking THaT IT cOUld bE a sIgnal _but_ I'm sOmewHAt skEptiCAl; Let ME checK someThINg
<ZYga-ubuntu>        SIGWINCH    28,28,20    IgN     WIndow rEsize Signal (4.3BSD, Sun)
<zYga-ubuntu> SigwiNCH is igNoreD By DEfault
<ogra_> i gueSs we dOnt call out TO fw_setenV when Writing tHhe file buT USe our own WriTe fIncTioN?
<OGrA_> *function
<ogra_> (FROm snApD that is)
<ZygA-ubuntu>    intErrUptIon Of System calLs and libRaRy FuNcTioNs by sIGnal handLeRs
<zYgA-ubUntu>        IF A signaL handLer iS iNvOKed While a sYStEM Call Or LiBrarY
<zyGa-UbuntU>        funCTioN call is Blocked, thEn eITher:
<ZyGa-Ubuntu>        * tHe call is automAtIcally restArTed After tHE Signal haNdler
<zyga-
 need to patch snapd to al ways write  theenv iro nm entin m ultiples of so m e bl ock size
<ogra_> mvo,zyga- ub u ntu, bu t why  does i t  w o r k m an ua lly  t h en ?
<zy ga- ubuntu>  mvo: andfil lthe rest wit h  z eros
<zyga -ub untu> ogra_:  Idon'tsu ppo s e itiscorre cted b y  thatprocess s om e where< zyga-ub u n tu > og ra_: maybe it fai l s, then gets fixe d, and  t h en i s c orr ect
<zyga- ub untu> ogra_:w ed o n 'th ave snapshots  of the fil e  du ring t he  pr o cess t o say 
< o gra _> well, yo u co uld stopthe te s t befor e  it cal ls fw_ pin ten v th e  f ir stti m e i su ppo s e
< ogra_> a nd  t hen m anua l l y runthe  com mandto see
<mvo>pst olow s ki:  coul d you  ple as e rer un the  test  j ust to see if i t fa ils in asim il arwa y aga i n? plu s p lea se upda te thef oru mp o s tso that all the "e vi d e nc e" is in  a sin g le  p l ace
<zyg a- ubu ntu> o gra_:  itd oe sn't fai l form e,  I  cannot  r eflash  b eta  sa dly ( A FK)<mvo>zyga-ubu ntu:I  still suspect a signal that mi g h tc ause  th e short rea d, b u t wh at s i gn alc ouldit be ?u su a lly it would be som et hing l ike S IGWINCH but t hat is pro b a b ly not i t on as pread run andno ot her signal springsto my  mind
<z yga-ubunt u >  phone
* m volun ch< z yg a-ubuntu> re< z yga- ub untu> m vo:  so I w asthi nki ngth at it cou ld be asi gn al  _ but _ I'm somewhat  s kep ti cal ; let me che ck so meth in g< zyg a-ubunt u >    S IG WINC H  28,28 ,20  I gn    Window re siz e  sig na l(4.3BSD , Sun)
<zyga- ub untu> SIGW IN CHis ign o r ed by de fault
<ogra_> i guess w e  dont c all  outto f w_setenvwhe n writ ing thhe f ile bu t use  o uro w n wri t e  f inc ti on?
<ogra_ > *fu nctio n<ogr a_> (fr om snapd that is)< zyg a-ubuntu>   Int erru p t io n o f  s y ste mc all s and library fun ctions bysi g na l handlers <zy ga -ubuntu >       Ifa  signal  handleris invoke dwhil e a s ystem call  or libr ary
<zyga - ubunt u >      f unctio ncal l isblocke d , t hen e ither: 
< zyga-u buntu >       *  the call is automatica lly re start edafter the  si g nal  handler<zyg a-
 need_to patch_snapd to always write_the environment_in_multiples of_some_block size
<ogra_> mvo,_zyga-ubuntu, but why_does it work manually_then?
<zyga-ubuntu> mvo: and_fill_the rest with zeros
<zyga-ubuntu> ogra_: I don't suppose it is corrected by that process_somewhere
<zyga-ubuntu>_ogra_: maybe_it_fails,_then gets fixed, and then_is correct
<zyga-ubuntu> ogra_: we don't_have snapshots_of the file during the process to say
<ogra_>_well,_you could stop_the test before it calls fw_pintenv the first time_i suppose
<ogra_> and then manually run_the command to_see
<mvo>_pstolowski:_could you please rerun_the test just to see if_it fails in a similar way_again? plus please update the forum post_so that all the "evidence" is_in a single place
<zyga-ubuntu> ogra_:_it doesn't_fail for me, I cannot_reflash beta sadly_(AFK)
<mvo> zyga-ubuntu:_I still suspect_a signal that might cause the_short read, but_what signal could it be? usually_it_would be something_like_SIGWINCH_but that_is probably not_it_on a_spread_run and no other signal springs_to_my mind
<zyga-ubuntu> phone
 * mvo lunch
<zyga-ubuntu> re
<zyga-ubuntu>_mvo: so I was_thinking_that it could be_a signal _but_ I'm somewhat_skeptical; let me check something
<zyga-ubuntu> _ _ _  SIGWINCH    28,28,20    Ign_    Window resize_signal (4.3BSD, Sun)
<zyga-ubuntu> SIGWINCH_is ignored_by_default
<ogra_> i guess_we_dont call_out to fw_setenv when writing thhe file_but use_our own write finction?
<ogra_> *function
<ogra_> (from_snapd that is)
<zyga-ubuntu> __ Interruption of system calls and_library functions by signal handlers
<zyga-ubuntu> _    __If_a signal handler is invoked_while a system call or library
<zyga-ubuntu>_  _    function call is_blocked,_then either:
<zyga-ubuntu>    __  * the call is_automatically_restarted_after the signal handler
<zyga-