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

redefinition of table error: print both locations #4760

Closed
matthiaskrgr opened this issue Nov 28, 2017 · 5 comments
Closed

redefinition of table error: print both locations #4760

matthiaskrgr opened this issue Nov 28, 2017 · 5 comments
Labels
A-diagnostics Area: Error and warning messages generated by Cargo itself.

Comments

@matthiaskrgr
Copy link
Member

matthiaskrgr commented Nov 28, 2017

currently cargo just prints

error: failed to parse manifest at `/home/matthias/vcs/github/cargo/Cargo.toml`

Caused by:
  could not parse input as TOML

Caused by:
  redefinition of table `profile.release` for key `profile.release` at line 79

However this is not very helpful when I just added the duplicate entry at line 79 because I still have to find the original one.

Something like

  redefinition of table `profile.release` at line 20 for key `profile.release` at line 79

would be more useful. :)

@alexcrichton alexcrichton added the A-diagnostics Area: Error and warning messages generated by Cargo itself. label Nov 29, 2017
@lukaslueg
Copy link
Contributor

This error comes straight from the toml crate, maybe you want to open an issue there

@stale
Copy link

stale bot commented Sep 19, 2018

As there hasn't been any activity here in over 6 months I've marked this as stale and if no further activity happens for 7 days I will close it.

I'm a bot so this may be in error! If this issue should remain open, could someone (the author, a team member, or any interested party) please comment to that effect?

The team would be especially grateful if such a comment included details such as:

  • Is this still relevant?
  • If so, what is blocking it?
  • Is it known what could be done to help move this forward?

Thank you for contributing!

(The cargo team is currently evaluating the use of Stale bot, and using #6035 as the tracking issue to gather feedback.)

If you're reading this comment from the distant future, fear not if this was closed automatically. If you believe it's still an issue please leave a comment and a team member can reopen this issue. Opening a new issue is also acceptable!

@stale stale bot added the stale label Sep 19, 2018
@stale
Copy link

stale bot commented Oct 23, 2018

As I didn't see any updates in 30 days I'm going to close this. Please see the previous comment for more information!

@stale stale bot closed this as completed Oct 23, 2018
@matthiaskrgr
Copy link
Member Author

stupid bot...

@dwijnand
Copy link
Member

Is there an issue tracking this in the toml crate?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-diagnostics Area: Error and warning messages generated by Cargo itself.
Projects
None yet
Development

No branches or pull requests

4 participants