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.

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:13 (8 by maintainers)

github_iconTop GitHub Comments

brilloutcommented, May 7, 2019

I know what’s going on but I have to run some errands. I’ll fix this later today.

brilloutcommented, May 9, 2019

Ah and I’ve started to make changes to the readme.

Read more comments on GitHub >

github_iconTop Results From Across the Web

5 common server issues and their effects on operations
Servers with power issues can cause end-user problems such as decreased productivity and increase data center work as staff troubleshoot ...
Read more >
10 Common Customer Service Problems and How to Resolve ...
Reasons: Here are some reasons why a customer call may get transferred: If the customer agent does not have a ready solution to...
Read more >
Managing Client Conflicts - Liquid Web
Learn how to manage client conflicts and get a step-by-step guide to successful conflict resolution for your WordPress agency.
Read more >
Troubleshoot Advanced Client push installation issues
There are some issues that can potentially occur when you deploy a client by using the Advanced Client Push install method. This article ......
Read more >
7 Common Network Issues and How to Resolve Them Fast
The Prevention Measure: Your local router might be configured to operate as a DNS Server, creating a DNS pass-through to your ISPs servers....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found