Sam Xie

The first thought in my head is only allowing the change to happen in the `Unreleased` section, which needs write a tool to parse markdown.

> As an alternative, could we keep the unreleased changes section in a separate file, and move it into the CHANGELOG as part of the release process? The tooling would...

Any process on this one? I have to iterate every SIG record that happened on the same day to confirm which one I want to watch. 😢

> Could this be an IAM issue? https://docs.aws.amazon.com/eks/latest/userguide/troubleshooting_iam.html#security-iam-troubleshoot-cannot-view-nodes-or-workloads I think it is not an IAM issue. The issue here is the EKS detector requires permission that a default namespace service...

> Another option, instead of environment variables, would be mounting a file inside the container. That file could be built in tmpfs, mounted read-only to a well known location like...

Thanks for filing this issue. @mnotti Would you like to paste errors so I will have more context about this issue? Also, do you have a small project that reproduces...

Hi, @mnotti thanks for providing the reproducer. `otelsql` assumes every `driver.Conn` implements these `driver.XXXContext`/`driver.XXXTx` interfaces that use `context.Context` for span collection. https://github.com/XSAM/otelsql/blob/b8a2dd4f7f2455ddf98eb8f08e5f2f87be809e08/conn.go#L24-L35 But if a `driver.Conn` did not implement these...

Hi @irl-segfault, Thanks for raising this issue. > I've set DisableSkipErr to true, however the spans representing the skipped operations (in this case, the sql.conn.Query spans) are still recorded. `DisableErrSkip`...

> I think the config params should be called OmitX to specify that they will not appear in the trace. DisableSkipErr specifically refers to the error attached to that operation's...

@grace-stytch Feel free to submit a PR if you are also interested. 🚀