When using gm_ctflow:spawn/1 and gm_ctflow:spawn_opt/2, the spawned process gets the same flow context (if any) as the parent. This way, calls to gm_ctflow:ct_log/2 appear in that flow context without the caller having to specify the flow.
When using `gm_ctflow:spawn/1` and `gm_ctflow:spawn_opt/2`, the spawned process gets the same flow context (if any) as the parent. This way, calls to `gm_ctflow:ct_log/2` appear in that flow context without the caller having to specify the flow.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
When using
gm_ctflow:spawn/1andgm_ctflow:spawn_opt/2, the spawned process gets the same flow context (if any) as the parent. This way, calls togm_ctflow:ct_log/2appear in that flow context without the caller having to specify the flow.