https://github.com/open-telemetry/opentelemetry-go-contrib/issues/6625
On Wednesday, January 15, 2025 at 11:02:37 PM UTC-8 John wrote:
> Thanks Kurtis for the advice. I was heading in that direction.
>
> This is definitely an OTEL problem. The minimal version required to
> create the issue:
>
Thanks Kurtis for the advice. I was heading in that direction.
This is definitely an OTEL problem. The minimal version required to create
the issue:
metrics.go
```go
package metrics
import (
_ "go.opentelemetry.io/contrib/instrumentation/host"
)
```
metrics_test.go
```go
package metrics
```
On Wed, Jan 15, 2025 at 8:31 PM John wrote:
> Hey Kurtis,
>
> Thanks for responding.
>
> Unfortunately, this does look like some type of OTEL problem. I was able
> to make a copy and strip out all the OTEL code. As soon as I did this,
> this stopped happening. Which means it is some type of OT
Hey Ian,
Certainly willing to fire up a debugger, but I’m assuming you don’t mean delve
and mean GDB for this?
I don’t generally use debuggers with Go, just making sure I am going down the
right path.
> On Jan 15, 2025, at 9:05 PM, Ian Lance Taylor wrote:
>
> On Wed, Jan 15, 2025 at 6:49
On Wed, Jan 15, 2025 at 6:49 PM John wrote:
>
> I'm running into a fault now when trying to run `go test -race`/
>
> I get the same when I disable CGO (because it lists a CGO signal in the
> fault):
> `CGO_ENABLED=0 go test -c -race`
>
> I've attempted to build a binary out of it and run it, with
Hey Kurtis,
Thanks for responding.
Unfortunately, this does look like some type of OTEL problem. I was able
to make a copy and strip out all the OTEL code. As soon as I did this,
this stopped happening. Which means it is some type of OTEL issue that I
should probably track down with the OTE
That your failure backtrace only has Go garbage collection threads and your
main thread is slightly surprising. It does look like your main function is
calling C code that is causing the SIGSEGV. Can you show us your "main"
package? You say you're using "various OTEL packages". Which ones
specifica
I'm running into a fault now when trying to run `go test -race`/
I get the same when I disable CGO (because it lists a CGO signal in the
fault):
`CGO_ENABLED=0 go test -c -race`
I've attempted to build a binary out of it and run it, with the same
results. This is not happening on all tests I
On Wed, Jan 15, 2025 at 4:07 AM Jamil Djadala wrote:
>
> As i understand, WriteTo is used to optimize write of multiple buffers
> to socket, using writev. But writev also ensure that these multiple
> buffers are written atomically, in case of concurrent writes, bytes
> from concurrent write are n
Since Go 1.21, the go directive in go.mod must be greater than or equal to
the go directive for all dependencies.
Almost certainly, in the first case there's a dependency that specifies
1.23.0 and in the second case all dependencies are 1.23 or older.
Jason
On Wednesday, January 15, 2025 at 1
Hello,
We set both go and toolchain in go.mod file, see below. But when executing
"go mod tidy" command, it automatically changes "go 1.23" to "go 1.23.0".
The local go version is 1.23.4 (darwin/arm64).
see.
https://github.com/etcd-io/etcd-operator/blob/7e8cf49ea8fef6f108084fb55cb437887dc71c3
Hi,
As i understand, WriteTo is used to optimize write of multiple buffers
to socket, using writev. But writev also ensure that these multiple
buffers are written atomically, in case of concurrent writes, bytes
from concurrent write are not inserted between buffers of writev.
https://cs.opensou
12 matches
Mail list logo
