Skip to content

Navigation Menu

Explore
For
- Enterprise
- Teams
- Startups
- Education
By Solution
Resources
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

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

apache / pulsar Public

Notifications You must be signed in to change notification settings
Fork 3.5k
Star 13.9k

Code
Issues 1k
Pull requests 340
Discussions
Actions
Projects 2
Wiki
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Projects
Wiki
Security
Insights

CI - Integration - Backwards Compatibility

[fix][broker][branch-2.10] Remove the unnecessary HTTP response header: Content-Encoding when calling getSchema #21118

Sign in to view logs

Sign in to view logs

[fix][broker][branch-2.10] Remove the unnecessary HTTP response header: Content-Encoding when calling getSchema

[fix][broker][branch-2.10] Remove the unnecessary HTTP response header: Content-Encoding when calling getSchema #21118

Summary
Jobs
- backwards-compatibility
Run details
- Usage
- Workflow file

Usage Workflow file

backwards-compatibility

backwards-compatibility

succeeded Mar 20, 2024 in 37m 44s

Re-running jobs...

You can’t perform that action at this time.