-
It would be nice if go modules could be obfuscated too.
I found a tool which does some basic obfuscation on modules, maybe we can take some ideas from there:
https://github.com/mvdan/garble
-
# Introduction to Go Modules in Go v1.11, Goodbye GOPATH!
[http://localhost:2368/go-version-1-11-modules/](http://localhost:2368/go-version-1-11-modules/)
-
Operator Framework sites are built with Hugo and the Docsy theme, which was previously versioned as a git submodule. We had to go pretty far outside of the accepted best practices to get our custom th…
-
Scans the keys in the currently selected database.
Reference: https://redis.io/docs/latest/commands/scan/
## Client-Server Spec:
Command File: ./internal/modules/generic/commands.go
Test File:…
-
## Overview
There is a `dagger shell` feature in development. It already works, but needs more polish before making it stable. This issue tracks my requests for that polish.
### Calling dependen…
-
**Is your feature request related to a problem? Please describe.**
The Go mod analyzer has been broken in all kinds of ways and entirely unusable at least since 6.x came out. It seems like most issue…
-
Hello,
It doesn't seem like gb is being actively worked on, would it be interesting to move away from gb to a traditional go build?
I've created a fork that uses dep for dependencies and I also …
-
In go 1.16, go modules would be turned on by default. It is also a general trend of using go modules for building golang apps.
-
I couldn't find any reliable way to extract current package name, as in here: https://github.com/getsentry/raven-go/blob/238ebd86338d2e91cb5c84663d695877dd5d0ff4/stacktrace_test.go#L109-L135 due to Go…
-
Currently, vercel fails to build any golang serverless functions when using go1.21 or later, it outputs:
```
go: module . listed in go.work file requires go >= 1.21, but go.work lists go 1.18; to …