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.

Sign up for GitHub

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

Jump to bottom

Bugfix/172 prediction with no inputs bug #173

Merged
merged 7 commits into from
May 2, 2024
Merged

Bugfix/172 prediction with no inputs bug #173

merged 7 commits into from
May 2, 2024

Conversation

sdahdah
Copy link
Member

@sdahdah sdahdah commented May 2, 2024 •
edited
Loading

Resolves #172, #171, #170, #169, #168

Checklist

  • Write unit tests
  • Add new estimators to existing scikit-learn compatibility tests
  • Write examples in docstrings
  • Update Sphinx documentation
  • Bump version number and date in setup.py, CITATION.cff, and
    README.rst

@sdahdah sdahdah self-assigned this May 2, 2024
@sdahdah sdahdah linked an issue May 2, 2024 that may be closed by this pull request
Prediction with no inputs bug #172
Closed
@sdahdah sdahdah added the bug Something isn't working label May 2, 2024
@sdahdah sdahdah merged commit fdf5099 into main May 2, 2024
7 checks passed
@sdahdah sdahdah deleted the bugfix/172-prediction-with-no-inputs-bug branch May 2, 2024 20:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@sdahdah sdahdah

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Prediction with no inputs bug
1 participant
@sdahdah