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

jarvis-scripts vor Update / Upgrade anlegen #2802

Open
mcuiobroker opened this issue Sep 14, 2024 · 5 comments
Open

jarvis-scripts vor Update / Upgrade anlegen #2802

mcuiobroker opened this issue Sep 14, 2024 · 5 comments
Assignees
Labels
alpha / beta 🚧 Issue related to an alpha or beta version bug 🐛 Something isn't working user scripts User scripts v3.2 Roadmap for v3.2

Comments

@mcuiobroker
Copy link
Collaborator

mcuiobroker commented Sep 14, 2024

Beim Upgrade von v3.1.8 auf v3.2.0.rc.X hat es mehrfach Probleme mit dem nicht vorhandenen Verzeichnis
jarvis-scripts gegeben. insofern sollte es vorab angelegt werden, wenn es nicht vorhanden ist.

@Zefau
Copy link
Owner

Zefau commented Sep 14, 2024

Im Release Candidate wird es bereits angelegt.

@mcuiobroker
Copy link
Collaborator Author

Die User haben auf v3.2.0-rc.3 upgegradet und einen Fehler erhalten.

	2024-09-14 16:35:51.756	error	Exception-Code: ENOENT: ENOENT: no such file or directory, stat '/opt/iobroker/iobroker-data/files/0_userdata.0/jarvis-scripts'
 
jarvis.0
2024-09-14 16:35:51.754	error	Error: ENOENT: no such file or directory, stat '/opt/iobroker/iobroker-data/files/0_userdata.0/jarvis-scripts' at Object.statSync (node:fs:1665:25) at [kFSWatchStart] (node:internal/fs/recursive_watch:204:37) at watch (node:fs:2488:36) at JarvisServer.init (/opt/iobroker/node_modules/iobroker.jarvis/lib/jarvis.server.js:1:2460) at /opt/iobroker/node_modules/iobroker.jarvis/jarvis.min.js:1:2672
 
jarvis.0
2024-09-14 16:35:51.752	error	unhandled promise rejection: ENOENT: no such file or directory, stat '/opt/iobroker/iobroker-data/files/0_userdata.0/jarvis-scripts'
 
jarvis.0
2024-09-14 16:35:51.751	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

https://forum.iobroker.net/topic/68566/jarvis-v3-2-x-just-another-remarkable-vis/288?_=1726256267688

@Zefau
Copy link
Owner

Zefau commented Sep 14, 2024

Jo, das stimmt, das ist dann mit rc-4 gefixed. Liegt daran, dass ich die Ordner überwache und die Erstellung des Ordners asynchron ist, also der Ordner noch nicht angelegt ist, wenn ich die Überwachung starte.

@Zefau Zefau added bug 🐛 Something isn't working alpha / beta 🚧 Issue related to an alpha or beta version #status: implemented-locally 🛠️ Status: Issue has been implemented locally (but not pushed to repository yet) v3.2 Roadmap for v3.2 labels Sep 14, 2024
@github-project-automation github-project-automation bot moved this to ROADMAP in jarvis v3.2 Sep 14, 2024
@Zefau Zefau added the user scripts User scripts label Sep 14, 2024
@Zefau
Copy link
Owner

Zefau commented Sep 14, 2024

Die Version v3.2.0-rc.4 sollte den Fehler beheben - bitte einmal prüfen. Sofern es behoben ist, gerne das Issue schließen.


The version v3.2.0-rc.4 should fix the bug - please verify. If the bug has been solved, you may close the issue.

@Zefau Zefau added #status: ready-to-test ✔️ Status: Issue fixed and ready-to-test and removed #status: implemented-locally 🛠️ Status: Issue has been implemented locally (but not pushed to repository yet) labels Sep 14, 2024
@mcuiobroker
Copy link
Collaborator Author

Der Ordner wird nicht automatisch angelegt.
https://forum.iobroker.net/topic/68566/jarvis-v3-2-x-just-another-remarkable-vis/371 und ff

@Zefau Zefau removed the #status: ready-to-test ✔️ Status: Issue fixed and ready-to-test label Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
alpha / beta 🚧 Issue related to an alpha or beta version bug 🐛 Something isn't working user scripts User scripts v3.2 Roadmap for v3.2
Projects
Status: ROADMAP
Development

No branches or pull requests

2 participants