Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get rid of some import cycle fragility that breaks LSP #8307

Merged
merged 1 commit into from
Feb 5, 2025
Merged

Conversation

msullivan
Copy link
Member

Follow ups we should do:

  • CI tests for LSP
  • A test that every module can be imported standalone

Follow ups we should do:
 * CI tests for LSP
 * A test that every module can be imported standalone
@msullivan msullivan added the to-backport-6.x PRs that *should* be backported to 6.x label Feb 5, 2025
@msullivan msullivan merged commit 51abacb into master Feb 5, 2025
23 checks passed
@msullivan msullivan deleted the lsp-cycle branch February 5, 2025 22:33
@msullivan msullivan added backported-6.x PRs that *have* been backported to 6.x and removed to-backport-6.x PRs that *should* be backported to 6.x labels Feb 5, 2025
msullivan added a commit that referenced this pull request Feb 5, 2025
Follow ups we should do:
 * CI tests for LSP
 * A test that every module can be imported standalone
deepbuzin pushed a commit that referenced this pull request Feb 18, 2025
Follow ups we should do:
 * CI tests for LSP
 * A test that every module can be imported standalone
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backported-6.x PRs that *have* been backported to 6.x
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants