| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
This reverts commit f56440b.
|
@frankyn, I've pushed a real PR. Only system tests are failing with Anonymous caller does not have storage.objects.create access to <bucket-name>/<file-name> (the same Jonathan Lui got) Everything except this seems to be fine |
Sorry, something went wrong.
|
Thanks @IlyaFaer, I'll review. I'll update group in V4 Sig Hangouts Chat. |
Sorry, something went wrong.
There was a problem hiding this comment.
Small nits
Sorry, something went wrong.
|
@frankyn, @crwilcox, I've moved conformance tests into this PR. I assume you'd like me to add the conformance tests data as well!? Locally I've added policy conformance tests data into url_signer_v4_test_data.json, and used it while running the tests. Is it a correct place? |
Sorry, something went wrong.
|
@IlyaFaer yes, keep it in the same file to reduce complexity of conformance tests. |
Sorry, something went wrong.
|
@IlyaFaer could you update conformance tests to follow the exact format of source conformance tests: https://github.com/googleapis/conformance-tests/blob/master/storage/v1/v4_signatures.json It can be a subsequent PR to reduce complexity for this one. I'm trying to prevent snowflakes. |
Sorry, something went wrong.
There was a problem hiding this comment.
Few more nits.
Sorry, something went wrong.
@frankyn, you mean, use these signingV4Tests and postPolicyV4Tests fields on a first level of the json? That's not a problem, though I assume some code should be changed in test__signing.py as well, so yes, that probably should be done in another PR. @crwilcox, @frankyn, I think, I saw random conformance tests are flakely failing in Python 2.7 and 3.5 while it all was in progress. I'll take a closer look. |
Sorry, something went wrong.
|
Hi @IlyaFaer,
Yes, that's correct, could you please open a tracking issue for it as well? Thank you.
Conformance tests should not have flakes, please keep us posted. |
Sorry, something went wrong.
|
It seems there are a few kokoro failures. @IlyaFaer are these expected or is this work to do yet? |
Sorry, something went wrong.
|
@frankyn, @crwilcox, I've found out what was causing flaky: dict.items() returns result in different order sometimes: So I've added sorted() for fields - didn't detect any new failing on 2.7/3.5 so far. I've fixed system tests as well (they were failing with Anonymous requests are not allowed for some time, but now they're okay, so I've fixed a couple of my bads). I hope nothing is forgotten. All checks are green now 🎉 |
Sorry, something went wrong.
|
Awesome. Yep @IlyaFaer ordered dicts weren't in 2.7 at all or even older versions of 3. |
Sorry, something went wrong.
* feat: add POST policies building method * add comments, ignoring x-ignore fields and required fields validation * fix docs style, add virtual hosted style URLs * add bucket_bound_hostname support * cosmetic changes * add unit tests * Revert "add unit tests" This reverts commit f56440b. * add few lines from the old implementation for consistency * add some system tests * move system tests into separate class * fix credentials scope URL mistake * fix unit tests * fix algorithm name * add an example * add access token support * add credentials as an argument * rename method * add conformance tests into client unit tests * align conformance tests with test data * add an ability to set expiration as integer * update conformance tests to avoid problems with json spaces and timestamp Z-symbol violation * update implementation to avoid Z symbol isoformat violation and json whitespaces encoding * fix error with bounded hostnames * fix problem with bounded hostnames in implementation * fix conformance tests * fix problems: ascii encoding of signature and fields order * change asserts order * fix conformance tests * fix encoding issues * cosmetic changes and adding conformance tests * fix russion "C" letter in comment * add conformance tests data * cosmetic changes * cosmetic changes * add fields sorting * fix system tests Co-authored-by: Frank Natividad <frankyn@users.noreply.github.com>
* feat: add POST policies building method * add comments, ignoring x-ignore fields and required fields validation * fix docs style, add virtual hosted style URLs * add bucket_bound_hostname support * cosmetic changes * add unit tests * Revert "add unit tests" This reverts commit f56440b. * add few lines from the old implementation for consistency * add some system tests * move system tests into separate class * fix credentials scope URL mistake * fix unit tests * fix algorithm name * add an example * add access token support * add credentials as an argument * rename method * add conformance tests into client unit tests * align conformance tests with test data * add an ability to set expiration as integer * update conformance tests to avoid problems with json spaces and timestamp Z-symbol violation * update implementation to avoid Z symbol isoformat violation and json whitespaces encoding * fix error with bounded hostnames * fix problem with bounded hostnames in implementation * fix conformance tests * fix problems: ascii encoding of signature and fields order * change asserts order * fix conformance tests * fix encoding issues * cosmetic changes and adding conformance tests * fix russion "C" letter in comment * add conformance tests data * cosmetic changes * cosmetic changes * add fields sorting * fix system tests Co-authored-by: Frank Natividad <frankyn@users.noreply.github.com>
| Back | FazBrowse Home | New Git URL |
Towards #8