You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We often receive incomplete bug reports, a lot of back and forth is needed just to get to being able to reproduce the issues, and often times the problems come from local configuration that we don't have access to.
Having a shared testing environment that both users and maintainers have access to would be extremely useful, and would allow us to define a workflow where bug reports must be supported by a reproduction in CI that all parties can access, including:
zookeeper/kafka stack started automatically
matrix of kafka versions
logs published as artifacts of the CI run
Something to explore is whether users can leverage this mechanism in their own Github account via a fork of the kafka-go repository.
The text was updated successfully, but these errors were encountered:
We often receive incomplete bug reports, a lot of back and forth is needed just to get to being able to reproduce the issues, and often times the problems come from local configuration that we don't have access to.
Having a shared testing environment that both users and maintainers have access to would be extremely useful, and would allow us to define a workflow where bug reports must be supported by a reproduction in CI that all parties can access, including:
Something to explore is whether users can leverage this mechanism in their own Github account via a fork of the kafka-go repository.
The text was updated successfully, but these errors were encountered: