HangfireIO/Hangfire

System.Globalization.CultureNotFoundException. Culture is not supported.

Open

#964 建立於 2017年8月11日

在 GitHub 查看
 (1 留言) (0 反應) (0 負責人)C# (10,068 star) (1,748 fork)batch import
a: corehelp wanted

描述

I'm using:

  • HangFire.Core v1.4.6
  • Hangfire.SqlServer v1.4.6
  • Windows 10 x64
  • IIS 8.5 (not important probably but still)

Suddenly I got failed jobs containing next exception:

System.Globalization.CultureNotFoundException

Culture is not supported. Parameter name: name en-SI is an invalid culture identifier.

System.Globalization.CultureNotFoundException: Culture is not supported.
Parameter name: name
en-SI is an invalid culture identifier.
   at System.Globalization.CultureInfo..ctor(String name, Boolean useUserOverride)
   at Hangfire.CaptureCultureAttribute.OnPerforming(PerformingContext filterContext)
   at Hangfire.Server.BackgroundJobPerformer.InvokePerformFilter(IServerFilter filter, PerformingContext preContext, Func`1 continuation)

Hangfire was using two servers if that makes any difference. After deleting all Hangfire tables it now works, but still don't know why this happened.

But why does CultureNotFoundException occurs? Thread is always running under valid culturename. I found next post: https://stackoverflow.com/questions/38690850/disable-preservecultureattribute-in-hangfire

貢獻者指南

技術棧
csharp
領域
backend
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
under 1 hour
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
C#.NET globalizationHangfire basics
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
70
研究方向
The issue is a CultureNotFoundException when Hangfire encounters the 'en SI' culture identifier. The key file is CaptureCultureAttribute.cs, specifically the OnPerforming method. Investigate how the culture is captured and consider adding validation to fall back to InvariantCulture or the system default culture when the specified culture is not supported. The StackOverflow link provided may offer additional insights. A potential fix could involve wrapping the culture creation in a try catch or using a culture factory method.