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

extensions/ext: Make get_calibrated_timestamps() return single value for max_deviation #738

Merged
merged 1 commit into from
May 6, 2023

Conversation

kanashimia
Copy link
Contributor

Per spec max_deviation is a single value, and not a vector.

Closes #737

@MarijnS95 MarijnS95 changed the title extensions/ext: get_calibrated_timestamps return (Vec<u64>, u64) extensions/ext: Make get_calibrated_timestamps return single value for maxDeviation Apr 9, 2023
@MarijnS95 MarijnS95 changed the title extensions/ext: Make get_calibrated_timestamps return single value for maxDeviation extensions/ext: Make get_calibrated_timestamps return single value for max_deviation Apr 10, 2023
@MarijnS95
Copy link
Collaborator

Can you make the changelog entry similar to the changed title? And do you want this to be backported to 37.3, in which case we need to deprecate the current function and add one with the updated function signature?

@MarijnS95 MarijnS95 changed the title extensions/ext: Make get_calibrated_timestamps return single value for max_deviation extensions/ext: Make get_calibrated_timestamps() return single value for max_deviation May 6, 2023
…e for `max_deviation`

Per spec `max_deviation` is a single value, not an array.
@MarijnS95
Copy link
Collaborator

I'm fine not backporting this to 0.37 for now.

@Ralith Ralith merged commit ad70ad7 into ash-rs:master May 6, 2023
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.

get_calibrated_timestamps should only return one value for maxDeviation
3 participants