Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

regression: parameter type may not live long enough #117055

Closed
Mark-Simulacrum opened this issue Oct 22, 2023 · 9 comments
Closed

regression: parameter type may not live long enough #117055

Mark-Simulacrum opened this issue Oct 22, 2023 · 9 comments
Labels
disposition-close This PR / issue is in PFCP or FCP with a disposition to close it. finished-final-comment-period The final comment period is finished for this PR / Issue. P-high High priority regression-from-stable-to-beta Performance or correctness regression from stable to beta. T-types Relevant to the types team, which will review and decide on the PR/issue.
Milestone

Comments

@Mark-Simulacrum
Copy link
Member

[INFO] [stdout] error[E0310]: the parameter type `S` may not live long enough
[INFO] [stdout]   --> src/uplink/ingest.rs:20:5
[INFO] [stdout]    |
[INFO] [stdout] 20 | /     tonic::transport::Server::builder()
[INFO] [stdout] 21 | |         .add_service(PacketServer::new(Gateways::new(sender)))
[INFO] [stdout]    | |______________________________________________________________^ ...so that the type `S` will meet its required lifetime bounds
[INFO] [stdout]    |
[INFO] [stdout] help: consider adding an explicit lifetime bound...
[INFO] [stdout]    |
[INFO] [stdout] 19 | pub async fn start<S: UplinkIngest + Clone + 'static>(sender: S, addr: SocketAddr) -> Result {
[INFO] [stdout]    |                                            +++++++++
@Mark-Simulacrum Mark-Simulacrum added T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. regression-from-stable-to-beta Performance or correctness regression from stable to beta. E-needs-bisection Call for participation: This issue needs bisection: https://github.com/rust-lang/cargo-bisect-rustc labels Oct 22, 2023
@Mark-Simulacrum Mark-Simulacrum added this to the 1.74.0 milestone Oct 22, 2023
@rustbot rustbot added I-prioritize Issue: Indicates that prioritization has been requested for this issue. needs-triage This issue may need triage. Remove it if it has been sufficiently triaged. labels Oct 22, 2023
@Noratrieb Noratrieb added T-types Relevant to the types team, which will review and decide on the PR/issue. and removed needs-triage This issue may need triage. Remove it if it has been sufficiently triaged. labels Oct 22, 2023
@apiraino
Copy link
Contributor

apiraino commented Oct 23, 2023

cargo-bisect seems to point at nightly 2023-09-24 13e6f24 cc@cjgillot

searched nightlies: from nightly-2023-08-30 to nightly-2023-10-23
regressed nightly: nightly-2023-09-24
searched commit range: e4133ba...13e6f24
regressed commit: 13e6f24

bisected with cargo-bisect-rustc v0.6.7

Host triple: x86_64-unknown-linux-gnu
Reproduce with:

cargo bisect-rustc 2023-08-30 --regress error -- check 

is it a breaking change, something we need to fix or something that can be fixed downstream?

@apiraino apiraino removed the E-needs-bisection Call for participation: This issue needs bisection: https://github.com/rust-lang/cargo-bisect-rustc label Oct 23, 2023
@apiraino
Copy link
Contributor

apiraino commented Oct 23, 2023

If this is really linked to #117059, maybe same priority also (Zulip discussion).

@rustbot label -I-prioritize +P-high

@rustbot rustbot added P-high High priority and removed I-prioritize Issue: Indicates that prioritization has been requested for this issue. labels Oct 23, 2023
@jackh726 jackh726 removed the T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. label Oct 23, 2023
@jackh726
Copy link
Member

We talked about this in the types team meeting today.

We agreed that there is a missing (or extra, depending how you look at it) 'static bound, and this regression is really a bug fix. We're going to try to put up a fix PR to the regressed crate, though.

@rfcbot fcp close

@rfcbot
Copy link

rfcbot commented Oct 23, 2023

Team member @jackh726 has proposed to close this. The next step is review by the rest of the tagged team members:

No concerns currently listed.

Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up!

See this document for info about what commands tagged team members can give me.

@rfcbot rfcbot added proposed-final-comment-period Proposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off. disposition-close This PR / issue is in PFCP or FCP with a disposition to close it. labels Oct 23, 2023
@nikomatsakis
Copy link
Contributor

@rfcbot reviewed

@nikomatsakis
Copy link
Contributor

We should notify authors of the helium crate and, ideally, open a PR with the 'static bound.

@rfcbot rfcbot added final-comment-period In the final comment period and will be merged soon unless new substantive objections are raised. and removed proposed-final-comment-period Proposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off. labels Oct 23, 2023
@rfcbot
Copy link

rfcbot commented Oct 23, 2023

🔔 This is now entering its final comment period, as per the review above. 🔔

@nikomatsakis
Copy link
Contributor

nikomatsakis commented Oct 23, 2023

Hey @michaeldjeffrey -- a heads-up that a recent soundness fix seems to be affected the code you contributed about 3 months ago to Helium! The fix is to add S: 'static.

michaeldjeffrey added a commit to helium/helium-packet-router-ingest that referenced this issue Oct 25, 2023
@rfcbot rfcbot added finished-final-comment-period The final comment period is finished for this PR / Issue. to-announce Announce this issue on triage meeting and removed final-comment-period In the final comment period and will be merged soon unless new substantive objections are raised. labels Nov 2, 2023
@rfcbot
Copy link

rfcbot commented Nov 2, 2023

The final comment period, with a disposition to close, as per the review above, is now complete.

As the automated representative of the governance process, I would like to thank the author for their work and everyone else who contributed.

@lcnr lcnr closed this as completed Nov 2, 2023
@apiraino apiraino removed the to-announce Announce this issue on triage meeting label Nov 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
disposition-close This PR / issue is in PFCP or FCP with a disposition to close it. finished-final-comment-period The final comment period is finished for this PR / Issue. P-high High priority regression-from-stable-to-beta Performance or correctness regression from stable to beta. T-types Relevant to the types team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

8 participants