I hate to say it, and Iām sure thereās got to be a better fix, but since your work is being blocked, unless anyone else here has a better suggestion, you should probably go ahead and roll back last nightās Windows update.
For anyone following along ā we jumped on a quick video chat and @jackpotās machine is resolving api.particle.io to strange IP addresses, not our actual API load balancers. I donāt know what else to suggest. Maybe the router has old IP addresses cached?
@zachary
I have been doing a little hunting myself and I have found that in fact the update that I thought was installed last night, actually failed. Your thoughts on that please?
Thanks
Caveat: I donāt use Windows! Take my advice with a grain of salt!
That said, system updates (for every OS) often fix tons of small bugs as well as important security issues. Theyāre generally a good thing. Iād recommend updating.
The whole Windows update thing seems probably unrelated to this DNS issueā¦ ĀÆ\_(ć)_/ĀÆ
Iām going to mark this thread solved since thereās no problem with systems.
Ok thanks. I guess I will perform the update, reset my router and hope for the best. I guess if that doesnt work, Ill have to move so I can have a different IP
To all
First of all, thanks for all the help. Amazingly enough, everything is back working. Chalk it up to one of those I have no idea why it quit or why it started working. I am just happy it is now working.
The problem with compiling 0.6.0-rc.2 is back again.... was working okay about one hour ago and yesterday evening.
Can compile under 0.5.2, but not 0.6.0-rc.2.
This looks to be the compile time issue:
ENOENT: no such file or directory, open '/workspace/project.properties'
{ Error: ENOENT: no such file or directory, open '/workspace/project.properties'
at Error (native)
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: '/workspace/project.properties' } [ 'Error: ENOENT: no such file or directory, open '/workspace/project.properties'',
' at Error (native)' ]
fatal: destination path 'firmware' already exists and is not an empty directory.
m
@kennethlimcp - great to hear from you. I didnāt capture the error log from the first incident some days ago, but it looks very much like the same issue.