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
Download minishift (or anything that opens up license file for user in editor)
Accept all and download the server
Assert: Server is downloaded
Assert: License is shown as ''workflow.license" in editor unsaved - strange naming btw.
Option A:
Try to save workflow.license in editor (CTRL+C)
Assert: File is saved (probably into some temp location)
Actual result: Failed to save 'workflow.license': Unable to write file '/workflow.license' (NoPermissions (FileSystemError): Error: EACCES: permission denied, open '/workflow.license') error notification pops up
Option B:
Add deployment to the server (does not need to be started)
Choose File deployment
Assert: File system native dialog is shown
Actual result: File system provider for untitled:workflow.license is not available. pops up
Workaround: Close the license in editor without saving it.
The text was updated successfully, but these errors were encountered:
This editor is not intended to be saved. I'm not sure how to make it not-savable. I can ask if that's possible, but yeah, user not intended to save it.
I guess it should not be an issue let it to be "savable". I think the problem is in underlying editor file, that, I guess, points somewhere the user does not have rights, and that is the problem, right? Maybe use user home location instead of root and at the same time create file on the file system, so it is not "dirty" when showing it to user?
Option A:
Actual result:
Failed to save 'workflow.license': Unable to write file '/workflow.license' (NoPermissions (FileSystemError): Error: EACCES: permission denied, open '/workflow.license')
error notification pops upOption B:
Actual result:
File system provider for untitled:workflow.license is not available.
pops upWorkaround: Close the license in editor without saving it.
The text was updated successfully, but these errors were encountered: