Pass a copy of the main coroutine context to the subroutine context
In PHP, coroutine is a powerful programming tool that can improve the execution efficiency of code. In coroutines, it is a common operation to pass a copy of the main coroutine context to the subroutine context. In this way, the context data of the main coroutine can be accessed in the subroutine to realize data sharing and transfer. This process is very simple in PHP, and you only need to use the yield keyword. In this article, we will introduce to you in detail how to pass a copy of the main coroutine context to the subroutine context, and give you some example code to help you better understand and apply this feature.
Question content
I have a golang API endpoint and its associated context.
The endpoint needs to do some heavy lifting behind the scenes, so I create a new subroutine inside the main endpoint and then return the response itself.
To handle context cancellation, I create a background context and pass it to the subroutine as a new context.
The problem is that by doing this, yes I can execute the background subroutine, but the values in the main context, such as request ID, span ID, etc. (most of the keys I don't know), are used for tracing will be lost.
How to pass parent context to child routine without canceling execution even after response is sent to client.
edit
I'm not passing any value into the context. But initially we are passing the request-id, span-id, etc. required for tracking. This information is all in context. This is an internal library and the context is where we save it.
I know this is an anti-pattern of passing values using context, no value will be passed except the request ID and other values that are important to the library and not the business logic
Workaround
When you cancel a parent context, all contexts derived from it will also be cancelled. So you are correct to create a new context for the goroutine generated by the request handler.
When you create a new context, you should copy all the values you are interested in from the original context to the new context. However, you say you don't know all the keys. Therefore, you can still keep a reference to the parent context so that it can be queried for its value. Something like this:
type nestedContext struct { context.Context parent context.Context } func (n nestedContext) Value(key any) any { return n.parent.Value(key) } ... newContext := nestedContext{ Context:context.Background(), parent: parentContext, }
This will create a new context from context.background()
which will look up the value from the canceled parent context.
Pass newcontext
as the context to the goroutine created from the handler.
The above is the detailed content of Pass a copy of the main coroutine context to the subroutine context. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



OpenSSL, as an open source library widely used in secure communications, provides encryption algorithms, keys and certificate management functions. However, there are some known security vulnerabilities in its historical version, some of which are extremely harmful. This article will focus on common vulnerabilities and response measures for OpenSSL in Debian systems. DebianOpenSSL known vulnerabilities: OpenSSL has experienced several serious vulnerabilities, such as: Heart Bleeding Vulnerability (CVE-2014-0160): This vulnerability affects OpenSSL 1.0.1 to 1.0.1f and 1.0.2 to 1.0.2 beta versions. An attacker can use this vulnerability to unauthorized read sensitive information on the server, including encryption keys, etc.

The article discusses writing unit tests in Go, covering best practices, mocking techniques, and tools for efficient test management.

The article explains how to use the pprof tool for analyzing Go performance, including enabling profiling, collecting data, and identifying common bottlenecks like CPU and memory issues.Character count: 159

The library used for floating-point number operation in Go language introduces how to ensure the accuracy is...

Queue threading problem in Go crawler Colly explores the problem of using the Colly crawler library in Go language, developers often encounter problems with threads and request queues. �...

This article introduces a variety of methods and tools to monitor PostgreSQL databases under the Debian system, helping you to fully grasp database performance monitoring. 1. Use PostgreSQL to build-in monitoring view PostgreSQL itself provides multiple views for monitoring database activities: pg_stat_activity: displays database activities in real time, including connections, queries, transactions and other information. pg_stat_replication: Monitors replication status, especially suitable for stream replication clusters. pg_stat_database: Provides database statistics, such as database size, transaction commit/rollback times and other key indicators. 2. Use log analysis tool pgBadg

Backend learning path: The exploration journey from front-end to back-end As a back-end beginner who transforms from front-end development, you already have the foundation of nodejs,...

The problem of using RedisStream to implement message queues in Go language is using Go language and Redis...
