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.

Sign up for GitHub

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

Jump to bottom

Error: Config key not found.... on test that uses Mneme #507

Closed
tcoopman opened this issue Nov 29, 2023 · 3 comments
Closed

Error: Config key not found.... on test that uses Mneme #507

tcoopman opened this issue Nov 29, 2023 · 3 comments
Assignees
@zachallaun
Labels
bug Something isn't working

Comments

@tcoopman
Copy link

image

this is the above error, my test_helper.exs does contain Mneme.start()
@scohen scohen added the bug Something isn't working label Nov 30, 2023
@scohen
Copy link
Collaborator

scohen commented Nov 30, 2023

@zachallaun this seems right in your wheelhouse.

@zachallaun
Copy link
Collaborator

Mneme assumes that test_helper.exs has already been executed when test modules are compiled. @scohen and I spoke briefly about this and what likely needs to happen is:

  1. Lexical should ensure that test_helper.exs is evaluated, and
  2. ensure that the System.at_exit callbacks registered by ExUnit don't run when the VM exits.

zachallaun added a commit to zachallaun/mneme that referenced this issue Apr 15, 2024
@zachallaun
fix: allow tests using mneme to compile when mneme hasn't started
fed2f79 
This allows as-you-type compilation in language servers.\n\nFixes lexical-lsp/lexical#507
@zachallaun
Copy link
Collaborator

Turns out there's a much easier fix on Mneme's side. I'm going to be cutting a release soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@zachallaun zachallaun

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@tcoopman @scohen @zachallaun