Stream: t-compiler/wg-prioritization/alerts

Topic: I-prioritize #74711 Segfault with increased recursion_limit


triagebot (Jul 24 2020 at 10:27, on Zulip):

@WG-prioritization/alerts issue #74711 has been requested for prioritization.

Procedure

lcnr (Jul 24 2020 at 13:43, on Zulip):

This seems important to me. Afaict it's a memory error in rust, which is always worrying

Yuki Okushi (Jul 24 2020 at 17:12, on Zulip):

and it's most recent stable-to-stable regression (1.44.1 -> 1.45.0, confirmed on my local and godbolt), so P-high at least?

lcnr (Jul 24 2020 at 17:13, on Zulip):

yeah, I don't think it's P-critical though as long as this only happens on the error path

LeSeulArtichaut (Jul 26 2020 at 20:45, on Zulip):

@Yuki Okushi could you please ping cleanup for me? triagebot is mean :frown:

lcnr (Jul 26 2020 at 20:46, on Zulip):

done

LeSeulArtichaut (Jul 26 2020 at 20:46, on Zulip):

Thanks

Yuki Okushi (Jul 26 2020 at 20:58, on Zulip):

hmm, but it's weird, doesn't triagebot listen to ping from the wg-prioritization? I thought LeSeulArtichaut did it in the past

Yuki Okushi (Jul 26 2020 at 20:59, on Zulip):

ah, https://rust-lang.zulipchat.com/#narrow/stream/224082-t-release.2Ftriagebot/topic/Unable.20to.20use.20the.20.60ping.60.20command

LeSeulArtichaut (Jul 26 2020 at 21:01, on Zulip):

Yuki Okushi said:

hmm, but it's weird, doesn't triagebot listen to ping from the wg-prioritization? I thought LeSeulArtichaut did it in the past

Probably one of the most frequent users, at least in this WG :innocent:

Yuki Okushi (Jul 26 2020 at 21:02, on Zulip):

hehe, I think so too

Last update: Apr 17 2021 at 00:00UTC