You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
some people (i fixed my code already) include a PerformContext into the arguments when scheduling jobs (for example from inside a job)
Example: BackgroundJob.Enqueue(() => new MyJobClass().SomeMethod(performContext, foo, bar));
Expected: a null as argument stored in the database
Actually: the full perfomContext is serialized in whole and stored in the database
when some job is queueing\scheduling other jobs, and maybe a couple of layers deep you end up with a whole bunch of nested PerfomContext's nested inside each other
so it would be nice to prevent this, and some users may do this without knowing this is very bad
some people (i fixed my code already) include a PerformContext into the arguments when scheduling jobs (for example from inside a job)
Example:
BackgroundJob.Enqueue(() => new MyJobClass().SomeMethod(performContext, foo, bar));
Expected: a
null
as argument stored in the databaseActually: the full perfomContext is serialized in whole and stored in the database
when some job is queueing\scheduling other jobs, and maybe a couple of layers deep you end up with a whole bunch of nested PerfomContext's nested inside each other
so it would be nice to prevent this, and some users may do this without knowing this is very bad
Versions:
Hangfire.Core 1.6.22
Hangfire.SqlServer 1.6.22
The text was updated successfully, but these errors were encountered: