fossasia/visdom

Panes with large data sizes may load in after swapping away from the env they're fetched for.

Open

#80 opened on May 10, 2017

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Python (9,831 stars) (1,152 forks)batch import
Fix Proposedbughelp wanted

Description

I have an visdom environment with large images in environment '0' and I'm accessing the server remotely. When I load the environment '0', the first image takes a long time to load and loads in '0'. If I then change to environment '1' on the webpage, the rest of the images load in the environment '1', even though they were assigned to '0'. No big deal, just wanted to file a report for it.

Contributor guide

Tech stack
python
Domain
frontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Investigate the frontend JavaScript code in visdom, particularly the environment switching and pane loading logic. Look for race conditions where asynchronous image loading may complete after the environment has changed. Check the comments in the issue for any additional context or suggestions. Consider adding a loading queue or verifying the environment ID before displaying images.