Anton Kolesnikov

Results 79 issues of Anton Kolesnikov

- [x] Make `storage.Put` to work concurrently - [x] Make sure cache `GetOrCreate` is thread-safe - [x] Add storage queue params - [ ] Document new params - ~Build tags...

has conflicts

Currently `/label-values` endpoint is used to list the applications. This is inconvenient by number of reasons, first of all due to the fact that the cloud storage accesses the data...

enhancement
frontend
backend

In order to make user authentication more secure we need to implement refresh tokens with rotation: - https://auth0.com/docs/secure/tokens/refresh-tokens - https://auth0.com/docs/secure/tokens/refresh-tokens/refresh-token-rotation Useful links: - https://dev.to/cotter/localstorage-vs-cookies-all-you-need-to-know-about-storing-jwt-tokens-securely-in-the-front-end-15id Depends on: - https://github.com/pyroscope-io/pyroscope/pull/739 - https://github.com/pyroscope-io/pyroscope/issues/802

frontend
backend
auth

We need a basic mechanism that would allow Pyroscope Server to require the user to change their password. Administrators should be able to request this at any time. This is...

frontend
backend
auth

The user's email must be verified before it can be used for any notifications (such as password recovery). Depends on: #739

enhancement
frontend
backend
auth

We need to extend pyroscope admin CLI to allow creating API keys. At the present time, if internal authentication or the build-in admin account is disabled, it's hard to automate...

backend
auth

Users should be able to restore their passwords via email. Depends on: - #739 - #805 - #804

frontend
backend

Pyroscope supports only predefined profile types: `cpu`, `inuse_objects`, `alloc_memory`, etc. Based on the profile type, pyroscope determines the following parameters: - Whether the profile is _cumulative_ or not. At the...

enhancement
backend

Recently we announced new Go push client https://github.com/pyroscope-io/client. We should use it in self-profiling and stop using the old client internally (but still maintain). May depend on https://github.com/pyroscope-io/client/issues/6.

enhancement
backend
integrations

During testing pyroscope compatibility with the latest .NET versions I noticed that some symbols can't be resolved (substituted with `?!?`) for traces collected in **.NET Preview 7**: ![image](https://user-images.githubusercontent.com/12090599/189958516-d7daa3fe-44b2-46a2-b75b-1b0a4ac68040.png) We need...

dotnet