tensorflow / tensorflow/tensorboard
load data from relative path with the projector plugin
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.2k
- Forks
- 1.7k
- Avg merge
- 4d 22h
- Merged PRs (30d)
- 1
Description
Migrated from https://github.com/tensorflow/tensorflow/issues/8342
This is a problem similar with issue #7382 but it has been closed.
@dandelionmane
Another place that still has the similar problem in #7382 is the request of project plugin data in Embeddings panel, e.g. /data/plugin/projector/runs still requests in a absolute path.
I found the code here , there is a leading slash for the route-prefix property in vz-projector-dashboard.
If that is correct, I will submit a PR. Thanks!Another question is when will the tensorboard be recompiled. As now in version 1.0 these features are not included.
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 in the vz-projector-dashboard code referenced by the issue, focusing on its route-prefix property and the Embeddings panel request to /data/plugin/projector/runs. Verify the request works from a relative path rather than an absolute root path, including when TensorBoard is served below a URL prefix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100