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

OpenID depedency migration failures with Authentication with newest *node* #1021

Closed
Martii opened this issue Jun 21, 2016 · 2 comments
Closed
Labels
CODE Some other Code related issue and it should clearly describe what it is affecting in a comment. migration Use this to indicate that it may apply to an existing or announced migration.

Comments

@Martii
Copy link
Member

Martii commented Jun 21, 2016

So post production maintenance yielded unexpected and probable failures in passport-yahoo and passport-aol when flipping to node@6.x

Possible solutions:

EDIT: We have ~3 months left on the node@4.x line before node@6.x goes into LTS (then another 6 months until maintenance) e.g. we should deal with this very soon. passport-steam worked with my account albeit their server threw an error the first time but with a retry it was fine so it was probably a hiccup... and this dep is by a different author/maintainer.

schedule

@Martii Martii added sooner Sooner would be appreciated. migration Use this to indicate that it may apply to an existing or announced migration. labels Jun 21, 2016
Martii pushed a commit to OpenUserJS/passport-openid that referenced this issue Oct 31, 2016
@Martii Martii self-assigned this Oct 31, 2016
Martii pushed a commit to OpenUserJS/passport-openid that referenced this issue Oct 31, 2016
* Should reduce the overall size of depth 1 dependencies and potential npm collisions

**NOTE**
Cherry picked as that repo is severely damaged.

Applies to OpenUserJS/OpenUserJS.org#1021
Martii pushed a commit to OpenUserJS/passport-aol that referenced this issue Oct 31, 2016
* Automatic editor white-space cleanup and verified

Applies to OpenUserJS/OpenUserJS.org#1021
Martii pushed a commit to OpenUserJS/passport-yahoo that referenced this issue Oct 31, 2016
* Automatic editor white-space cleanup and verified

Applies to OpenUserJS/OpenUserJS.org#1021
Martii pushed a commit to Martii/OpenUserJS.org that referenced this issue Oct 31, 2016
* AOL tested and passes... awaiting Yahoo verification

Applies to OpenUserJS#1021 and presumably OpenUserJS#1031
Martii pushed a commit to Martii/OpenUserJS.org that referenced this issue Nov 1, 2016
* Please read their CHANGELOGs
* Fix dead links for *octicons* ... author name change detected for redirect. See below notes.
* Bump project requirements to latest LTS
* *bundler* gem update
* Add README.md refs for OpenUserJS#1021 and OpenUserJS#1031
* Delete op retested

**NOTES**
*octicons* has gone svg and no longer a font type in the next major rev... Awaiting further detailed analysis before dep update. Related to OpenUserJS#186
@Martii
Copy link
Member Author

Martii commented Nov 1, 2016

Closing from a49abdd

@Martii Martii closed this as completed Nov 1, 2016
@Martii Martii removed their assignment Nov 1, 2016
@Martii Martii added CODE Some other Code related issue and it should clearly describe what it is affecting in a comment. and removed sooner Sooner would be appreciated. labels Nov 1, 2016
Martii pushed a commit to Martii/OpenUserJS.org that referenced this issue Nov 2, 2016
* Way back in https://github.com/liamcurry/passport-steam/blob/765869b566319bf7e5c44a4d3e1d4b6439731383/README.md the callback signature was modified to include a profile. The "hijacking" didn't account for this.
* Prevents a server trip

Applies to OpenUserJS#1021 (comment)
@Martii
Copy link
Member Author

Martii commented Nov 3, 2016

Martii pushed a commit to OpenUserJS/passport-steam that referenced this issue Aug 27, 2017
*NOTE(S)*
* Testing this fix for permanence in contrast to alternate fix of `"passport-openid": "^0.4.0",` in liamcurry@4d19567

Applies to OpenUserJS/OpenUserJS.org#1021
@OpenUserJS OpenUserJS locked as resolved and limited conversation to collaborators Apr 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
CODE Some other Code related issue and it should clearly describe what it is affecting in a comment. migration Use this to indicate that it may apply to an existing or announced migration.
Development

No branches or pull requests

1 participant