Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / mvniekerk/tokio-cron-scheduler issues and pull requests

#69 - Update num-derive

Pull Request - State: open - Opened by Jesse-Bakker 11 days ago

#68 - [requests] new_one_shot!().

Issue - State: open - Opened by okrightall 26 days ago

#67 - Update README.md

Pull Request - State: closed - Opened by tpmccallum about 2 months ago - 1 comment

#66 - The features "signal" didn't work when combined with Axum

Issue - State: open - Opened by linyihai about 2 months ago - 1 comment

#65 - Improve code quality

Issue - State: open - Opened by JakkuSakura 2 months ago - 1 comment

#64 - fix: offset logic calculated for east_opt not for west_opt

Pull Request - State: closed - Opened by rlienlaf 2 months ago - 1 comment

#63 - How to use reqwest or blocking inside

Issue - State: closed - Opened by baerwang 2 months ago

#62 - Fix misprint

Pull Request - State: closed - Opened by frederikhors 4 months ago - 1 comment

#60 - Added additional feature to allow to use log crate instead of tracing crate

Pull Request - State: closed - Opened by marioloko 5 months ago - 1 comment

#59 - Scheduler state or data shared across the jobs

Issue - State: open - Opened by vsavovski 5 months ago - 1 comment

#58 - Make channel capacity configurable

Issue - State: open - Opened by vsavovski 5 months ago

#57 - Getting a RecvError() no matter what I do

Issue - State: open - Opened by kaspar-p 8 months ago - 2 comments

#55 - Outdated example on crates.io

Issue - State: open - Opened by 0xMimir 9 months ago

#54 - Support Generic Storage Layer For Jobs? (MongoDB)

Issue - State: open - Opened by LuisOsta 10 months ago - 4 comments

#53 - Incorrect schedule delay after job adding(first execution)

Issue - State: closed - Opened by Dkwcs 10 months ago

#52 - Could scheduler resume jobs execution after reload?

Issue - State: open - Opened by Dkwcs 10 months ago - 3 comments

#51 - "0 0/1 15 * * ?" execute no result

Issue - State: open - Opened by zhengxingjian 11 months ago - 1 comment

#50 - Run tasks non-concurrently?

Issue - State: open - Opened by Zerowalker 11 months ago - 2 comments

#49 - Support using local time instead of utc for cron

Pull Request - State: closed - Opened by 4t145 12 months ago - 7 comments

#48 - Make `shutdown_on_signal` only available on Unix

Pull Request - State: closed - Opened by SandroHc about 1 year ago - 1 comment

#47 - utc problem!

Issue - State: closed - Opened by wing-zacharias about 1 year ago - 1 comment

#46 - Fix example in README

Pull Request - State: closed - Opened by sueskind about 1 year ago - 1 comment

#45 - cron syntax for run every 1 minute runs more often

Issue - State: closed - Opened by rbtcollins over 1 year ago - 1 comment

#44 - Custom code use Local time

Issue - State: closed - Opened by daiguadaidai over 1 year ago - 1 comment

#43 - fix missing whitespace when updating ticks

Pull Request - State: closed - Opened by grahamhub over 1 year ago - 1 comment

#42 - missing whitespace in PostgreSQL query when updating ticks

Issue - State: closed - Opened by grahamhub over 1 year ago

#41 - How to support run in LOCAL time

Issue - State: closed - Opened by daiguadaidai over 1 year ago - 1 comment

#40 - JobDeleter::remove gets stuck when called from tokio::spawn

Issue - State: closed - Opened by skrcka over 1 year ago - 3 comments

#39 - Example doesn't work (#37 continued?)

Issue - State: closed - Opened by tobymurray over 1 year ago - 2 comments

#38 - disable oldtime feature on chrono

Issue - State: closed - Opened by ImUrX over 1 year ago - 2 comments

#36 - Shutdown on signal feature only works on unix

Issue - State: closed - Opened by jupyterkat over 1 year ago - 4 comments
Labels: question

#35 - `Tick send error SendError(true)` after a while

Issue - State: open - Opened by jukanntenn over 1 year ago - 1 comment

#34 - Can't add job from within another job

Issue - State: closed - Opened by ghost over 1 year ago - 3 comments
Labels: question

#33 - Can't run in tokio::test ?

