Ask questions, find answers and collaborate at work with Stack Overflow for Teams. Explore Teams Collectives™ on Stack Overflow Find centralized, trusted content and collaborate around the technologies you use most. Learn more about Collectives
BPFtrace As root, you can retrieve the kernel's TSC rate with bpftrace: # bpftrace -e 'BEGIN { printf("%u\n", *kaddr("tsc_khz")); exit(); }' 2>/dev/null | grep '^[1-9]' (tested it on CentOS 7 and Fedora 37) That is the value that is defined, exported and maintained/calibrated in arch/x86/kernel/tsc.c. Drgn Another way is to use drgn - a Python-programmable debugger: # python -c 'import drgn; p=drg
In the Kubernetes/Docker ecosystem there is a convention of using /healthz as a health-check endpoint for applications. Where does the name 'healthz' come from, and are there any particular semantics associated with that name?
I have seen several different test package naming strategies within Go and wanted to know what pros and cons of each are and which one I should use. Strategy 1: File name: github.com/user/myfunc.go package myfunc Test file name: github.com/user/myfunc_test.go package myfunc See bzip2 for an example. Strategy 2: File name: github.com/user/myfunc.go package myfunc Test file name: github.com/user/myf
I'm using the package: os/exec http://golang.org/pkg/os/exec/ to execute a command in the operating system but I don't seem to find the way to get the exit code. I can read the output though ie. package main import( "os/exec" "bytes" "fmt" "log" ) func main() { cmd := exec.Command("somecommand", "parameter") var out bytes.Buffer cmd.Stdout = &out if err := cmd.Run() ; err != nil { //log.Fatal( cmd
Is there an established best practice for separating unit tests and integration tests in GoLang (testify)? I have a mix of unit tests (which do not rely on any external resources and thus run really fast) and integration tests (which do rely on any external resources and thus run slower). So, I want to be able to control whether or not to include the integration tests when I say go test. The most
I'm in a progress to migrate to kuberenetes from docker-compose. One of the services we're using is rabbit-mq. When I try to deploy rabbit-mq 3.6.16-management I receive the error: /usr/local/bin/docker-entrypoint.sh: line 382: /etc/rabbitmq/rabbitmq.config: Permission denied. While it works in docker-compose deployment. Kuberentes: apiVersion: apps/v1 kind: Deployment metadata: labels: app: rabbi
I'm running Docker on CentOS 7, from time to time there's the following message displayed: Message from syslogd@dev-master at Mar 29 17:23:03 ... kernel:unregister_netdevice: waiting for lo to become free. Usage count = 1 I've googled a lot, read a lot of resources found and tried many ways like keeping my system updated, upgrading kernel etc, but the message still keeps showing up, it's not too o
I'd rather not have to push every little change to .travis.yml and every little change I make to the source in order to run the build. With jenkins you can download jenkins and run locally. Does travis offer something like this? Note: I've seen the travis-ci cli and downloaded it, but all it seems to do is call their API, which then connects to my GitHub repo, so if I don't push, it won't matter t
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く