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
When there are some synapse configuration issues which fails the deployment of the capp or when we continuously keep on deploying capp changes to the server below issues can be observed.
After the server start the debug controls disappear which blocks the user from stopping the running server.
When we stop a running server it does not terminate the server completely and therefore when a user try to run the server again via the extension the user will get an error mentioning that the server is already running.
If we try to use the build and run option again while the server is starting it will try to show in the extension that another server is starting but in the backend nothing as such is happening as we can only run a single server instance via the extension.
Existing capps in the carbonapps folder of the server does not get deleted completely when deploying a new capp via the extension.
Please note that some of the aforementioned issues may be intermittent.
Version
1.1.3
Environment Details (with versions)
No response
The text was updated successfully, but these errors were encountered:
Description
When there are some synapse configuration issues which fails the deployment of the capp or when we continuously keep on deploying capp changes to the server below issues can be observed.
Please note that some of the aforementioned issues may be intermittent.
Version
1.1.3
Environment Details (with versions)
No response
The text was updated successfully, but these errors were encountered: