Skip to content

Add null check for consumer in MessageListenerProxy #219

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.

Sign up for GitHub

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

Merged
k2la merged 2 commits into from
Jul 12, 2022
Merged

Add null check for consumer in MessageListenerProxy #219

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ca46fc2
Add null check for consumer in MessageListenerProxy
BewareMyPower Jun 14, 2022
4c2f468
Add comments for the workround
BewareMyPower Jul 8, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion src/Consumer.cc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,7 +63,9 @@ void MessageListenerProxy(Napi::Env env, Napi::Function jsCallback, MessageListe
Consumer *consumer = data->consumer;
delete data;

jsCallback.Call({msg, consumer->Value()});
if (consumer) {

@gaoran10 gaoran10 Jun 21, 2022 •
edited
Loading

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need to print some warning messages when the consumer is a null value?

@BewareMyPower BewareMyPower Jun 21, 2022

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No. The initial value is null. And I found the NodeJS wrapper never logs any message. Even if you added a log here, there is still helpless to find in which scenario consumer is null here.

@gaoran10 gaoran10 Jun 23, 2022

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure if users lose to handle some messages when the consumer is null.

@BewareMyPower BewareMyPower Jun 23, 2022

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the controversial point is whether should we skip the null consumer.

  • Yes: might lose messages (not sure)
  • No: fast fail

Adding logs doesn't solve anything. There is no logger in NodeJS client, printing logs to console is meaningless and helpless as I said.

@BewareMyPower BewareMyPower Jun 23, 2022

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need more info to reproduce the segmentation fault. But for now, a safe solution is to avoid accessing a null consumer.

jsCallback.Call({msg, consumer->Value()});
}
}

void MessageListener(pulsar_consumer_t *rawConsumer, pulsar_message_t *rawMessage, void *ctx) {
Expand Down