-
Notifications
You must be signed in to change notification settings - Fork 3
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
Development: Current state #10
Merged
Merged
Conversation
This file contains 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
Message Layer is still under development.
Coordinator sign-in/out improved. Tests expanded. Heartbeat handling improved and tested.
Also a PostgreSQL data_logger version added.
Closed
BenediktBurger
force-pushed
the
development
branch
from
January 8, 2024 14:10
77988df
to
dfe1750
Compare
Rework MessageHandler. Rename fname to full_name in Coordinator.
BenediktBurger
force-pushed
the
development
branch
from
January 11, 2024 13:04
bb3a17a
to
22ce4cf
Compare
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Instead of
transfer-layer
in #1 , I'm going to use thedevelopment
branch as the running edge branch.The
stable-development
branch is going to be a moving tag for stable checkpoints along that development, such that you can stay on stable-development to follow the development, but with a (reasonably) stable environment.Instead of developing pyleco in my lab software and copying unregularly to
transfer-layer
, as I did until now, I'm going to work directly in the development branch until most features are in main.Btw. The readme contains a useful summary of the classes and their purpose.