-
Notifications
You must be signed in to change notification settings - Fork 21
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
fix(pipeline): fix trigger error when start operator has field input
#287
Merged
donch1989
merged 5 commits into
main
from
huitang/ins-2514-bug-using-input-key-in-start-operator-will-cause-traces-data
Nov 5, 2023
Merged
fix(pipeline): fix trigger error when start operator has field input
#287
donch1989
merged 5 commits into
main
from
huitang/ins-2514-bug-using-input-key-in-start-operator-will-cause-traces-data
Nov 5, 2023
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
INS-2514 [Bug] using `input` key in start operator will cause traces data error
Is There an Existing Issue for This?
ProjectInstill VDP Describe the Bug
Steps to Reproduce
Actual Result
Expected Behavior
Technical Details
Anything Else?No response |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main instill-ai/community#287 +/- ##
=====================================
Coverage 0.00% 0.00%
=====================================
Files 7 7
Lines 2131 2131
=====================================
Misses 2131 2131
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
donch1989
force-pushed
the
huitang/ins-2514-bug-using-input-key-in-start-operator-will-cause-traces-data
branch
from
November 5, 2023 16:02
c8f64e9
to
f981dcf
Compare
donch1989
force-pushed
the
huitang/ins-2514-bug-using-input-key-in-start-operator-will-cause-traces-data
branch
from
November 5, 2023 16:04
f981dcf
to
ad27002
Compare
donch1989
deleted the
huitang/ins-2514-bug-using-input-key-in-start-operator-will-cause-traces-data
branch
November 5, 2023 16:21
donch1989
pushed a commit
that referenced
this pull request
Nov 11, 2023
🤖 I have created a release *beep* *boop* --- ## [0.16.2-alpha](v0.16.1-alpha...v0.16.2-alpha) (2023-11-11) ### Bug Fixes * **pipeline:** fix trigger error when start operator has field `input` ([#287](#287)) ([9f7ae76](9f7ae76)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
This was referenced Dec 25, 2023
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.
Because
input
in start operator, the trigger will be error when setinstill-return-traces=true
This commit
input
unrtf
package install errorinput
key in start operator will cause traces data error instill-core#575