This is an important release that makes timeout detection much more robust. First of all, Redis server itself now acts as a single time authority for performing timeout checks for both jobs and servers rather than UTC time of a current Hangfire Server. So you don’t need to use synchronized clocks to prevent false positives for timeout checks.
Continue Reading →rss feed Blog
Hangfire.Pro.Redis 2.4.0
-
by
@odinserj
- release, hangfire-pro
- 0 Comments
- Edit on GitHub
Hangfire 1.6.22
-
by
@odinserj
- release, hangfire-core
- 0 Comments
- Edit on GitHub
This version finally fixes interoperability issues that arise, because primitive built-in types like String reside in assemblies with different name in .NET Core (System.Private.CoreLib.dll) and .NET Framework (mscorlib.dll). This led to JobLoadException in .NET Framework-based applications, when they tried to perform background jobs created by a .NET Core-based one. The new version solves this problem by re-writing assembly name when resolving a type for a job and its parameters.
Hangfire.Pro 2.1.2
-
by
@odinserj
- release, hangfire-pro
- 0 Comments
- Edit on GitHub
This release fixes unexpected behaviors when we are cancelling a batch that has continuations for its inner items as in the following sample. When those continuations have continuations themselves, or when we attaching a job with continuation to a cancelled batch, our leaf-level continuations stuck in the awaiting or non-initialized state until queued manually.
Continue Reading →Hangfire 1.6.21
-
by
@odinserj
- release, hangfire-core
- 0 Comments
- Edit on GitHub
This are late release notes for a maintenance release with minor fixes. Please see the list of fixed issues below and upgrade if necessary.
Continue Reading →Hangfire.Pro.Redis 2.3.0
-
by
@odinserj
- release, hangfire-pro
- 0 Comments
- Edit on GitHub
The goal of this release is to resolve the timeout issues that appear in .NET Core 2.X applications. Such behavior was caused by networking implementation of SE.Redis, which posted Redis response processing logic to thread pool’s worker threads, instead of completion ports or custom threads, due to the lack of the corresponding API in netstandard1.X specification.