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

New error on nightly 'overflow evaluating the requirement' #123622

Closed
weiznich opened this issue Apr 8, 2024 · 1 comment
Closed

New error on nightly 'overflow evaluating the requirement' #123622

weiznich opened this issue Apr 8, 2024 · 1 comment
Labels
C-bug Category: This is a bug.

Comments

@weiznich
Copy link
Contributor

weiznich commented Apr 8, 2024

Code

I tried this code: diesel-rs/diesel@9fe91c3

git clone https://github.com/diesel-rs/diesel/
cd diesel
git checkout 9fe91c3ce6124ef86f714a3928e0db3db803c64e
cargo check --all-targets -p diesel_tests --features "sqlite"

I expected to see this happen: Compilation succeeds as on stable/beta/older nightlies.

Instead, this happened: New "overflow evalualing the requirement" errors are emitted:

error[E0275]: overflow evaluating the requirement `(&_, &_, &_, ..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ...): diesel::Insertable<...>`
  |
  = help: consider increasing the recursion limit by adding a `#![recursion_limit = "2048"]` attribute to your crate (`integration_tests`)
  = note: required for `&(_, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _)` to implement `diesel::Insertable<schema::trees::table>`
  = note: 1023 redundant requirements hidden
  = note: required for `(&..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ...)` to implement `diesel::Insertable<schema::trees::table>`
  = note: the full name for the type has been written to '/tmp/diesel/target/debug/deps/integration_tests-f4624868b3b3c56d.long-type-14619293875363383290.txt'
  = note: consider using `--verbose` to print the full type name to the console

error[E0275]: overflow evaluating the requirement `(&_, &_, &_, ..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ...): diesel::Insertable<...>`
  |
  = help: consider increasing the recursion limit by adding a `#![recursion_limit = "2048"]` attribute to your crate (`integration_tests`)
  = note: required for `&(_, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _)` to implement `diesel::Insertable<schema::users::table>`
  = note: 1023 redundant requirements hidden
  = note: required for `(&..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ...)` to implement `diesel::Insertable<schema::users::table>`
  = note: the full name for the type has been written to '/tmp/diesel/target/debug/deps/integration_tests-f4624868b3b3c56d.long-type-14619293875363383290.txt'
  = note: consider using `--verbose` to print the full type name to the console

error[E0275]: overflow evaluating the requirement `(&_, &_, &_, ..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ...): diesel::Insertable<...>`
  |
  = help: consider increasing the recursion limit by adding a `#![recursion_limit = "2048"]` attribute to your crate (`integration_tests`)
  = note: required for `&(_, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _)` to implement `diesel::Insertable<schema::with_keywords::table>`
  = note: 1023 redundant requirements hidden
  = note: required for `(&..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ...)` to implement `diesel::Insertable<schema::with_keywords::table>`
  = note: the full name for the type has been written to '/tmp/diesel/target/debug/deps/integration_tests-f4624868b3b3c56d.long-type-14619293875363383290.txt'
  = note: consider using `--verbose` to print the full type name to the console

error[E0275]: overflow evaluating the requirement `(&_, &_, &_, ..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ...): diesel::Insertable<...>`
  |
  = help: consider increasing the recursion limit by adding a `#![recursion_limit = "2048"]` attribute to your crate (`integration_tests`)
  = note: required for `&(_, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _)` to implement `diesel::Insertable<has_time_types::table>`
  = note: 1023 redundant requirements hidden
  = note: required for `(&..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ..., ...)` to implement `diesel::Insertable<has_time_types::table>`
  = note: the full name for the type has been written to '/tmp/diesel/target/debug/deps/integration_tests-f4624868b3b3c56d.long-type-14619293875363383290.txt'
  = note: consider using `--verbose` to print the full type name to the console

Version it worked on

It most recently worked on: nightly-2024-04-05

Version with regression

rustc --version --verbose:

rustc 1.79.0-nightly (9d5cdf75a 2024-04-07)
binary: rustc
commit-hash: 9d5cdf75aa42faaf0b58ba21a510117e8d0051a3
commit-date: 2024-04-07
host: x86_64-unknown-linux-gnu
release: 1.79.0-nightly
LLVM version: 18.1.3

I've run cargo bisect-rustc and got back the following report:


Regression in 9d79cd5


Attempting to search unrolled perf builds
ERROR: couldn't find perf build comment

searched nightlies: from nightly-2024-04-05 to nightly-2024-04-08
regressed nightly: nightly-2024-04-06
searched commit range: 385fa9d...9d79cd5
regressed commit: 9d79cd5

bisected with cargo-bisect-rustc v0.6.8

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

cargo bisect-rustc --start 2024-04-05 --script script.sh --regress error 

cc @Urgau as author of the relevant PR.

@rustbot modify labels: +regression-from-nightly-to-nightly -regression-untriaged

@weiznich weiznich added C-bug Category: This is a bug. regression-untriaged Untriaged performance or correctness regression. labels Apr 8, 2024
@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 Apr 8, 2024
@Urgau
Copy link
Member

Urgau commented Apr 8, 2024

Duplicate of #123573

@oli-obk oli-obk closed this as completed Apr 8, 2024
@jieyouxu jieyouxu removed the needs-triage This issue may need triage. Remove it if it has been sufficiently triaged. label Apr 8, 2024
@apiraino apiraino removed I-prioritize Issue: Indicates that prioritization has been requested for this issue. regression-untriaged Untriaged performance or correctness regression. labels Apr 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: This is a bug.
Projects
None yet
Development

No branches or pull requests

6 participants