Error on loading [undisclosed] endpoint. about inql HOT 8 CLOSED

Hi there, can you try upgrading to jython 2.7.2b?

from inql.

Hi thypon, with jython 2.7.2 I have another error:

Exception in thread Thread-2:Traceback (most recent call last):
  File "/Applications/jython-standalone-2.7.2.jar/Lib/threading.py", line 222, in _Thread__bootstrap
    self.run()
  File "/Applications/jython-standalone-2.7.2.jar/Lib/threading.py", line 213, in run
    self._target(*self._args, **self._kwargs)
  File "/var/folders/rn/8g3wbky125nghvbyw9whlt3r0000gn/T/tmpjJzBAH/inql/utils.py", line 159, in async_run
  File "/var/folders/rn/8g3wbky125nghvbyw9whlt3r0000gn/T/tmpjJzBAH/inql/widgets/generator.py", line 312, in async_run
  File "/var/folders/rn/8g3wbky125nghvbyw9whlt3r0000gn/T/tmpjJzBAH/inql/introspection.py", line 281, in init
  File "/Applications/jython-standalone-2.7.2.jar/Lib/json/__init__.py", line 338, in loads
    return _default_decoder.decode(s)
  File "/Applications/jython-standalone-2.7.2.jar/Lib/json/decoder.py", line 365, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
TypeError: expected string or buffer, but got <type 'NoneType'>

from inql.

This second error is due to the http response being None. This can be due to an unauthorized response or something similar.
May I ask you the endpoint you are trying to run inql on?

from inql.

Hum you are right now I don't have any error but nothing is loaded. I tried manually loading the json and it works.

I think it might be the size of the response the problem: 893299.

I can't share the URL publicly, is there a way to send it to you privatly ?

from inql.

github[at]pompel[dot]me should be fine

from inql.

Mh @Techbrunch I tested the endpoint you provided and it is outputting the analysis immediately. Are you enabling cycles detection? There may be a timeout/race condition with super connected graphs with that option enabled, which is not on by default anyway.

I will wait 7 days and close as unreproducible on my side.

from inql.

FYI I'm using the Burp Suite plugin and not the standalone client, if that's what you tried then you can just close the issue.

from inql.

Indeed, tested on latest machine. I think it was a transient condition due timing.

Feel free to reopen if you think the bug is still there.

from inql.