-
Couldn't load subscription status.
- Fork 1.1k
[Big change] Server refactor (Part 1) #858
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
80949fc
Refactoring server.py into more intentional files
JackUrb 802c612
Splitting all handlers into socket and base handlers
JackUrb fb3541f
reapply all changes since server refactor
da-h 75c63e3
server: simplify & fix get_visdom_path/_to
da-h 26a9ef1
server: move LAYOUT_FILE to defaults.py
da-h 8bdb9c1
server: cleanup of imports
da-h 277bcbf
setup: adapt console_script to new file structure
da-h d3ce2d3
server: remove zmq (as it has not been used & zmq.ioloop is deprecated)
da-h b3d838a
server: (minor) changed order of imports
da-h f597e9e
server: move MAX_SOCKET_WAIT to defaults.py
da-h 2bbe4c7
server: added implementation comments about Sockets/Handlers
da-h 77d5931
server: renamed ClientSocketWrapper -> SocketWrapper to unify naming …
da-h fd70fcd
github: adapted workflows to new filestructur in py/visdom/server
da-h c573028
github: (may be reverted after merge) ensures that cypress tests on m…
da-h f54852f
release version 0.2.2
da-h File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1 +1 @@ | ||
| 0.2.1 | ||
| 0.2.2 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As an aside, it's not the best that the entirety of visdom lives in the
__init__.pyfile too. For a future refactor 😉Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, that's true; the python-client code grew out of control. ^^
Considering some of the issues, there are quite some bugs to fix there as well, but tons of tiny things to keep track of at the same time. Any Idea how to improve the code efficiently?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For things like this, I'd argue that visdom has reached a scale that we need to hit on more DevX and codebase quality. Before jumping into the small changes, reorganizing would come first. Then I'd probably want to start using
typing, though that can happen in parallel with small changes (every time you take a pass through to fix a bug, doing code quality improvements in the same pass). Typing and testing make sure that as you're making changes, the code is to some degree keeping track of things by itself so you don't have to.