Comments (9)
/priority important-soon
from results.
i got the same problem. is there any idea to resove ?
from results.
We were able to solve this issue by removing this conditional in watcher/results/results.go 167
and the watcher was able to update the records.
if o.GetGeneration() != 0 && o.GetGeneration() == u.GetGeneration() {
// The record data already matches what's stored. Don't update
// since this will rev update times which throws off resource
// cleanup checks.
return curr, nil
}
But I don't think that's a permanent solution and it may cause problems in the future.
from results.
The intent behind this was to only update when there's a change to the data. If this isn't capturing all cases, we can do something more involved like a cmp.Equal or something similar.
Anyone happen to have a reference as to when generation increments?
from results.
I fount this link: https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/
The .metadata.generation value is incremented for all changes, except for changes to .metadata or .status.
So as I mentioned in the question, if the pipelinerun's status changes from Pending
to Succeeded
, record won't be updated.
from results.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen
with a justification.
/lifecycle stale
Send feedback to tektoncd/plumbing.
from results.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen
with a justification.
/lifecycle rotten
Send feedback to tektoncd/plumbing.
from results.
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
with a justification.
Mark the issue as fresh with /remove-lifecycle rotten
with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen
with a justification.
/close
Send feedback to tektoncd/plumbing.
from results.
@tekton-robot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen
with a justification.
Mark the issue as fresh with/remove-lifecycle rotten
with a justification.
If this issue should be exempted, mark the issue as frozen with/lifecycle frozen
with a justification./close
Send feedback to tektoncd/plumbing.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
from results.
Related Issues (20)
- Support ElasticSearch for Log Storage with Delegated Forwarding
- wrong response when using `()` and operators in filters HOT 2
- Results API server should watch configmap HOT 3
- Tekton Results objects not getting reconciled HOT 2
- GRPC Stream Leak on Error
- Subject Access Review in API RBAC is not considering Groups and Extra
- Logs not forwarded when PipelineRun status is "Completed"
- S3 client should support AssumeRoleWithWebIdentity
- Integration of Knative Adapter for Enhanced Logging in Tekton Results API HOT 3
- Persist TaskRun logs with timestamps (opt-in) HOT 1
- Expose Watcher configuration through configMap HOT 2
- Problem with how `result.summary.status` gets set
- TaskRuns gets deleted before PipelineRun completes if check_owner flag is disabled
- Document Pruning Behavior HOT 1
- Memory consumption of the watcher container keeps increasing over time
- log processing was not handling runs that have been cancelled
- prototype and document how to run multiple replicas of the api server HOT 2
- Storing logs fails with `operation error S3: UploadPart, https response error StatusCode: 404 ... api error NoSuchUpload: UnknownError` HOT 4
- UpdateLog calls from watcher intermittently fail with canceled context; no UpdateLog call error from watcher are re-reconciled
- Results and Record annotations are missing when summary annotation is used. HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from results.