mirror of
https://github.com/hibiken/asynq.git
synced 2026-04-26 07:25:56 +03:00
[PR #616] [CLOSED] Fal/dev #1810
Labels
No labels
CLI
bug
designing
documentation
duplicate
enhancement
good first issue
good first issue
help wanted
idea
invalid
investigate
needs-more-info
performance
pr-welcome
pull-request
question
wontfix
work in progress
work in progress
work-around-available
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/asynq#1810
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
📋 Pull Request Information
Original PR: https://github.com/hibiken/asynq/pull/616
Author: @Obelisk-The-Tormentor
Created: 2/15/2023
Status: ❌ Closed
Base:
master← Head:fal/dev📝 Commits (9)
519985ffeat: add custom unique key option4106a22ci(): remove go1.14 go1.15 from build workflow matrix94a4b7dchore(): export Scheduler.ID() Scheduler.Entries()a7e533fMerge pull request #2 from easyops-cn/xuy/export-scheduler-funcsf27a72cchore(): set scheduler_history TTL22f2c00chore(): set archived task TTL56f1b60Merge pull request #5 from 22dm/custom-unique-key21981e4chore(): 代码优化, *subscriber.start()支持PubSub channel的关闭校验, 如果channel被关闭,重新初始化PubSub获取channel3c5aa6fchore(): 代码优化, *subscriber.start()支持PubSub channel的关闭校验, 如果channel被关闭,重新初始化PubSub获取channel📊 Changes
10 files changed (+172 additions, -56 deletions)
View changed files
📝
.github/workflows/build.yml(+1 -1)📝
client.go(+30 -2)📝
client_test.go(+43 -0)📝
go.mod(+0 -1)📝
go.sum(+3 -32)📝
inspector.go(+6 -0)📝
internal/base/base.go(+6 -0)📝
internal/rdb/rdb.go(+10 -1)📝
scheduler.go(+38 -3)📝
subscriber.go(+35 -16)📄 Description
代码优化,*subscriber.start()处理时,PubSub channel如果被关闭,尝试重新初始化PubSub,重新获取Channel
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.