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

Python packages.fluidasserts #80828

Merged
merged 5 commits into from Feb 23, 2020
Merged

Python packages.fluidasserts #80828

merged 5 commits into from Feb 23, 2020

Conversation

kamadorueda
Copy link
Member

@kamadorueda kamadorueda commented Feb 22, 2020

Motivation for this change
Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.

- Keberos is a dependency that you really want included in the pkg,
  this is also needed to run the test suite by default
- Release entirely the version pinning, the active development of
  the package makes it be compatible with the latest dependency
  versions
- Added more tests, and missing packages
Copy link
Contributor

@jonringer jonringer left a comment

Choose a reason for hiding this comment

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

diff LGTM
commits LGTM

failure is an upstream issue

[12 built (1 failed), 27 copied (158.2 MiB), 3.3 MiB DL]
error: build of '/nix/store/sfglznhrmqaryvp7i50sxwdg5marn9sa-env.drv' failed
https://github.com/NixOS/nixpkgs/pull/80828
1 package failed to build:
python38Packages.pywinrm

8 package built:
fluidasserts python27Packages.pywinrm python37Packages.graphql-core python37Packages.graphql-server-core python37Packages.promise python37Packages.pywinrm python38Packages.graphql-core python38Packages.promise

failure:

    /nix/store/9nh4qk8zjgzqlnzj6hp5n1nkyzicss4x-python3.8-unittest2-1.1.0/lib/python3.8/site-packages/unittest2/compatibility.py:143: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated since Python 3.3, and in 3.9 it will stop working
      class ChainMap(collections.MutableMapping):

@kamadorueda
Copy link
Member Author

@jonringer in the last force push I disabled pywinrm for py38 so now the nix-review passes

Copy link
Contributor

@jonringer jonringer left a comment

Choose a reason for hiding this comment

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

LGTM

[1 built, 0.0 MiB DL]
https://github.com/NixOS/nixpkgs/pull/80828
8 package built:
fluidasserts python27Packages.pywinrm python37Packages.graphql-core python37Packages.graphql-server-core python37Packages.promise python37Packages.pywinrm python38Packages.graphql-core python38Packages.promise

@jonringer
Copy link
Contributor

@GrahamcOfBorg build fluidasserts python27Packages.pywinrm python37Packages.graphql-core python37Packages.graphql-server-core python37Packages.promise python37Packages.pywinrm python38Packages.graphql-core python38Packages.promise

@jonringer jonringer merged commit 3c72558 into NixOS:master Feb 23, 2020
@jonringer
Copy link
Contributor

@kamadorueda do you care about fluidasserts being available on the release channel?

It's still broken on release-20.03

@kamadorueda
Copy link
Member Author

@jonringer where do you see that info? last time I reviewed some hydra logs and adjusted the package to pass

@kamadorueda
Copy link
Member Author

@jonringer alright! although it seems to be the previous hard-pinned-dependencies problem

https://hydra.nixos.org/build/113405614/nixlog/1

i'll keep an eye on it

@jonringer
Copy link
Contributor

it does, but if your use case only includes unstable, then I'm not sure how much benefit you will get

@strager
Copy link
Contributor

strager commented May 16, 2020

@kamadorueda In this PR, you introduced graphql-core and graphql-server-core. These packages depend on the rx package. I am upgrading the rx package as a part of my PR (#71166). graphql-core has a release (3.1.0) which is compatible with rx version 3, but graphql-server-core does not yet have a release which is compatible. With my unmerged PR, the graphql-core (and thus the graphql-server-core) builds are broken.

I don't see any use of graphql-server-core or graphql-core in this PR. fluidasserts doesn't seem to depend on these packages.

I see a few options:

  1. upgrade rx from 1.6 to 3.0; upgrade graphql-core to 3.1.0; upgrade graphql-server-core to an unreleased version
  2. upgrade rx from 1.6 to 3.0; upgrade graphql-core to 3.1.0; delete graphql-server-core
  3. upgrade rx from 1.6 to 3.0; delete graphql-core; delete graphql-server-core
  4. add rx 3.0 along-side rx 1.6; have graphql-core use rx 1.6 and have twitch-python use rx 3.0

Let me know what you recommend. I am leaning toward option 2.

@jonringer
Copy link
Contributor

fluidasserts has been broken for over a month, I would say just do upgrade of rx to 3.0, and mark graphql-server-core as broken.

strager added a commit to strager/nixpkgs that referenced this pull request May 20, 2020
I want to upgrade rx (a Python library) from version 1.6 to version 3.0.
graphql-core version 2.3.1 requires rx version <2. This prevents me from
upgrading rx.

Upgrade graphql-core to the latest release, removing its dependency on
rx entirely.

Unfortunately, graphql-server-core (which depends on graphql-core) does
not have a release which works with this latest version of graphql-core.
Because graphql-server-core isn't used anywhere yet [1], disable the
package to unblock me upgrading rx.

[1] NixOS#80828 (comment)
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.

None yet

3 participants