Labels
Labels
34 labels
- Referencing changes to the API spec
- Reporting an unexpected or problematic behavior of the codebase
- Issues that are specific to C behavior or domain within the library independent of library logic
- Issues that are specific to Python or versions of Python independent of library logic
- Issues tied specifically to admin logic or code paths
- Issues tied specifically to consumer logic or code paths
- For issues tied to the librdkfka elements
- Issues tied specifically to producer logic or code paths
- Any schema registry related isues rather than kafka isolated ones
- Avro, JSON, Protobof, Schema-registry
- Requesting a documentation change
- Requesting a feature change
- Helpful tag for inviting new users to contribute
- Any issue related to library installation. Please consider adding an operating system label as well
- It's unclear what the issue is at this time but there is enough interest to look into it
- Any tech debt or routine action tasks that should be tracked with an issue
- For issues specific to Linux environments. Please add more specific OS details in the issue
- For issues specific to OS Mac environments. Please add more specific OS details in the issue
- For issues specific to Windows environments. Please add more specific OS details in the issue
- Maintainer triage tag for indicating high impact or criticality issues
- Maintainer triage tag for indicating low impact or criticality issues
- A question about how to use or about expected behavior of the library
- A clarifying tag for bug that are a recurrence of a former issue
- Use the Security policy to direct how to share vulnerability or sensitive information
- Maintainer triage tag for indicating change required is very large and requires long term planning
- Maintainer triage tag for indicating change required is particularly large or complex
- Maintainer triage tag for indicating change required is particularly small
- Used when an issue has a blocking dependency or awaiting some other external change
- A repeat issue already reported. Use on issues closed for this reason.