I am currently working on a file in the arduino IDE and I am running into a problem I had not been encountering until recently. Image shows error I am receiving upon upload. Sometimes I am able to unpload files with no problem and this error doesnt occur but sometimes it does occur and I am no longer able to upload anything. The file I uploaded that I initially started noticing this was an example file in the Ethernet_Generic library called UdpNTPClient. Im not sure if maybe this file just backs up my upload or if its lingering in the background.
The hardware I'm uploading to is an ESP32. Any help or advice would be greatly appreciated!
Related
I recently installed Visual Studio Code 1.72.2 on a Windows 10 OS.
Since I started using it, I had a hard time when saving source files in VS Code, with the error message very frequently appearing and saying "Failed to save 'Test.py': Unable to write file '[file_path]' (Unknown (FileSystemError): Error: UNKNOWN: unknown error, open '[file_path]')"
When I create a workspace and the first source file, it actually saves without a problem. Then, after about 5-10 minutes of editing and debugging, the aforementioned error message suddenly pops up and I can't save the file from there on.
After searching Google many times, I could only find one post written by someone who was probably in an identical situation as mine (identical problems like files becoming corrupted after experiencing this "Failed to save" error), but the post was closed without any useful information.
I could find some posts about having "Failed to save" type of errors like File Permission error, but since my error exclusively says "UNKNOWN" I can't even guess what went wrong.
I already have tried disabling the installed extensions, but still no luck. This error happens regardless of the language of the source files, hence it shouldn't be a problem with a particular extension.
One last note, the file system I am using for source files and workspaces is D:, which is a 256GB external USB Mass Storage Device.
Any suggestions would be appreciated.
I set up a new project with Visual Studio 2019 version 16.3.10. When I try to build I get the following error:
EasyTcpStubs.c : fatal error C1090: PDB API call failed, error code '3':
W:\Dropbox\Me (Mine)\TcpToNamedPipe\TcpToNamedPipe\Debug\vc142.pdb
I have searched the internet and this site for any explanation of this error. Maybe I missed it but I could not find anything.
The project is a Console project.
The error occurs without a line number so it does not seem to be the source. I tried another project and it compiles OK (but it is an old project whereas this error is occuring on a brand new project.
Does anyone know something about this?
For me, I stopped Dropbox and it works. It seems that something is using W:\Dropbox\Me (Mine)\TcpToNamedPipe\TcpToNamedPipe\Debug.
In my experience this error is likely due to some permission error. If your project is in Dropbox, OneDrive, etc, most likely you get this error because your Dropbox cannot sync and update files properly. Restart Dropbox and that should fix the issue.
In My case, I suspect it is some type of race condition/lock issue with the code that opens/closes the *.pdb file. In my case I am running /MP (Multiprocessor Compile) so up to 4 *.cpp modules being built at a time. It works fine on a stand alone build machine. But I'm a vendor and must use a VM environment to develop for my customer, and the disk requirements are so large I must place the builds on a network share.
The latency of file I/O access over a network share seems to be the issue.
Thats all I know about the issue at the moment.
As I learn/test discover more, I can improve this answer.
Synology Drive Client (v3.2.0) caused this error for me. Pausing the sync eliminated the error. Thanks to all for the clue of DropBox, OneDrive, etc. causing the issue.
I made a modification in a php file and uploaded it via Filezilla. It always worked fine for me, even if sometimes it would not upload immediately. This time, however, it's not working anymore in any way. I upload the file with the same name and it looks like it overwrites the old one, but the size of the file doesn't change. When I open the site on the browser (I've been testing in Chrome and Firefox and already cleaned their caches many times since then, and still nothing happens) and look at the source code, it shows the new code with the modification, but even so the site is still the same old one. When I open the file directly from Filezilla it also shows the modified file, but the file size doesn't change. It started yesterday, before the upgrading to version 3.7.3. It's updated now, but the files are still not being updated. I also tried renaming the file, deleting it from the ftp and uploading again, uploading it to another folder and then moving it to the root, but nothing happens. Any idea of what can be causing this?
It turns out it was a problem with the permissions with the host. I contacted them and the issue was solved.
Has anyone ever encountered a situation where your assets (image png files) got deleted from your web path?
Let me explain it little more clearly.
I am loading some images located in my localhost (not in flex4 application path) from my flex4 application using the loader and also with BulkLoader
This is the second time it happened that some of the images got deleted from the path which are in localhost.
I am not sure what is causing this? is that the loader? or bulkloader or the webserver? (WAMP) or any virus?
It happened 2nd time in last 7 days. I was lucky that I had a copy in the remote host so I got them back easily. But its a mistrey what and why it is getting deleted.
Any thoughts what might have caused this? or anyone knows any bug in the Loader or BulkLoader?
Well I found the answer. The culprit is the Flash Builder.
I am prity sure many of flash developers have faced the debugger launching issue where the flash builder never launches the app as it might have struck up some where and it halts the launching process at around 50-60% progress. It happened to me too and happens considerable enough times in a day.
I just found that this is linked to the issue which I have asked.
FB cleans the debug/output folder every time the app is compiled. I wouldn't have mind if it cleans only the project files. However, it just removes all the contents in the folder and adds them back. This happens in the back ground every time I change the code and save and run or "Clean" the project to build a fresh copy.
During this process (removing and adding files back) if the FB struck up and I forcefully terminate the process (which is must some times); my files are gone.
The flash output folder is my web root where I will have all my php, assets and all server-side stuff.
I will open a topic to discuss on how to avoid it which also I have problem there too.
I took a backup of my live Magento site yesterday (zipped up the files and took a DB dump then created the site from those dumps).
Oddly though, on my local machine I get a firebug error that states "$ is not a function" and this error occurs every 500ms or so. So after a minute or 2 I have thousands of errors in the console all the same.
The site is an exact replica of my live site and I don't get the error on that so I'm stumped!
Usually I would think this is a prototype/jquery conflict, but it only seems to happen on my local machine.
Any one have a clue what might be going on?
Thanks
Load a page where you see the error.
View the source of the page.
Find the line that's supposed to load prototype.js by searching for the string prototype.js.
ex. http://magento.example.com/js/prototype/prototype.js
Discover that, for one of myriad reasons, the file isn't loading. (wrong URL, permissions, corrupt file, etc.)
Address problem discovered above.
Ok so this was the problem:
The reason it worked on live and not dev was because I had merge JS enabled on live and not on dev. Live was therefore looking at an old cached bunch of js. Disabling merge js on live highlighted that the problem did in fact occur on the live site.
This knowledge allowed me to debug further and I discovered that the problem lay with my jquery.hove.intent.js file. I updated this to the latest version and it solved everything! :)
Thanks all for your help and input though.