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

[improve][fn] Add missing "exception" argument to some log.error #22140

Merged
merged 1 commit into from
Feb 29, 2024

Conversation

jiangpengcheng
Copy link
Contributor

@jiangpengcheng jiangpengcheng commented Feb 28, 2024

Fixes #xyz

Main Issue: #xyz

PIP: #xyz

Motivation

While debugging an error for function trigger, the logs only print: Function in trigger function is not ready @ /public/default/test, which is useless without the error stack trace, it's better to add it, I also found other log.error missed the "exception" argument while most of log.error has it.

Modifications

Add exception as the last argument to calling of log.error which missed it

Verifying this change

  • Make sure that the change passes the CI checks.

  • This change is a trivial rework / code cleanup without any test coverage.

Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

  • Dependencies (add or upgrade a dependency)
  • The public API
  • The schema
  • The default values of configurations
  • The threading model
  • The binary protocol
  • The REST endpoints
  • The admin CLI options
  • The metrics
  • Anything that affects deployment

Documentation

  • doc
  • doc-required
  • doc-not-needed
  • doc-complete

Matching PR in forked repository

PR in forked repository:

@github-actions github-actions bot added the doc-not-needed Your PR changes do not impact docs label Feb 28, 2024
@jiangpengcheng jiangpengcheng changed the title [improve][fn] Print stack trace when log errors [improve][fn] Add missing "exception" argument to some log.error Feb 28, 2024
@dao-jun dao-jun merged commit c7cedc6 into apache:master Feb 29, 2024
75 of 79 checks passed
@heesung-sn
Copy link
Contributor

@jiangpengcheng We have a conflict in branch-3.0. Can you hep to raise a cherry-pick PR to branch-3.0?

@gaoran10
Copy link
Contributor

gaoran10 commented Mar 4, 2024

@jiangpengcheng Could you help to also raise a cherry-pick PR to branch-3.1?

jiangpengcheng added a commit to jiangpengcheng/pulsar that referenced this pull request Mar 7, 2024
mukesh-ctds pushed a commit to datastax/pulsar that referenced this pull request Apr 15, 2024
mukesh-ctds pushed a commit to datastax/pulsar that referenced this pull request Apr 17, 2024
mukesh-ctds pushed a commit to datastax/pulsar that referenced this pull request Apr 17, 2024
mukesh-ctds pushed a commit to datastax/pulsar that referenced this pull request Apr 19, 2024
srinath-ctds pushed a commit to datastax/pulsar that referenced this pull request Apr 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants