Fix Issue #34: fractional_beat=0.0 with sparse pulse data #35

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

Merged

jon-myers merged 3 commits into main from investigate-fractional-beat-issue

Sep 10, 2025

Merged

Fix Issue #34: fractional_beat=0.0 with sparse pulse data #35

refactor: remove unnecessary sparse pulse fallback code

Annotations

4 warnings

A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):

Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers

The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fix Issue #34: fractional_beat=0.0 with sparse pulse data #35

Uh oh!

Uh oh!

Fix Issue #34: fractional_beat=0.0 with sparse pulse data #35

Uh oh!

Annotations

The logs for this run have expired and are no longer available.

Re-running jobs...