Florian PERRICHOT
Florian PERRICHOT
Without any information, your question cannot be answered. I think it's related to your data. Can your reproduce it? - if no, issue cannot be fixed with only the stack...
I think that the lock is done and the next call, the exception is thrown (see LocalLock source code) ; ``` private LocalLock(string resource, TimeSpan timeout) { _lock = Locks.GetOrAdd(resource,...
Thank you about the explanation of the issue and your MR proposal
As you can see, no PR was provided but some workarounds have been explained. Please don't hesitate to help.
Hi, The HangfireJobRentionAttribute is not used. The ExpirationManager uses the ExpireAt (IExpirable interface) property of the job.
The loop is not done one by one but by 1000 (of one of the managed type).
You've right, if this version does not fit to the purpose the more recent MemoryProvider could resolve it.
Thank you for your check and advise.
Hi, Seems that the console should be provider agnostic. As nothing is required by the console plugin, maybe it's a plugin issue ?
You've right. The order has been defined like this because others plugins use the same order before my first commit... So, seems to be an old choice. I'll change the...