When previous records of container timing should be invalidated?
Open
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 72
- Forks
- 10
- Avg merge
- 9d 15h
- Merged PRs (30d)
- 3
Description
There are several scenarios where changes in the containertiming attributes changes may have effect on the events generated for container timing:
- When
containertimingis removed from a node. - When the
containertimingidentifier changes. - When the nesting policy changes for a node.
What should we do in each case for the events that may have been collected before the attribute change?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by reviewing the three listed attribute-change scenarios and the existing Container Timing event behavior, then determine the intended invalidation rules for previously collected events; done means each scenario has an agreed, documented outcome.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100