Commit efb24456 authored by Kyle Clarke's avatar Kyle Clarke 💬

Typo in readme in regards to saftey breach.

parent dffa23c5
Pipeline #4130936 passed with stage
in 29 seconds
......@@ -222,10 +222,11 @@ job additions. To date Kevin has not been performance profiled so use micro/nano
seconds at your own peril.
**Will a runner run forever?**
***No!*** Internally Kevin has a safety check based on a `uint64` value range. If the runner iterates over the `uint64`
limit, Kevin will break from the running loop, just to be safe!. If this event should occur and you want/need to keep
processing, then simply check on the Kevin Error of `ErrJobMaximumTickBreach`. The remove the job from the schedule
and re-add as required. But do you really need a job to execute 18446744073709551615 times?
limit, Kevin will break from the running loop, just to be safe! If this event should occur and you want/need to keep
processing, then simply check the returned Kevin Error of `ErrJobMaximumTickBreach`. Then remove the existing job from
the schedule and re-add as required. But do you really need a job to execute 18446744073709551615 times?
**What about Return Values?**
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment