question-mark
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.

Error is displayed in the editor even after it has been fixed (Linux)

See original GitHub issue

Hey everyone, thanks for all the hard work on Spyder 4. When I introduce an error in my code (eg by assigning a variable to a non-existing variable) and fix it immediately, the original error message will not go away unless I restart the python language server.

This only occurs when I introduce the error in the middle of my scripts, but not at the beginning.

This GIF shows what I am talking about: spyder_bug

Issue Report Checklist

  • Searched the issues page for similar reports
  • Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
  • Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
  • Could not reproduce inside jupyter qtconsole (if console-related)
  • Tried basic troubleshooting (if a bug/error)
    • Restarted Spyder
    • Reset preferences with spyder --reset
    • Reinstalled the latest version of Anaconda
    • Tried the other applicable steps from the Troubleshooting Guide
  • Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description

Pyflakes error message does not disappear after error in code is fixed.

Steps to reproduce

  1. Open medium-to-large script in spyder
  2. Go to somewhere in the middle
  3. Add faulty line that references a non-existing variable
  4. Fix faulty line

Notes on reproducibility:

  • occurred with several medium (~100 lines or more) to large scripts
  • failed to reproduce with simple mock code
  • failed to reproduce when introducing error in beginning of script (see GIF)

Versions

  • Spyder version: 4.1.2
  • Python version: 3.8.2
  • Qt version: 5.9.7
  • PyQt version: 5.9.2
  • Operating System name/version: Ubuntu 19.10

Dependencies


# Mandatory:
atomicwrites >=1.2.0           :  1.3.0 (OK)
chardet >=2.0.0                :  3.0.4 (OK)
cloudpickle >=0.5.0            :  1.3.0 (OK)
diff_match_patch >=20181111    :  20181111 (OK)
intervaltree                   :  None (OK)
IPython >=4.0                  :  7.13.0 (OK)
jedi =0.15.2                   :  0.15.2 (OK)
keyring                        :  None (OK)
nbconvert >=4.0                :  5.6.1 (OK)
numpydoc >=0.6.0               :  0.9.2 (OK)
parso =0.5.2                   :  0.5.2 (OK)
pexpect >=4.4.0                :  4.8.0 (OK)
pickleshare >=0.4              :  0.7.5 (OK)
psutil >=5.3                   :  5.7.0 (OK)
pygments >=2.0                 :  2.6.1 (OK)
pylint >=0.25                  :  2.4.4 (OK)
pyls >=0.31.9;<0.32.0          :  0.31.9 (OK)
qdarkstyle >=2.8               :  2.8.1 (OK)
qtawesome >=0.5.7              :  0.7.0 (OK)
qtconsole >=4.6.0              :  4.7.2 (OK)
qtpy >=1.5.0                   :  1.9.0 (OK)
rtree >=0.8.3                  :  0.9.4 (OK)
sphinx >=0.6.6                 :  3.0.0 (OK)
spyder_kernels >=1.9.0;<1.10.0 :  1.9.0 (OK)
watchdog                       :  None (OK)
xdg >=0.26                     :  0.26 (OK)
zmq >=17                       :  19.0.0 (OK)

# Optional:
cython >=0.21                  :  None (OK)
matplotlib >=2.0.0             :  3.1.3 (OK)
numpy >=1.7                    :  1.18.1 (OK)
pandas >=0.13.1                :  1.0.3 (OK)
scipy >=0.17.0                 :  1.4.1 (OK)
sympy >=0.7.3                  :  None (OK)

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:15 (8 by maintainers)

github_iconTop GitHub Comments

1reaction
basslerfishcommented, Jul 29, 2020

Just wanted to say that the error does not occur anymore with 4.1.4. Thanks again for taking care of this!

1reaction
basslerfishcommented, Jun 22, 2020

@ccordoba12 Thank you very much for taking care of this, I’ll make sure to check out 4.1.4!

Read more comments on GitHub >

github_iconTop Results From Across the Web

How can I fix git commit error "Waiting for your editor to close ...
I got that error while i configured with Atom. I got it solved by opening the app in background before executing the command...
Read more >
Resolving errors that occur when using the IBM Integration ...
Solution 2: Restart the IBM Integration Toolkit; do not load the file into an editor again until you have fixed the syntax errors....
Read more >
Error when changing Scripts - Unity Forum
This error seems to pop up every time I change code in Entities.ForEach. Restarting the editor fixes the problem, but it's very annoying ......
Read more >
Tips and Tricks for Troubleshooting LaTeX - Overleaf
Error messages are shown in red. They are usually more problematic and prevent the document from properly compiling, or indicate a bigger problem....
Read more >
How to Fix the "There Has Been a Critical Error on Your ...
Knowing that the cause is likely PHP-related, these may involve editing core WordPress files. Even with your site in a broken state, make...
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 Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found