-
-
Notifications
You must be signed in to change notification settings - Fork 162
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
Malformed URL (Server Error) when trying to open project details #684
Comments
In 4.10.0 I cannot reproduce, however, the Frontend did not change for 4.10.1. Did you update from <4.10.0 to 4.10.1? could it be there is some caching issue? (Try strg+f5 or clear browser cache). I am running regularly in frontend cache issues after doing an upgrade, because the frontend is cached in an older version by the browser and not loading the latest. |
I directly updated to 4.10.1 but STRG+F5 seemed to do the trick for me. It seemed to be a caching issue. |
I have just encountered on v4.10.1 this after coming back to DT this morning, everything was fine yesterday. |
It's just happened again, the request is Going to a new project in DT does not show the error in the private tab session, but does in my normal session when looking at the details of the same project. The only change I recollect making to the server yesterday was to enable "GitHub Advisories", and I don't see how that could impact things. In the Console logs the only problems I can see are some requests showing In some cases I can see a subsequent call to the same URL succeed. Can this issue please be reopened? Tested clients:
|
Tesing again:
I am not sure if it is something about expanding the parent project, so I tried a different route to get to Project 3:
Final run:
So it looks like there can be something about a particular project that breaks the frontend. Checking the repsonse payload for |
Have just noticed that in Project 3 it's parent is missing. I have no idea how it got out of sync with itself, but that seems to be the root cause. |
This suspiciously sounds like a timing issue in the frontend. As in, one Vue component relies on data (i.e. the project UUID) being loaded by its parent component, but the child component is "mounted" before said data is present. Sometimes it works out, sometimes it doesn't, depending on how fast the API server responds, network latency, and how quickly the frontend is loaded.
This will be fixed in v4.11:
I'm reopening this as there's clearly something off here. |
Also, an |
Many resources accept UUID parameters, but because they use the type `String`, requests with invalid UUIDs are not properly rejected, causing `HTTP 500` responses being returned. This commit adds a `@ValidUuid` annotation. It further adds a Jersey `ExceptionMapper` to handle validation exceptions properly. Additionally, it add the `format = "uuid"` hint to Swagger annotations, making the API docs less ambiguous as to what format is being expected. Relates to DependencyTrack/frontend#684 Signed-off-by: nscuro <[email protected]>
@nscuro this reminds me of DependencyTrack/dependency-track#4048 is it the same? |
Yeah pretty sure this is a duplicate of DependencyTrack/dependency-track#4048, which has just been fixed and will ship with DT v4.11.6 (which I am in the process of releasing in this very moment). |
Current Behavior
After updating to dependency track 4.10.1 it is not possible anymore to open the details of a project. A Server Error (500) is shown is this case.
The URL that is requested when pressing the "Show details" link is always https://server/api/v1/project/undefined, which leads to the following exception on the server:
Steps to Reproduce
Expected Behavior
The details dialog should be opened without any error message.
Dependency-Track Frontend Version
4.10.0
Browser
Microsoft Edge
Browser Version
120.0.2210.77
Operating System
Windows
Checklist
The text was updated successfully, but these errors were encountered: