openclaw/clawhub
1
0
Fork 0
mirror of https://github.com/openclaw/clawhub.git synced 2026-07-21 19:25:25 -04:00
Code Issues 183 Packages Projects Releases 1 Wiki Activity

[PR #176] [CLOSED] fix: reduce skill stat processing interval from 15m to 1m #282

New Issue
Closed
opened 2026-02-15 17:16:39 -05:00 by yindo · 0 comments
yindo commented 2026-02-15 17:16:39 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/openclaw/clawhub/pull/176
Author: @tanujbhaud
Created: 2/8/2026
Status: ❌ Closed

Base: main ← Head: fix/stat-metrics-delay

📝 Commits (10+)

  • 500c51f fix: reduce skill stat processing interval from 15m to 1m
  • 06ed8b5 fix: use correct numeric interval for cron
  • b68d9d9 fix: use correct object format for cron interval
  • 60093b8 fix: attempt bare numeric interval for cron (testing)
  • 64dfb78 fix: revert to object format for cron interval as per documentation
  • 5e84e5f fix: use numeric millisecond interval for cron to ensure compatibility
  • 9271596 fix: restore standard { minutes: 1 } object format for cron interval
  • ae91a65 fix: format cron interval object for clarity
  • e9bffcb fix: use valid cron syntax for skill-stat-events
  • b4a66c4 fix: use valid crons.interval instead of schedule for 1m interval

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 convex/crons.ts (+1 -1)

📄 Description

This improves the responsiveness of download and star metrics on the website, addressing user feedback that these metrics were not updating in a timely manner (Issue #156).

Greptile Overview

Greptile Summary

This PR updates the Convex cron schedule for skill-stat processing to run much more frequently (from 15 minutes to 1 minute) to make download/star metrics update more responsively on the site (Issue #156). The change is localized to the Convex cron configuration (convex/crons.ts).

Confidence Score: 3/5

  • This PR is low-risk if the cron syntax is correct, but as written it likely won’t run at all.
  • Only one file changes and the intent is straightforward, but the new schedule string appears to use a non-cron duration format that typical Convex cron scheduling won’t accept, which would prevent the job from registering/executing.
  • convex/crons.ts

(4/5) You can add custom instructions or style guidelines for the agent here!

Context used:

  • Context from dashboard - AGENTS.md (source)

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/openclaw/clawhub/pull/176 **Author:** [@tanujbhaud](https://github.com/tanujbhaud) **Created:** 2/8/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/stat-metrics-delay` --- ### 📝 Commits (10+) - [`500c51f`](https://github.com/openclaw/clawhub/commit/500c51f7eacc9405fc1b88430ed0d76ab595980e) fix: reduce skill stat processing interval from 15m to 1m - [`06ed8b5`](https://github.com/openclaw/clawhub/commit/06ed8b544b5a08c344ad4ef413106be5e62f3778) fix: use correct numeric interval for cron - [`b68d9d9`](https://github.com/openclaw/clawhub/commit/b68d9d9831502123ffd9e88c38d7907877a0b4d1) fix: use correct object format for cron interval - [`60093b8`](https://github.com/openclaw/clawhub/commit/60093b888b3c87f8d674a26e67c4fe05e59ed0b0) fix: attempt bare numeric interval for cron (testing) - [`64dfb78`](https://github.com/openclaw/clawhub/commit/64dfb78901b36497dc2b8c3439e7f4a98a35a589) fix: revert to object format for cron interval as per documentation - [`5e84e5f`](https://github.com/openclaw/clawhub/commit/5e84e5ff97fd5437fb676a34d77ab59ea611b581) fix: use numeric millisecond interval for cron to ensure compatibility - [`9271596`](https://github.com/openclaw/clawhub/commit/92715963cc31b3e00ef76df6b7b8796aaa9312a5) fix: restore standard { minutes: 1 } object format for cron interval - [`ae91a65`](https://github.com/openclaw/clawhub/commit/ae91a65493ea12468e240c00e98f4e4a1c748717) fix: format cron interval object for clarity - [`e9bffcb`](https://github.com/openclaw/clawhub/commit/e9bffcbc5b3ca08524c5dda1f5d49346d248b0b9) fix: use valid cron syntax for skill-stat-events - [`b4a66c4`](https://github.com/openclaw/clawhub/commit/b4a66c4c0a3a75fc25729bc155ceea2535f712d6) fix: use valid crons.interval instead of schedule for 1m interval ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `convex/crons.ts` (+1 -1) </details> ### 📄 Description This improves the responsiveness of download and star metrics on the website, addressing user feedback that these metrics were not updating in a timely manner (Issue #156). <!-- greptile_comment --> <h2>Greptile Overview</h2> <h3>Greptile Summary</h3> This PR updates the Convex cron schedule for skill-stat processing to run much more frequently (from 15 minutes to 1 minute) to make download/star metrics update more responsively on the site (Issue #156). The change is localized to the Convex cron configuration (`convex/crons.ts`). <h3>Confidence Score: 3/5</h3> - This PR is low-risk if the cron syntax is correct, but as written it likely won’t run at all. - Only one file changes and the intent is straightforward, but the new schedule string appears to use a non-cron duration format that typical Convex cron scheduling won’t accept, which would prevent the job from registering/executing. - convex/crons.ts <!-- greptile_other_comments_section --> <sub>(4/5) You can add custom instructions or style guidelines for the agent [here](https://app.greptile.com/review/github)!</sub> **Context used:** - Context from `dashboard` - AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=a1d58d20-b4dd-4cbb-973a-9fd7824e1921)) <!-- /greptile_comment --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-15 17:16:39 -05:00
yindo closed this issue 2026-02-15 17:16:39 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
pull-request
Mirrored from GitHub Pull Request
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: openclaw/clawhub#282
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?