tensorflow / tensorflow/tensorboard
Support binding to a Unix domain socket
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.2k
- Forks
- 1.7k
- Avg merge
- 4d 22h
- Merged PRs (30d)
- 1
Description
For users who run tensorboard on a multi-user host (e.g., on a shared compute server, or HPC cluster as in this example), it would be beneficial for security to allow tensorboard to bind to a Unix domain socket (instead of a TCP port). File permissions on the socket file could be set to allow access only by the user that created it, and the user could securely access their tensorboard session on the remote host via Unix domain socket forwarding (which OpenSSH has supported since v6.7).
The Werkzeug dev server supports listening on a unix domain socket.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No implementation file or test is named. Start by locating TensorBoard's server startup and its Werkzeug integration, then review the linked Werkzeug Unix-socket behavior. Done means TensorBoard can bind to a Unix domain socket for the described multi-user use case, with coverage for the new binding path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100