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][SDK] Python dataproxy sdk callback function call leads to coredump #10811

Closed
2 tasks done
yfsn666 opened this issue Aug 19, 2024 · 0 comments · Fixed by #10812
Closed
2 tasks done

[Bug][SDK] Python dataproxy sdk callback function call leads to coredump #10811

yfsn666 opened this issue Aug 19, 2024 · 0 comments · Fixed by #10812
Assignees
Labels
type/bug Something is wrong
Milestone

Comments

@yfsn666
Copy link
Contributor

yfsn666 commented Aug 19, 2024

What happened

When using python sdk, when a callback function is defined and triggered, it causes coredump to exit the process abnormally.

What you expected to happen

The defined callback function should be able to be triggered normally and not cause a coredump to exit the process.

How to reproduce

Define the callback function in the project, use it when calling the send function, and set inlong_group_id and inlong_stream_id to a set of non-existing ids to trigger the callback function.

Environment

No response

InLong version

master

InLong Component

InLong SDK

Are you willing to submit PR?

  • Yes, I am willing to submit a PR!

Code of Conduct

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Something is wrong
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants