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.

GraphQL error on startup

See original GitHub issue

Issue Description

When starting KingPhisher client, an error dialog appears. Cancelling allows messages to be sent, however the View Campaign tab, and campaign selection freezes.

I haven’t tried a fresh installation, but a fresh installation on a different OS (Windows Server 2012) seems fine.

Reproduction Steps

Start King Phisher (error appears)

Environment Details

Host OS: Windows 10 King Phisher Version: 1.11.0

Error Details / Stack Trace

Stack trace in client:

Error Type: king_phisher.errors.KingPhisherGraphQLQueryError
Error Details: KingPhisherGraphQLQueryError()
Error UID: 9da2cdc6-239c-44ce-91d6-083a91218548
RPC Error: N/A (Not a remote RPC error)
King Phisher Version: 1.11.0
Platform Version: Windows: 10 10.0.16299  Multiprocessor Free (Frozen=True)
Python Version: 3.4.4
Gtk Version: 3.18.9
Timezone: Pacific/Auckland

Thread Information:
    Thread-12 (alive=True daemon=True)
 => MainThread (alive=True daemon=False)
    Thread-7 (alive=True daemon=True)
    Thread-6 (alive=True daemon=True)
    Thread-2 (alive=True daemon=True)
    Thread-13 (alive=True daemon=True)
    Thread-1 (alive=True daemon=False)

Stack Trace:
Traceback (most recent call last):
  File "C:\king-phisher\king_phisher\client\gui_utilities.py", line 123, in wrapper
  File "C:\king-phisher\king_phisher\client\tabs\campaign.py", line 597, in <lambda>
  File "C:\king-phisher\king_phisher\client\graphs.py", line 332, in refresh
  File "C:\king-phisher\king_phisher\client\graphs.py", line 417, in _get_graphql_campaign_cache
  File "C:\king-phisher\king_phisher\client\client_rpc.py", line 205, in graphql
king_phisher.errors.KingPhisherGraphQLQueryError

Possibly related (?) logs on the server:

2018-10-10 02:35:07,674 graphql.execution.utils                            ERROR    graphql.error.located_error.GraphQLLocatedError: The address 103.101.42.253 is not in the database.

Issue Analytics

State:
Created 5 years ago
Comments:14

Top GitHub Comments

1reaction

zeroSteinercommented, Oct 10, 2018

That’s a good point, I’ll add a note into the Updating King Phisher wiki page.

1reaction

zeroSteinercommented, Oct 10, 2018

Well done! That sounds about right and confirms my suspicion as well. This is definitely a bug I’ll need to patch.

FWIW, you should have been able to stop the server, use the --update-geoip-db option for the server and then restart it instead of making changes to the code. IIRC, the server will log a warning message if the database is over 90 days old. We include this as a step in our routine maintenance of our internal servers.

Top Results From Across the Web

Error handling - Apollo GraphQL Docs

Built-in error codes ; GRAPHQL_VALIDATION_FAILED. The GraphQL operation is not valid against the server's schema. ; BAD_USER_INPUT. The GraphQL operation includes ...

Understanding GraphQL Error Handling Mechanisms in ...

Today's episode is about setting up your Spring-boot project to host your first GraphQL API entry points then call them using the web-based...

Top GraphQL Errors and How to fix them

Top GraphQL Errors and How to Fix them. Error handling in GraphQL is different on both server and client side tooling.

Error Handling in GraphQL With Spring Boot - Baeldung

A practical guide to GraphQL error handling with Spring Boot. ... We'll look at what the GraphQL spec says about the error responses....

A Guide to GraphQL Errors

Stage 2: Ad Hoc Error Fields ... OK so if top-level errors are not ideal for user-facing errors, we have to start thinking...