Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upDiesel complains that it can't find Cargo.toml despite successfully running migrations #1760
Comments
sgrif
added
the
mentoring available
label
Jun 14, 2018
This comment has been minimized.
|
Looks like this error occurs when Diesel CLI looks for a config file (the default location is in the same place as |
sgrif
added
bug
cli
labels
Jun 14, 2018
galuhsahid
referenced this issue
Jun 23, 2018
Merged
Allows migrations to run without Cargo.toml #1763
weiznich
closed this
in
#1763
Jun 23, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
SamWhited commentedJun 14, 2018
•
edited
Setup
Versions
Feature Flags
Problem Description
When running any migration command (eg. diesel migration redo) migrations complete successfully, but diesel complains:
I don't have a Cargo.toml because I am not using Cargo.
What is the expected output?
No unnecessary warnings about a build system that I am not using.
What is the actual output?
Checklist
closed if this is not the case)
eg.