-
Notifications
You must be signed in to change notification settings - Fork 68
feat: Concurrent executions with indexedDB Main Finalization #1328
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
base: feature/distributed-demo
Are you sure you want to change the base?
feat: Concurrent executions with indexedDB Main Finalization #1328
Conversation
Codecov Report❌ Patch coverage is Please upload reports for the commit 70a9d39 to get more accurate results. Additional details and impacted files@@ Coverage Diff @@
## feature/distributed-demo #1328 +/- ##
============================================================
- Coverage 95.72% 92.50% -3.23%
============================================================
Files 103 113 +10
Lines 2875 3534 +659
Branches 483 570 +87
============================================================
+ Hits 2752 3269 +517
- Misses 120 262 +142
Partials 3 3
... and 2 files with indirect coverage changes
🚀 New features to boost your workflow:
|
|
Pull Request Template
Title
Finalize Implementation of Concurrent Digital Twin Execution with IndexedDB Integration
Type of Change
Description
This PR finalizes the implementation of the concurrent execution for Digital Twins with IndexedDB integration. Users can now start multiple executions of the same Digital Twin simultaneously, with execution history persisted in the browser's IndexedDB. The implementation includes a new execution history data model, IndexedDB service, and UI components to display and manage execution history.
New is that it merges recent changes of the up-coming version 0.8 of DTaaS such as settings menu and new interface design.
Working on Testing
Impact
Additional Information
This PR builds on top of #1235 by Microchesst.
Checklist