Issue - State: closed - Opened by killme2008 almost 2 years ago - 3 comments

#32 - Can there has an api to get a job next_run_time?

Issue - State: closed - Opened by Hellager almost 2 years ago - 3 comments

#31 - Examples are outdated

Issue - State: closed - Opened by PaulDotSH almost 2 years ago - 2 comments

#30 - Fix issues with signal handling not properly triggering shutdown

Pull Request - State: closed - Opened by tuck182 almost 2 years ago - 2 comments

#29 - Example is out of date

Issue - State: closed - Opened by inferiorhumanorgans almost 2 years ago - 2 comments

#28 - Thread dead lock occures

Issue - State: closed - Opened by gy0801151351 about 2 years ago - 2 comments

#27 - JobScheduler::new() - CantInit Error

Issue - State: closed - Opened by ev94 about 2 years ago - 7 comments

#26 - There is no way to define and use customized job store

Issue - State: closed - Opened by gy0801151351 about 2 years ago - 2 comments

#25 - Use with-uuid-1 feature for tokio-postgres

Pull Request - State: closed - Opened by tiqwab about 2 years ago - 1 comment

#24 - Can 'tokio-cron-scheduler' support run in LOCAL time?

Issue - State: closed - Opened by rts-gordon about 2 years ago - 5 comments

#23 - Missing `impl Error for JobSchedulerError`

Issue - State: closed - Opened by Czocher about 2 years ago - 1 comment

#22 - fix: cp on Windows

Pull Request - State: closed - Opened by wormtql about 2 years ago - 2 comments

#21 - Can't compile on Windows

Issue - State: closed - Opened by wormtql about 2 years ago - 1 comment

#20 - How about do not depend on prost if not enable nats_storage or postgres_storage?

Issue - State: closed - Opened by deftsp about 2 years ago - 8 comments

#19 - Cannot remove jobs because adding does not return a UUID

Issue - State: closed - Opened by mmstick about 2 years ago - 2 comments

#18 - 0.6 Postgres

Pull Request - State: closed - Opened by mvniekerk about 2 years ago

#17 - 0.6 beta 2

Pull Request - State: closed - Opened by mvniekerk about 2 years ago

#16 - Sporadic deadlock happens on v0.6.0

Issue - State: closed - Opened by BlackDex over 2 years ago - 5 comments

#15 - future created by async block is not `Sync`

Issue - State: closed - Opened by sheldonth over 2 years ago - 3 comments

#14 - Shutdown handling/signal example

Issue - State: closed - Opened by fmorency over 2 years ago - 6 comments

#13 - Remove unnecessary Sync

Pull Request - State: closed - Opened by vkill over 2 years ago - 5 comments

#12 - 0.6 beta 1

Pull Request - State: closed - Opened by mvniekerk over 2 years ago

#11 - Allow cron::Schedules as function arguments

Pull Request - State: closed - Opened by hgzimmerman over 2 years ago - 8 comments

#10 - How to use async function in run thread?

Issue - State: closed - Opened by marvinpan8 over 2 years ago - 1 comment

#9 - sample on crates.io has a borrow error.

Issue - State: closed - Opened by davehorner over 2 years ago - 1 comment

#8 - Can't run an async function that operate MySQL via Connection Pool.

Issue - State: closed - Opened by rts-gordon over 2 years ago - 8 comments

#7 - sample in readme miss dependencies

Issue - State: closed - Opened by elderbig over 2 years ago - 1 comment

#6 - hi, can you support some shortcut to create cron expresions, such as daily?

Issue - State: closed - Opened by vidyli almost 3 years ago - 2 comments
Labels: enhancement

#5 - Remove unused Tokio feature flags

Pull Request - State: closed - Opened by mucinoab almost 3 years ago - 1 comment

#4 - can I use await in the job?

Issue - State: closed - Opened by mrxiaozhuox about 3 years ago - 4 comments
Labels: enhancement

#3 - Lots of problems in documentation

Issue - State: closed - Opened by krojew about 3 years ago - 2 comments
Labels: documentation

#2 - Should have a way to deal with graceful shutdown

Issue - State: closed - Opened by dialtone about 3 years ago - 4 comments

#1 - Remove job funcitonality unusable

Issue - State: closed - Opened by MrDarthShoe over 3 years ago - 3 comments