8000 error when using configu store for eval · Issue #731 · configu/configu · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

error when using configu store for eval #731

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

Closed
davidmeirlevy opened this issue Mar 31, 2025 · 1 comment · Fixed by #732
Closed

error when using configu store for eval #731

davidmeirlevy opened this issue Mar 31, 2025 · 1 comment · Fixed by #732
Labels
bug Something isn't working

Comments

@davidmeirlevy
Copy link
Contributor

Current Behavior

  1. installed configu from scratch.
  2. configu login worked as expected.
  3. running configu eval from configu store.

got an error:

■  Could not read package.json: Error: ENOENT: no such file or directory, open '/Users/my-user/.configu/cache/packages/b11dbb3f9de1fd8f7f963b3b97e7cab3/package.json'

the folder "b11dbb3f9de1fd8f7f963b3b97e7cab3" is empty.

Expected Behavior

eval should work.

To Reproduce

No response

Context

configu store library changed its name to "configu-platform".

@davidmeirlevy davidmeirlevy added the bug Something isn't working label Mar 31, 2025
@RichardAkman
Copy link
Contributor
RichardAkman commented Apr 3, 2025

I've looked into the issue and identified two separate problems:

  1. Incorrect Store Type:
    The configu login command generates a .configu file with an outdated store type. This happened because the library was renamed to "configu-platform", but the login command wasn’t updated accordingly.

  2. Uninformative Error Message:
    The CLI returns a vague error about a missing directory. This occurs because the underlying configu common package interface is trying to look up a non-existing store type, leading to a misleading error message.

Let's limit this issue to addressing the incorrect store type generated during login. I'll open a separate issue to improve the error messaging in the CLI.

EDIT: follow-up issue to the 2nd problem: #733

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment < 489D /div>
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants
0