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

Use "--use-feature=2020-resolver" to fix #390 #508

Merged
merged 1 commit into from
Sep 12, 2020

Conversation

HiromuHota
Copy link
Contributor

Description of the problems or issues

Is your pull request related to a problem? Please describe.

See #390.

Does your pull request fix any issue.

Fix #390.

Description of the proposed changes

Use --use-feature=2020-resolver option along with pip install.
This option is currently "robust beta" and will become the default resolver as of 20.3, slated to be released on October, 2020 (see here).
We could wait for 20.3, but I'd like to start testing this.
If something does not work for us, we could report an issue to the pip community before it is released.

Test plan

Manually check if dependencies are correctly resolved.

Checklist

  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • I have updated the CHANGELOG.rst accordingly.

@codecov-commenter
Copy link

codecov-commenter commented Sep 12, 2020

Codecov Report

Merging #508 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #508   +/-   ##
=======================================
  Coverage   85.84%   85.84%           
=======================================
  Files          88       88           
  Lines        4585     4585           
  Branches      855      855           
=======================================
  Hits         3936     3936           
  Misses        464      464           
  Partials      185      185           
Flag Coverage Δ
#unittests 85.84% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
setup.py 0.00% <ø> (ø)

@HiromuHota
Copy link
Contributor Author

The GitHub Actions job on the master branch still complains about incompatibility among dependencies.

mlflow 1.11.0 requires sqlalchemy<=1.3.13, but you'll have sqlalchemy 1.3.19 which is incompatible.

https://github.com/HazyResearch/fonduer/runs/1103656295?check_suite_focus=true

With this PR, the dependencies are nicely resolved.
Actually, mlflow-1.7.0 is installed, which is compatible with sqlalchemy 1.3.19.

@HiromuHota HiromuHota marked this pull request as ready for review September 12, 2020 00:53
Copy link
Contributor

@lukehsiao lukehsiao left a comment

Choose a reason for hiding this comment

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

LGTM.

@lukehsiao lukehsiao added this to the v0.8.4 milestone Sep 12, 2020
@lukehsiao lukehsiao merged commit 9176baf into HazyResearch:master Sep 12, 2020
@HiromuHota HiromuHota deleted the fix/390 branch September 14, 2020 16:39
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.

scikit-learn 0.22.2.post1 and tensorboard 2.2.0 that are incompatible with snorkel 0.9.5 are installed
3 participants