🤗 [Question]: Is `fiber.Ctx` thread safe? If not, is that documented? about fiber

[welcome]

Thanks for opening your first issue here! 🎉 Be sure to follow the issue template! If you need help or want to chat with us, join us on Discord https://gofiber.io/discord

[ReneWerner87]

https://docs.gofiber.io/#zero-allocation

correct, the request/response context is not thread safe or cannot be used in other concurrent go routines outside of this flow

you need to make copies of the values you want to use in this flow

we achieve this performance in our framework by reusing this context after the run for the next one

[ReneWerner87]

@omaskery does it answer your question?

[omaskery]

Ah, so to me the wording of the documentation makes it clear that you should not keep references to Ctx that outlive the handler's execution, but it does not make clear to me that it isn't thread-safe during the execution of a handler.

If I'm understanding you correctly that the fiber.Ctx is not thread-safe, even within the handler's duration, then I think you've answered my question, thank you.

I do feel that it might be worth explicitly stating in the documentation that this struct is not thread-safe. What do you think?

[ReneWerner87]

I do feel that it might be worth explicitly stating in the documentation that this struct is not thread-safe. What do you think?

yes that would be good

can you provide this as a contribution to our current documentation ?

[omaskery]

Yeah I'm willing to give that a go :)

[umardev500]

I still never get it, hard to understand for me haha

[ReneWerner87]

I still never get it, hard to understand for me haha

what do you not understand ? the context cannot be torn out of its process and simply be used in a parallel process
because it is reused after the request response process
and it is not designed to access the methods in parallel, there might be problems in some places
therefore you should extract the values beforehand and use them in the parallel run