-
Notifications
You must be signed in to change notification settings - Fork 535
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][SDK] Go SDK pressure test and optimization #10465
Milestone
Comments
17 tasks
您好,想请问一下直接在腾讯文档上填写姓名+GitHub就算认领issuse成功了么?这个issue是只需要对inlong-sdk/dataproxy-sdk-golang这个sdk进行压力测试和优化是么?具体优化哪些部分? |
Successfully claimed this issue |
This issue is stale because it has been open for 60 days with no activity. |
github-actions
bot
added
the
stage/stale
Issues or PRs that had no activity for a long time
label
Sep 28, 2024
github-actions
bot
removed
the
stage/stale
Issues or PRs that had no activity for a long time
label
Oct 11, 2024
This issue is stale because it has been open for 60 days with no activity. |
github-actions
bot
added
the
stage/stale
Issues or PRs that had no activity for a long time
label
Dec 12, 2024
github-actions
bot
removed
the
stage/stale
Issues or PRs that had no activity for a long time
label
Jan 9, 2025
Thanks to all the contributors, the Tencent Rhino-bird 2024 is finished, and this issue will be closed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Localtion:
inlong-sdk/dataproxy-sdk-golang
Requirements:
This issue is a dedicated issue for the 2024 Tencent Rhino-bird Open Source Talent Training event and is only available for college students to claim
【Claim the issue】Sign up for the corresponding issue in columns M~R of the Research and Study Base "issue Camp" to be considered as successfully claimed.
【Complete the issue】For students who have claimed the issue, please also reply "Successfully claimed this issue" in the comment section of this issue; if there is no progress submitted within 7 days, including but not limited to comments, commits, or Pull Requests, it will be considered as voluntarily giving up the issue and the committee will release the issue to the next person in line.
InLong Component
InLong SDK
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: