IRC logs for #buildstream for Wednesday, 2018-07-25

hipp__Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
hipp__Voice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
Guest89349or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
averell_or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
neptuneor maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
clorophormoVoice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
richvdhRead what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
richvdhVoice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
OctoberRead what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
OctoberVoice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
neptune_or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
averell__or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
host_Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
Taylor_Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
Guest89349_or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
*** sirnaysayer has quit IRC00:00
-jrabe___- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
Zx3_Voice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
rosseauxVoice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
aprilVoice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
KindOneVoice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
*** sirnaysayer_ has quit IRC00:00
richvdh_Voice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
clorophormo_Voice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
October_Voice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
april__Voice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
KindOne_Voice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
april_Voice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
-siinus`- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
Guest89349__Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
neptune__Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
*** Pici_ has quit IRC00:00
rosseaux_Voice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
KindOne__Voice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
-Pici- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
*** arza has quit IRC00:00
Texou_Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
lostlabyrinthRead what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
thisRead what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
lostlabyrinth_Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
this_Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
Cork___Voice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
-ikevin- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
ArsenArsenRead what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
ArsenArsenVoice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
Texou__Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
averell___or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-ikevin_- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
PengVoice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
slackjeffVoice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
c0dedVoice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
Peng_Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
-hipp- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
-Cork_- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
-Adbray- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
hostVoice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
Zx3Voice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
*** hipp_ has quit IRC00:00
Texou___or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
Taylor__Voice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
TaylorVoice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
-joepie91__- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
janusRead what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
berndjRead what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
Adbray_Voice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
Cork__Voice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
*** jrabe_ has quit IRC00:00
-dan-- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
*** Zx3 has quit IRC00:00
-Dan_Bennett- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
host__Voice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
-SolarAquarion- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
-digitalcold- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
-jrabe__- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
*** Taylor__ has quit IRC00:00
Peng__Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
Zx3__Voice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
*** Taylor has quit IRC00:00
-xunplini__- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
-Ishaq- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
averellRead what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
-xunplini- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
-caf_- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-iczero_- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-bolt- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-`d- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
-rdococ- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
-loeken- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
*** host__ has quit IRC00:00
-wiggle- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-Frosty_- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-BurningPrincess- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
-Randy- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
-Kraps- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
-BurningPrincess_- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
-Kraps_- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
-Randy_- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
*** BurningPrincess_ has quit IRC00:00
-caf- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
*** Dan_Bennett has quit IRC00:00
*** Zx3__ has quit IRC00:00
*** Taylor_ has quit IRC00:00
neptuneRead what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
*** Randy has quit IRC00:00
host_Voice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
*** joepie91__ has quit IRC00:00
averell_Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
Guest89349Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
Guest89349Voice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
-hipp__- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
neptune_Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
*** Frosty_ has quit IRC00:00
-clorophormo- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
-richvdh- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
*** siinus` has quit IRC00:00
*** clorophormo has quit IRC00:00
*** richvdh has quit IRC00:00
-October- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
averell__Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
Guest89349_Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
Guest89349_Voice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
*** wiggle has quit IRC00:00
*** host has quit IRC00:00
-jrabe___- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
*** October has quit IRC00:00
-Zx3_- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
*** jrabe__ has quit IRC00:00
-april- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
*** Kraps_ has quit IRC00:00
-rosseaux- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
-KindOne- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
*** xunplini__ has quit IRC00:00
*** Randy_ has quit IRC00:00
*** Ishaq has quit IRC00:00
*** xunplini has quit IRC00:00
*** rdococ has quit IRC00:00
*** `d has quit IRC00:00
Guest89349__Voice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
neptune__Voice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
*** loeken has quit IRC00:00
*** host_ has quit IRC00:00
thisVoice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
lostlabyrinthVoice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
*** DarthGandalf has joined #buildstream00:00
DarthGandalfHey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
*** cfields has joined #buildstream00:00
cfieldsHey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
Texou_Voice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
-richvdh_- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
*** HarryCross2 has joined #buildstream00:00
HarryCross2Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
this_Voice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
lostlabyrinth_Voice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
-October_- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
-clorophormo_- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
*** caf has quit IRC00:00
Texou__Voice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
-Pici- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-ikevin- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-KindOne_- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
-april_- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
-april__- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
-rosseaux_- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
-KindOne__- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
*** Zx3_ has quit IRC00:00
Peng_Voice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
-Cork___- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
-ikevin_- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
janusVoice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
berndjVoice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
-hipp- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-Cork_- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-Adbray- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-dan-- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
Peng__Voice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
-ArsenArsen- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
averellVoice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
averell___Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
-SolarAquarion- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
*** BurningPrincess has quit IRC00:00
-digitalcold- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
*** jrabe___ has quit IRC00:00
-slackjeff- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
*** SolarAquarion has quit IRC00:00
-Peng- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
*** Kraps has quit IRC00:00
-c0ded- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
iczeroRead what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
*** dan- has quit IRC00:00
Texou___Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
-Cork__- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
-Adbray_- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
-caf_- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
*** caf_ has quit IRC00:00
-bolt- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
*** bolt has quit IRC00:00
neptuneVoice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
*** ikevin_ has quit IRC00:00
-iczero_- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
*** iczero_ has quit IRC00:00
averell_Voice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
*** digitalcold has quit IRC00:00
*** Pici has quit IRC00:00
neptune_Voice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
*** Cork_ has quit IRC00:00
*** ikevin has quit IRC00:00
-hipp__- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
averell__Voice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
-Guest89349- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
*** hipp has quit IRC00:00
-Guest89349_- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
iczeroVoice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
-april- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-rosseaux- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-KindOne- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-richvdh_- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
DarthGandalfor maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
cfieldsor maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-clorophormo_- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-October_- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
*** Adbray has quit IRC00:00
HarryCross2or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-Guest89349__- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
-neptune__- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
-KindOne_- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-april_- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-april__- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-rosseaux_- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-this_- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
-lostlabyrinth_- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
-this- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
-lostlabyrinth- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
-Texou_- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
-KindOne__- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-Cork___- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-Texou__- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
*** slackjeff has quit IRC00:00
averell___Voice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
-Peng_- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
*** c0ded has quit IRC00:00
*** ArsenArsen has quit IRC00:00
-Peng- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
Texou___Voice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
-janus- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
-berndj- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
-Cork__- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-Adbray_- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-Peng__- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
-averell- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
*** Adbray_ has quit IRC00:00
-iczero- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
-neptune- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
-averell_- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
-neptune_- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
*** Cork__ has quit IRC00:00
*** KindOne_ has quit IRC00:00
-Guest89349- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-hipp__- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
-averell__- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
-Guest89349_- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-iczero- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-april- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
-rosseaux- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
-KindOne- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
-neptune__- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-Guest89349__- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-this- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-lostlabyrinth- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
DarthGandalfRead what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
cfieldsRead what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
-Texou_- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-richvdh_- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
-this_- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-lostlabyrinth_- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
HarryCross2Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
-clorophormo_- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
-October_- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
*** hipp__ has quit IRC00:00
-Texou__- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
*** Peng_ has quit IRC00:00
-april_- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
-april__- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
-rosseaux_- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
-KindOne__- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
-Cork___- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
-janus- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-berndj- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-averell___- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
-Peng__- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-averell- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-Peng- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
-Texou___- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:00
-neptune- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
*** KindOne has quit IRC00:00
*** april has quit IRC00:00
*** rosseaux has quit IRC00:00
-averell_- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-iczero- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
-neptune_- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
*** iczero has quit IRC00:00
-averell__- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
*** richvdh_ has quit IRC00:00
*** clorophormo_ has quit IRC00:00
*** October_ has quit IRC00:00
-Guest89349- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
*** april__ has quit IRC00:00
*** april_ has quit IRC00:00
*** rosseaux_ has quit IRC00:00
*** KindOne__ has quit IRC00:00
*** Cork___ has quit IRC00:00
-Guest89349_- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
*** Peng has quit IRC00:00
cfieldsVoice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
DarthGandalfVoice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
HarryCross2Voice your opinions at https://webchat.freenode.net/?channels=#freenode00:00
-neptune__- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
-Guest89349__- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
-this- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
-lostlabyrinth- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
-Texou_- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
-this_- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
-lostlabyrinth_- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
-Texou__- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
*** Guest89349 has quit IRC00:00
-averell___- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-Texou___- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:00
-janus- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
*** janus has quit IRC00:00
-berndj- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
*** berndj has quit IRC00:00
*** Guest89349_ has quit IRC00:00
-Peng__- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
-averell- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
*** averell has quit IRC00:00
*** Peng__ has quit IRC00:00
-neptune- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
*** neptune has quit IRC00:00
-averell_- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
*** averell_ has quit IRC00:00
-neptune_- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
*** neptune_ has quit IRC00:00
*** neptune__ has quit IRC00:00
*** Guest89349__ has quit IRC00:00
-averell__- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:00
*** averell__ has quit IRC00:00
*** this has quit IRC00:01
*** lostlabyrinth has quit IRC00:01
*** Texou_ has quit IRC00:01
*** this_ has quit IRC00:01
*** lostlabyrinth_ has quit IRC00:01
*** Texou__ has quit IRC00:01
-cfields- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:01
-DarthGandalf- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:01
-HarryCross2- Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:01
-averell___- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:01
*** averell___ has quit IRC00:01
-Texou___- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:01
*** Texou___ has quit IRC00:01
-cfields- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:01
-DarthGandalf- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:01
-HarryCross2- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:01
-cfields- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:01
-DarthGandalf- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:01
*** DarthGandalf has quit IRC00:01
*** cfields has quit IRC00:01
-HarryCross2- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:01
*** HarryCross2 has quit IRC00:01
*** nikow has quit IRC00:01
*** Kronuz has joined #buildstream00:01
KronuzHey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/00:01
Kronuzor maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/00:01
KronuzRead what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate00:01
*** Kronuz has quit IRC00:05
*** l4z4i has joined #buildstream01:41
l4z4iHey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/01:41
l4z4ior maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/01:41
*** enyc has joined #buildstream01:41
enycHey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/01:41
enycor maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/01:41
l4z4iRead what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate01:41
enycRead what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate01:41
enycVoice your opinions at https://webchat.freenode.net/?channels=#freenode01:41
l4z4iVoice your opinions at https://webchat.freenode.net/?channels=#freenode01:41
*** Dan_Bennett has joined #buildstream01:41
Dan_BennettHey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/01:41
Dan_Bennettor maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/01:41
Dan_BennettRead what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate01:41
Dan_BennettVoice your opinions at https://webchat.freenode.net/?channels=#freenode01:41
*** Dan_Bennett has quit IRC01:42
*** l4z4i has quit IRC01:42
*** enyc has quit IRC01:42
*** leopi has joined #buildstream02:34
*** leopi has quit IRC03:00
*** leopi has joined #buildstream03:51
*** mohan43u has quit IRC05:15
*** mohan43u has joined #buildstream05:19
*** ernestask has joined #buildstream05:35
paulsherwoodthis is a bit much, now06:25
*** WSalmon has joined #buildstream07:25
*** noisecell has joined #buildstream07:42
*** Kinnison has quit IRC07:48
*** Kinnison has joined #buildstream07:48
*** coldtom has joined #buildstream07:53
*** tristan has joined #buildstream07:58
*** qinusty has joined #buildstream08:00
gitlab-br-botbuildstream: issue #498 ("Cannot set LD_LIBRARY_PATH") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/49808:11
gitlab-br-botbuildstream: merge request (valentindavid/498_bwrap_environment->master: Set environment in bwrap command line instead of its environment) #565 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/56508:18
gitlab-br-botbuildstream: merge request (valentindavid/498_bwrap_environment->master: WIP: Set environment in bwrap command line instead of its environment) #565 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/56508:19
gitlab-br-botbuildstream: merge request (valentindavid/498_bwrap_environment->master: WIP: Set environment in bwrap command line instead of its environment) #565 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/56508:20
jjardonNot sure is possible yet, bit how people feel about configuring the channel so only registered nicks can join/talk ?08:27
* jjardon tries to avoid spam08:27
KinnisonThe issue with that kind of thing is that it breaks reconnection for most clients with auto-identify since the asynchronous nature of IRC means they try and join the channel before auto-identify08:30
*** leopi has quit IRC08:30
* Kinnison ended up leaving every such channel on another network because it was unreliable08:31
CyBeRalso it's a bit of an overreaction08:31
jjardonKinnison: yeah, I had that problem before too. What about only restrict the ability to talk in the channel? Reentering would not be a problem08:32
KinnisonThat is less painful08:32
* Kinnison wonders if those joined via matrix? are able to register08:33
* Kinnison doesn't know if the gimpnet servers support that kind of restriction though08:33
jjardonYeah, I'm registered through matrix; I will ask about the other restriction08:34
*** toscalix has joined #buildstream08:34
CyBeRhonestly to me this sounds like you're wanting to disable the ability for anyone you don't know to e-mail you because you got one spam e-mail, that btw pretty much everyone on the planet got.08:35
jjardonCyBeR: not need to send any email to register your nickname08:36
CyBeRI think you're missing my point08:36
jjardonProbably08:36
*** tiagogomes has quit IRC08:37
KinnisonCyBeR: to be fair, that was a *lot* of spam which means any conversation which happened before it is effectively lost in scrollback08:37
*** tiagogomes has joined #buildstream08:37
* Kinnison understands jjardon's desire to prevent that08:37
CyBeRthat is understandable, but limiting access to those registered and identified is a huge barrier to new people so I would use that option sparingly08:38
CyBeRyou would typically want to use such options only *during* an attack and not just in general08:39
CyBeRit also helps a lot to have active moderation, which it appears this channel lacks as I currently see no ops08:39
*** jonathanmaw has joined #buildstream08:39
*** jercos has joined #buildstream08:40
*** armin has joined #buildstream08:40
*** Turandot has joined #buildstream08:40
qinustySpeaking of08:40
KinnisonCyBeR: that requires people to be around when these things happen08:43
KinnisonCyBeR: specifically ops people08:43
Kinnison7364 lines of spam08:43
Kinnisonwow08:43
*** mohan43u has quit IRC08:44
CyBeRyes, it requires you have more than two such people08:44
Kinnisonsorry, maybe 2 fewer08:45
tristanjjardon, I've been seeing #evolution and #gtk+ doing that but only temporarily in times of heavy spam08:45
* Kinnison finds such behaviour very sad on IRC08:45
tristani.e. not because one offending line of text was posted08:45
Kinnison(the spamming, not the limitation)08:45
*** av sets mode: +o jjardon08:47
jjardontristan: we had 7364 lines of spam yesterday, as Kinnison said. They restrict enter the channel or talking in the channel?08:47
tristanjjardon, I've had to sign in on some days just to enter the channel08:48
tristanusually it goes away after a day or two08:48
tristanjjardon, it's a bit of a balance, we dont want people to have to jump through hoops, but we can't endure situations where spam is flooding conversation08:49
KinnisonThat was by far and away the worst IRC spam I've seen in many years though, so hopefully it won't happen again soon08:49
*** jjardon has left #buildstream08:49
*** jjardon has joined #buildstream08:49
*** ChanServ sets mode: +o jjardon08:49
* tristan sees it now in the log08:50
CyBeRthat was the worst I've seen ever08:50
tristanjjardon, I would personally be happier if only voice was restricted08:50
*** mohan43u has joined #buildstream08:51
tristanjjardon, I would also not mind if someone like you or let's say "anyone who develops BuildStream" were to have the power to manually turn it on and off08:51
jjardonYup, me too. Another option is to set limits on messages/joins in a period of time08:52
tristanjjardon, I'm gonna eat lunch, don't block on my opinion to take action :)08:56
gitlab-br-botbuildstream: merge request (valentindavid/498_bwrap_environment->master: Set environment in bwrap command line instead of its environment) #565 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/56508:59
*** tristan has quit IRC09:00
*** tpollard has quit IRC09:08
*** tpollard has joined #buildstream09:08
gitlab-br-botbuildstream: issue #499 ("Progress Report for Large Downloads") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/49909:14
*** flatmush has quit IRC09:23
*** flatmush has joined #buildstream09:24
*** edb has joined #buildstream09:29
gitlab-br-botbuildstream: merge request (Qinusty/491->master: Cache size is now restricted to available disk space) #563 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/56309:36
*** bochecha has joined #buildstream09:39
valentindWas the build artifact merged?09:41
valentindFor freedesktop-sdk I am getting an error with socket files.09:42
qinustyjuergbi: Within the cascache are we intending to raise grpc errors or should these be reraised as ArtifactError? From what I can see, we aren't catching grpc errors outside of cascache.py09:42
valentindFAILURE base/gpgme.bst: Cannot extract /home/valentin/.cache/buildstream/build/base-gpgme-_z05id4i/root/buildstream/base-sdk/base/gpgme.bst/bst_build_dir/tests/gpg/S.gpg-agent into staging-area. Unsupported type.09:42
juergbiqinusty: expected grpc errors should be reraised as ArtifactError09:43
*** tristan has joined #buildstream09:44
gitlab-br-botbuildstream: issue #500 ("While caching build artifact:  "Cannot extract [path to socket file] into staging-area. Unsupported type."") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/50009:44
qinustyOkay, there are one or two reraises of grpc errors I believe. e.g. https://gitlab.com/BuildStream/buildstream/commit/1d36df25de46979245a13f4a9149ca1eec30c4eb#note_9021914509:44
qinustyI am currently working around this area for the retry logic. Should I make the change as part of this MR?09:45
gitlab-br-botbuildstream: merge request (jmac/virtual_directories->master: Abstract directory class and filesystem-backed implementation) #445 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/44509:50
tristanqinusty, I'm missing some context, I suppose the referred, already merged commit needs to print that info message when `e.code() == grpc.StatusCode.NOT_FOUND` (instead of !=... Doh)09:50
tristanqinusty, regarding the MR though, I think it's preferable to not cross subjects and file a separate MR to fix that09:51
qinustySounds good. Yeah I spotted that earlier tristan https://gitlab.com/BuildStream/buildstream/commit/1d36df25de46979245a13f4a9149ca1eec30c4eb#note_90219145 :D09:59
qinustyHmmm, wait. I think I pasted the wrong link for juergbi. I see why the context is confusing now. This is the correct link https://gitlab.com/BuildStream/buildstream/blob/master/buildstream/_artifactcache/cascache.py#L28910:00
qinustyI assumed gitlabs line link automatically clipboarded it, but it just put it in the url10:00
juergbiNOT_FOUND is no error there, that condition shouldn't be changed, afaict10:01
*** edb has quit IRC10:02
gitlab-br-botbuildstream: issue #501 ("Misleading info message for CASCache pull") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/50110:05
*** finn has quit IRC10:07
qinustyI agree juergbi, but when != NOT_FOUND the exception is reraised. Which will cause grpc.RpcError to propagate up and never be handled.10:07
*** finn has joined #buildstream10:08
juergbiright, this means that network errors may end up as BUG10:08
gitlab-br-botbuildstream: issue #502 ("Unhandled excpetions within CASCache on grpc errors") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/50210:13
gitlab-br-botbuildstream: merge request (Qinusty/397->master: WIP: Modify retry behaviour to be opt-in on exceptions during job processing) #559 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/55910:24
qinustytristan: How do I go about working on a fix which relies on another MR? Wait for the MR to hit master?10:26
tristanqinusty, Ummm I'm not sure I understand... how does the fail permanent/temporary stuff depend on the info message in the other commit ?10:27
qinustyWell, what I was referring to with juergbi was https://gitlab.com/BuildStream/buildstream/issues/502 So if I am to add these new ArtifactError calls, they probably want to be temporary.10:28
jmacqinusty: Base your work on the branch in that MR. You can work on it, then when the original MR is merged, rebase your branch10:29
*** edb has joined #buildstream10:29
tristanqinusty, right, what jmac says basically - but if these are as simple fixes as they seem to be, please post quickly and lets merge them quickly10:31
qinustyI agree, I have just pushed to the retry branch with the push/pull change. Besides DownloadableSources and Artifact push/pull, can you think of any other 'temporary' errors?10:32
tristanI'm not sure I understand what juergbi means about NOT_FOUND not being an error; if it's raising an error and a not found artifact causes a BUG, that... seem pretty weird10:32
qinustyI get that. Not found passes through and returns False10:33
tristanI see, ok that makes sense if it does that10:33
qinustyWhereas other exceptions /should/ be raised as ArtifactError, they are currently reraised10:33
*** slaf has quit IRC10:33
tristanqinusty, I can't think of any others really10:33
qinustyAlright, well let's wait on the pipeline and go from there. I'll work on the reraises now10:34
tristanqinusty, as an eventuality, I have another plausible candidate, but it's quite contorted10:34
* tristan searches issue10:34
tristanqinusty, e.g. https://gitlab.com/BuildStream/buildstream/issues/18510:34
tristanqinusty, for instance, if webkit failed it's mega link stage because the host ran out of memory, that could potentially be a temporary error I suppose10:35
tristanbut we don't have fancy ways of determining that at the moment :)10:35
qinustyWell we can always leave a comment in the issue suggesting temporary as a potential future solution10:36
tristanqinusty, I'd rather close the issue as we implemented the supporting framework, and figuring out 185 is reaching for the moon a bit10:36
qinustyFair enough10:37
tristanif we figure out 185, temporary failures will be one of the courses of action which will be at our disposal10:37
qinustyTurned out to be only the one reraise, the other reraise was warranted due to a nested try/catch block10:41
tristanqinusty, fwiw, at least as far as I'm concerned, when it comes to these quick one line patches, it's not really necessary to also open an issue10:43
qinustyAlright, I just threw it up there in case I didn't end up doing it today10:44
tristanif an MR is forthcoming anyway... I don't object to your raising an issue for it but just don't want to generate unnecessary work :)10:44
tristansure :)10:44
qinustyOkay, fix for #502 is ready for when retry lands in master. I'll get that misleading info message stripped out too.10:45
gitlab-br-botbuildstream: merge request (richardmaw/cache-fail->master: WIP: Store failed builds in the cache) #475 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/47510:46
* tristan hunts down the next MR... and is probably not doing reviews in FIFO order...10:47
tristanneed to clear the board haha10:47
gitlab-br-botbuildstream: merge request (richardmaw/cache-fail->master: WIP: Store failed builds in the cache) #475 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/47510:47
qinustyOh wait, https://gitlab.com/BuildStream/buildstream/issues/496 tristan. Opinions? This should really go into the retry patch as it will allow us to retry git clone operations.10:47
tristanqinusty, ohhhhhh I didnt think of that10:48
tristanhmm10:48
qinustyIt is a change to the API, but one I would argue really should be in there since Plugin throws them10:49
tristanqinusty, commenting on the issue... sec...10:50
tristanqinusty, commented... essentially I agree that PluginError being public and having plugins catch/reraise is a possible approach, but I think it goes against the current design10:54
*** slaf has joined #buildstream10:54
*** slaf has joined #buildstream10:54
tristanIf we can have the core do more grunt work, we make life easier for plugins10:54
*** slaf has joined #buildstream10:54
*** slaf has joined #buildstream10:55
qinustyOkay, that seems reasonable10:55
*** slaf has joined #buildstream10:55
qinustyI'll take a look and get it changed10:55
*** slaf has joined #buildstream10:55
tristannote that an additional keyword argument is not an API break, but still an API addition10:55
tristanas such it needs annotation in the docstring10:56
qinustyYup10:56
tristanCurrently we have APIs which add "*Since 1.2*" at the end, but not much prior art I can find for extension of kwargs10:56
tristanqinusty, I think we can add *Since 1.4* at the end of the documentation of the actual kwarg, maybe in parenthesis ?10:58
tristanI think this will be the precedent establishing kwarg addition10:58
qinustySeems reasonable. Will this change to the API go in as part of the retry MR or as it's own?10:59
tristanqinusty, I think that's quite related to the MR so lets keep it with that10:59
qinustyAlright10:59
tristanthe MR adds the temporary failure possibility, so we couldnt really add it separately anyway11:00
qinustyAlso, pipeline failed. Only tests-unix. This has happened a few times over the last 2 days.11:03
qinustyRestarting the test sequence seems to fix it.11:03
qinustyidk if we want to note anything down from it tristan11:03
tpollardthat has happened to me also11:03
qinustytest_build_track seems to occasionally fail11:04
qinustyhttps://gitlab.com/BuildStream/buildstream/-/jobs/8424035311:04
tristanoh damn, ok I think I misread that the other day and it may be a regression from CAS11:07
tristantest_build_track... does this reuse the same git repo for multiple sources ?11:08
* tristan checks11:08
tristanyep, ok so it's the race, I don't understand why we have CAS in the stack trace11:09
tristanright11:10
tristanso this is failing in cli.remove_artifact_from_cache()11:10
tristanand prints an error which seems unrelated11:11
tristanvery strange11:11
qinustyI'm happy to look into it after all of these MRs which are about to land at some point today11:11
tristanqinusty, right; OK I'll take care of filing the issue11:12
qinustyCheers11:12
qinustyI thought it was just me tpollard :P11:13
paulsherwoodis there a buildstream glossary anywhere? if not, should there be?11:14
tpollardqinusty: yeh it passed on a commit, but then failied on the same commit that was just rebased with a different commit message11:15
qinustyAlso tristan: Regarding the kwargs annotation, the current kwargs don't appear to be documented in any docstrings?11:16
toscalixpaulsherwood: it should be, as well as a FAQ11:21
toscalixhopefully will be part of the release. There are quite a few content pages missing11:22
qinustyI agree a glossary would be quite handy. Coming into the project I just slowly absorbed terms through the code base and IRC11:22
toscalixhopefully tomorrow I will start working on the proposal for the release, including the contents11:22
gitlab-br-botbuildstream: issue #503 ("spurious failures in test_build_track") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/50311:26
tristanqinusty, isn't the fail string documented here: https://gitlab.com/BuildStream/buildstream/blob/master/buildstream/plugin.py#L486 ?11:28
qinustyOkay, slightly step back. When you say keyword args you mean fail_temporarily=False, as opposed to kwargs["fail_temporarily"]11:29
tristanqinusty, the way Plugin.call() works is admittedly a bit dirty, we are forwarding the args and kwargs which the caller passed onwards to subprocess APIs, and adding our own kwargs to it11:30
tristanProviding an exhaustive list of kwargs which we support, would be more bullet proof11:31
tristanqinusty, i.e. if that wasnt clear... the "fail" keyword argument is what we add, the popenargs and kwargs are magic things which derive from subprocess python API (which is indeed a dirty trick which could be improved)11:32
qinustyAlright11:32
*** WSalmon has quit IRC11:33
gitlab-br-botbuildstream: issue #504 ("Overview and glossary/dictionary of buildstream terms/meanings") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/50411:35
valentindtristan, so we have found another issue with the old ostree cache. Another reason why ostree is not good for artifact cache. The summary is limited to 10MB. You cannot change that limit. So no matter how much disk you have. If You have more than a certain number of elements, we cannot pull anymore. We have reached it with freedesktop-sdk.11:35
paulsherwoodtoscalix: i have raised 504 as a start11:35
tristanvalentind, interesting that we hit an ostree limitation after having completely moved to CAS11:37
tristanvalentind, I think it's reasonable to say that, we should focus now on making sure CAS is working well11:37
paulsherwood+111:38
paulsherwoodtristan: what's the best way to request/suggest logging improvements, please? i know this is a strangely controversial subject :)11:38
tristanpaulsherwood, heh, ok well now we have configurability in log lines I hope it is less controversial !11:39
tristanpaulsherwood, I would say raise an issue stating the information which is required; the harder question is whether it should be default for end users11:40
paulsherwoodtristan: i think i previously raised one issue with several things about logs... should i do that again, or one issue per thing?11:41
tristan(of course this also depends on whether it even extends the standard log line, or if it is a case of something that can be logged in it's own line)11:41
tristanpaulsherwood, I would prefer individual issues which we can treat and handle separately, but I don't mind doing some triage after an issue is posted11:42
paulsherwoodok11:42
gitlab-br-botbuildstream: merge request (Qinusty/397->master: WIP: Modify retry behaviour to be opt-in on exceptions during job processing) #559 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/55911:53
qinustytristan: https://gitlab.com/BuildStream/buildstream/merge_requests/563 has been reviewed and is ready for review/merge whenever you get a minute. The retry MR should be good to go once the pipeline completes.11:53
jjardontristan: should we declare the bst-1.0 branch as not supported when bst-2.0 is out maybe? as we are not going to maintain the cache server anymore there11:53
gitlab-br-botbuildstream: issue #505 ("Default log behaviour should be useful, easy-to-read with maximum information and minimal waste lines") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/50511:54
juergbivalentind: in case this is still causing issues before transitioning to CAS, you can simply drop the summary file for recent buildstream versions (since May 11)11:54
tristanjjardon, Yes - we haven't really had users of 1.0 as they all relied on 1.1.x11:54
tristanjjardon, note that you mean bst-1.2; bst-2.0 with our versioning semantics would mean a clear API break11:55
gitlab-br-botbuildstream: merge request (501-misleading-info-message-for-cascache-pull->master: WIP: Resolve "Misleading info message for CASCache pull") #566 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/56611:55
jjardontristan: yup sorry, I meant 1.211:55
gitlab-br-botbuildstream: merge request (501-misleading-info-message-for-cascache-pull->master: WIP: Resolve "Misleading info message for CASCache pull") #566 changed state ("closed"): https://gitlab.com/BuildStream/buildstream/merge_requests/56611:56
gitlab-br-botbuildstream: merge request (328-support-for-downloading-sources-from-mirrors->master: Resolve "Support for downloading sources from mirrors") #404 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/40411:56
valentindjuergbi, ostree still tries to download summary when pulling. There is no way to pull at all. Even if you know the ref is there.11:57
tristanvalentind, I think what he means is, on the server it is no longer required to create and update the summary file periodically11:59
tristanvalentind, i.e. you could delete it on the share server and disable the cron job which updates it11:59
valentindtristan, Ah OK. Then that would work yes.11:59
gitlab-br-botbuildstream: merge request (Qinusty/501->master: Remove misleading info message) #567 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/56711:59
tristanthat is ever since the scheduler changes which landed in advance of remote cache cleanup stuff, we no longer predict if an artifact will be accessible at the beginning of a session12:00
valentindBut I think the next time we update the version of builstream is to use CAS.12:01
qinustyhttps://gitlab.com/BuildStream/buildstream/merge_requests/567 Is a oneliner ready for review/merge.12:02
* jonathanmaw has a peek12:03
gitlab-br-botbuildstream: merge request (Qinusty/501->master: Remove misleading info message) #567 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/56712:05
tristando we still have a tlater hanging around ?12:06
gitlab-br-botbuildstream: issue #506 ("Raw logs contain lots of unnecessary progress information") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/50612:08
gitlab-br-botbuildstream: issue #507 ("Some log lines appear to be duplicates") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/50712:10
gitlab-br-botbuildstream: issue #508 ("Empty timestamps") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/50812:10
jonathanmawtristan: tlater's travelling down to London today, iirc12:15
* Kinnison thinks tlater and jennis won't be available today/tomorrow12:16
Kinnisonsorry, not jennis, phildawson12:16
tristanqinusty, I feel like I wish tlater could review and land https://gitlab.com/BuildStream/buildstream/merge_requests/56312:17
tristanqinusty, he would be the most efficient in that area12:17
gitlab-br-botbuildstream: issue #509 ("Wallclock time in logs") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/50912:18
laurencetlater may not have chance today, fyi12:19
laurencehe's down in London12:19
gitlab-br-botbuildstream: issue #509 ("Wallclock time in logs") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/50912:27
gitlab-br-botbuildstream: issue #510 ("message format in user configuration is undocumented") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/51012:32
tristanqinusty, if your merge request closes 501, then please close 50112:34
gitlab-br-botbuildstream: issue #506 ("Raw logs (from GitLab ci) contain lots of unnecessary progress information") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/50612:46
tristantoscalix, I think we should make the "bug" template be the default for filing issues; mostly the people who are familiar with gitlab will know to choose a template, while the majority of users will show up and use the default template to file a bug12:49
tristanI'd like to make the change if that's alright (as I'm seeing bugs filed as tasks...), but need to figure out how12:49
jonathanmawtristan: https://gitlab.com/BuildStream/buildstream/merge_requests/404 is ready for review again, now that I've fixed what was going wrong with the GitSource12:49
tristanjonathanmaw, source mirrors !12:50
tristanjonathanmaw, nice I was looking forward to that... as a side note, remember that newly added API surface needs to advertise the Since version :)12:50
tristannot sure if you did that already, but targeting master should be Since 1.4 (next stable)12:50
* jonathanmaw has not done that12:51
tristanI hope to backport it, once I do that I'll update the since markers to 1.212:51
toscalixtristan: no objection12:57
toscalixbut I think in terms of users we need to look at what we have. Probably for stable branches we will have way more bugs than tasks and for dev could be the other way around.12:58
toscalixit is also true though that community people is more familiar with ticketing systems associated to bugs, not tasks12:59
toscalixwe have a86 bugs out of 583 issues13:00
toscalix186/58313:00
noisecellsome issues could be classify as bugs but need triage, IMO13:01
toscalixand some has no label and some bugs are not bugs... so ignored13:01
toscalixyes, the data could be wrong, but it is a first approach13:02
*** xjuan has joined #buildstream13:02
skullmantoscalix: a template for Feature Request issues may be useful. It's not always easy to rephrase a missing feature as a bug.13:02
toscalixskullman: that will happen13:02
gitlab-br-botbuildstream: issue #501 ("Misleading info message for CASCache pull") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/50113:02
toscalixit is just that I will propose a slightly different process that we have today, as I mentioned by mail13:03
gitlab-br-botbuildstream: merge request (phil/203-BuildStream-crashes-when-dependency-tree-too-deep->master: Phil/203 BuildStream crashes when dependency tree too deep) #512 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/51213:03
toscalixbut yes, we will benefit from having requests that include enough structured information so they are easy to consume13:03
toscalixand a template is the easiest way, as guidance13:04
toscalixskullman: follow this ticket to check progress on that front: https://gitlab.com/BuildStream/nosoftware/alignment/issues/1813:05
toscalixtristan: the default template can be changed in the repo Settings. I would propose it in the mailing list though, sice it was a matter of policy13:08
gitlab-br-botbuildstream: merge request (Qinusty/397->master: WIP: Modify retry behaviour to be opt-in on exceptions during job processing) #559 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/55913:08
tristantoscalix, okay... if you want to bundle that together with proposing an enhancement template, that might get things rolling quicker :)13:10
gitlab-br-botbuildstream: issue #511 ("Fixing VCS reduction") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/51113:10
tristantoscalix, I'll hold off on changing the default; my point of view is mostly that the default should be optimized towards those who are not familiar with the ticketing system and how we use it13:11
toscalixI think it is fine. The numbers are not significant enough for me to object. I understand your point. I will propose it in the list and do it13:12
toscalixtristan: did you receive the mail from gnome sysadmins with the password to the new notification list?13:13
*** xuanrui has joined #buildstream13:17
gitlab-br-botbuildstream: merge request (Qinusty/397->master: WIP: Modify retry behaviour to be opt-in on exceptions during job processing) #559 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/55913:18
gitlab-br-botbuildstream: issue #512 ("Workspace builds are unable to preserve intermediate results not stored in the source directory.") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/51213:20
tlaterAbout the CAS artifact cache - is there a way to update the client certificates while the server is running?13:37
tlaterI.e., could I have a server running and add new users to the system on-the-fly, giving out individual certificates to people?13:37
jmacI don't think so13:39
tlaterHrm, that sounds like a bit of an oversight :| Should I open up an issue?13:40
tristantoscalix, ah yes I did...13:40
jmactlater: Sure.13:41
*** WSalmon has joined #buildstream13:41
tristantoscalix, you and tlater are alread listed as admins there13:42
tristantoscalix, I suppose you need the password, though ?13:42
tristanor, your should have also received an email ? not sure how that works13:42
gitlab-br-botbuildstream: merge request (phil/203-BuildStream-crashes-when-dependency-tree-too-deep->master: Phil/203 BuildStream crashes when dependency tree too deep) #512 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/51213:43
gitlab-br-botbuildstream: merge request (phil/203-BuildStream-crashes-when-dependency-tree-too-deep->master: Phil/203 BuildStream crashes when dependency tree too deep) #512 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/51213:43
toscalixwe need the password13:43
toscalixtristan ^13:43
toscalixI need to configure the list13:43
tristantoscalix, I've sent over through a more secure channel :)13:44
tristanpaulsherwood, thanks for filing all of those separately btw, that was helpful13:49
* tristan tries to focus on jonathanmaw's branch for the last timeslot...13:50
paulsherwoodtristan: np, it helped me too :-)13:54
gitlab-br-botbuildstream: issue #513 ("Allow updating remote cache client certificates without rebooting") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/51313:57
gitlab-br-botbuildstream: merge request (bst_workspace_open_force_does_nothing->master: _stream.py: Added functionality for workspace open -f) #549 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/54914:01
tristantlater, since you seem to have surfaced, do you think you could review https://gitlab.com/BuildStream/buildstream/merge_requests/563 and merge that ?14:05
jjardonsorry, can someone remind me again what is the last commit before mergin the CAS stuff?14:08
gitlab-br-botbuildstream: merge request (bst_workspace_open_force_does_nothing->master: _stream.py: Added functionality for workspace open -f) #549 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/54914:15
tristanjjardon, 4c6512d6f6e4defbddebab56a19e5e7f9e50c20c14:15
gitlab-br-botbuildstream: merge request (bst_workspace_open_force_does_nothing->master: _stream.py: Added functionality for workspace open -f) #549 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/54914:16
tristanjonathanmaw, It appears your commit to the bzr plugin is not really related to source mirroring, or ... is it ?14:16
Nexusdum dum dummmmmm14:16
tristanjonathanmaw, i.e. bzr plugin would be improved by that commit with or without the source mirroring14:16
jonathanmawtristan: the meat of the change to the bzr mirroring changes is in `bzr pull`, where I append the branch url14:18
*** andries has joined #buildstream14:18
jonathanmawsince the url used to create the bzr repository isn't always the same as the one used when fetching14:18
tristanjonathanmaw, alright, was just curious14:22
jjardontristan: tvm14:23
jjardontristan: would it be possible to tag that commit?14:24
tristanjjardon, you really have a use case for a PRE_CAS_CACHE kind of tag ?14:29
tristanjjardon, I mean, it seems it will be useful for a very temporary period of time hehe14:29
jjardontristan: all the users of buildstream I know are using a pre CAS cache commit14:30
jjardonwe can not upgrade until we upgrade the cache servers14:30
jjardonso it would be helpful for now so I do not have to ask again :)14:31
gitlab-br-botbuildstream: issue #514 ("BuildStream CI is not configured to perform any system level testing") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/51414:32
tristanjjardon, Ok, following the naming convention of another tag I see there, I will call it PRE_CAS_MERGE_JULY_201814:34
jjardontristan: tvm14:35
tristanjjardon, tag is up now14:35
tlatertristan: I'll take a look - I resurfaced mostly to raise an issue, but might have enough time now :)14:38
tristantlater, if you could do that today or tmw that can free me up a bit14:40
tristanif not, I'll get back to it :)14:40
tristanI would like to have it checked by you, though14:40
tlaterDefinitely will have time at some point today/tomorrw14:41
tlaterI've had a look before, thought jennis was handling it14:41
WSalmonI am looking at the doc's in line with kinnison's comments and i have found that sphinx renders -- differently if it is in a "paragraph" or a indented out quote.14:45
WSalmoni there a way we have decided to do --option in paragraphs that only some people are following or shall i sort something and put in a MR and we can review decide that way?14:46
WSalmoni will probs go with ``--option`` but then you get a anoying box around the hole "--option" but that looks like the least worst i have found so far14:48
Kinnison`` is for code samples14:48
gitlab-br-botbuildstream: merge request (Qinusty/491->master: Cache size is now restricted to available disk space) #563 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/56314:49
KinnisonYou might find :literal:`--option` works better, but it'll depend on how sphinx sets up the rST roles14:50
WSalmonthat still seems to put a equally ugly box in but if thats the better practice i will use that.14:52
tristanKinnison, WSalmon ... from what I've been understanding: .. code:: python  blocks are for code samples14:53
tristanAnd ``pony`` is for literals14:53
Kinnisontristan: yeah but `` seems to syntax hilight as though it were python14:54
tristanHowever, I should note that I am also peeved that since we changed the theme, they started appearing with the obnoxious boxes14:54
tlaterThanks qinusty - patch looks great, I think you cleaned up some stupidly expressed logic :)14:54
tristanSo, since we've got a lot of code which assumes ``pony`` to be literals... I think it might be better to tweak the theme ?14:54
qinustyCheers, just making the changes you suggested. As for the headroom documentation, There is an issue at https://gitlab.com/BuildStream/buildstream/issues/49714:55
tristanrather than chasing down everything ? it's worth a double check into what the rst syntax wants it to mean, that would be another deciding factor14:55
coldtomI need to install a .ttf file using buildstream, is there a way to do this from a remote source or do i have to download the file?14:57
tlaterqinusty: I'm aware of the docs, mostly concerned about showing a less confusing warning14:58
toscalixnew notifications mailing list: https://mail.gnome.org/archives/buildstream-list/2018-July/msg00057.html14:58
tlaterPreferably that warning is vague about *why* you need at least 2 GB14:58
tlaterBecause the actual reason is just confusing14:58
qinustyI realised I had misread :P I am now adding that14:59
* tlater probably heads off for the rest of the day - I'll be back tomorrow if anyone needs me :)15:00
qinustyOn a related note tlater. In the error message, it tells you your available system storage (currently with the headroom taken into consideration)15:00
gitlab-br-botbuildstream: merge request (bst_workspace_open_force_does_nothing->master: _stream.py: Added functionality for workspace open -f) #549 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/54915:01
tristanjonathanmaw, I think I'm done commenting for today, and think we're getting very close to merge this monster branch !15:01
*** tristan has quit IRC15:07
gitlab-br-botbuildstream: merge request (Qinusty/491->master: Cache size is now restricted to available disk space) #563 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/56315:12
laurenceqinusty, wrt https://gitlab.com/BuildStream/buildstream/merge_requests/559#note_9028891815:15
laurenceif all of your ToDo's are completed for that patch, it's worth taking the WIP off15:15
laurence(and prodding the reviewer again)15:16
qinustyAh yes, I was just waiting on the pipeline to pass :) I think we've got everything in there now15:16
*** tristan has joined #buildstream15:16
qinustyPipeline failed 3/4 times due to this spurious failing test https://gitlab.com/BuildStream/buildstream/issues/50315:17
gitlab-br-botbuildstream: merge request (phil/437-junction-tutorial->master: Phil/437 junction tutorial) #550 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/55015:20
laurenceqinusty, aha, i may have been hasty :)15:21
laurenceso that's the bug in the test rather than the code is it?15:21
laurencecode in the patch *15:21
qinustyTristan believes it is. It is reported on several branches including one from tpollard15:22
*** edb has quit IRC15:22
gitlab-br-botbuildstream: merge request (Qinusty/397->master: Modify retry behaviour to be opt-in on exceptions during job processing) #559 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/55915:23
gitlab-br-botbuildstream: issue #515 ("`bst push` will report success even if the local artifacts don't exist (and therefore aren't pushed)") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/51515:25
gitlab-br-botbuildstream: merge request (phil/437-junction-tutorial->master: Phil/437 junction tutorial) #550 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/55015:47
tlaterGrr, can't catch a break with these issues today. In https://buildstream.gitlab.io/buildstream/install_artifacts.html#serve-the-cache-over-https, why do we need to add the user certificate to a file in /home/artifacts/authorized.crt15:47
tlaterAs far as I can tell, we don't even need a specific user anymore15:48
tlaterSo why this random default file?15:48
tlaterAh, sorry, this is the actual heading: https://buildstream.gitlab.io/buildstream/install_artifacts.html#authenticating-users15:49
gitlab-br-botbuildstream: merge request (tpollard/386->master: _frontend: Don't print failure summary on build success) #561 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/56115:49
juergbitlater: not needed but we still recommend it: https://buildstream.gitlab.io/buildstream/install_artifacts.html#setting-up-the-user15:50
gitlab-br-botbuildstream: merge request (tpollard/386->master: _frontend: Don't print failure summary on build success) #561 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/56115:50
juergbiadmins can use other means of isolation but those people should be able to adapt things accordingly with ease15:50
tiagogomesRegarding logging, I am unhappy that bst shows the shell commands executed by default15:51
tlaterjuergbi: That's fair, but why do we need to cat anything to ~/authorized.crt?15:51
juergbitlater: the server needs this file. what else do you recommend for the documentation?15:52
tlaterHuh15:52
juergbi--client-certs authorized.crt15:53
tlaterAh!15:53
tlaterRifht15:53
tlater*right15:53
tlaterSorry, I misread. This is a bit more turorial-ey than I thought15:53
tlaterThanks!15:53
juergbiimprovements welcome, of course, I'm not necessarily good at writing docs15:54
tlaterjuergbi: The only thing I'd improve is make that --client-certs path absolute15:54
gitlab-br-botbuildstream: merge request (tpollard/386->master: _frontend: Don't print failure summary on build success) #561 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/56115:54
tlaterSo that it matches with where you cat to15:54
gitlab-br-botbuildstream: merge request (Qinusty/491->master: Cache size is now restricted to available disk space) #563 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/56315:55
tlaterI'll fix that when I get time for it. Documentation is great otherwise, this just confused me a bit :)15:55
juergbicould make sense but then I wonder whether we should do the same for the other relative paths15:55
tpollardbah, sorry for making the bot spam, I forgot the MR was tracking a branch I was rebasing15:56
tlaterHm, for consistency that would make sense.15:56
juergbialternatively, use relative path also for the >> line15:57
gitlab-br-botbuildstream: merge request (phil/437-junction-tutorial->master: WIP: Phil/437 junction tutorial) #550 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/55015:59
jennisWe should have an image which is a terminal screenshot of `bst build ELEMENT`, which shows a pipeline with some "cached" elements, some "fetch needed" some "waiting", etc, with arrows pointing to different parts of the screenshot... Thoughts?16:38
jennisSomething that can live in the docs16:39
jennisI still don't know what the numbers after the project name refer too16:39
jmacWhich project name?16:40
jennisSo when you run `bst build ELEMENT`, you'll get a ======= TIMER project-name (1/20) ======= on your terminal, for example16:42
jennisthat 1/20 is a mystery to me16:42
jennishttps://snag.gy/7GQcTp.jpg16:45
jennisThis ^16:45
*** flatmush has quit IRC16:45
tiagogomesThumbs up for anything that helps demystifying the BuildStream log16:47
gitlab-br-botbuildstream: merge request (328-support-for-downloading-sources-from-mirrors->master: Resolve "Support for downloading sources from mirrors") #404 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/40416:47
qinustyagreed tiagogomes, screenshots always help jennis16:54
qinustyHowever they come with the overhead of updating them whenever the log format changes. They're harmful if out of date :/16:55
* qinusty is unable to reproduce random failing test locally :(16:56
gitlab-br-botbuildstream: merge request (tpollard/386->master: _frontend: Don't print failure summary on build success) #561 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/56117:00
*** qinusty has quit IRC17:04
*** flatmush has joined #buildstream17:11
juergbijennis: the first number is the number of elements in the build plan and the second number is the number of elements loaded17:11
juergbiaka as session_elements and total_elements in Stream17:14
*** toscalix has quit IRC17:15
*** jonathanmaw has quit IRC17:39
tristantiagogomes, regarding showing shell commands, I half agree, there is a back story and possibly a regression17:45
tristantiagogomes, --verbose/--no-verbose is basically not being used, and I think doesnt do anymore what I originally intended; when not in verbose mode, none of the STATUS messages should appear at all17:46
tristanbut I do think that verbosity enabled by default is the correct default17:46
tristanit should still be overrideable in the user config and CLI17:47
tristanI should clarify further what juergbi said I think: The intention is to show the total number of elements which need to be processed, vs the number of elements which need processing in this session17:54
tristanwhich is useful, but not always easy to calculate, what with potential downloads which might happen, etc17:54
gitlab-br-botbuildstream: merge request (chandan/sourcetransform->master: WIP: Allow source plugins to access previous sources) #568 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/56818:56
gitlab-br-botbuildstream: merge request (chandan/sourcetransform->master: WIP: Allow source plugins to access previous sources) #568 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/56818:57
gitlab-br-botbuildstream: merge request (chandan/sourcetransform->master: WIP: Allow source plugins to access previous sources) #568 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/56818:59
*** ernestask has quit IRC19:37
gitlab-br-botbuildstream: merge request (edbaunton/remote-source->master: Add remote source plugin) #541 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/54119:43
gitlab-br-botbuildstream: merge request (edbaunton/remote-source->master: Add remote source plugin) #541 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/54119:44
*** xjuan has quit IRC20:49
*** tristan has quit IRC21:17
*** bochecha has quit IRC21:42

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!