You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create a package with an invalid license URL. I was able to reproduce this behavior with a URL that was over 4000 chars long.
Attempt to upload the package using the Gallery UI.
Result: After the initial package upload, you'll receive a WSOD. Investigating the error logs reveals that we don't handle the EntityException that gets thrown. For the full stack trace and error details, see https://qa.nugettest.org/Admin/Errors.axd/detail?id=3774.
Expected: Package validation errors should be presented to the user ideally in a way that resembles form validation errors. In any case, though, we shouldn't white-screen.
The text was updated successfully, but these errors were encountered:
Validation works. This is just an edge case. URLs don't normally run 4000 characters, so I think the rational allocation of bug to milestone is this goes to up for grabs.
We need to validate all package metadata to ensure it matches the requirements of the database fields. For example, if I upload a package with a bogus version, what happens? etc.
To repro:
Result: After the initial package upload, you'll receive a WSOD. Investigating the error logs reveals that we don't handle the EntityException that gets thrown. For the full stack trace and error details, see https://qa.nugettest.org/Admin/Errors.axd/detail?id=3774.
Expected: Package validation errors should be presented to the user ideally in a way that resembles form validation errors. In any case, though, we shouldn't white-screen.
The text was updated successfully, but these errors were encountered: