hipp__ | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 |
---|---|---|
hipp__ | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
Guest89349 | 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 |
neptune | or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/ | 00:00 |
clorophormo | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
richvdh | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 |
richvdh | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
October | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 |
October | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00: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/Freenodegate | 00:00 |
Taylor_ | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 |
Guest89349_ | or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/ | 00:00 |
*** sirnaysayer has quit IRC | 00: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=#freenode | 00:00 |
rosseaux | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
april | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
KindOne | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
*** sirnaysayer_ has quit IRC | 00:00 | |
richvdh_ | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
clorophormo_ | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
October_ | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
april__ | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
KindOne_ | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
april_ | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
-siinus`- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
Guest89349__ | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 |
neptune__ | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 |
*** Pici_ has quit IRC | 00:00 | |
rosseaux_ | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
KindOne__ | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00: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 IRC | 00:00 | |
Texou_ | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 |
lostlabyrinth | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 |
this | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 |
lostlabyrinth_ | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 |
this_ | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 |
Cork___ | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 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 | |
ArsenArsen | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 |
ArsenArsen | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
Texou__ | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00: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 | |
Peng | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
slackjeff | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
c0ded | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
Peng_ | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00: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 | |
host | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
Zx3 | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
*** hipp_ has quit IRC | 00: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=#freenode | 00:00 |
Taylor | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
-joepie91__- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
janus | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 |
berndj | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 |
Adbray_ | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
Cork__ | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
*** jrabe_ has quit IRC | 00: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 IRC | 00:00 | |
-Dan_Bennett- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
host__ | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00: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/Freenodegate | 00:00 | |
*** Taylor__ has quit IRC | 00:00 | |
Peng__ | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 |
Zx3__ | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
*** Taylor has quit IRC | 00:00 | |
-xunplini__- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
-Ishaq- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
averell | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 |
-xunplini- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00: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/Freenodegate | 00:00 | |
-rdococ- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
-loeken- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
*** host__ has quit IRC | 00: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 IRC | 00:00 | |
-caf- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
*** Dan_Bennett has quit IRC | 00:00 | |
*** Zx3__ has quit IRC | 00:00 | |
*** Taylor_ has quit IRC | 00:00 | |
neptune | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 |
*** Randy has quit IRC | 00:00 | |
host_ | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
*** joepie91__ has quit IRC | 00:00 | |
averell_ | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 |
Guest89349 | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 |
Guest89349 | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00: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/Freenodegate | 00:00 |
*** Frosty_ has quit IRC | 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 | |
-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 IRC | 00:00 | |
*** clorophormo has quit IRC | 00:00 | |
*** richvdh has quit IRC | 00: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/Freenodegate | 00:00 |
Guest89349_ | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 |
Guest89349_ | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
*** wiggle has quit IRC | 00:00 | |
*** host has quit IRC | 00:00 | |
-jrabe___- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
*** October has quit IRC | 00: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 IRC | 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 | |
*** Kraps_ has quit IRC | 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 | |
*** xunplini__ has quit IRC | 00:00 | |
*** Randy_ has quit IRC | 00:00 | |
*** Ishaq has quit IRC | 00:00 | |
*** xunplini has quit IRC | 00:00 | |
*** rdococ has quit IRC | 00:00 | |
*** `d has quit IRC | 00:00 | |
Guest89349__ | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
neptune__ | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
*** loeken has quit IRC | 00:00 | |
*** host_ has quit IRC | 00:00 | |
this | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
lostlabyrinth | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
*** DarthGandalf has joined #buildstream | 00:00 | |
DarthGandalf | Hey, 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 #buildstream | 00:00 | |
cfields | Hey, 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=#freenode | 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 | |
*** HarryCross2 has joined #buildstream | 00:00 | |
HarryCross2 | Hey, 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=#freenode | 00:00 |
lostlabyrinth_ | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00: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 IRC | 00:00 | |
Texou__ | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00: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 IRC | 00:00 | |
Peng_ | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 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 | |
-ikevin_- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/ | 00:00 | |
janus | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
berndj | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00: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=#freenode | 00: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 | |
averell | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
averell___ | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 |
-SolarAquarion- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/ | 00:00 | |
*** BurningPrincess has quit IRC | 00:00 | |
-digitalcold- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/ | 00:00 | |
*** jrabe___ has quit IRC | 00: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 IRC | 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 | |
*** Kraps has quit IRC | 00: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 | |
iczero | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 |
*** dan- has quit IRC | 00:00 | |
Texou___ | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 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 | |
-caf_- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
*** caf_ has quit IRC | 00:00 | |
-bolt- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
*** bolt has quit IRC | 00:00 | |
neptune | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
*** ikevin_ has quit IRC | 00:00 | |
-iczero_- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
*** iczero_ has quit IRC | 00:00 | |
averell_ | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
*** digitalcold has quit IRC | 00:00 | |
*** Pici has quit IRC | 00:00 | |
neptune_ | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
*** Cork_ has quit IRC | 00:00 | |
*** ikevin has quit IRC | 00: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=#freenode | 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 | |
*** hipp has quit IRC | 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 | |
iczero | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 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 | |
-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 | |
DarthGandalf | or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/ | 00:00 |
cfields | or 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 IRC | 00:00 | |
HarryCross2 | or 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 IRC | 00:00 | |
averell___ | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 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 | |
*** c0ded has quit IRC | 00:00 | |
*** ArsenArsen has quit IRC | 00: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=#freenode | 00: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 IRC | 00: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 IRC | 00:00 | |
*** KindOne_ has quit IRC | 00: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/Freenodegate | 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 | |
-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/Freenodegate | 00:00 | |
-rosseaux- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
-KindOne- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00: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 | |
DarthGandalf | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 |
cfields | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00: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/Freenodegate | 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 | |
HarryCross2 | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 |
-clorophormo_- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
-October_- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
*** hipp__ has quit IRC | 00:00 | |
-Texou__- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/ | 00:00 | |
*** Peng_ has quit IRC | 00:00 | |
-april_- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
-april__- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
-rosseaux_- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
-KindOne__- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
-Cork___- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00: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/Freenodegate | 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 | |
-neptune- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/ | 00:00 | |
*** KindOne has quit IRC | 00:00 | |
*** april has quit IRC | 00:00 | |
*** rosseaux has quit IRC | 00: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/Freenodegate | 00:00 | |
-neptune_- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/ | 00:00 | |
*** iczero has quit IRC | 00:00 | |
-averell__- or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/ | 00:00 | |
*** richvdh_ has quit IRC | 00:00 | |
*** clorophormo_ has quit IRC | 00:00 | |
*** October_ has quit IRC | 00:00 | |
-Guest89349- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
*** april__ has quit IRC | 00:00 | |
*** april_ has quit IRC | 00:00 | |
*** rosseaux_ has quit IRC | 00:00 | |
*** KindOne__ has quit IRC | 00:00 | |
*** Cork___ has quit IRC | 00:00 | |
-Guest89349_- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
*** Peng has quit IRC | 00:00 | |
cfields | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
DarthGandalf | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
HarryCross2 | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 00:00 |
-neptune__- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
-Guest89349__- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
-this- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
-lostlabyrinth- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
-Texou_- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
-this_- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
-lostlabyrinth_- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
-Texou__- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
*** Guest89349 has quit IRC | 00: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/Freenodegate | 00:00 | |
*** janus has quit IRC | 00:00 | |
-berndj- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
*** berndj has quit IRC | 00:00 | |
*** Guest89349_ has quit IRC | 00:00 | |
-Peng__- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
-averell- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
*** averell has quit IRC | 00:00 | |
*** Peng__ has quit IRC | 00:00 | |
-neptune- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
*** neptune has quit IRC | 00:00 | |
-averell_- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
*** averell_ has quit IRC | 00:00 | |
-neptune_- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
*** neptune_ has quit IRC | 00:00 | |
*** neptune__ has quit IRC | 00:00 | |
*** Guest89349__ has quit IRC | 00:00 | |
-averell__- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:00 | |
*** averell__ has quit IRC | 00:00 | |
*** this has quit IRC | 00:01 | |
*** lostlabyrinth has quit IRC | 00:01 | |
*** Texou_ has quit IRC | 00:01 | |
*** this_ has quit IRC | 00:01 | |
*** lostlabyrinth_ has quit IRC | 00:01 | |
*** Texou__ has quit IRC | 00: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/Freenodegate | 00:01 | |
*** averell___ has quit IRC | 00:01 | |
-Texou___- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:01 | |
*** Texou___ has quit IRC | 00: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/Freenodegate | 00:01 | |
-DarthGandalf- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:01 | |
*** DarthGandalf has quit IRC | 00:01 | |
*** cfields has quit IRC | 00:01 | |
-HarryCross2- Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:01 | |
*** HarryCross2 has quit IRC | 00:01 | |
*** nikow has quit IRC | 00:01 | |
*** Kronuz has joined #buildstream | 00:01 | |
Kronuz | Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/ | 00:01 |
Kronuz | or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/ | 00:01 |
Kronuz | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 00:01 |
*** Kronuz has quit IRC | 00:05 | |
*** l4z4i has joined #buildstream | 01:41 | |
l4z4i | Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/ | 01:41 |
l4z4i | or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/ | 01:41 |
*** enyc has joined #buildstream | 01:41 | |
enyc | Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/ | 01:41 |
enyc | or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/ | 01:41 |
l4z4i | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 01:41 |
enyc | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 01:41 |
enyc | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 01:41 |
l4z4i | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 01:41 |
*** Dan_Bennett has joined #buildstream | 01:41 | |
Dan_Bennett | Hey, I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/ | 01:41 |
Dan_Bennett | or maybe this blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/ | 01:41 |
Dan_Bennett | Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate | 01:41 |
Dan_Bennett | Voice your opinions at https://webchat.freenode.net/?channels=#freenode | 01:41 |
*** Dan_Bennett has quit IRC | 01:42 | |
*** l4z4i has quit IRC | 01:42 | |
*** enyc has quit IRC | 01:42 | |
*** leopi has joined #buildstream | 02:34 | |
*** leopi has quit IRC | 03:00 | |
*** leopi has joined #buildstream | 03:51 | |
*** mohan43u has quit IRC | 05:15 | |
*** mohan43u has joined #buildstream | 05:19 | |
*** ernestask has joined #buildstream | 05:35 | |
paulsherwood | this is a bit much, now | 06:25 |
*** WSalmon has joined #buildstream | 07:25 | |
*** noisecell has joined #buildstream | 07:42 | |
*** Kinnison has quit IRC | 07:48 | |
*** Kinnison has joined #buildstream | 07:48 | |
*** coldtom has joined #buildstream | 07:53 | |
*** tristan has joined #buildstream | 07:58 | |
*** qinusty has joined #buildstream | 08:00 | |
gitlab-br-bot | buildstream: issue #498 ("Cannot set LD_LIBRARY_PATH") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/498 | 08:11 |
gitlab-br-bot | buildstream: 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/565 | 08:18 |
gitlab-br-bot | buildstream: 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/565 | 08:19 |
gitlab-br-bot | buildstream: 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/565 | 08:20 |
jjardon | Not 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 spam | 08:27 | |
Kinnison | The 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-identify | 08:30 |
*** leopi has quit IRC | 08:30 | |
* Kinnison ended up leaving every such channel on another network because it was unreliable | 08:31 | |
CyBeR | also it's a bit of an overreaction | 08:31 |
jjardon | Kinnison: yeah, I had that problem before too. What about only restrict the ability to talk in the channel? Reentering would not be a problem | 08:32 |
Kinnison | That is less painful | 08:32 |
* Kinnison wonders if those joined via matrix? are able to register | 08:33 | |
* Kinnison doesn't know if the gimpnet servers support that kind of restriction though | 08:33 | |
jjardon | Yeah, I'm registered through matrix; I will ask about the other restriction | 08:34 |
*** toscalix has joined #buildstream | 08:34 | |
CyBeR | honestly 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 |
jjardon | CyBeR: not need to send any email to register your nickname | 08:36 |
CyBeR | I think you're missing my point | 08:36 |
jjardon | Probably | 08:36 |
*** tiagogomes has quit IRC | 08:37 | |
Kinnison | CyBeR: to be fair, that was a *lot* of spam which means any conversation which happened before it is effectively lost in scrollback | 08:37 |
*** tiagogomes has joined #buildstream | 08:37 | |
* Kinnison understands jjardon's desire to prevent that | 08:37 | |
CyBeR | that is understandable, but limiting access to those registered and identified is a huge barrier to new people so I would use that option sparingly | 08:38 |
CyBeR | you would typically want to use such options only *during* an attack and not just in general | 08:39 |
CyBeR | it also helps a lot to have active moderation, which it appears this channel lacks as I currently see no ops | 08:39 |
*** jonathanmaw has joined #buildstream | 08:39 | |
*** jercos has joined #buildstream | 08:40 | |
*** armin has joined #buildstream | 08:40 | |
*** Turandot has joined #buildstream | 08:40 | |
qinusty | Speaking of | 08:40 |
Kinnison | CyBeR: that requires people to be around when these things happen | 08:43 |
Kinnison | CyBeR: specifically ops people | 08:43 |
Kinnison | 7364 lines of spam | 08:43 |
Kinnison | wow | 08:43 |
*** mohan43u has quit IRC | 08:44 | |
CyBeR | yes, it requires you have more than two such people | 08:44 |
Kinnison | sorry, maybe 2 fewer | 08:45 |
tristan | jjardon, I've been seeing #evolution and #gtk+ doing that but only temporarily in times of heavy spam | 08:45 |
* Kinnison finds such behaviour very sad on IRC | 08:45 | |
tristan | i.e. not because one offending line of text was posted | 08:45 |
Kinnison | (the spamming, not the limitation) | 08:45 |
*** av sets mode: +o jjardon | 08:47 | |
jjardon | tristan: we had 7364 lines of spam yesterday, as Kinnison said. They restrict enter the channel or talking in the channel? | 08:47 |
tristan | jjardon, I've had to sign in on some days just to enter the channel | 08:48 |
tristan | usually it goes away after a day or two | 08:48 |
tristan | jjardon, 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 conversation | 08:49 |
Kinnison | That was by far and away the worst IRC spam I've seen in many years though, so hopefully it won't happen again soon | 08:49 |
*** jjardon has left #buildstream | 08:49 | |
*** jjardon has joined #buildstream | 08:49 | |
*** ChanServ sets mode: +o jjardon | 08:49 | |
* tristan sees it now in the log | 08:50 | |
CyBeR | that was the worst I've seen ever | 08:50 |
tristan | jjardon, I would personally be happier if only voice was restricted | 08:50 |
*** mohan43u has joined #buildstream | 08:51 | |
tristan | jjardon, 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 off | 08:51 |
jjardon | Yup, me too. Another option is to set limits on messages/joins in a period of time | 08:52 |
tristan | jjardon, I'm gonna eat lunch, don't block on my opinion to take action :) | 08:56 |
gitlab-br-bot | buildstream: 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/565 | 08:59 |
*** tristan has quit IRC | 09:00 | |
*** tpollard has quit IRC | 09:08 | |
*** tpollard has joined #buildstream | 09:08 | |
gitlab-br-bot | buildstream: issue #499 ("Progress Report for Large Downloads") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/499 | 09:14 |
*** flatmush has quit IRC | 09:23 | |
*** flatmush has joined #buildstream | 09:24 | |
*** edb has joined #buildstream | 09:29 | |
gitlab-br-bot | buildstream: 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/563 | 09:36 |
*** bochecha has joined #buildstream | 09:39 | |
valentind | Was the build artifact merged? | 09:41 |
valentind | For freedesktop-sdk I am getting an error with socket files. | 09:42 |
qinusty | juergbi: 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.py | 09:42 |
valentind | FAILURE 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 |
juergbi | qinusty: expected grpc errors should be reraised as ArtifactError | 09:43 |
*** tristan has joined #buildstream | 09:44 | |
gitlab-br-bot | buildstream: 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/500 | 09:44 |
qinusty | Okay, there are one or two reraises of grpc errors I believe. e.g. https://gitlab.com/BuildStream/buildstream/commit/1d36df25de46979245a13f4a9149ca1eec30c4eb#note_90219145 | 09:44 |
qinusty | I am currently working around this area for the retry logic. Should I make the change as part of this MR? | 09:45 |
gitlab-br-bot | buildstream: merge request (jmac/virtual_directories->master: Abstract directory class and filesystem-backed implementation) #445 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/445 | 09:50 |
tristan | qinusty, 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 |
tristan | qinusty, regarding the MR though, I think it's preferable to not cross subjects and file a separate MR to fix that | 09:51 |
qinusty | Sounds good. Yeah I spotted that earlier tristan https://gitlab.com/BuildStream/buildstream/commit/1d36df25de46979245a13f4a9149ca1eec30c4eb#note_90219145 :D | 09:59 |
qinusty | Hmmm, 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#L289 | 10:00 |
qinusty | I assumed gitlabs line link automatically clipboarded it, but it just put it in the url | 10:00 |
juergbi | NOT_FOUND is no error there, that condition shouldn't be changed, afaict | 10:01 |
*** edb has quit IRC | 10:02 | |
gitlab-br-bot | buildstream: issue #501 ("Misleading info message for CASCache pull") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/501 | 10:05 |
*** finn has quit IRC | 10:07 | |
qinusty | I 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 #buildstream | 10:08 | |
juergbi | right, this means that network errors may end up as BUG | 10:08 |
gitlab-br-bot | buildstream: issue #502 ("Unhandled excpetions within CASCache on grpc errors") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/502 | 10:13 |
gitlab-br-bot | buildstream: 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/559 | 10:24 |
qinusty | tristan: How do I go about working on a fix which relies on another MR? Wait for the MR to hit master? | 10:26 |
tristan | qinusty, 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 |
qinusty | Well, 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 |
jmac | qinusty: Base your work on the branch in that MR. You can work on it, then when the original MR is merged, rebase your branch | 10:29 |
*** edb has joined #buildstream | 10:29 | |
tristan | qinusty, right, what jmac says basically - but if these are as simple fixes as they seem to be, please post quickly and lets merge them quickly | 10:31 |
qinusty | I 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 |
tristan | I'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 weird | 10:32 |
qinusty | I get that. Not found passes through and returns False | 10:33 |
tristan | I see, ok that makes sense if it does that | 10:33 |
qinusty | Whereas other exceptions /should/ be raised as ArtifactError, they are currently reraised | 10:33 |
*** slaf has quit IRC | 10:33 | |
tristan | qinusty, I can't think of any others really | 10:33 |
qinusty | Alright, well let's wait on the pipeline and go from there. I'll work on the reraises now | 10:34 |
tristan | qinusty, as an eventuality, I have another plausible candidate, but it's quite contorted | 10:34 |
* tristan searches issue | 10:34 | |
tristan | qinusty, e.g. https://gitlab.com/BuildStream/buildstream/issues/185 | 10:34 |
tristan | qinusty, 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 suppose | 10:35 |
tristan | but we don't have fancy ways of determining that at the moment :) | 10:35 |
qinusty | Well we can always leave a comment in the issue suggesting temporary as a potential future solution | 10:36 |
tristan | qinusty, I'd rather close the issue as we implemented the supporting framework, and figuring out 185 is reaching for the moon a bit | 10:36 |
qinusty | Fair enough | 10:37 |
tristan | if we figure out 185, temporary failures will be one of the courses of action which will be at our disposal | 10:37 |
qinusty | Turned out to be only the one reraise, the other reraise was warranted due to a nested try/catch block | 10:41 |
tristan | qinusty, 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 issue | 10:43 |
qinusty | Alright, I just threw it up there in case I didn't end up doing it today | 10:44 |
tristan | if 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 |
tristan | sure :) | 10:44 |
qinusty | Okay, 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-bot | buildstream: merge request (richardmaw/cache-fail->master: WIP: Store failed builds in the cache) #475 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/475 | 10:46 |
* tristan hunts down the next MR... and is probably not doing reviews in FIFO order... | 10:47 | |
tristan | need to clear the board haha | 10:47 |
gitlab-br-bot | buildstream: merge request (richardmaw/cache-fail->master: WIP: Store failed builds in the cache) #475 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/475 | 10:47 |
qinusty | Oh 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 |
tristan | qinusty, ohhhhhh I didnt think of that | 10:48 |
tristan | hmm | 10:48 |
qinusty | It is a change to the API, but one I would argue really should be in there since Plugin throws them | 10:49 |
tristan | qinusty, commenting on the issue... sec... | 10:50 |
tristan | qinusty, 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 design | 10:54 |
*** slaf has joined #buildstream | 10:54 | |
*** slaf has joined #buildstream | 10:54 | |
tristan | If we can have the core do more grunt work, we make life easier for plugins | 10:54 |
*** slaf has joined #buildstream | 10:54 | |
*** slaf has joined #buildstream | 10:55 | |
qinusty | Okay, that seems reasonable | 10:55 |
*** slaf has joined #buildstream | 10:55 | |
qinusty | I'll take a look and get it changed | 10:55 |
*** slaf has joined #buildstream | 10:55 | |
tristan | note that an additional keyword argument is not an API break, but still an API addition | 10:55 |
tristan | as such it needs annotation in the docstring | 10:56 |
qinusty | Yup | 10:56 |
tristan | Currently we have APIs which add "*Since 1.2*" at the end, but not much prior art I can find for extension of kwargs | 10:56 |
tristan | qinusty, I think we can add *Since 1.4* at the end of the documentation of the actual kwarg, maybe in parenthesis ? | 10:58 |
tristan | I think this will be the precedent establishing kwarg addition | 10:58 |
qinusty | Seems reasonable. Will this change to the API go in as part of the retry MR or as it's own? | 10:59 |
tristan | qinusty, I think that's quite related to the MR so lets keep it with that | 10:59 |
qinusty | Alright | 10:59 |
tristan | the MR adds the temporary failure possibility, so we couldnt really add it separately anyway | 11:00 |
qinusty | Also, pipeline failed. Only tests-unix. This has happened a few times over the last 2 days. | 11:03 |
qinusty | Restarting the test sequence seems to fix it. | 11:03 |
qinusty | idk if we want to note anything down from it tristan | 11:03 |
tpollard | that has happened to me also | 11:03 |
qinusty | test_build_track seems to occasionally fail | 11:04 |
qinusty | https://gitlab.com/BuildStream/buildstream/-/jobs/84240353 | 11:04 |
tristan | oh damn, ok I think I misread that the other day and it may be a regression from CAS | 11:07 |
tristan | test_build_track... does this reuse the same git repo for multiple sources ? | 11:08 |
* tristan checks | 11:08 | |
tristan | yep, ok so it's the race, I don't understand why we have CAS in the stack trace | 11:09 |
tristan | right | 11:10 |
tristan | so this is failing in cli.remove_artifact_from_cache() | 11:10 |
tristan | and prints an error which seems unrelated | 11:11 |
tristan | very strange | 11:11 |
qinusty | I'm happy to look into it after all of these MRs which are about to land at some point today | 11:11 |
tristan | qinusty, right; OK I'll take care of filing the issue | 11:12 |
qinusty | Cheers | 11:12 |
qinusty | I thought it was just me tpollard :P | 11:13 |
paulsherwood | is there a buildstream glossary anywhere? if not, should there be? | 11:14 |
tpollard | qinusty: yeh it passed on a commit, but then failied on the same commit that was just rebased with a different commit message | 11:15 |
qinusty | Also tristan: Regarding the kwargs annotation, the current kwargs don't appear to be documented in any docstrings? | 11:16 |
toscalix | paulsherwood: it should be, as well as a FAQ | 11:21 |
toscalix | hopefully will be part of the release. There are quite a few content pages missing | 11:22 |
qinusty | I agree a glossary would be quite handy. Coming into the project I just slowly absorbed terms through the code base and IRC | 11:22 |
toscalix | hopefully tomorrow I will start working on the proposal for the release, including the contents | 11:22 |
gitlab-br-bot | buildstream: issue #503 ("spurious failures in test_build_track") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/503 | 11:26 |
tristan | qinusty, isn't the fail string documented here: https://gitlab.com/BuildStream/buildstream/blob/master/buildstream/plugin.py#L486 ? | 11:28 |
qinusty | Okay, slightly step back. When you say keyword args you mean fail_temporarily=False, as opposed to kwargs["fail_temporarily"] | 11:29 |
tristan | qinusty, 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 it | 11:30 |
tristan | Providing an exhaustive list of kwargs which we support, would be more bullet proof | 11:31 |
tristan | qinusty, 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 |
qinusty | Alright | 11:32 |
*** WSalmon has quit IRC | 11:33 | |
gitlab-br-bot | buildstream: issue #504 ("Overview and glossary/dictionary of buildstream terms/meanings") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/504 | 11:35 |
valentind | tristan, 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 |
paulsherwood | toscalix: i have raised 504 as a start | 11:35 |
tristan | valentind, interesting that we hit an ostree limitation after having completely moved to CAS | 11:37 |
tristan | valentind, I think it's reasonable to say that, we should focus now on making sure CAS is working well | 11:37 |
paulsherwood | +1 | 11:38 |
paulsherwood | tristan: what's the best way to request/suggest logging improvements, please? i know this is a strangely controversial subject :) | 11:38 |
tristan | paulsherwood, heh, ok well now we have configurability in log lines I hope it is less controversial ! | 11:39 |
tristan | paulsherwood, I would say raise an issue stating the information which is required; the harder question is whether it should be default for end users | 11:40 |
paulsherwood | tristan: 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 |
tristan | paulsherwood, I would prefer individual issues which we can treat and handle separately, but I don't mind doing some triage after an issue is posted | 11:42 |
paulsherwood | ok | 11:42 |
gitlab-br-bot | buildstream: 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/559 | 11:53 |
qinusty | tristan: 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 |
jjardon | tristan: 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 there | 11:53 |
gitlab-br-bot | buildstream: 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/505 | 11:54 |
juergbi | valentind: 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 |
tristan | jjardon, Yes - we haven't really had users of 1.0 as they all relied on 1.1.x | 11:54 |
tristan | jjardon, note that you mean bst-1.2; bst-2.0 with our versioning semantics would mean a clear API break | 11:55 |
gitlab-br-bot | buildstream: 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/566 | 11:55 |
jjardon | tristan: yup sorry, I meant 1.2 | 11:55 |
gitlab-br-bot | buildstream: 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/566 | 11:56 |
gitlab-br-bot | buildstream: 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/404 | 11:56 |
valentind | juergbi, 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 |
tristan | valentind, I think what he means is, on the server it is no longer required to create and update the summary file periodically | 11:59 |
tristan | valentind, i.e. you could delete it on the share server and disable the cron job which updates it | 11:59 |
valentind | tristan, Ah OK. Then that would work yes. | 11:59 |
gitlab-br-bot | buildstream: merge request (Qinusty/501->master: Remove misleading info message) #567 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/567 | 11:59 |
tristan | that 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 session | 12:00 |
valentind | But I think the next time we update the version of builstream is to use CAS. | 12:01 |
qinusty | https://gitlab.com/BuildStream/buildstream/merge_requests/567 Is a oneliner ready for review/merge. | 12:02 |
* jonathanmaw has a peek | 12:03 | |
gitlab-br-bot | buildstream: merge request (Qinusty/501->master: Remove misleading info message) #567 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/567 | 12:05 |
tristan | do we still have a tlater hanging around ? | 12:06 |
gitlab-br-bot | buildstream: issue #506 ("Raw logs contain lots of unnecessary progress information") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/506 | 12:08 |
gitlab-br-bot | buildstream: issue #507 ("Some log lines appear to be duplicates") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/507 | 12:10 |
gitlab-br-bot | buildstream: issue #508 ("Empty timestamps") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/508 | 12:10 |
jonathanmaw | tristan: tlater's travelling down to London today, iirc | 12:15 |
* Kinnison thinks tlater and jennis won't be available today/tomorrow | 12:16 | |
Kinnison | sorry, not jennis, phildawson | 12:16 |
tristan | qinusty, I feel like I wish tlater could review and land https://gitlab.com/BuildStream/buildstream/merge_requests/563 | 12:17 |
tristan | qinusty, he would be the most efficient in that area | 12:17 |
gitlab-br-bot | buildstream: issue #509 ("Wallclock time in logs") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/509 | 12:18 |
laurence | tlater may not have chance today, fyi | 12:19 |
laurence | he's down in London | 12:19 |
gitlab-br-bot | buildstream: issue #509 ("Wallclock time in logs") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/509 | 12:27 |
gitlab-br-bot | buildstream: issue #510 ("message format in user configuration is undocumented") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/510 | 12:32 |
tristan | qinusty, if your merge request closes 501, then please close 501 | 12:34 |
gitlab-br-bot | buildstream: issue #506 ("Raw logs (from GitLab ci) contain lots of unnecessary progress information") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/506 | 12:46 |
tristan | toscalix, 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 bug | 12:49 |
tristan | I'd like to make the change if that's alright (as I'm seeing bugs filed as tasks...), but need to figure out how | 12:49 |
jonathanmaw | tristan: https://gitlab.com/BuildStream/buildstream/merge_requests/404 is ready for review again, now that I've fixed what was going wrong with the GitSource | 12:49 |
tristan | jonathanmaw, source mirrors ! | 12:50 |
tristan | jonathanmaw, 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 |
tristan | not sure if you did that already, but targeting master should be Since 1.4 (next stable) | 12:50 |
* jonathanmaw has not done that | 12:51 | |
tristan | I hope to backport it, once I do that I'll update the since markers to 1.2 | 12:51 |
toscalix | tristan: no objection | 12:57 |
toscalix | but 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 |
toscalix | it is also true though that community people is more familiar with ticketing systems associated to bugs, not tasks | 12:59 |
toscalix | we have a86 bugs out of 583 issues | 13:00 |
toscalix | 186/583 | 13:00 |
noisecell | some issues could be classify as bugs but need triage, IMO | 13:01 |
toscalix | and some has no label and some bugs are not bugs... so ignored | 13:01 |
toscalix | yes, the data could be wrong, but it is a first approach | 13:02 |
*** xjuan has joined #buildstream | 13:02 | |
skullman | toscalix: a template for Feature Request issues may be useful. It's not always easy to rephrase a missing feature as a bug. | 13:02 |
toscalix | skullman: that will happen | 13:02 |
gitlab-br-bot | buildstream: issue #501 ("Misleading info message for CASCache pull") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/501 | 13:02 |
toscalix | it is just that I will propose a slightly different process that we have today, as I mentioned by mail | 13:03 |
gitlab-br-bot | buildstream: 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/512 | 13:03 |
toscalix | but yes, we will benefit from having requests that include enough structured information so they are easy to consume | 13:03 |
toscalix | and a template is the easiest way, as guidance | 13:04 |
toscalix | skullman: follow this ticket to check progress on that front: https://gitlab.com/BuildStream/nosoftware/alignment/issues/18 | 13:05 |
toscalix | tristan: 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 policy | 13:08 |
gitlab-br-bot | buildstream: 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/559 | 13:08 |
tristan | toscalix, okay... if you want to bundle that together with proposing an enhancement template, that might get things rolling quicker :) | 13:10 |
gitlab-br-bot | buildstream: issue #511 ("Fixing VCS reduction") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/511 | 13:10 |
tristan | toscalix, 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 it | 13:11 |
toscalix | I 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 it | 13:12 |
toscalix | tristan: did you receive the mail from gnome sysadmins with the password to the new notification list? | 13:13 |
*** xuanrui has joined #buildstream | 13:17 | |
gitlab-br-bot | buildstream: 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/559 | 13:18 |
gitlab-br-bot | buildstream: 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/512 | 13:20 |
tlater | About the CAS artifact cache - is there a way to update the client certificates while the server is running? | 13:37 |
tlater | I.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 |
jmac | I don't think so | 13:39 |
tlater | Hrm, that sounds like a bit of an oversight :| Should I open up an issue? | 13:40 |
tristan | toscalix, ah yes I did... | 13:40 |
jmac | tlater: Sure. | 13:41 |
*** WSalmon has joined #buildstream | 13:41 | |
tristan | toscalix, you and tlater are alread listed as admins there | 13:42 |
tristan | toscalix, I suppose you need the password, though ? | 13:42 |
tristan | or, your should have also received an email ? not sure how that works | 13:42 |
gitlab-br-bot | buildstream: 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/512 | 13:43 |
gitlab-br-bot | buildstream: 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/512 | 13:43 |
toscalix | we need the password | 13:43 |
toscalix | tristan ^ | 13:43 |
toscalix | I need to configure the list | 13:43 |
tristan | toscalix, I've sent over through a more secure channel :) | 13:44 |
tristan | paulsherwood, thanks for filing all of those separately btw, that was helpful | 13:49 |
* tristan tries to focus on jonathanmaw's branch for the last timeslot... | 13:50 | |
paulsherwood | tristan: np, it helped me too :-) | 13:54 |
gitlab-br-bot | buildstream: issue #513 ("Allow updating remote cache client certificates without rebooting") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/513 | 13:57 |
gitlab-br-bot | buildstream: 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/549 | 14:01 |
tristan | tlater, 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 |
jjardon | sorry, can someone remind me again what is the last commit before mergin the CAS stuff? | 14:08 |
gitlab-br-bot | buildstream: 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/549 | 14:15 |
tristan | jjardon, 4c6512d6f6e4defbddebab56a19e5e7f9e50c20c | 14:15 |
gitlab-br-bot | buildstream: 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/549 | 14:16 |
tristan | jonathanmaw, It appears your commit to the bzr plugin is not really related to source mirroring, or ... is it ? | 14:16 |
Nexus | dum dum dummmmmm | 14:16 |
tristan | jonathanmaw, i.e. bzr plugin would be improved by that commit with or without the source mirroring | 14:16 |
jonathanmaw | tristan: the meat of the change to the bzr mirroring changes is in `bzr pull`, where I append the branch url | 14:18 |
*** andries has joined #buildstream | 14:18 | |
jonathanmaw | since the url used to create the bzr repository isn't always the same as the one used when fetching | 14:18 |
tristan | jonathanmaw, alright, was just curious | 14:22 |
jjardon | tristan: tvm | 14:23 |
jjardon | tristan: would it be possible to tag that commit? | 14:24 |
tristan | jjardon, you really have a use case for a PRE_CAS_CACHE kind of tag ? | 14:29 |
tristan | jjardon, I mean, it seems it will be useful for a very temporary period of time hehe | 14:29 |
jjardon | tristan: all the users of buildstream I know are using a pre CAS cache commit | 14:30 |
jjardon | we can not upgrade until we upgrade the cache servers | 14:30 |
jjardon | so it would be helpful for now so I do not have to ask again :) | 14:31 |
gitlab-br-bot | buildstream: issue #514 ("BuildStream CI is not configured to perform any system level testing") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/514 | 14:32 |
tristan | jjardon, Ok, following the naming convention of another tag I see there, I will call it PRE_CAS_MERGE_JULY_2018 | 14:34 |
jjardon | tristan: tvm | 14:35 |
tristan | jjardon, tag is up now | 14:35 |
tlater | tristan: I'll take a look - I resurfaced mostly to raise an issue, but might have enough time now :) | 14:38 |
tristan | tlater, if you could do that today or tmw that can free me up a bit | 14:40 |
tristan | if not, I'll get back to it :) | 14:40 |
tristan | I would like to have it checked by you, though | 14:40 |
tlater | Definitely will have time at some point today/tomorrw | 14:41 |
tlater | I've had a look before, thought jennis was handling it | 14:41 |
WSalmon | I 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 |
WSalmon | i 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 |
WSalmon | i 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 far | 14:48 |
Kinnison | `` is for code samples | 14:48 |
gitlab-br-bot | buildstream: 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/563 | 14:49 |
Kinnison | You might find :literal:`--option` works better, but it'll depend on how sphinx sets up the rST roles | 14:50 |
WSalmon | that still seems to put a equally ugly box in but if thats the better practice i will use that. | 14:52 |
tristan | Kinnison, WSalmon ... from what I've been understanding: .. code:: python blocks are for code samples | 14:53 |
tristan | And ``pony`` is for literals | 14:53 |
Kinnison | tristan: yeah but `` seems to syntax hilight as though it were python | 14:54 |
tristan | However, I should note that I am also peeved that since we changed the theme, they started appearing with the obnoxious boxes | 14:54 |
tlater | Thanks qinusty - patch looks great, I think you cleaned up some stupidly expressed logic :) | 14:54 |
tristan | So, 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 |
qinusty | Cheers, just making the changes you suggested. As for the headroom documentation, There is an issue at https://gitlab.com/BuildStream/buildstream/issues/497 | 14:55 |
tristan | rather than chasing down everything ? it's worth a double check into what the rst syntax wants it to mean, that would be another deciding factor | 14:55 |
coldtom | I 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 |
tlater | qinusty: I'm aware of the docs, mostly concerned about showing a less confusing warning | 14:58 |
toscalix | new notifications mailing list: https://mail.gnome.org/archives/buildstream-list/2018-July/msg00057.html | 14:58 |
tlater | Preferably that warning is vague about *why* you need at least 2 GB | 14:58 |
tlater | Because the actual reason is just confusing | 14:58 |
qinusty | I realised I had misread :P I am now adding that | 14:59 |
* tlater probably heads off for the rest of the day - I'll be back tomorrow if anyone needs me :) | 15:00 | |
qinusty | On 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-bot | buildstream: 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/549 | 15:01 |
tristan | jonathanmaw, 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 IRC | 15:07 | |
gitlab-br-bot | buildstream: 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/563 | 15:12 |
laurence | qinusty, wrt https://gitlab.com/BuildStream/buildstream/merge_requests/559#note_90288918 | 15:15 |
laurence | if all of your ToDo's are completed for that patch, it's worth taking the WIP off | 15:15 |
laurence | (and prodding the reviewer again) | 15:16 |
qinusty | Ah yes, I was just waiting on the pipeline to pass :) I think we've got everything in there now | 15:16 |
*** tristan has joined #buildstream | 15:16 | |
qinusty | Pipeline failed 3/4 times due to this spurious failing test https://gitlab.com/BuildStream/buildstream/issues/503 | 15:17 |
gitlab-br-bot | buildstream: merge request (phil/437-junction-tutorial->master: Phil/437 junction tutorial) #550 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/550 | 15:20 |
laurence | qinusty, aha, i may have been hasty :) | 15:21 |
laurence | so that's the bug in the test rather than the code is it? | 15:21 |
laurence | code in the patch * | 15:21 |
qinusty | Tristan believes it is. It is reported on several branches including one from tpollard | 15:22 |
*** edb has quit IRC | 15:22 | |
gitlab-br-bot | buildstream: 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/559 | 15:23 |
gitlab-br-bot | buildstream: 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/515 | 15:25 |
gitlab-br-bot | buildstream: merge request (phil/437-junction-tutorial->master: Phil/437 junction tutorial) #550 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/550 | 15:47 |
tlater | Grr, 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.crt | 15:47 |
tlater | As far as I can tell, we don't even need a specific user anymore | 15:48 |
tlater | So why this random default file? | 15:48 |
tlater | Ah, sorry, this is the actual heading: https://buildstream.gitlab.io/buildstream/install_artifacts.html#authenticating-users | 15:49 |
gitlab-br-bot | buildstream: 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/561 | 15:49 |
juergbi | tlater: not needed but we still recommend it: https://buildstream.gitlab.io/buildstream/install_artifacts.html#setting-up-the-user | 15:50 |
gitlab-br-bot | buildstream: 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/561 | 15:50 |
juergbi | admins can use other means of isolation but those people should be able to adapt things accordingly with ease | 15:50 |
tiagogomes | Regarding logging, I am unhappy that bst shows the shell commands executed by default | 15:51 |
tlater | juergbi: That's fair, but why do we need to cat anything to ~/authorized.crt? | 15:51 |
juergbi | tlater: the server needs this file. what else do you recommend for the documentation? | 15:52 |
tlater | Huh | 15:52 |
juergbi | --client-certs authorized.crt | 15:53 |
tlater | Ah! | 15:53 |
tlater | Rifht | 15:53 |
tlater | *right | 15:53 |
tlater | Sorry, I misread. This is a bit more turorial-ey than I thought | 15:53 |
tlater | Thanks! | 15:53 |
juergbi | improvements welcome, of course, I'm not necessarily good at writing docs | 15:54 |
tlater | juergbi: The only thing I'd improve is make that --client-certs path absolute | 15:54 |
gitlab-br-bot | buildstream: 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/561 | 15:54 |
tlater | So that it matches with where you cat to | 15:54 |
gitlab-br-bot | buildstream: 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/563 | 15:55 |
tlater | I'll fix that when I get time for it. Documentation is great otherwise, this just confused me a bit :) | 15:55 |
juergbi | could make sense but then I wonder whether we should do the same for the other relative paths | 15:55 |
tpollard | bah, sorry for making the bot spam, I forgot the MR was tracking a branch I was rebasing | 15:56 |
tlater | Hm, for consistency that would make sense. | 15:56 |
juergbi | alternatively, use relative path also for the >> line | 15:57 |
gitlab-br-bot | buildstream: merge request (phil/437-junction-tutorial->master: WIP: Phil/437 junction tutorial) #550 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/550 | 15:59 |
jennis | We 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 |
jennis | Something that can live in the docs | 16:39 |
jennis | I still don't know what the numbers after the project name refer too | 16:39 |
jmac | Which project name? | 16:40 |
jennis | So when you run `bst build ELEMENT`, you'll get a ======= TIMER project-name (1/20) ======= on your terminal, for example | 16:42 |
jennis | that 1/20 is a mystery to me | 16:42 |
jennis | https://snag.gy/7GQcTp.jpg | 16:45 |
jennis | This ^ | 16:45 |
*** flatmush has quit IRC | 16:45 | |
tiagogomes | Thumbs up for anything that helps demystifying the BuildStream log | 16:47 |
gitlab-br-bot | buildstream: 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/404 | 16:47 |
qinusty | agreed tiagogomes, screenshots always help jennis | 16:54 |
qinusty | However 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-bot | buildstream: 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/561 | 17:00 |
*** qinusty has quit IRC | 17:04 | |
*** flatmush has joined #buildstream | 17:11 | |
juergbi | jennis: the first number is the number of elements in the build plan and the second number is the number of elements loaded | 17:11 |
juergbi | aka as session_elements and total_elements in Stream | 17:14 |
*** toscalix has quit IRC | 17:15 | |
*** jonathanmaw has quit IRC | 17:39 | |
tristan | tiagogomes, regarding showing shell commands, I half agree, there is a back story and possibly a regression | 17:45 |
tristan | tiagogomes, --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 all | 17:46 |
tristan | but I do think that verbosity enabled by default is the correct default | 17:46 |
tristan | it should still be overrideable in the user config and CLI | 17:47 |
tristan | I 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 session | 17:54 |
tristan | which is useful, but not always easy to calculate, what with potential downloads which might happen, etc | 17:54 |
gitlab-br-bot | buildstream: merge request (chandan/sourcetransform->master: WIP: Allow source plugins to access previous sources) #568 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/568 | 18:56 |
gitlab-br-bot | buildstream: merge request (chandan/sourcetransform->master: WIP: Allow source plugins to access previous sources) #568 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/568 | 18:57 |
gitlab-br-bot | buildstream: merge request (chandan/sourcetransform->master: WIP: Allow source plugins to access previous sources) #568 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/568 | 18:59 |
*** ernestask has quit IRC | 19:37 | |
gitlab-br-bot | buildstream: merge request (edbaunton/remote-source->master: Add remote source plugin) #541 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/541 | 19:43 |
gitlab-br-bot | buildstream: merge request (edbaunton/remote-source->master: Add remote source plugin) #541 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/541 | 19:44 |
*** xjuan has quit IRC | 20:49 | |
*** tristan has quit IRC | 21:17 | |
*** bochecha has quit IRC | 21:42 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!