microsoft / microsoft/vscode-tensorboard

Extension asks for directory even after setting `tensorBoard.logDirectory`

Open
#28 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
7
Forks
9
Avg merge
1d 2h
Merged PRs (30d)
1

Description

Environment data

  • VS Code version: 1.92.2
  • Tensorboard Extension version: v2023.10.1002992421
  • Jupyter Extension version: v2024.7.0
  • Python Extension version: v2024.12.3
  • OS and version: Windows 11 version 22H2
  • Python and/or Anaconda version: Python 3.10.14
  • Type of virtual environment used: venv
  • Jupyter server running: N/A

Expected behaviour

When launching tensorboard, the extension should not ask for a directory when tensorBoard.logDirectory is set.

Actual behaviour

The extension asks for a directory even when tensorBoard.logDirectory is set.

Steps to reproduce:

[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]

  1. Open settings JSON and edit tensorBoard.logDirectory.
{
  "tensorBoard.logDirectory": "/mnt/train/"
}
  1. Open command palette and launch tensorboard Python: Launch Tensorboard

  2. The extension opens a quickpick menu and asks for a directory.

Logs

Output for Jupyter in the Output panel (ViewOutput, change the drop-down the upper-right of the Output panel to Jupyter)

N/A

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue by setting tensorBoard.logDirectory in settings JSON, then running the Python: Launch Tensorboard command. Trace the launch flow's configuration handling and quick pick prompt. Done means the configured directory is used without prompting, with coverage for this behavior if the repository has relevant tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
devtools, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.