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

Opening workflow.license file in editor after downloading some adapter (minishift, wf, eap) introduces strange behavior #158

Open
odockal opened this issue Feb 12, 2021 · 3 comments
Assignees

Comments

@odockal
Copy link
Contributor

odockal commented Feb 12, 2021

  1. Have RSP started
  2. Download minishift (or anything that opens up license file for user in editor)
  3. Accept all and download the server
  4. Assert: Server is downloaded
  5. Assert: License is shown as ''workflow.license" in editor unsaved - strange naming btw.

Option A:

  1. Try to save workflow.license in editor (CTRL+C)
  2. 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:

  1. Add deployment to the server (does not need to be started)
  2. Choose File deployment
  3. 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.

@robstryker
Copy link
Collaborator

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.

@odockal
Copy link
Contributor Author

odockal commented Feb 19, 2021

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?

@robstryker
Copy link
Collaborator

I think the problem is in underlying editor file, that, I guess, points somewhere the user does not have rights,

The editor is opened without a backing file. It is filled with content and has no official location at all.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants