New for viscode editor.
Environment: No Internet-access, but local network is perfect. Login in as root. Client: window-10, Server: Ubuntu 20
Description: when Carl+S is pressed, no any promotion appears, but a white dot besides the file name always showing. When close the vscode app, it tells:
Closing the window is taking a bit longer…
The following operations are still running:
- saving test files
Permission: 777 for all files and folder.
Others issues: install extensions by clicking install in SSH, showing XHR failed in bottom-left corner.
Any suggestion to solve this problem?
Related
Edit 1: I am using the floobits plugin (latest release), uninstalled and installed again from the package manager. I am not getting a traceback but an error window with the following error message: Unable to join workspace. CERTIFICATE_VERIFY_FAILED unable to get local issuer certificate (_ssl.c:1124).
Edit 2: I had tried the Package Control Upgrade package and Staisfy Dependencies, but that did not help fix it.
I was able to fix it (answer below).
I have been stuck on this issue for days now. When I try to connect to a floobits workspace in sublime text, I get the error message that CERTIFICATE_VERIFY_FAILED unable to get local issuer certificate (_ssl.c:1124).
I searched about this a lot but I don't know what's wrong anymore.
I started by upgrading certifi and pip itself.
Then I read somewhere that I should check if OpenSSl(and the requests library of py) and cURL can open the URL (floobits.com) since the workspace is hosted there. curl returned no errors but OpenSSL (and requests) wasn't able to verify, gave the same error.
So I downloaded the certificates from the website on opening it in chrome. I downloaded all three certificates (for the root, intermediate and the website itself), and appended them to cacert.pem inside the certifi package folder. After that, when I ran it, OpenSSL was able to open it (and the requests library too, got a 200 response code).
But, floobits still wasn't able to connect and gave the same error. I know that there is nothing wrong with floobits.com and the sublime extension since a friend can still open the workspace without problems.
Please tell me what I can do to fix this.
So I managed to 'solve' the problem by bringing Sublime back to a fresh state and then copying my files again. Answering here if anyone gets this problem.
Method:
Go to the Sublime > Preferences > Browse Packages
In this folder, copy and backup the 'User' folder to someplace else.
Delete all the folders in this location (Sublime need not be closed during this but it's best if you do close it)
Copy the backed-up 'User' folder back here (remember the location where you deleted, %AppData%\Roaming\Sublime Text 3\Packages (for Windows))
All set, you now have a fresh installation of sublime.
Sublime will start installing all packages again, wait for it to finish and resume work.
This solved the problem I was having. Unfortunately, I couldn't track down the problem.
I am trying to download Appium Desktop in Ubuntu 16 (I've just been using the terminal to run it so far).
I understand that for Ubuntu, I must download the source code release they have on git (Source Code tar.gz), as apposed to their .exe (windows) or .dmg (mac) releases. After downloading it and un-tarring it, I do not know how to "install" it. I tried reading the README.md, but cannot find the instruction.
How to do this?
Many thanks in advance
1.2.0-beta.2 offers an AppImage for Linux - https://github.com/appium/appium-desktop/releases/
Download it, run chmod a+x on it, and then ./AppImage to execute it.
Offical url: https://github.com/appium/appium-desktop/releases
If you have no idea which file to download, there's a file contains "linux" and end with format "yml", the file name is contained in it.
The file should be an AppImage file as above mentioned, you should change the permission by checking box of "Allow executing file as program" of its "Properties".
And then run "./appiumimagename" in terminal to launch Appium Desktop or install it.
download file named'Appium-linux-1.18.2.AppImage'.
change file permission to "Allow executing file as program" in file properties.
Right click and click on RUN.
I'm not sure if this is an issue with vagrant, virtualbox or a configuration issue inside the box itsef, however:
Using the following setup: Apache is running in the guest with its server root set to /srv/http, this is a synched folder which points to ./public_html on the host.
While most of the time it works as expected, the following steps causes an issue
1) Navigate to a file that doesn't exist localhost:8080/test2.css -- shows a 404 error as expected but correctly connects to the guest which is serving the error
2) Create test2.css with some content and place it in public_html
3) Reload localhost:8080/test2.css -- Still shows a 404 error even though the file now exists
4) To debug, run vagrant ssh and then ls /srv/http. Which shows:
ls: cannot access test2.css: No such file or directory
So it's seeing the file, sort of but it shows without any permissions:
-????????? ? ? ? ? test2.css
-rw-rw-r-- 1 vagrant 7 Oct 23 11:13 test3.css
If I then re-save the file as test3.css, a file that hasn't yet been accessed it works perfectly. E.g. on the host, save the file I had open as test3.css and then navigate to it, it works as expected!
Any ideas? On why this might be?
In short: If apache has tried to read a file that doesn't exist, creating that file will then cause it to have invalid permissions. If apache has never tried to read the file before, it can be created and work as expected.
Thanks for any help, I'm really confused by this!
This turned out to be a kernel bug on the guest. Upgrading to 4.2.4 using the same Vagrant/Virtualbox/Guest Modules solved the issue.
I'm experimenting a weird issue. Most of the time (almost everytime) my pdf are getting generated with the permission (rwx-r--r--) 644 which is correct.
But 'sometimes'.. and I cannot understand why this happens but they get created with permission (rw-------) 600. this cause a "permission denied" when other systems try to copy or read the PDF...
Did someone already had this issue? Is it possible that is it a problem in my Jasper config ? or the Server config ?
Ps: I'm running my web app on an redhat server (container is Weblogic ).
This happens when the program through which you run and generate PDF is in the same permission that is root.
you can run your PDF generating software ( or whatever you are using ) in home user mode and not root user mode)
Or just go to that folder where your PDF has been generated and run from terminal
user#your_folder>> sudo chown username:username *
give password if asked.... You can use this with every file and folder that has this problem
You will see once you run this command a 'LOCK' icon goes away and file/folder becomes normal
Hope this helps you
I recently switched to a different computer for my programming. it was another collegue's computer and was not reformated. i installed xCode on it. This is the first time i've tried to update an app of ours on this machine. i archived w/out errors and i validated w/out errors. when i go to submit, i get these two errors:
*Unable to create configuration directory: /Users/username/.itmstransporter
*Your home folder must be writable in order to save run-time configuration data. Please
ensure your home folder exists and is writable.
i am not a mac OS person and can barely get around on a mac. a coworker checked and i do have read/write permisions for /Users directory.
can i fix this or do i need to re-install xCode or the OS?
I belive this is because your username on that machine can not write to your home directory (some how)..
Try opening a finder window and "get info" on your home folder. (from finder, Cmd-N opens a window, right click on the folder in the left that is your user name, that is your home folder, and select get info. Right click might not work, if it does not work, use ctrl-click.)
In the "get info" dialog, at the bottom you will see "Sharing & Permissions" you may have to turn the triangle by clicking on it. In the list, make sure your username has Read & Write prifileges, if not, you need to add them by logging in as an admin and changing them.
This photo is just for reference, but you can see justin (me) has Read & Write, that is what you need on your home directory.