Skip to content

Big projects lead to Propagating panic for cycle head that panicked in an earlier execution in that revision in lsp features, specifically auto import #3287

@Wade-Roberts

Description

@Wade-Roberts

Summary

Some context from VS Code server logs:

2026-04-16 16:02:48.513105285  INFO Version: 0.0.31
2026-04-16 16:02:48.527272881  INFO Defaulting to python-platform `linux`
2026-04-16 16:02:48.527636881  INFO Python version: Python 3.12, platform: linux

In my smaller projects where I use uv, auto-import works fine, e.g.

Image

When I'm working in a large workspace based monorepo though, I get this in the server logs when I try to inspect the actions on an unresolved import error:

2026-04-16 16:04:23.886670807  WARN Propagating panic for cycle head that panicked in an earlier execution in that revision
2026-04-16 16:04:23.886672182  WARN Propagating panic for cycle head that panicked in an earlier execution in that revision
2026-04-16 16:04:23.886715182  WARN Propagating panic for cycle head that panicked in an earlier execution in that revision
2026-04-16 16:04:23.886726057  WARN Propagating panic for cycle head that panicked in an earlier execution in that revision
2026-04-16 16:04:23.886857057  WARN Propagating panic for cycle head that panicked in an earlier execution in that revision
2026-04-16 16:04:23.905581364  WARN Propagating panic for cycle head that panicked in an earlier execution in that revision
...

Version

0.0.31

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-infoMore information is needed from the issue author

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions