What problem are you trying to solve?
If use UDS path as server's addr in console_subscriber, the UDS path created during the server's execution will not be automatically cleaned up after the server completes its run. When the server is executed again, it may result in an error:
thread 'console_subscriber' panicked at console-subscriber-0.4.1/src/builder.rs:551:26:
console subscriber server failed: Os { code: 48, kind: AddrInUse, message: "Address already in use" }
How should the problem be solved?
Automatically clean up the UDS path created by console subscriber server when it finishes running.
Any alternatives you've considered?
Manual Cleanup : Users could manually delete the UDS file before restarting the application. However, this approach is error-prone and inconvenient.
How would users interact with this feature?
No response
Would you like to work on this feature?
yes
What problem are you trying to solve?
If use UDS path as server's addr in
console_subscriber, the UDS path created during the server's execution will not be automatically cleaned up after the server completes its run. When the server is executed again, it may result in an error:How should the problem be solved?
Automatically clean up the UDS path created by console subscriber server when it finishes running.
Any alternatives you've considered?
Manual Cleanup : Users could manually delete the UDS file before restarting the application. However, this approach is error-prone and inconvenient.
How would users interact with this feature?
No response
Would you like to work on this feature?
yes