[PR #644] [CLOSED] Support cronspec seconds field #804

New issue

Closed

opened 2026-03-02 06:05:40 +03:00 by kerem · 0 comments

kerem commented

2026-03-02 06:05:40 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/hibiken/asynq/pull/644
Author: @acaloiaro
Created: 4/12/2023
Status: ❌ Closed

Base: master ← Head: add-cronspec-seconds-field-support

📝 Commits (1)

d875dfa Support cronspec seconds field

📊 Changes

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

View changed files

📝 scheduler.go (+1 -1)

📄 Description

This is related to #447

As a user it can be surprising to discover how to specify asynq tasks with second-level resolution.

This extends the cronspec parser to support the seconds field. Currently, cronspecs must be specified with the @every Xs format when they're to be run more frequently than every minute.

This PR permits the 6th cronspec field (seconds) to be used when specifying periodic asynq tasks.

E.g.

@every 1s -> * * * * * *
@every 30s -> */30 * * * * *

_{🔄 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/hibiken/asynq/pull/644 **Author:** [@acaloiaro](https://github.com/acaloiaro) **Created:** 4/12/2023 **Status:** ❌ Closed **Base:** `master` ← **Head:** `add-cronspec-seconds-field-support` --- ### 📝 Commits (1) - [`d875dfa`](https://github.com/hibiken/asynq/commit/d875dfa7ec859a521a91dfe2c8892310320c6fa9) Support cronspec seconds field ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `scheduler.go` (+1 -1) </details> ### 📄 Description This is related to #447 As a user it can be surprising to discover how to specify asynq tasks with second-level resolution. This extends the cronspec parser to support the seconds field. Currently, cronspecs must be specified with the `@every Xs` format when they're to be run more frequently than every minute. This PR permits the 6th cronspec field (seconds) to be used when specifying periodic asynq tasks. E.g. `@every 1s` -> `* * * * * *` `@every 30s` -> `*/30 * * * * *` --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>