Align report and log timestamps with fosslight_util time helpers

[bjk7119]

No description provided.

[coderabbitai]

Warning

Review limit reached

@bjk7119, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 38 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 5bb17ca7-ac22-4c37-a079-7f5275dc66fb

📥 Commits

Reviewing files that changed from the base of the PR and between 0591fb2 and 9ef4f68.

📒 Files selected for processing (2)

• pyproject.toml
• src/fosslight_android/android_binary_analysis.py

📝 Walkthrough

Walkthrough

Updates the utility dependency and Android scan timestamp handling to use UTC helpers, shared filename timestamps, measured runtime reporting, and utility-based result-log dumping.

Changes

UTC timestamp and reporting flow

Layer / File(s)	Summary
UTC timestamps and output paths pyproject.toml, src/fosslight_android/android_binary_analysis.py	The utility dependency is raised to >=2.2.2; scan start and output filenames now use UTC timestamp helpers, including intermediate results, reports, logs, and notice archives.
Measured runtime and result-log output src/fosslight_android/android_binary_analysis.py	Final reporting records the UTC finish time, reads runtime from scan_item.cover.running_time, and uses dump_result_log.

Estimated code review effort: 2 (Simple) | ~10 minutes

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.
Description check	❓ Inconclusive	No pull request description was provided, so there is no meaningful text to evaluate.	Add a brief description of the timestamp helper changes and affected outputs.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly matches the main change: moving report and log timestamps to fosslight_util time helpers.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch running

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}