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

Jump to bottom

Improve this error message: RuntimeError: Expected from <= to to be true, but got false. (Could this error message be improved? If so, please report an enhancement request to PyTorch.) #65980

Open
Sheldonfrith opened this issue Oct 1, 2021 · 2 comments
Open

Improve this error message: RuntimeError: Expected from <= to to be true, but got false. (Could this error message be improved? If so, please report an enhancement request to PyTorch.) #65980

Sheldonfrith opened this issue Oct 1, 2021 · 2 comments
Labels
good first issue module: error checking triaged

Comments

@Sheldonfrith
Copy link

@Sheldonfrith Sheldonfrith commented Oct 1, 2021

🚀 Feature

Add information to this error message which will help an end-user actually figure out what is wrong:
RuntimeError: Expected from <= to to be true, but got false. (Could this error message be improved? If so, please report an enhancement request to PyTorch.)

Motivation

The error message itself told me to ask for an improvement... I cannot find any useful info on this error message through google searching.
@Sheldonfrith
Copy link
Author

@Sheldonfrith Sheldonfrith commented Oct 1, 2021

Additional context:

For me specifically this error showed up during a hyperparameter search when using RRelu with a "lower" bound larger than the "higher" bound.

@TechMirage TechMirage mentioned this issue Oct 8, 2021
Closed
@SamGulinello
Copy link

@SamGulinello SamGulinello commented Oct 9, 2021

Is this issue still open? It looks like VitalyFedyunin fixed this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue module: error checking triaged
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
@VitalyFedyunin @Sheldonfrith @SamGulinello