Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ExecuteContext can not free #906

Closed
virtualcca opened this issue Jun 2, 2017 · 0 comments
Closed

ExecuteContext can not free #906

virtualcca opened this issue Jun 2, 2017 · 0 comments
Labels
a: core t: bug
Milestone
Hangfire 1.8.18

Comments

@virtualcca
Copy link

If I use CallContext or AsyncLocal (base on ExecuteContext) to cache data
it can not free and always is first cache data

can I use ExecuteContext like Web Api or Mvc to cache data in execution flow????
@odinserj odinserj added this to the Hangfire 1.8.17 milestone Dec 11, 2024
odinserj added a commit that referenced this issue Dec 11, 2024
@odinserj
Don't leak AsyncLocal values from synchronous background job methods
92c9de3 
This behavior matches the behavior of async methods, where `AsyncLocal` values are allowed to flow into methods (will be useful for context-aware logging in the future), but not allowed to leak them outside of background job methods.
Closes #2409, #906
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
a: core t: bug
Milestone
Hangfire 1.8.18
Development

No branches or pull requests
2 participants
@odinserj @virtualcca