-
Notifications
You must be signed in to change notification settings - Fork 23
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
refactor: Example application with image processing workflow #263
Conversation
Codecov Report
@@ Coverage Diff @@
## main #263 +/- ##
==========================================
- Coverage 73.07% 72.75% -0.32%
==========================================
Files 65 67 +2
Lines 6313 6702 +389
==========================================
+ Hits 4613 4876 +263
- Misses 1700 1826 +126
|
001829d
to
fe2cd2f
Compare
@bgins is looking at a warning and a fix to activeworkflowstate for ordering of workflow plays. |
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.
Looks good! 🎉
Left a few comments on the example docs. As discussed, I'll look at the frontend to prevent the user from running multiple workflows at the same time.
ba96753
to
da11985
Compare
Includes: - removal of libp2p record checks on scheduler (leaves it to worker) - update across the board toward async channels - resource map now includes content over the network as part of fetching - new fetch module - better use of channels to spread out work between internal and swarm events - websocket-relay app documentation and more - no fmt generated files on nightly
Co-authored-by: Brian Ginsburg <7957636+bgins@users.noreply.github.com> Signed-off-by: Zeeshan Lakhani <zeeshan.lakhani@gmail.com>
# Description This PR implements the following changes: - [x] Only render nodes when previous task has completed - [x] Remove task out-of-order error case - [x] Disable a workflow play button when the other workflow is active - [x] Prevent multiple runs of a workflow when it is active (spinner that replaces play button is not clickable) - [x] Rename `task.active` to `task.selected` to better indicate that this is UI state - [x] Remove receipt and instruction CID from completed task dropdown We had an issue where Firefox would receive receipts over the Websocket channel nearly simultaneously which resulted in out-of-order errors. This PR fixes that by delaying the rendering of nodes until each previous task has completed and removing the error case. ## Type of change - [x] Bug fix (non-breaking change that fixes an issue) - [x] Refactor ## Test plan (required) The play button should be disabled when the other workflow is running. The button should not handle click events when in a spinner state. Test in Firefox. No errors should be present and workflows should run and render as expected.
6471c7b
to
5f16416
Compare
Includes:
Closes #246.