Skip to content

Conversation

carols10cents
Copy link
Member

…-source-3.15.0, r=Turbo87"

This reverts commit 97ecbf3, reversing
changes made to 6cfc3bf.

@Turbo87 I did manual testing of logging in because you mentioned you weren't able to test it; when I was on face1f3 logging in didn't work for me.

I did a git bisect and it pointed to the ember-source upgrade #2001 which is... all of ember? I'm not really sure how to go about debugging this further, but I'm going to try and I'll open a new issue with more details as I figure them out.

Reverting the ember-source upgrade lets me log in again, so this should make master deployable.

I really really wish we could have a full-stack automated test for logging in with GitHub, but I don't see that happening anytime soon!!

…arn/ember-source-3.15.0, r=Turbo87"

This reverts commit 97ecbf3, reversing
changes made to 6cfc3bf.
@rust-highfive
Copy link

r? @smarnach

(rust_highfive has picked a reviewer for you, use r? to override)

@carols10cents
Copy link
Member Author

r? @Turbo87

@carols10cents
Copy link
Member Author

cursed log line #666 from the rust tests:

  process didn't exit successfully: `/home/travis/build/rust-lang/crates.io/target/debug/deps/all-5d37589f67418c19` (signal: 11, SIGSEGV: invalid memory reference)

so that's fun

@carols10cents
Copy link
Member Author

🙈

bors added a commit that referenced this pull request Dec 20, 2019
routes/github-authorize: Fix `queryParams` code

Accessing `queryParams` on the `transition` object was never officially public API in Ember.js, and has been deprecated in Ember.js v3.6 (see https://deprecations.emberjs.com/v3.x#toc_transition-state). Since it was only considered "intimate" API its removal was done in v3.9 instead of v4.0. Since we skipped both of these versions we unfortunately never saw the corresponding deprecation warning... 😞

But even if we did upgrade to v3.8 LTS in between, we probably still would have missed it, because the `github-authorize` route is only called in a popup window where the usual DevTools console is not attached, and we unfortunately don't have any test for the login flow (yet!).

Closes #2027, Resolves #2028

@carols10cents r?
@carols10cents
Copy link
Member Author

Closing in favor of #2029.

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.

4 participants