learningequality / learningequality/studio
Staging time reflecting the main tree's time and not the time of the latest successful chef run
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 191
- Forks
- 307
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 10
Description
Observed behavior
The datetime on the staged channel should be based off the time when the channel was last modified (when the staging tree was updated from a recent chef run). Right now it seems the staging time isn't reflecting that but instead it appears to be reflecting the main tree's time.
Expected behavior
The datetime should reflect the latest successful chef run.
User-facing consequences
Impossible to know when was the last staging tree update performed.
Errors and logs
...
Additional information
Steps to reproduce the issue
Run a chef and observe the datetime on the staged channel.
Usage Details
...
cc @bjester
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
Start by reproducing the issue: run a chef and inspect the datetime shown for the staged channel. Trace how that timestamp is selected for the staging tree versus the main tree. Done means the displayed staging datetime matches the latest successful chef run and identifies the last staging update.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100