changed telemetry methods to async and changed refrences to await

[shaybc]

Context

Implementation

Screenshots

before	after

How to Test

Get in Touch

---

Important

Converted telemetry methods to asynchronous and updated references to use await in TelemetryService.ts, Cline.ts, and ClineProvider.ts.

• Telemetry Methods:
  • Changed telemetry methods in TelemetryService.ts to be asynchronous, including capture(), captureEvent(), captureTaskCreated(), captureTaskRestarted(), captureTaskCompleted(), captureConversationMessage(), captureModeSwitch(), and captureToolUsage().
• Usage Updates:
  • Updated references to telemetry methods to use await in Cline.ts for methods like captureToolUsage(), captureTaskCompleted(), and captureConversationMessage().
  • Updated captureModeSwitch() in ClineProvider.ts to use await.

^{This description was created by for 2004cca. It will automatically update as commits are pushed.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 2004cca

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[mrubens]

I don't think the telemetry should need to be blocking - seems like there's something else going on here

[shaybc]

I don't think the telemetry should need to be blocking - seems like there's something else going on here

i agree - i made a mistake, the solution is correct but it is not necessary, the problem i originally encountered was in the sub-tasks PR that did not cover a case of a command being ran in the end of a task, for some reason, after disabling the telemetry the ai decided for un-related reason to not execute a cmd - and that fixed the behavior not the disablement of the telemetry,

after doing some testing i found the solution to disable the telemetry (or making it sync) is not consistent, i have undo my changes and fixed the sub-tasks bug,

i am closing this PR and i will promote the next sub-tasks bug fix along with the user approval UI

[shaybc]

no need to convert telemetry calls to sync (awaited on async), telemetry calls should not come on the expense of the users

[mrubens]

Thank you for digging in!