You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Try to start dashdot with above mentioned command.
Errors.
Relevant log output
node:internal/fs/utils:345
throw err;
^
Error: ENOENT: no such file or directory, open '/home/yunohost.app/dashdot/version.json'
at Object.openSync (node:fs:585:3)
at readFileSync (node:fs:453:35)
at /home/yunohost.app/dashdot/dist/apps/api/main.js:2:2650516
at /home/yunohost.app/dashdot/dist/apps/api/main.js:2:2653387
at Object.<anonymous> (/home/yunohost.app/dashdot/dist/apps/api/main.js:2:2653619)
at Module._compile (node:internal/modules/cjs/loader:1105:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10)
at Module.load (node:internal/modules/cjs/loader:981:32)
at Function.Module._load (node:internal/modules/cjs/loader:822:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12) {
errno: -2,
syscall: 'open',
code: 'ENOENT',
path: '/home/yunohost.app/dashdot/version.json'
}
Info output of dashdot cli
INFO
=========
Yarn: 3.2.1
Node: v16.16.0
Dash: unknown
Cwd: /home/yunohost.app/dashdot
Hash: 015eab35801f45646399d9d3e958b792d763a5cd
In Docker: false
In Podman: false
In Docker (env):
What browsers are you seeing the problem on?
Firefox
Where is your instance running?
Linux Server
Additional context
No response
The text was updated successfully, but these errors were encountered:
## [4.3.1](v4.3.0...v4.3.1) (2022-07-09)
### Bug Fixes
* **api:** dont fail on missing version file for integrations ([87449ff](87449ff)), closes [#193](#193)
Description of the bug
This is the error when trying to start dashdot:
And this is the command I use to launch dashdot:
How to reproduce
Relevant log output
Info output of dashdot cli
What browsers are you seeing the problem on?
Firefox
Where is your instance running?
Linux Server
Additional context
No response
The text was updated successfully, but these errors were encountered: