Piotr Skalski

@onuralpszr sounds great! 🔥

Hi @dfreilich 👋🏻 ! Thank you very much for your interest in Supervision. - Given that we don't yet have a concrete idea for end-to-end testing of annotators, I wouldn't...

Hi @NickHerrig 👋🏻 Do we already have some assets that we would like to distribute this way?

Hi @onuralpszr 👋🏻, I would prefer those badges to be justified to left, not to center.

Hi @jcruz-ferreyra 👋🏻 Thanks a lot of opening the new PR.

Hi @AntonioConsiglio 👋🏻 I am not sure if my instructions are unclear, so I decided to prepare a [Colab](https://colab.research.google.com/drive/1rpcK_i8RdJLk88WHF8OLW5sZC58PlvFx?usp=sharing) for you illustrating what we need. As far as I know,...

> Why do you want to split the process? Most importantly, because you changed API. The `update_with_tensors` method is a public API and must stay unchanged.

> The question is, make it sense to have update_with_tensors API public? `update_with_tensors` is public as it is use internally by Roboflow team. > what do you think to leave...

Hi @AntonioConsiglio 👋🏻 As usual, thanks for all the time and effort you put into making this PR. This PR significantly increases the complexity of the ByteTrack code. We added...

Hi @AntonioConsiglio 👋🏻 I'm closing this issue as the solution is now implemented via https://github.com/roboflow/supervision/pull/1035. Thanks a lot for all the effort @AntonioConsiglio 🙏🏻