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

bug: error reported when use v0.5.0 #118

Closed
ben1009 opened this issue Aug 25, 2023 · 8 comments
Closed

bug: error reported when use v0.5.0 #118

ben1009 opened this issue Aug 25, 2023 · 8 comments

Comments

@ben1009
Copy link

ben1009 commented Aug 25, 2023

error as below

rustc --version
rustc 1.70.0-nightly (171693274 2023-03-14)
image
@mucks-cdc
Copy link

having the same problem with rustc 1.70.0-nightly (da7c50c08 2023-03-19)

@epage
Copy link
Collaborator

epage commented Aug 25, 2023

Is that nightly from before IsTerminal was stabilized? To be safest, id recommend a 1.71 nightly (assuming you have a hard requirement on nightly).

@aminya
Copy link

aminya commented Aug 27, 2023

I am having the same issue. Does this mean that this package only works on nightly?

@IceTDrinker
Copy link

IceTDrinker commented Aug 28, 2023

looks like the package uses unstable features in every situation making it incompatible with stables toolchains, is it expected ?

hitting the same error via transitives deps

info: latest update on 2023-04-12, rust version 1.70.0-nightly (9df3a39fb 2023-04-11)

@epage
Copy link
Collaborator

epage commented Aug 28, 2023

@aminya

I am having the same issue. Does this mean that this package only works on nightly?

The package works with stable releases starting with 1.70.0.

@mataha
Copy link

mataha commented Aug 28, 2023

I am having the same issue. Does this mean that this package only works on nightly?

Definitely not - I can confirm that latest stable works:

> rustc --version
rustc 1.71.0 (8ede3aae2 2023-07-12)

@epage
Copy link
Collaborator

epage commented Aug 28, 2023

@IceTDrinker

hitting the same error via transitives deps

info: latest update on 2023-04-12, rust version 1.70.0-nightly (9df3a39fb 2023-04-11)

Note you are using a nightly of 1.70 which means you are dependent on when the feature was merged. It looks like the tracking issue was closed on April 13th, so if you are needing a nightly, it would need to be at earliest an April 13th but it might need to be 14th or later, depending on whether it missed a cutoff for building a specific nightly.

Since this is just a problem with people using 1.70.0-nightlies that are too early, I'm closing this.

@epage epage closed this as not planned Won't fix, can't repro, duplicate, stale Aug 28, 2023
@IceTDrinker
Copy link

yes my bad @epage thanks for the quick answer !

yashmasani added a commit to yashmasani/humi_bot that referenced this issue Aug 30, 2023
github-merge-queue bot pushed a commit to aurora-is-near/aurora-engine that referenced this issue Aug 31, 2023
…ging toolchain (#832)

# Description

Currently impossible to update toolchain, it's related to [NEAR
issue](near/nearcore#9143).

And it is impossible to do `cargo update`, because
[issue](rust-cli/anstyle#118 (comment)).

- Updated clippy requirements to `nightly-2023-08-24`, without updating
`rust-toolchain`.
- Fixed clippy issues, related to clippy requirements for
`nightly-2023-08-24` version.
aleksuss pushed a commit to aurora-is-near/aurora-engine that referenced this issue Sep 25, 2023
…ging toolchain (#832)

# Description

Currently impossible to update toolchain, it's related to [NEAR
issue](near/nearcore#9143).

And it is impossible to do `cargo update`, because
[issue](rust-cli/anstyle#118 (comment)).

- Updated clippy requirements to `nightly-2023-08-24`, without updating
`rust-toolchain`.
- Fixed clippy issues, related to clippy requirements for
`nightly-2023-08-24` version.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants