Open Boy132 opened 2 weeks ago
I attempted to test this with editing a server but it caused the panel to lock up...
Edit Server -> Remove Owner, click save.
This seems to break the stock error handling as the owner is a required field.
I attempted to test this with editing a server but it caused the panel to lock up...
Edit Server -> Remove Owner, click save.
This seems to break the stock error handling as the owner is a required field.
Yeah, seems like Filament doesn't like the livewire exception
hook. I used good old try-catchs now.
Anyway we can catch the 500 on the create allocation, on the create server page?
Unless we just need to rewrite the logic, the port already exists... we should just skip over it, and present an error saying something along the lines of
Failed to Create Allocation
Failed to Create:
Anyway we can catch the 500 on the create allocation, on the create server page?
![]()
![]()
Unless we just need to rewrite the logic, the port already exists... we should just skip over it, and present an error saying something along the lines of
Failed to Create Allocation Failed to Create: :,
Wouldn't #395 fix/ change that anyways?
It would, but who knows when that would be done.
With latest changes 500's are still thrown when it skips the ports and does not return anything
^^ Memory Leak when creating ports that already exist.
We probably want to add some more fine tuned exception handling at some point but for now this stops all 500 errors or silent errors and replaces them with a notification.