Open coreyward opened 6 years ago
What's up with that? why in 2020 thread safe can't be done?
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. Thank you for your contributions.
Its not fixed
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. Thank you for your contributions.
Not stale, just being ignored by the Facebook team.
Not stale.
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. Thank you for your contributions.
Still not stale.
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. Thank you for your contributions.
Stale bot, please trade yourself in for Ignored bot. This issue is still not stale.
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. Thank you for your contributions.
What's up with that? why in 2020 thread safe can't be done?
why in 2022 thread safe can't be done?
The README has the following disclaimer:
Is there a particular area of the SDK that isn't thread-safe that can be avoided? I see the
with_session
method definitely isn't; can we avoid some elements to utilize the library in threaded background workers now?If not, what can be done to improve thread safety? Is it a matter of prioritization? Allocation of resources? Lack of interest?
Thanks!