[stelfrag]

#18218 removed _aclk_queue_query(), which set both query->created_tv and query->created, but moved only created_tv into aclk_query_new(). created is serialized as t-rx in every HTTP reply to Cloud, so it has been 0 since then.

This stamps created with now_realtime_usec() in aclk_query_new(), as before.

Tested on a live agent with a fake-Cloud harness that injects HTTP cmd messages through the real receive path and captures the reply headers (30 queries per build, success and invalid-request replies): master sends t-rx: 0 in every reply; with the fix t-rx is the receipt wall time, 3–37 ms after injection and under 1 ms before the reply.

Summary by CodeRabbit

• Improvements
  • Queued queries now record both realtime and monotonic timestamps, improving the available timing information.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: f55f4c25-90af-49ee-90f8-ef241b039668

---

---

📥 Commits

Reviewing files that changed from the base of the PR and between 1af7795 and 17e6103.

---

---

📒 Files selected for processing (1)

• src/aclk/aclk_query_queue.c

---

---

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 8 remain after this review.

---

---

---

📝 Walkthrough

📝 Walkthrough

Walkthrough

aclk_query_new now records the query creation time in microseconds using the realtime clock. The existing monotonic timestamp remains.

Changes

ACLK query timestamp

Layer / File(s)	Summary
Record query creation time src/aclk/aclk_query_queue.c	aclk_query_new sets query->created to the current realtime time in microseconds.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~2 minutes

Change: Bug fix

---

---

Merge Risk: ⚪ Minimal · up to 17e61

Cloud query replies should include the restored receipt timestamp. The supplied change context indicates no actionable risk requiring a pre-merge fix.

Pre-merge checks | 4 | 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage		Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 1 files.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly and concisely describes the main change: restoring the t-rx timestamp in HTTP replies by recording the query creation time.

---

• Fix all pre-merge checks with AI

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

---

---

---

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

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.}

[cubic-dev-ai]

No issues found across 1 file

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{View guided diff | Re-trigger cubic}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[thiagoftsm]

Cloud is working as expected. LGTM!