OverflowException when <CheckForOverflowUnderflow>True</CheckForOverflowUnderflow>

[joesdu]

[odinserj]

Thanks, but could you provide more context on this? E.g. whether you set this option in your application or in Cronos directly, if the latter – what was the reason? I'm trying to understand the implications on Cronos package consumers.

[joesdu]

Thanks, but could you provide more context on this? E.g. whether you set this option in your application or in Cronos directly, if the latter – what was the reason? I'm trying to understand the implications on Cronos package consumers.

Later I'll try to get a demo with minimal repros and upload it to GitHub

[odinserj]

Ok, sounds good 👍

…

On Wednesday, June 4, 2025, Joe Du ***@***.***> wrote: *joesdu* left a comment (HangfireIO/Cronos#82) <#82 (comment)> Thanks, but could you provide more context on this? E.g. whether you set this option in your application or in Cronos directly, if the latter – what was the reason? I'm trying to understand the implications on Cronos package consumers. Later I'll try to get a demo with minimal repros and upload it to GitHub — Reply to this email directly, view it on GitHub <#82 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIHLPUNV2I7JIO4WTT3C6T3B3CFBAVCNFSM6AAAAAB6OT5EESVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMZZGQ2TSNJQG4> . You are receiving this because you commented.Message ID: ***@***.***>

-- Kind regards, Sergey Odinokov, CEO @ https://www.hangfire.io

[joesdu]

Ok, sounds good 👍
…

https://github.com/joesdu/CronosAppIssue

[odinserj]

I see that the problem occurs when one is recompiling the project with this option enabled, and doesn't cause any problems when NuGet package is consumed. This is not a bug on itself – the problematic fields aren't involved in regular calculations and only bit operations are used for them. So the thing is just that the project isn't yet prepared to be compiled with this option. If you'd like to change this – I will be happy to receive a pull request for that, that changes long to ulong, int to uint and so on.

[joesdu]

I see that the problem occurs when one is recompiling the project with this option enabled, and doesn't cause any problems when NuGet package is consumed. This is not a bug on itself – the problematic fields aren't involved in regular calculations and only bit operations are used for them. So the thing is just that the project isn't yet prepared to be compiled with this option. If you'd like to change this – I will be happy to receive a pull request for that, that changes long to ulong, int to uint and so on.

fixed in PR83