Rowan Seymour
Rowan Seymour
Hi @Kangaroux. If you can create this issue on https://github.com/nyaruka/django-hamlpy we'll try to get it fixed
Nevermind I see you already did
@jacobwegner it still works (thanks!), but I think in your solution you meant `("*",)` instead of `("*")`?
Same here.. if I call ```python client.captureMessage("test message", extra={"a": {"b": ["c"]}}) ``` my Sentry report looks like: 
This bit us recently in production. I get that implementing this is hard but this limitation really needs to be flagged in the documentation. Or even better replace that method...
Please if you're not going to fix it, just remove it. Better to break compatibility than let users unwittingly use a function we know is wrong.
Wouldn't it be cleaner and simpler to have the library defer to `func (t T) Equal(u T) bool` if it exists.. `time.Time` and `decimal.Decimal` already have that method. Like others...
Nil pointers getting silently wrapped into a non-nil interfaces is a go feature that has bitten us a few times. Can be tricky to spot and it'd be great if...
Would be nice to have an easy way to hook or wrap queries so we can catch and log long running queries at an application level
It definitely feels weird that I can have `[tool.poetry_bumpversion.file."foo/__init__.py"]` in my pyproject.toml, but if I don't have bumpversion installed, it's silently ignored. Ideally pyproject.toml ensures that building is consistent regardless...