Klever

Evgeny Novikov wrote:

I didn't see any specific errors in the browser console as promised by corresponding pop-ups when, say, the error trace visualizer couldn't get new source file due to the connection was lost. When I click on source line number I always see just the following error message:
[...]
that doesn't depend on connection failures.
My browser is Firefox 49.0.2.

I suppose it is bug in firefox (it think that $('#' + v) is empty but it is not if v != '').

Concerning the bug I suppoose your browser use old javascript from cache. Or you click lines of already uploaded source code (there are no requests to server in this case), find others in your error trace.

Vladimir Gratinskiy wrote:

Evgeny Novikov wrote:

I didn't see any specific errors in the browser console as promised by corresponding pop-ups when, say, the error trace visualizer couldn't get new source file due to the connection was lost. When I click on source line number I always see just the following error message:
[...]
that doesn't depend on connection failures.
My browser is Firefox 49.0.2.

I suppose it is bug in firefox (it think that $('#' + v) is empty but it is not if v != '').

Concerning the bug I suppoose your browser use old javascript from cache. Or you click lines of already uploaded source code (there are no requests to server in this case), find others in your error trace.

I switched off caches a long ago. Also I didn't see related sources, i.e. they weren't downloaded early (I switch off the network immediately after I just get the visualized error trace). I see pop-ups that say about ajax errors, but can't find something useful in any browser log or console. Can you try Firefox to specify where these errors can be actually found?

Evgeny Novikov wrote:

I switched off caches a long ago. Also I didn't see related sources, i.e. they weren't downloaded early (I switch off the network immediately after I just get the visualized error trace). I see pop-ups that say about ajax errors, but can't find something useful in any browser log or console. Can you try Firefox to specify where these errors can be actually found?

Logging is enabled when console is opened. So you should repeat action that led to error with opened console.

Vladimir Gratinskiy wrote:

Evgeny Novikov wrote:

I switched off caches a long ago. Also I didn't see related sources, i.e. they weren't downloaded early (I switch off the network immediately after I just get the visualized error trace). I see pop-ups that say about ajax errors, but can't find something useful in any browser log or console. Can you try Firefox to specify where these errors can be actually found?

Logging is enabled when console is opened. So you should repeat action that led to error with opened console.

Of course I did that. I just see that some requests were made but there isn't any responses on them. Also there wasn't anything that looks like an error.

Evgeny Novikov wrote:

Vladimir Gratinskiy wrote:

Evgeny Novikov wrote:

I switched off caches a long ago. Also I didn't see related sources, i.e. they weren't downloaded early (I switch off the network immediately after I just get the visualized error trace). I see pop-ups that say about ajax errors, but can't find something useful in any browser log or console. Can you try Firefox to specify where these errors can be actually found?

Logging is enabled when console is opened. So you should repeat action that led to error with opened console.

Of course I did that. I just see that some requests were made but there isn't any responses on them. Also there wasn't anything that looks like an error.

I didn't find errors in firefox's console too. So I will change the message to "Ajax request error. Maybe connection refused".