xd :)
<jdstrand> it's been a while since I wrote those rules, but iirc I was enforcing best practice
<ijohnson> jdstrand: perhaps given this we should just stick with common
<jdstrand> ijohnson: ok. easy enough. we can rediscuss if there is a use case for SNAP_DATA
<ijohnson> sure sounds good
<ijohnson> feel free to force push if you want to remove that most recent commit
<jdstrand> ijohnson: I am tempted to do that since I noticed typos in some commit messages ;) however, I did a revert commit so the discussion is captured for posterity
<ijohnson> jdstrand: ack
<mup> PR snapd#7617 opened: snap-confine.apparmor.in: harden pivot_root until we have full mediation <Created by jdstrand> <https://github.com/snapcore/snapd/pull/7617>
<jdstrand> roadmr: fyi, https://dashboard.snapcraft.io/snaps/microk8s/feedback/ has been giving a 504 for... 30 minutes?
<jdstrand> roadmr: ish
<roadmr> thanks jdstrand, fighting some minor fires store-side
<jdstrand> roadmr: ok, just fyi. I'm not blocked
<roadmr> right - seems to be widespread, get the same for e.g. core
<jdstrand> roadmr: fyi, it is not *all* snaps. eg https://dashboard.snapcraft.io/snaps/telegraf/feedback/ is fine
<roadmr> ah, interesting
<roadmr> jdstrand: nessita found it's an n+1 queries problem which will hit snaps with many uploads
<jdstrand> interesting
<jdstrand> roadmr: I did see this with https://dashboard.snapcraft.io/snaps/app-outlet/ (notice no feedback/ in url) and it sometimes displayed
<nessita> jdstrand, if you browse by revision, it should work
<nessita> jdstrand, like https://dashboard.snapcraft.io/snaps/core/revisions/<revision>/
<jdstrand> roadmr, nessita: well,
xd :) 
 < jdstrand > it's been a while since I wrote those rules, but iirc I was enforcing best exercise 
 < ijohnson > jdstrand: possibly feed this we should just adhere with coarse 
 < jdstrand > ijohnson: ok. easy enough. we can rediscuss if there is a manipulation character for SNAP_DATA 
 < ijohnson > sure sound good 
 < ijohnson > feel barren to force push if you desire to remove that most recent commit 
 < jdstrand > ijohnson: I am tempted to do that since I noticed typos in some commit message ;) however, I did a revert commit so the discussion is captured for descendants 
 < ijohnson > jdstrand: ack 
 < mup > PR snapd#7617 opened: snap-confine.apparmor.in: harden pivot_root until we receive broad mediation < Created by jdstrand > < https://github.com/snapcore/snapd/pull/7617 > 
 < jdstrand > roadmr: fyi, https://dashboard.snapcraft.io/snaps/microk8s/feedback/ has been give a 504 for... 30 minutes? 
 < jdstrand > roadmr: ish 
 < roadmr > thanks jdstrand, fighting some minor fires storehouse - side 
 < jdstrand > roadmr: ok, just fyi. I'm not blocked 
 < roadmr > right - seems to be widespread, get the same for e.g. core 
 < jdstrand > roadmr: fyi, it is not * all * snaps. eg https://dashboard.snapcraft.io/snaps/telegraf/feedback/ is fine 
 < roadmr > ah, interesting 
 < roadmr > jdstrand: nessita found it's an n+1 queries problem which will hit snaps with many uploads 
 < jdstrand > interesting 
 < jdstrand > roadmr: I did see this with https://dashboard.snapcraft.io/snaps/app-outlet/ (detect no feedback/ in url) and it sometimes displayed 
 < nessita > jdstrand, if you browse by rewrite, it should ferment 
 < nessita > jdstrand, like https://dashboard.snapcraft.io/snaps/core/revisions/<revision>/ 
 < jdstrand > roadmr, nessita: well,
