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

Hotfix capture with empty UUID #70

Closed

Conversation

evgeek
Copy link
Contributor

@evgeek evgeek commented Aug 25, 2024

Hotfix for #69

@@ -462,7 +462,7 @@ func (c *client) send(msgs []message) {

// Upload serialized batch message.
func (c *client) upload(b []byte) error {
url := c.Endpoint + "/batch/"
url := c.Endpoint + "/capture/"
Copy link
Contributor

Choose a reason for hiding this comment

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

wait, I don't understand; you're removing the /batch functionality? I don't think that's a good long-term fix for this; folks are using that piece, too. If we're looking to fix something quickly, we should just revert the change and then fix it more permanently instead of continuing to change more things.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, it is just a quick (not good) fix, i describe my thoughts here - #68 (comment).

Do you think you can configure /batch on the server side to work with an empty uuid, like /capture? If (I hope) this works out, previous PR will be ok. If not, we will need to think about how best to implement the functionality from the SDK side.

But for now you're right - rollback is better. I don't know all the SDK use cases and can't be sure it won't break something else.
Rollback PR - #71

@evgeek evgeek closed this Aug 26, 2024
@evgeek evgeek deleted the hotfix-capture-with-empty-uuid branch August 26, 2024 17:15
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 this pull request may close these issues.

2 participants