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

[Bug]: Creating a Shell via POST:/shells is not persistent #240

Open
BohnSeb opened this issue Apr 18, 2024 · 3 comments
Open

[Bug]: Creating a Shell via POST:/shells is not persistent #240

BohnSeb opened this issue Apr 18, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@BohnSeb
Copy link

BohnSeb commented Apr 18, 2024

Contact Details

No response

Describe the bug

Creating a Shell over the REST API creates the shell successfully. However after a server restart the shell is no longer existing. I believe this was not the case in the v2023-09-13A release. Using DB instead doesn't help, it doesn't get saved.

To reproduce

Create a Shell using a POST request and restart the server. The shell will no longer be displayed or available via rest requests.

Screenshots

![DESCRIPTION](LINK.png)

Expected Behaviour

The Shell should be saved on file system in the data-path specified folder or in the database, so it is available after restarting the server.

Version

2023-11-17A

Operating System

Windows

Relevant log output

No response

@BohnSeb BohnSeb added the bug Something isn't working label Apr 18, 2024
@BohnSeb
Copy link
Author

BohnSeb commented May 2, 2024

There is a workaround for this. If you download the package one time it get's created locally. However if things get manipulated via the rest api the changes are then not written to the harddrive, even if you apply the same trick again

@andercrzz
Copy link

Hi @BohnSeb, have you solve it? I need this feature for my project and i think the bug is still unresolved. Thanks

@BohnSeb
Copy link
Author

BohnSeb commented Dec 10, 2024

Hi @BohnSeb, have you solve it? I need this feature for my project and i think the bug is still unresolved. Thanks

No, I only found the workaround. I cannot contribute a bugfix as I am not familiar with the programming language

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

No branches or pull requests

2 participants