Friedrich Große

Hey there :) I'm not 100% sure I understand the question completely but I guess you want to emit your own custom events? If that is true you can find...

I'm glad you found a solution. For your small code snipped I want to point you at [`Bot.Say(…)`][1] instead of `b.Adapter.Send(…)`. It does the same thing but also takes care...

We also noticed that recording the time in high throughput scenarios was a bottleneck, basically because we had a lot of debug messages. However I'm afraid you cannot merge this...

Using a `ValueConverter` did the trick just as @l3pp4rd suggested. This is the working code, assuming you are using `pq.StringArray(…)` in your code: ```go // StringArrayConverter is a database/sql driver.ValueConverter...

Did you ever get it to work? We have the same issue

If you generally want to supress stack traces on specific logger calls you can always pass the error message instead of the entire error: ``` log.Error("Oh noe", "error", err) //...

You can see at the top of your run when you expand the "Set up job" step and then click on `GITHUB_TOKEN Permissions`, that it actually has the wrong permissions...

Not sure how to proceed here as the issue seems to be in your repository or workflow/job configuration. I checked on [a recent job run][1] in your repo and verified...

To debug this, you can try if there is any effect when you remove the top-level `permissions` field. Since you only have a single job in your `Coverage Report` workflow,...

Yeah that makes sense. I didn't really think about forks yet but I think this action wouldn't work well for them exactly because of these (sensible) security defaults :thinking: