tensorflow / tensorflow/tensorboard
Explicitly indicate `--logdir_spec`/`--load_fast` mismatch
Open
Nobody has claimed this yet.
core:rustboard
type:feature
- Dominant language
- TypeScript
- Stars
- 7.2k
- Forks
- 1.7k
- Avg merge
- 4d 22h
- Merged PRs (30d)
- 1
Description
You can’t use the (deprecated) --logdir_spec flag with RustBoard. As
of #4794, we’ll gracefully fall back to the multiplexer if you attempt
to do so. But maybe this particular invocation is common enough that it
merits an explicit explanation of the problem rather than a silent
fallback:
$ tensorboard --logdir_spec foobar --load_fast auto
warning: --logdir_spec not supported with --load_fast; falling back to
slow data loading paths
TensorBoard 2.5.0a0 at ...
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
Start at the CLI handling for --logdir_spec and --load_fast, then run the example command from the issue to observe the current fallback behavior. Done means the mismatch produces an explicit warning explaining that --logdir_spec is unsupported with --load_fast and that slow data-loading paths will be used.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100