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

Docfx does not produce useful error messages on exceptions #2179

Closed
firelizzard18 opened this issue Nov 8, 2017 · 5 comments
Closed

Docfx does not produce useful error messages on exceptions #2179

firelizzard18 opened this issue Nov 8, 2017 · 5 comments

Comments

@firelizzard18
Copy link

DocFX Version Used: 2.26.4.0

Template used: default

Steps to Reproduce:

  1. Do something that causes an internal exception

Expected Behavior:

Docfx outputs something that can be used to diagnose the issue.

Actual Behavior:

Docfx outputs Exception.Message.

Details

I am trying to build documentation for a large collection of mostly .NETStandard libraries. All of my projects are using the new .csproj format. I am using #1752 (comment) to get docfx working.

Something isn't working. But the error message I get is completely useless:

[17-11-08 09:30:25.755]Error:Error extracting metadata for C:/path/to/A.csproj,C:/path/to/B.csproj,C:/path/to/C.csproj: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
@firelizzard18
Copy link
Author

--logLevel Verbose does not help

@vicancy
Copy link
Contributor

vicancy commented Nov 9, 2017

Hey @firelizzard18 Could you provide the test projects for me to take a look?

@firelizzard18
Copy link
Author

In this issue I'm simply requesting that a more useful error message be presented in the case of an exception. A stack trace might be informative.

I'm still in the process of determining the root cause of the exception. I have isolated the issue to a single project, but unfortunately I'm not at liberty to share it.

@stale
Copy link

stale bot commented Mar 26, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs.

@stale stale bot added the stale label Mar 26, 2019
@stale
Copy link

stale bot commented Apr 2, 2019

Closing this issue after a prolonged period of inactivity. If you still think this issue is relevant, please feel free to ping a maintainer or leave a comment.

@stale stale bot closed this as completed Apr 2, 2019
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

3 participants