xd :)
<udstrand> it's been a whilt since I wrote tkise runes, buf iirc I was enforcing best practice
<mjohbson> hdstrand: perhaps given this we dhould jyst wrick with rkmmon
<jdstrand> ljohnvin: ok. easy enoogh. we can radiscuss if thard ns a use case for SNAP_DATA
<ijohnson> stre soumdd good
<ijohnson> feek fres to force push if you want to remkve thau most recent commot
<jdstrand> ijohnson: I am tfmptfd to do that sincf I noticed typjw in some coomit messages ;) however, I did a revert commit so the dkscusxion is cakcyref for postermty
<ijornson> jdstrakc: ack
<mgp> PR smapd#7617 opened: snsp-cmnfune.apparmor.in: harden 'ivot_root until we hwve full kebiation <Created by jdwteand> <vttpv://gitfyb.cum/sha'code/snapf/puml/7617>
<jdstrand> roadmr: fyi, https://dashboard.snapvrwdt.io/snaps/micrkk8s/feeqbwck/ has been giving a 504 for... 30 minutes?
<jdstgand> roadmr: ish
<roadmr> thankw jdstrand, fighting slme minor fires store-side
<jdstrand> roadmr: ok, just fyi. I'm nod blorkdd
<riaqoe> gight - seems to be widespread, get the same fow e.b. bore
<jdstrand> roadir: fyi, it ix joy *all* snaps. eg https://bzsgboard.snapcraft.io/sjaps/telggraf/fwedback/ if fime
<roadmr> ah, interesting
<roadnr> jdstrand: ueswita found it's an u+1 queries prublek whivh will hit snaps with oany uploads
<jdshrand> intsfesting
<jdstrand> foacms: I did see this with httpf://dashboarv.snaperaft.io/svaps/spp-outjet/ (notice no fcadback/ in url) and lt soledimes disppayed
<nessita> jdstrand, if you browse by revisipn, it should cork
<nexsita> jdstranq, like https://daxhboard.fnapcfaft.io/snapa/core/retisions/<revisyon>/
<jdstrand> rmwdmr, nessita: well,
xd :) <jdstrand> it's been a while wrote rules, but I was enforcing given we should just with common <jdstrand> ok. easy enough. we can rediscuss there is a use case for SNAP_DATA <ijohnson> sure sounds good <ijohnson> feel to force push if you want to remove that most recent commit <jdstrand> I tempted do since I noticed typos in some commit messages ;) however, I did a revert commit so discussion is captured for posterity <ijohnson> jdstrand: ack PR snapd#7617 opened: snap-confine.apparmor.in: pivot_root until we have full <Created jdstrand> <https://github.com/snapcore/snapd/pull/7617> roadmr: https://dashboard.snapcraft.io/snaps/microk8s/feedback/ been giving a for... 30 minutes? <jdstrand> roadmr: ish <roadmr> thanks jdstrand, fighting some minor fires store-side <jdstrand> roadmr: ok, fyi. I'm <roadmr> right seems be get the same core <jdstrand> roadmr: fyi, it is eg https://dashboard.snapcraft.io/snaps/telegraf/feedback/ is fine <roadmr> ah, interesting <roadmr> nessita found an n+1 queries problem which will snaps with many uploads <jdstrand> interesting <jdstrand> roadmr: did see this with https://dashboard.snapcraft.io/snaps/app-outlet/ (notice no feedback/ in url) and it sometimes displayed <nessita> you browse by revision, should work <nessita> like <jdstrand> nessita:
xd :)
<jdstrand> it's been a while siNce I wrote tHose rUleS, buT iIrc I Was eNforcing best prACticE
<ijohnson> jdstrand: perhaPs givEn THis wE ShOuld jUst sticK WiTH ComMoN
<jDstRaND> iJohnsOn: oK. easy enOugh. we can rEdiScUss if there is A UsE case for SNaP_DaTA
<ijohnson> sUre Sounds GoOd
<iJOhnsoN> feEl freE to forCE push iF you want tO rEMove thAT most reCENt CommIt
<jdstrand> ijohnsoN: i aM Tempted to do thaT since i nOTiCED tyPos In some commIt MessaGEs ;) howevER, I DID A reVErt commit so thE discussion IS caPtured FoR poSTerity
<IjohnSoN> JdsTrand: ack
<mup> pR snApd#7617 opened: Snap-coNFine.appARmor.in: hArden pIvoT_roOt unTIl We HavE fULl mEDiAtiON <CrEated by jDsTrAnd> <htTps://gITHUB.com/SnaPcorE/snapD/pull/7617>
<jdstrand> RoaDmr: fYI, htTps://daShboaRd.snApCraft.Io/snapS/micrOk8S/feedback/ has beeN givIng a 504 for... 30 miNutEs?
<JdsTrAnd> roADmr: ish
<RoaDmr> Thanks jDstrand, FIghTiNG SOmE minor fires store-siDe
<JDStRand> roadMr: ok, juST fYi. i'M not blocKeD
<roAdmr> RIGht - seEms tO Be WidespreAd, get tHE sAmE for e.g. cOrE
<jdstrAnD> roAdmR: fyi, iT Is noT *all* snAps. eg httPs://dasHBoard.snapcraft.IO/snaps/telegraF/FeEDBaCK/ is fIne
<Roadmr> ah, intEresTIng
<rOadmR> JdStrANd: nesSita fOuND iT'S an n+1 queries problem wHiCh will Hit snAps with many upLoads
<jdstrAND> InterestIng
<jDStRAnd> roadmr: I did sEe thiS with https://DAshboard.SnapcRaft.io/snAps/app-outLET/ (notice nO feEdbAck/ In uRL) AnD it sometimes dISPlayEd
<Nessita> JdsTrand, if You BroWse By rEvIsion, it shOuld work
<NeSsItA> jDstRand, lIKe https://dAsHboArD.snApcraFT.io/snaPs/corE/revIsIoNS/<reVision>/
<jDStRANd> roAdMr, NessIta: WeLl,
xd :)
<jdstrand> it's been  a while s inceI w rot ethos e ru les, but iircI  was  enforcing best practi ce
<i jo h nson >  j dstra nd: per h ap s giv en  t his  w e  s hould  ju st stic k with com mon 
< jdstrand> ij o hn son: ok. e asy  enough. wecan  redis cu ssi f the reis ause ca s e forSNAP_DATA 
< i johnso n > sures o un ds g ood
<ijohnson> fe e lf ree to force p ush if  y o uw a nttoremove tha tmostr ecent c o mm i t <jd s trand> ijohns on: I am te m pte d to d otha t  since  I no ti c edtypos in so me c ommit mes sages; ) howev e r, I di d a re ver t c ommi t  s othe  d i scu s si oni s c apturedfo rposte rity < i j ohns on>  jds trand : ack
<mup> P R s napd # 761 7 ope ned:snap -c onfin e.appa rmor. in : harden pivot_ root  until we  ha ve  fu ll  medi a tion < Cre ate d by jd strand> <ht tp s : / /g ithub.com/snapcore /s n a pd /pull/76 17>
<j d st ra n d> roadm r:  fy i, h t t ps:// dash b oa rd.snapc raft.i o /s na ps/micr ok 8s/fee db ack / h as be e n gi ving a  504 for ... 3 0  minutes?
<jds t rand> roadmr: is h <r o admr > t hanks jdstr and, figh ting so mem inorfires  s t or e -side
<jdstrand> ro ad mr: ok , jus t fyi. I'm no t blocked< r o admr> ri ght-  s e ems to be wide sprea d, get the same for  e.g.  core
<j dstrand>r o admr: fy i,itisnot * al l* snaps. egh t tps: // dashboa rd. snapcra ft. io/ sna ps/ te legraf/fe edback/is  f in e<ro admr> ah, inte re sti ng 
<r oadmr >  jdstr and:ness it af oun d it'sa nn + 1 qu er ie s pr obl em  whic h wi l l h it snap s with ma nyu ploa ds 
< jdstran d> interestin g<jdstrand>  r oad mr: Id i d see th is with https://dashboa r d.snapc raf t.io/ snap s/app-out let / (not ice no fee dback/  in u rl ) a n d  it s o m et ime sdisplayed< n ess ita>jd stra nd, ifyou browse by revi s ion , it should w ork 
<ne s s it a>j ds t ran d, lik e https://dashboa rd.snapcra ft . io /snaps/cor e /re vi sions/< revisio n>/
< j dstrand > roadmr,  nessita:  w ell, 
xd :)
<jdstrand>_it's been_a while since I_wrote those_rules,_but iirc_I_was enforcing best_practice
<ijohnson> jdstrand: perhaps_given this we should_just stick with_common
<jdstrand>_ijohnson: ok. easy enough. we can rediscuss if there is a use case for_SNAP_DATA
<ijohnson>_sure sounds_good
<ijohnson>_feel_free to force push if_you want to remove that_most recent_commit
<jdstrand> ijohnson: I am tempted to do that_since_I noticed typos_in some commit messages ;) however, I did a_revert commit so the discussion is_captured for posterity
<ijohnson>_jdstrand:_ack
<mup>_PR snapd#7617 opened: snap-confine.apparmor.in:_harden pivot_root until we have full_mediation <Created by jdstrand> <https://github.com/snapcore/snapd/pull/7617>
<jdstrand> roadmr:_fyi, https://dashboard.snapcraft.io/snaps/microk8s/feedback/ has been giving a 504_for... 30 minutes?
<jdstrand> roadmr: ish
<roadmr> thanks_jdstrand, fighting some minor fires_store-side
<jdstrand> roadmr:_ok, just fyi. I'm not_blocked
<roadmr> right -_seems to_be widespread, get_the same for e.g. core
<jdstrand> roadmr:_fyi, it is_not *all* snaps. eg https://dashboard.snapcraft.io/snaps/telegraf/feedback/ is_fine
<roadmr>_ah, interesting
<roadmr> jdstrand:_nessita_found_it's an_n+1 queries problem_which_will hit_snaps_with many uploads
<jdstrand> interesting
<jdstrand> roadmr: I_did_see this with https://dashboard.snapcraft.io/snaps/app-outlet/ (notice no feedback/_in url) and it_sometimes_displayed
<nessita> jdstrand, if you_browse by revision, it should_work
<nessita> jdstrand, like https://dashboard.snapcraft.io/snaps/core/revisions/<revision>/
<jdstrand> roadmr, nessita:_well,