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

Import context from golang.org/x/net #110

Closed
tbpg opened this issue Mar 9, 2018 · 11 comments
Closed

Import context from golang.org/x/net #110

tbpg opened this issue Mar 9, 2018 · 11 comments

Comments

@tbpg
Copy link
Contributor

tbpg commented Mar 9, 2018

[REQUIRED] Step 2: Describe your environment

  • Operating System version: N/A
  • Firebase SDK version: N/A
  • Library version: Master
  • Firebase Product: all

[REQUIRED] Step 3: Describe the problem

Steps to reproduce:

What happened? How can we make the problem occur?
This could be a description, log/console output, etc.

go version 1.6
go get -u firebase.google.com/go

Log from a failed Travis build:

get "firebase.google.com/go": found meta tag main.metaImport{Prefix:"firebase.google.com/go", VCS:"git", RepoRoot:"https://github.com/firebase/firebase-admin-go"} at https://firebase.google.com/go?go-get=1
firebase.google.com/go (download)
package context: unrecognized import path "context" (import path does not begin with hostname)

https://travis-ci.org/GoogleCloudPlatform/golang-samples/jobs/351066691#L1064

Relevant Code:

import "context" should be import "golang.org/x/net/context".

This is mentioned in the v.2.5.0 changelog, but looks like there are some references remaining: https://github.com/firebase/firebase-admin-go/search?utf8=%E2%9C%93&q=context&type=.

This is blocking GoogleCloudPlatform/golang-samples#418.

I'll work on a PR.

@google-oss-bot
Copy link
Collaborator

Hmmm this issue does not seem to follow the issue template. Make sure you provide all the required information.

@google-oss-bot
Copy link
Collaborator

Hey there! I couldn't figure out what this issue is about, so I've labeled it for a human to triage. Hang tight.

@mbleigh
Copy link

mbleigh commented Mar 9, 2018

I believe Go 1.6 is not supported by the Firebase Admin SDK. @hiranya911 to confirm.

@hiranya911
Copy link
Contributor

Correct. We never really supported 1.6 properly, and starting from last release we officially dropped 1.6 support: #101

Our documentation might be a little behind with regard to this change. I'll iron those our in the next few days.

@tbpg
Copy link
Contributor Author

tbpg commented Mar 12, 2018

Any way to revisit that decision? I have a PR ready which brings back compatibility.

Go 1.6 is still available in AppEngine, which we need to support in https://github.com/GoogleCloudPlatform/golang-samples/. In particular, I'm working on extending https://cloud.google.com/appengine/docs/standard/go/building-app/ to support authentication and it would be great to be able to use Firebase.

@hiranya911
Copy link
Contributor

Why not use golang1.8 in App Engine? Given that Go no longer supports anything older than 1.9 (see https://golang.org/doc/devel/release.html), it seems unnecessary to support something as old as 1.6.

@tbpg
Copy link
Contributor Author

tbpg commented Mar 12, 2018

AppEngine Standard still has 1.6 available.

@hiranya911
Copy link
Contributor

That is true, but developers can choose 1.8 when using Firebase. Is there any reason that takes that choice out of the picture?

@tbpg
Copy link
Contributor Author

tbpg commented Mar 12, 2018

Some users are stuck on older versions of Go without an easy ability to upgrade. So, for https://github.com/GoogleCloudPlatform/golang-samples/, we support all possible versions of Go.

@hiranya911
Copy link
Contributor

In #98 we found that the Admin SDK never really supported Go 1.6. What's interesting is that we didn't hear about this from any users. We discovered it ourselves while setting up CI for Go 1.6. So I think it's fair to assume that all Admin SDK users are already on Go 1.7 or higher. Given that, and all the internal discussions we've had on this topic, I'm reluctant to go back.

But if you're willing to provide a PR, with the necessary code changes and a working Travis config for 1.6, then we can revisit this.

This was referenced Mar 15, 2018
@tbpg
Copy link
Contributor Author

tbpg commented Mar 15, 2018

Thank you, Hiranya! I appreciate it. I opened #119 and #120.

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

No branches or pull requests

4 participants