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

Error: Environment variable SERVICE_ID is not set #286

Closed
1 task done
DaleLJefferson opened this issue Dec 1, 2017 · 4 comments
Closed
1 task done

Error: Environment variable SERVICE_ID is not set #286

DaleLJefferson opened this issue Dec 1, 2017 · 4 comments
Assignees

Comments

@DaleLJefferson
Copy link

This issue pertains to:

  • graphql-playground-middleware-lambda

What OS and OS version are you experiencing the issue(s) on?

Mac OS, Chrome 63, AWS Lambda Node 6.10

What version of graphql-playground(-electron/-middleware) are you experience the issue(s) on?

1.3.0

What is the expected behavior?

Successfully load the playground

What is the actual behavior?

I see an error message

Error: Environment variable SERVICE_ID is not set
    at s (resolveRefStrings.ts:69)
    at resolveRefStrings.ts:3
    at Array.map (<anonymous>)
    at r (resolveRefStrings.ts:3)
    at resolveRefStrings.ts:22
    at Array.forEach (<anonymous>)
    at i (resolveRefStrings.ts:19)
    at resolveRefStrings.ts:24
    at Array.forEach (<anonymous>)
    at i (resolveRefStrings.ts:19)
    at resolveRefStrings.ts:24
    at Array.forEach (<anonymous>)
    at i (resolveRefStrings.ts:19)
    at resolveRefStrings.ts:24
    at Array.forEach (<anonymous>)
    at i (resolveRefStrings.ts:19)
    at resolveRefStrings.ts:24
    at Array.forEach (<anonymous>)
    at i (resolveRefStrings.ts:19)
    at resolveRefStrings.ts:24
    at Array.forEach (<anonymous>)
    at Object.i [as resolveEnvsInValues] (resolveRefStrings.ts:19)
    at t.parseGraphQLConfig (MiddlewareApp.tsx:202)
    at new t (MiddlewareApp.tsx:86)
    at constructClassInstance (react-dom.production.min.js:140)
    at beginWork (react-dom.production.min.js:150)
    at o (react-dom.production.min.js:182)
    at u (react-dom.production.min.js:183)
    at l (react-dom.production.min.js:184)
    at h (react-dom.production.min.js:188)
    at f (react-dom.production.min.js:187)
    at Object.updateContainer (react-dom.production.min.js:248)
    at react-dom.production.min.js:254
    at Object.unbatchedUpdates (react-dom.production.min.js:190)
    at dt (react-dom.production.min.js:254)
    at Object.render (react-dom.production.min.js:255)
    at Object.init (middlewareIndex.tsx:18)
    at playground:48

What steps may we take to reproduce the behavior?

Upgrade to graphql-playground-middleware-lambda 1.3.0

import lambdaPlayground from 'graphql-playground-middleware-lambda'

export const handler = lambdaPlayground({endpoint: 'graphql'})
@schickling
Copy link
Collaborator

Thanks for reporting this @dalejefferson. We'll release a fix shortly.

@timsuchanek
Copy link
Member

Fix has been released in 1.3.1 👍

@DaleLJefferson
Copy link
Author

DaleLJefferson commented Dec 1, 2017

@timsuchanek @schickling Thanks for taking a look at this, I've upgraded to 1.3.1 and now it can't find my schema.

POST http://localhost:3000/undefined 404 (Not Found)

Queries work fine it's just the schema lookup that is broken.

screen shot 2017-12-01 at 13 55 17

@DaleLJefferson
Copy link
Author

I've created a new issue for this follow up #287

DeltaEvo pushed a commit to Popcorn-moe/graphql-playground that referenced this issue Dec 16, 2017
cgxxv pushed a commit to cgxxv/graphql-playground that referenced this issue Mar 25, 2022
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

3 participants