Release0.2.5 #110
Merged
Release0.2.5 #110
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
Merge hotfixes on main into develop
Upgrade nicegui
Adapt nicegui color scheme
Merge hotfixes into develop
Cli enhacement
improve management of components in the dashboard: - only component versions that have been tagged can be added - the commits will be directly taken from the tagged versions - the overall flow has been improved - bugs have been remove (they were related to storage handling)
Improve dashboard components
component versions in ODTP should correspond to the tags on their github repos. Therefore only version names are taken, where the tags can be found on github. Additionally the url is taken from github for a component. This avoids that the component will be registered multiple time datetime.utcnow() is deprecated and is been replaced by datetime.now(timezone.utc) make settings safer by putting it into a try except block and use `eval` instead of `bool` to evaluate boolean settings
…mits Component version instead of commits
a new db function is added to find the versions for a component name and version tag the parser is adapted to use that function and react on the version ids that are found in an approriete way the spelling of some function names is corrected
Fix cli new execution
otherwise page link from the execution page to the component details will land on the component list page
add validator for step number to be an integer below a threshold add validator for a port mapping
display also same components as different steps in the workflow initialize mermaid diagram since this is necessary even if it does not carry any items add new functions to get keys and values form parameters add custom dashboard function for display of component versions
use user workdirectory instead of home directory as base when picking the project path
the form for creating executions was completely refactored: it is now able to have executions that have multiple steps that are based on the same component version. Parameters can be loaded into the form from files and then overwritten. The form recognizes its state and the user can walk between steps with ease without losing any previous inputs in the execution table the order of the executions changed: the newest executions come first now
this setting is needed in the dasboard to set a users base directory
allow users to set a working directory that will be used as base when reading files from the server
this will be used as starting point for users to set their working directory on the dashboard
add two new function to get a collection back sorted by field field values extend existing function with an option to sort and the default for this new argument is None the new fuctions will be used to sort component versions and executions
the new setting variable is not needed
so that function can be reused on multiple pages
for the selection of executions, the display and the storage the reusable functions are now used instead of the custom code that was there before in case of more parameters in a file, the setting for the number of parameters is now adjusted automatically in the form for adding executions
a stepper was added and the workarea was improved with the goal to make the page easier to understand for a user selection of executions for run was decoupled from selection of executions for display on the executions page
caviri
approved these changes
May 6, 2024
Closed
sabinem
force-pushed
the
release0.2.5
branch
2 times, most recently
from
00aa3d3
to
843c37c
Compare
the ODTP_PATH is used in the dashbaord as working directory for user data and projects
also display cli command before they are submitted from the dashboard
the selection should be preset with the current user
digital twins and executions should be next to each other
replace some notification by error logs
logging errors will be more helpful in regards to debugging
if data has not been added yet the user is redirected to a page where he can add the data
add more clarity to workflow and show user better at which step he currently is
Bug fixes 0.2.5
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.
No description provided.