Anton Kolesnikov

@petethepig I have updated the PR so that it won't affect existing deployments: storage queue will have one worker by default, thus effectively doing writes synchronously. Please, give it a...

Thank you for reporting the issue @ArtemTrofimushkin! Unfortunately, we haven't implemented [support for .NET 6](https://pyroscope.io/docs/dotnet/#supported-net-versions) yet. I'll see if we can do this quickly.

Oh, good to know - thank you for sharing, that's really helpful! I guess the example program may not trigger the crash because it collects the trace data just once...

I didn't manage to reproduce the issue with the latest .NET 6 versions (

Yeah, we definitely should make it work with spaces. As a quick fix I'm thinking about using regex for tag matchers instead of parsing, e.g something like [this](https://go.dev/play/p/wSe9Dr3ibUG): `^\s*(\w*)\s*(=|=~|!=|!~)\s*"(.*)"\s*$`. The...

Thank you for creating the issue @Honst211! Is this an error you're seeing when running `pyroscope server` on Windows or it happens in other context? I'm afraid but pyroscope server...

Looks like the data has been corrupted. Are these messages repeating with the same numbers in the key name (for example, `pyroscope.server.cpu{}:5:1644403200`) or they are changing? Do you see similar...

Also, could you please clarify which Go client you are using: - github.com/pyroscope-io/client/pyroscope - github.com/pyroscope-io/pyroscope/pkg/agent/profiler

I'd say it should work fine unless the tree size reaches hundreds of megabytes. The relation between the error message and the HTTP timeout is pretty indirect - the code...

I can't say I fully support the idea of modular API in pyroscope server. Regarding API groups: although, I see _some_ pros for us as maintainers of the API, I...