Context retrieved from cobra subcommand is empty
I want a global timeout (set in rootCmd
), so I set it in rootCmd
is set as follows
ctxInit := context.Background() timeout := viper.GetInt("timeout") ctx, cancel := context.WithTimeout(ctxInit, time.Duration(timeout)*time.Second) defer cancel() cmd.SetContext(ctx)
Then in the subcommand
ctx := rootCmd.Context()
But ctx
is context.emptyCtx {}
Am I doing something wrong in setting/retrieving the context?
edit
My rootCmd
Statement
// rootCmd represents the base command when called without any subcommands var rootCmd = &cobra.Command{ Use: "my-cli", TraverseChildren: true, Short: "cli", PersistentPreRunE: func(cmd *cobra.Command, _ []string) error { var err error logger, err = logging.InitialiseLogger(*logLevel, *logFormat) if err != nil { return err } if err := viper.BindPFlags(cmd.Flags()); err != nil { return fmt.Errorf("error binding flags to %s command: %w\n", cmd.Name(), err) } if err := cloneMethodValidator(cmd); err != nil { return err } if err := InitConfig(false); err != nil { logger.Fatal("ERROR initiating configuration:\n", err) } ctxInit := context.Background() timeout := viper.GetInt("timeout") ctx, cancel := context.WithTimeout(ctxInit, time.Duration(timeout)*time.Second) defer cancel() cmd.SetContext(ctx) return nil }, }
Correct answer
As @Peter mentioned, cmd and rootCmd are not the same. The Cobra documentation describes PersistentPreRun(E)
:
So cmd.SetContext(ctx)
does not set the context of rootCmd, but sets the context of the subcommand.
Then in the subcommand you can use:
ctx := cmd.Context()
instead of rootCmd.Context()
.
The above is the detailed content of Context retrieved from cobra subcommand is empty. 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...
