07:48:55 <gcp> There's a bug for having the connect timing in telemetry, it's attached to that other bug.
07:49:17 <gcp> (probably already pointed out, I have no backscroll here)
16:40:14 <mccr8> I'm going to skip the IPC meeting today
23:16:06 <haik> jld: regarding bug 1562785, I'm going to change the expiration to "never" per mconley's comment on the original code review. Do you foresee the sync launch support going away eventually? I'm wondering if the sync probes should be "never" also.
23:16:08 <firebot> https://bugzil.la/1562785 — NEW, haftandilian⊙mc — Extend/revive the process launch telemetry
23:17:55 <jld> The current long-term plan is to break the dependency on having the pid/handle to create endpoints, so it's more like that async launch will go away.  There isn't a concrete timeframe for that yet.
23:19:48 <jld> (i.e., the API will be sync, but it won't block on anything)
23:20:23 <haik> jld: so the parts of code the telemetry is measuring with be sync, but launch will still be async?
23:20:28 <haik> s/with/will
23:26:49 <jld> haik: Right.
23:31:23 <haik> OK, I think it makes sense to let these be "never" expiring and when we rework the launching code we would delete any we no longer need.
23:32:32 <jld> Agreed.  Unexpiring telemetry will generally get more scrutiny, but timings should be relatively low concern.