Marcus Ilgner

That's my guess, too. I'm not sure which message is the culprit here, so I can't say for certain.

I'm currently working on a very similar issue and the query structure outlined in https://github.com/timescale/timescaledb-toolkit/issues/548#issuecomment-1284392569 seems to work very well. Unfortunately in the data I'm processing there is a special...

Seeing the same behaviour on my system. While working on a potential fix for #1170 I found myself unable to run the full test suite on my system without running...

Unfortunately, creating tables is only part of the picture. Over time, the overall schema will change. Sometimes operations will be as simple as renaming columns, but other times more complex...

Just ran into a bug where the first value of a queried timerange was `null`. This led the plugin to assume the field in question wasn't a number and renders...

In my project, `before(:create)` doesn't seem to be run at all. This leads to a situation where ``` FactoryBot.build(:my_factory).save! ``` works - the `after(:build)` callback runs as expected and fills...

I think I just stumbled over this issue when trying to write a serializer for `javax.measure.Unit`. The original definition for that one is `interface Unit`. But the serialization doesn't even...

> @milgner In your specific case you might be able to avoid it using `KSerializer`. Using `Nothing` should fit in the type constraints while also being a non-related serializer. Note...

Update: it looks like I might have been too hasty in my assumption that everything works when basic the mock on the `Impl` class. Even though the mock setup doesn't...

After checking this with the latest versions of Kotlin, mockk and Arrow, it turns out that this has the same root cause as #1130 which in turn is caused by...