2.3/RC1 Filter Text example KF component doesn't work
See original GitHub issueDescribe the issue A clear and concise description of what the issue is.
To Reproduce Steps to reproduce the behavior:
- Create KF pipeline
- Add “Filter Text” component
- Try to export/run pipeline
- See error
Invalid pipeline operation: Missing field 'operation runtime image'.
The bug needs to be fixed or the component needs to be removed from the 2.3 distribution.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
All Articles - CUPS.org
CUPS 2.1.3 fixes some issues in the scheduler, sample drivers, and user commands. A detailed list of changes can be found in the...
Read more >Allow for data exchange between custom KFP components
Describe the issue Currently the VPE does not expose KFP component outputs, making it impossible for users to choose them as inputs for ......
Read more >ERROR: Invalid JSON string on filepicker - Moodle Tracker
I have been testing the filepicker upload by 5 people located at 5 different places, 3 of them not working getting the Invalid...
Read more >XWiki JavaScript API
XWiki JavaScript API · Observable XWiki Events · RequireJS and jQuery APIs · Get some information about the current document (Since 6.3M2) ·...
Read more >https://www.cs.cmu.edu/afs/andrew/scs/cs/15-494-sp...
The Contributing Authors and Group 42, Inc. specifically permit, without * fee, and encourage the use of this source code as a component...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@marthacryan found out that this is a canvas issue (?) where it doesn’t update (and hence doesn’t send) node properties in the case where no changes have been made to the properties before submitting. Can probably be bypassed in the pipeline editor