Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] NOTICE-BINARY has 2 copies of the Jackson notice #2306

Closed
2 of 3 tasks
pjfanning opened this issue Dec 26, 2024 · 0 comments · Fixed by #2311
Closed
2 of 3 tasks

[Bug] NOTICE-BINARY has 2 copies of the Jackson notice #2306

pjfanning opened this issue Dec 26, 2024 · 0 comments · Fixed by #2311

Comments

@pjfanning
Copy link

Code of Conduct

Search before asking

  • I have searched in the issues and found no similar issues.

Describe the bug

The section starting with:

# Jackson JSON processor

appears twice.

Affects Version(s)

master & 0.9.2-rc1

Uniffle Server Log Output

No response

Uniffle Engine Log Output

No response

Uniffle Server Configurations

No response

Uniffle Engine Configurations

No response

Additional context

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!
jerqi added a commit to jerqi/incubator-uniffle that referenced this issue Dec 27, 2024
jerqi added a commit to jerqi/incubator-uniffle that referenced this issue Dec 27, 2024
jerqi added a commit that referenced this issue Dec 30, 2024
### What changes were proposed in this pull request?

Remove repeated notice information

### Why are the changes needed?

Fix: #2306


### Does this PR introduce _any_ user-facing change?
No.

### How was this patch tested?
No need.
jerqi added a commit that referenced this issue Dec 30, 2024
### What changes were proposed in this pull request?

Remove repeated notice information

### Why are the changes needed?

Fix: #2306


### Does this PR introduce _any_ user-facing change?
No.

### How was this patch tested?
No need.
jerqi added a commit that referenced this issue Jan 1, 2025
### What changes were proposed in this pull request?

Remove repeated notice information

### Why are the changes needed?

Fix: #2306


### Does this PR introduce _any_ user-facing change?
No.

### How was this patch tested?
No need.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant