Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
dmv.community is one of the many independent Mastodon servers you can use to participate in the fediverse.
A small regional Mastodon instance for those in the DC, Maryland, and Virginia areas. Local news, commentary, and conversation.

Administered by:

Server stats:

163
active users

dmv.community: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#golang

33 posts21 participants2 posts today
Public
Golang Weekly

Capturing console output in Go tests

rednafi.com/go/capture_console

Discussions: discu.eu/q/https://rednafi.com

Redowan's Reflections · Capturing console output in Go testsIdeally, every function that writes to the stdout probably should ask for a io.Writer and write to it instead. However, it’s common to encounter functions like this: func frobnicate() { fmt.Println("do something") } This would be easier to test if frobnicate would ask for a writer to write to. For instance: func frobnicate(w io.Writer) { fmt.Fprintln(w, "do something") } You could pass os.Stdout to frobnicate explicitly to write to the console: func main() { frobnicate(os.Stdout) } This behaves exactly the same way as the first version of frobnicate.
#golang#programming
Public
Socket

🐚 New from the Socket Threat Research Team: threat actors are weaponizing shell techniques to persist, pivot, and exfiltrate across npm, PyPI, Go, and more.

Reverse shells. Web shells. TCP tunnels. It's all in here.

🐢 Read: socket.dev/blog/shell-usage
#JavaScript #Golang #Python #Java

SocketTurtles, Clams, and Cyber Threat Actors: Shell Usage - Socke...The Socket Threat Research Team uncovers how threat actors weaponize shell techniques across npm, PyPI, and Go ecosystems to maintain persistence and ...
ExploreLive feeds
About