Log creating single malformed entry immediately following enrollment
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 303
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
I'm seeing this occur on both the machines in front of me right now whereby after a device goes from unenrolled to enrolled, there seems to be a collision of write to the logfile which look like this:
```
Waiting for DEP record check...
Waiting foChecking mdm status - modern
MDM enrolled device 10.14.5
Checking mdm status - modern
```
Doesn't seem to be a big deal, and feel free to close this if it is a "Won't fix" sort of thing, just wanted to raise it before it forever fell out of the depths of my brainbucket.
Contributor guide
No contributing guide indexed for this repository
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
Reproduce the transition from unenrolled to enrolled and capture the logfile output around the DEP record check and MDM status checks. Trace where these messages are written and verify that enrollment no longer produces interleaved or malformed log entries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100