Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Potential problem with client actions resolving on server

See original GitHub issue

Hi @brillout

Today I noticed something strange, and I thought I’d notify you now - I might run some more tests to see if its really an issue on my side or with wildcard-api - but the behaviour is new and I’m pretty sure I haven’t changed anything with my code and wildcard-api.

I’m getting these errors now when my server is running “client” endpoints:

****************************************
************* Stack Trace **************
****************************************
    at getCallStack (C:\dev\_projects\vibescout-web-workspace\node_modules\reassert\assert.js:170:27)
    at Function.reassert (C:\dev\_projects\vibescout-web-workspace\node_modules\reassert\assert.js:25:21)
    at Function.module.exports [as usage] (C:\dev\_projects\vibescout-web-workspace\node_modules\reassert\usage.js:9:19)
    at assert_context (C:\dev\_projects\vibescout-web-workspace\node_modules\wildcard-api\server\WildcardApi.js:541:14)
    at Object.set (C:\dev\_projects\vibescout-web-workspace\node_modules\wildcard-api\server\WildcardApi.js:527:5)
    at Function.assign (<anonymous>)
    at runEndpoint (C:\dev\_projects\vibescout-web-workspace\node_modules\wildcard-api\server\WildcardApi.js:273:12)
    at Object.__directCall (C:\dev\_projects\vibescout-web-workspace\node_modules\wildcard-api\server\WildcardApi.js:99:45)


****************************************
************* Wrong Usage **************
****************************************
Cannot get context `this.endpointName`.
Context is missing while running the Wildcard client on Node.js.
Make sure to add the request context with `bind`: `endpoints.postSearchQuery.bind(requestContext)`.

The only difference between now and a couple days ago is that I updated my Node.js installation to version 12.1.0 - so I think that there may be an issue with that version.

I’m going to try and downgrade and see.