-
-
Notifications
You must be signed in to change notification settings - Fork 15.5k
aws-sam-cli: 1.6.2 -> 1.14.0 #104782
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
aws-sam-cli: 1.6.2 -> 1.14.0 #104782
Conversation
Can you please target staging? |
d4b2e52
to
7f10ce0
Compare
7f10ce0
to
9fceba8
Compare
oh, sorry, I fixed the current build, and that caused some conflicts |
bb9b789
to
6faddb8
Compare
Rebased + conflict resolved 🤞 |
@freezeboy You might want to bump it once more: https://github.com/aws/aws-sam-cli/releases/tag/v1.14.0 |
in | ||
|
||
with py.pkgs; | ||
with python3.pkgs; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer moving this to where it is needed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is okay, mostly because it's not mixing toolchains. Since it's a "standard" python package, I think the context is apparent enough. However, if it was also doing some c++/rust builds, and something more complicated; then I would agree that scoping is vital.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I admit I simply replaced the with call as no more override was needed
This is a semi-automatic executed nixpkgs-review which is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch). Result of 1 package built:
The following issues got detected with the above build packages. aws-sam-cli: Please consider this feature to be alpha. A substituteInPlace with an unmatched pattern got detected:
Please check the offending substituteInPlace for typos or changes in source. |
This is a semi-automatic executed nixpkgs-review which is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch). Result of 1 package built:
The following issues got detected with the above build packages. aws-sam-cli: Please consider this feature to be alpha. A substituteInPlace with an unmatched pattern got detected:
Please check the offending substituteInPlace for typos or changes in source. |
6faddb8
to
cb0e509
Compare
@hirenashah Ok updated ... again Really sad this trivial change is pending since November 2020 ... |
This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch). Result of 1 package built:
The following issues got detected with the above build packages. aws-sam-cli: Please consider this feature to be alpha. A substituteInPlace with an unmatched pattern got detected:
Please check the offending substituteInPlace for typos or changes in source. |
If the stale substituteInPlace is removed this can be merged. The version bump could also have been a new PR. |
So the remaining task is simply to delete this one line?
|
I think so. |
cb0e509
to
96a0d30
Compare
Rebased, dangling substition removed, built locally, and force pushed |
Motivation for this change
Upstream update
Should wait after #103742
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)