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.

Saving opens up the bug report

See original GitHub issue

Description

What steps will reproduce the problem?

Literally I just pressed Ctrl+s to save, and it’s been bringing up this dialogue. Hopefully if I exit out and reopen Spyder it will go away. I don’t notice anything particularly concerning happening…

Traceback

Traceback (most recent call last):
  File "C:\Users\sterg\anaconda3\envs\ElM2D\lib\site-packages\spyder\plugins\editor\widgets\editor.py", line 1904, in _save_file
    self.modification_changed(index=index)
  File "C:\Users\sterg\anaconda3\envs\ElM2D\lib\site-packages\spyder\plugins\editor\widgets\editor.py", line 2360, in modification_changed
    finfo = self.data[index]
IndexError: list index out of range

Versions

  • Spyder version: 5.0.5
  • Python version: 3.7.11
  • Qt version: 5.9.6
  • PyQt5 version: 5.9.2
  • Operating System: Windows 10

Dependencies


# Mandatory:
atomicwrites >=1.2.0          :  1.4.0 (OK)
chardet >=2.0.0               :  4.0.0 (OK)
cloudpickle >=0.5.0           :  1.6.0 (OK)
cookiecutter >=1.6.0          :  1.7.2 (OK)
diff_match_patch >=20181111   :  20200713 (OK)
intervaltree >=3.0.2          :  3.1.0 (OK)
IPython >=7.6.0               :  7.22.0 (OK)
jedi =0.17.2                  :  0.17.2 (OK)
jsonschema >=3.2.0            :  3.2.0 (OK)
keyring >=17.0.0              :  23.0.1 (OK)
nbconvert >=4.0               :  6.1.0 (OK)
numpydoc >=0.6.0              :  1.1.0 (OK)
paramiko >=2.4.0              :  2.7.2 (OK)
parso =0.7.0                  :  0.7.0 (OK)
pexpect >=4.4.0               :  4.8.0 (OK)
pickleshare >=0.4             :  0.7.5 (OK)
psutil >=5.3                  :  5.8.0 (OK)
pygments >=2.0                :  2.9.0 (OK)
pylint >=1.0                  :  2.9.6 (OK)
pyls >=0.36.2;<1.0.0          :  0.36.2 (OK)
pyls_black >=0.4.6            :  0.4.6 (OK)
pyls_spyder >=0.3.2;<0.4.0    :  0.3.2 (OK)
qdarkstyle =3.0.2             :  3.0.2 (OK)
qstylizer >=0.1.10            :  0.1.10 (OK)
qtawesome >=1.0.2             :  1.0.2 (OK)
qtconsole >=5.1.0             :  5.1.0 (OK)
qtpy >=1.5.0                  :  1.9.0 (OK)
rtree >=0.9.7                 :  0.9.7 (OK)
setuptools >=39.0.0           :  57.4.0 (OK)
sphinx >=0.6.6                :  4.0.2 (OK)
spyder_kernels >=2.0.4;<2.1.0 :  2.0.5 (OK)
textdistance >=4.2.0          :  4.2.1 (OK)
three_merge >=0.1.1           :  0.1.1 (OK)
watchdog >=0.10.3             :  2.1.3 (OK)
zmq >=17                      :  20.0.0 (OK)

# Optional:
cython >=0.21                 :  0.29.24 (OK)
matplotlib >=2.0.0            :  3.4.2 (OK)
numpy >=1.7                   :  1.21.1 (OK)
pandas >=1.1.1                :  1.3.1 (OK)
scipy >=0.17.0                :  1.7.1 (OK)
sympy >=0.7.3                 :  None (NOK)

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:7 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
sgbairdcommented, Sep 6, 2021

It’s been pretty sporadic - I haven’t noticed any consistent way to cause the error. I’ll try to update the issue if I figure out a sort of MWE (fine with it being closed until then). For now, I’ve just been restarting or “ignoring errors during this session”, since it seems to still be saving, thankfully.

0reactions
ccordoba12commented, Sep 6, 2021

Thanks for your help @sgbaird.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Capture and read bug reports - Android Developers
A bug report contains device logs, stack traces, and other diagnostic information to help you find and fix bugs in your app.
Read more >
How to Write A Good Bug Report? Tips and Tricks
Your effort towards writing a good Bug report will not only save the resources of the company but also create a good relationship...
Read more >
Save time and money by writing useful bug reports - codeburst
Bad bug reports are not only annoying because they create a lot of overhead and cost time, but they also indirectly cost money....
Read more >
How to write a bug report effectively: examples and templates
Learn how to write bug reports effectively with this guide, including examples and templates. We've also included downloadable templates in ...
Read more >
ReportingBugs - Community Help Wiki
Apport will then upload the problem information to Launchpad, and a new browser window will then open to inform you that the bug...
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