particle-iot-archived / particle-dev-app Goto Github PK

2 things:
Selecting device: doesn't list Electrons -- but you can type the names in.

When you click on the "compile & upload" button, unsaved source changes are not used. The similar Arduino app does an auto save before the compile.

When performing actions that alter the file structure (e.g. deleting files/folders, building and downloading a binary, ...) currently open tree branches won't get updated.
Only after collapsing and re-opening the branch the change gets visible.

In some cases this results in users suspecting their action was not performed (e.g. https://community.particle.io/t/particle-dev-breaks-after-first-compile/12997/14?u=scruffr) or when repeating actions like deleting files, you'll get a red error message that the respective file isn't available - which is confusing too.

When Serial.writeing (for debug-purposes) stuff that contains XML-code, like a SOAP request the Serial terminal will loose characters and just generally print garbage... It doesn't appear when using screen so I really assume there is some escaping missing.

I've been having this problem for a few weeks on two different machines (one Win10, one Win7) using the same Particle login. If there are any compile errors even a single missing semicolon Dev returns the error "compiler timed out or encountered an error" with no information about where or what the error is. If the code is clean it will compile and left you flash. This is not intermittent but is 100% of the time.

I have tried logging out and back in, no change. Reinstall Dev, no change. Install CLI log in and out of that and Dev, no change. How do i get all traces of Dev and user info off my machine? After i reinstall Dev it starts up and I'm still logged in and back in the last folder i was in. If i could clear this out maybe it would help.

Seems I'm not the only one having this problem:
https://community.particle.io/t/error-message-on-ide-dev/33599
https://community.particle.io/t/compiler-timed-out-or-encountered-an-error/30581/21

Particle Dev itself already works on Linux distributions running Atom but it would be nice to have a standalone version for those systems too.

This ticket is a follow up to Ubuntu Support #16

Unilke the web IDE, Particle Dev does not currently save before compiling or flashing, and it compiles the last saved version of the file. Particle Dev should automatically save (or request to save) firmware before compiling or flashing to reduce user confusion in firmware updates and debugging.

One day a week or so ago, all of a sudden, when I get an error, and display it and click on the line, you get a blank screen.

This is because the file its point to is within a folder called /workspace/. Everything else is correct after it, as in the file name and line/char numbers.

Where did this come from. The problem is that you cannot click on the line to go to the line number, you get a blank screen.

I did absolutely nothing to change the environment, same stuff I do 100 times a day every day.

Where did /workspace/ come from? What happened, as now the very handy error line "link" does not work.

Thanks

Marcus

I have been using Particle Desktop IDE excursive for over a year now. After making changes to a file, I just click Compile, as I know it will save it first save all changed files, and then compile. It always has done so.
But for a while now I noticed that it’s not doing this anymore. If i make a change to any file and click Compile it shows that it saved the file (by removing the blue dot on the file’s tab) and it does compile it. Yet when I flash it those changes are not applied to the running code. If i make changes and save first, then click build, and flash they do. I have tried this several times and its repeatable.

Right now, as far as I can tell, it's impossible for the same github repo to contain code for a library that works on Arduino hardware and Particle hardware, due to the fact that Particle IDE demands lib/firmware and Arduino demands lib/src for source location.

This is a huge problem. We won't get any traction for Particle support in official libraries from Arduino component vendors if they have to maintain a separate repo for Particle libraries. The process of porting libraries to Particle has to be simpler.

Please do something about this. It could be as simple as adding a config option to spark.json that specifies the source root, or as complicated as supporting the Arduino IDE 1.5 library format out of the box.

As it stands, we are ending up with shitty community forks of Arduino libraries that constantly fall out of sync with their upstream versions, or don't compile in the first place, because the community doesn't have the time to keep up with all the upstream changes.

I don't want to maintain my own fork for every component I use. I don't want to use the fork ported by someone who had 10 minutes to do in the middle of one of their projects. I want vendors to be able to easily port their Arduino libraries to Particle, and right now that is too hard.

I issued the command apm install particle-dev-complete and relaunched atom. The dependencies are installing, but at some point, the following error message is thrown and the installation fails. This problem occurs on Ubuntu 16.04 with atom 1.9.6 deb package.

Error installing particle-dev-complete dependencies
Error Installing particle-dev
> [email protected] install /tmp/apm-install-dir-11678-3357-1eni3if/node_modules/particle-dev/node_modules/serialport
> node-pre-gyp install --fallback-to-build --runtime=atom-shell
make: Entering directory '/tmp/apm-install-dir-11678-3357-1eni3if/node_modules/particle-dev/node_modules/serialport/build'
  CXX(target) Release/obj.target/serialport/src/serialport.o
serialport.target.mk:90: recipe for target 'Release/obj.target/serialport/src/serialport.o' failed
make: Leaving directory '/tmp/apm-install-dir-11678-3357-1eni3if/node_modules/particle-dev/node_modules/serialport/build'
Failed to execute 'node-gyp build --fallback-to-build --runtime=atom-shell --module=/tmp/apm-install-dir-11678-3357-1eni3if/node_modules/particle-dev/node_modules/serialport/build/Release/electron-v0.37-linux-x64/serialport.node --module_name=serialport --module_path=/tmp/apm-install-dir-11678-3357-1eni3if/node_modules/particle-dev/node_modules/serialport/build/Release/electron-v0.37-linux-x64' (1)
npm WARN deprecated [email protected]: Use particle-api-js instead
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN installMany node-pre-gyp was bundled with [email protected], but bundled package wasn't found in unpacked tree
npm WARN installMany node-pre-gyp-github was bundled with [email protected], but bundled package wasn't found in unpacked tree
npm WARN installMany nopt was bundled with [email protected], but bundled package wasn't found in unpacked tree
npm WARN installMany npmlog was bundled with [email protected], but bundled package wasn't found in unpacked tree
npm WARN installMany request was bundled with [email protected], but bundled package wasn't found in unpacked tree
npm WARN installMany semver was bundled with [email protected], but bundled package wasn't found in unpacked tree
npm WARN installMany tar was bundled with [email protected], but bundled package wasn't found in unpacked tree
npm WARN installMany tar-pack was bundled with [email protected], but bundled package wasn't found in unpacked tree
npm WARN installMany mkdirp was bundled with [email protected], but bundled package wasn't found in unpacked tree
npm WARN installMany rc was bundled with [email protected], but bundled package wasn't found in unpacked tree
npm WARN installMany rimraf was bundled with [email protected], but bundled package wasn't found in unpacked tree
npm WARN engine [email protected]: wanted: {"node":">=0.12.0","iojs":">=1.0.0"} (current: {"node":"0.10.40","npm":"2.13.3"})
In file included from ../src/serialport.h:5:0,
                 from ../src/serialport.cpp:3:
../node_modules/nan/nan.h:590:20: error: variable or field ‘AddGCEpilogueCallback’ declared void
       v8::Isolate::GCEpilogueCallback callback
                    ^
../node_modules/nan/nan.h:590:7: error: ‘GCEpilogueCallback’ is not a member of ‘v8::Isolate’
       v8::Isolate::GCEpilogueCallback callback
       ^
../node_modules/nan/nan.h:591:18: error: expected primary-expression before ‘gc_type_filter’
     , v8::GCType gc_type_filter = v8::kGCTypeAll) {
                  ^
../node_modules/nan/nan.h:596:20: error: variable or field ‘RemoveGCEpilogueCallback’ declared void
       v8::Isolate::GCEpilogueCallback callback) {
                    ^
../node_modules/nan/nan.h:596:7: error: ‘GCEpilogueCallback’ is not a member of ‘v8::Isolate’
       v8::Isolate::GCEpilogueCallback callback) {
       ^
../node_modules/nan/nan.h:601:20: error: variable or field ‘AddGCPrologueCallback’ declared void
       v8::Isolate::GCPrologueCallback callback
                    ^
../node_modules/nan/nan.h:601:7: error: ‘GCPrologueCallback’ is not a member of ‘v8::Isolate’
       v8::Isolate::GCPrologueCallback callback
       ^
../node_modules/nan/nan.h:602:18: error: expected primary-expression before ‘gc_type_filter’
     , v8::GCType gc_type_filter = v8::kGCTypeAll) {
                  ^
../node_modules/nan/nan.h:607:20: error: variable or field ‘RemoveGCPrologueCallback’ declared void
       v8::Isolate::GCPrologueCallback callback) {
                    ^
../node_modules/nan/nan.h:607:7: error: ‘GCPrologueCallback’ is not a member of ‘v8::Isolate’
       v8::Isolate::GCPrologueCallback callback) {
       ^
make: *** [Release/obj.target/serialport/src/serialport.o] Error 1
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/share/atom/resources/app/apm/node_modules/npm/node_modules/node-gyp/lib/build.js:269:23)
gyp ERR! stack     at ChildProcess.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:820:12)
gyp ERR! System Linux 4.4.0-31-generic
gyp ERR! command "node" "/usr/share/atom/resources/app/apm/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--runtime=atom-shell" "--module=/tmp/apm-install-dir-11678-3357-1eni3if/node_modules/particle-dev/node_modules/serialport/build/Release/electron-v0.37-linux-x64/serialport.node" "--module_name=serialport" "--module_path=/tmp/apm-install-dir-11678-3357-1eni3if/node_modules/particle-dev/node_modules/serialport/build/Release/electron-v0.37-linux-x64"
gyp ERR! cwd /tmp/apm-install-dir-11678-3357-1eni3if/node_modules/particle-dev/node_modules/serialport
gyp ERR! node -v v0.10.40
gyp ERR! node-gyp -v v2.0.2
gyp ERR! not ok 
node-pre-gyp ERR! build error 
node-pre-gyp ERR! stack Error: Failed to execute 'node-gyp build --fallback-to-build --runtime=atom-shell --module=/tmp/apm-install-dir-11678-3357-1eni3if/node_modules/particle-dev/node_modules/serialport/build/Release/electron-v0.37-linux-x64/serialport.node --module_name=serialport --module_path=/tmp/apm-install-dir-11678-3357-1eni3if/node_modules/particle-dev/node_modules/serialport/build/Release/electron-v0.37-linux-x64' (1)
node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/tmp/apm-install-dir-11678-3357-1eni3if/node_modules/particle-dev/node_modules/serialport/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:98:17)
node-pre-gyp ERR! stack     at maybeClose (child_process.js:766:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:833:5)
node-pre-gyp ERR! System Linux 4.4.0-31-generic
node-pre-gyp ERR! command "node" "/tmp/apm-install-dir-11678-3357-1eni3if/node_modules/particle-dev/node_modules/serialport/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build" "--runtime=atom-shell"
node-pre-gyp ERR! cwd /tmp/apm-install-dir-11678-3357-1eni3if/node_modules/particle-dev/node_modules/serialport
node-pre-gyp ERR! node -v v0.10.40
node-pre-gyp ERR! node-pre-gyp -v v0.6.17
node-pre-gyp ERR! not ok 
npm ERR! Linux 4.4.0-31-generic
npm ERR! argv "/usr/share/atom/resources/app/apm/bin/node" "/usr/share/atom/resources/app/apm/node_modules/npm/bin/npm-cli.js" "--globalconfig" "/home/francis/.atom/.apm/.apmrc" "--userconfig" "/home/francis/.atom/.apmrc" "install" "/tmp/d-11678-3357-1qu23ef/package.tgz" "--target=0.37.8" "--arch=x64" "--production"
npm ERR! node v0.10.40
npm ERR! npm  v2.13.3
npm ERR! code ELIFECYCLE
npm ERR! [email protected] install: `node-pre-gyp install --fallback-to-build --runtime=atom-shell`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] install script 'node-pre-gyp install --fallback-to-build --runtime=atom-shell'.
npm ERR! This is most likely a problem with the serialport package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-pre-gyp install --fallback-to-build --runtime=atom-shell
npm ERR! You can get their info via:
npm ERR!     npm owner ls serialport
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /tmp/apm-install-dir-11678-3357-1eni3if/npm-debug.log

OS:
Solus Linux (4.9.32-31.lts kernel)

What I Did:
apm install particle-dev-complete
started atom
clicked 'Start a new project' Named it and clicked okay.
Received error that '(...).runParticleCommand is not a function'

What I expected:
To start a new project

When I try to compile a project with some errors in the cloud by clicking the cloud icon, compiling works only once. Although I remove the error and click to recompile, nothing happens and the error prompt remains the same.

[sorry, this issue was already mentioned here, continued there]

[Enter steps to reproduce below:]

1. Start Particle Dev, it brings up last project by default, one .ino file open
2. Select device (photon)
3. Wait a few minutes
4. Does not seem to affect function, still complies and flashes. you just lose the left side of the window to error messages.

Atom Version: 1.8.0
System: Microsoft Windows 7 Professional
Thrown From: particle-dev package, v0.1.20

Stack Trace

Uncaught TypeError: Cannot read property 'error' of undefined

At C:\Users\mikesej\AppData\Local\particledev\app-1.8.0\resources\app.asar\node_modules\particle-dev\node_modules\spark\lib\spark.js:116

TypeError: Cannot read property 'error' of undefined
    at [object Object].Spark.normalizeErr (C:\Users\mikesej\AppData\Local\particledev\app-1.8.0\resources\app.asar\node_modules\particle-dev\node_modules\spark\lib\spark.js:116:19)
    at [object Object].<anonymous> (C:\Users\mikesej\AppData\Local\particledev\app-1.8.0\resources\app.asar\node_modules\particle-dev\node_modules\spark\lib\spark.js:151:16)
    at Request.self.callback (C:\Users\mikesej\AppData\Local\particledev\app-1.8.0\resources\app.asar\node_modules\nodegit\node_modules\request\request.js:200:22)
    at emitTwo (events.js:87:13)
    at Request.emit (events.js:172:7)
    at Request.<anonymous> (C:\Users\mikesej\AppData\Local\particledev\app-1.8.0\resources\app.asar\node_modules\nodegit\node_modules\request\request.js:1041:10)
    at emitOne (events.js:82:20)
    at Request.emit (events.js:169:7)
    at IncomingMessage.<anonymous> (C:\Users\mikesej\AppData\Local\particledev\app-1.8.0\resources\app.asar\node_modules\nodegit\node_modules\request\request.js:968:12)
    at emitNone (events.js:72:20)
    at IncomingMessage.emit (events.js:166:7)
    at endReadableNT (_stream_readable.js:905:12)
    at doNTCallback2 (node.js:465:9)
    at process._tickCallback (node.js:379:17)

Commands

  2x -0:44.5.0 particle-dev:append-menu (atom-workspace.workspace.scrollbars-visible-always.theme-monokai.theme-one-dark-ui)
     -0:44.2.0 particle-dev:update-login-status (atom-workspace.workspace.scrollbars-visible-always.theme-monokai.theme-one-dark-ui)
     -0:44.1.0 particle-dev:update-menu (atom-workspace.workspace.scrollbars-visible-always.theme-monokai.theme-one-dark-ui)
  2x -0:44 particle-dev:append-menu (atom-workspace.workspace.scrollbars-visible-always.theme-monokai.theme-one-dark-ui)
     -0:43.7.0 particle-dev:update-login-status (atom-workspace.workspace.scrollbars-visible-always.theme-monokai.theme-one-dark-ui)
     -0:43.6.0 particle-dev:update-menu (atom-workspace.workspace.scrollbars-visible-always.theme-monokai.theme-one-dark-ui)
     -0:43.5.0 particle-dev:append-menu (atom-workspace.workspace.scrollbars-visible-always.theme-monokai.theme-one-dark-ui)
     -0:40.5.0 particle-dev:select-device (atom-workspace.workspace.scrollbars-visible-always.theme-monokai.theme-one-dark-ui)
     -0:33.5.0 particle-dev:update-core-status (atom-workspace.workspace.scrollbars-visible-always.theme-monokai.theme-one-dark-ui)
     -0:33.4.0 particle-dev:update-menu (atom-workspace.workspace.scrollbars-visible-always.theme-monokai.theme-one-dark-ui)
     -0:33.4.0 particle-dev:append-menu (atom-workspace.workspace.scrollbars-visible-always.theme-monokai.theme-one-dark-ui)
     -0:31.1.0 particle-dev:compile-cloud (atom-text-editor.editor)
     -0:31 window:save-all (atom-workspace.workspace.scrollbars-visible-always.theme-monokai.theme-one-dark-ui)
  2x -0:31 particle-dev:update-compile-status (atom-workspace.workspace.scrollbars-visible-always.theme-monokai.theme-one-dark-ui)
     -0:29.5.0 particle-dev:core-status-updated (atom-workspace.workspace.scrollbars-visible-always.theme-monokai.theme-one-dark-ui)
     -0:19.4.0 particle-dev:flash-cloud (atom-text-editor.editor)

Config

{
  "core": {
    "projectHome": "C:\\Users\\mikesej\\Google Drive\\Particle\\projects",
    "themes": [
      "one-dark-ui",
      "monokai"
    ]
  }
}

Installed Packages

# User
No installed packages

# Dev
No dev packages

The current operation is not intuitive. When verifying or compile & flashing the current project should be saved. Reported by a Particle user through a support ticket.

I used the apm download command in my terminal, opened atom, and was prompted to install the dependencies. It is saying that it "Failed to install particle-dev-complete dependencies. These packages were not installed, check your console for more info"

Here's some context in the community: https://community.particle.io/t/multiple-folders-in-the-dev-ide-compile-errors-go-to-blank-file/18876

When in a project with subfolders. If there is a compiler error, the message box links to the correct line number but to a file that doesn't exist. It opens up an empty file.

This is how I and Joe4455 in the forum experienced it. It might not actually be a subfolder issue, but might be something else related to how the compiler handles files.

It appears that the installer is trying to create a directory that happens to be invalid.

2017-03-22 19:14:32> Program: Starting Squirrel Updater: --install . 2017-03-22 19:14:32> Program: Starting install, writing to C:\Users\Christopher Willard\AppData\Local\SquirrelTemp 2017-03-22 19:14:32> Program: About to install to: C:\Users\Christopher Willard\AppData\Local\particledev 2017-03-22 19:14:32> CheckForUpdateImpl: Failed to load local releases, starting from scratch: System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Users\Christopher Willard\AppData\Local\particledev\packages\RELEASES'. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share) at Squirrel.Utility.LoadLocalReleases(String localReleaseFile) at Squirrel.UpdateManager.CheckForUpdateImpl.<CheckForUpdate>d__3f.MoveNext() 2017-03-22 19:14:32> CheckForUpdateImpl: Reading RELEASES file from C:\Users\Christopher Willard\AppData\Local\SquirrelTemp 2017-03-22 19:14:32> CheckForUpdateImpl: First run or local directory is corrupt, starting from scratch 2017-03-22 19:14:32> ApplyReleasesImpl: Writing files to app directory: C:\Users\Christopher Willard\AppData\Local\particledev\app-1.8.0 2017-03-22 19:14:57> IEnableLogger: Failed to install package to app dir: System.IO.PathTooLongException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters. at System.IO.PathHelper.GetFullPathName() at System.IO.Path.LegacyNormalizePath(String path, Boolean fullCheck, Int32 maxPathLength, Boolean expandShortPaths) at System.IO.Path.NormalizePath(String path, Boolean fullCheck, Int32 maxPathLength, Boolean expandShortPaths) at System.IO.Path.GetFullPathInternal(String path) at ICSharpCode.SharpZipLib.Zip.FastZip.ExtractEntry(ZipEntry entry) at ICSharpCode.SharpZipLib.Zip.FastZip.ExtractZip(Stream inputStream, String targetDirectory, Overwrite overwrite, ConfirmOverwriteDelegate confirmDelegate, String fileFilter, String directoryFilter, Boolean restoreDateTime, Boolean isStreamOwner) at Squirrel.UpdateManager.ApplyReleasesImpl.<>c__DisplayClassb4.<<installPackageToAppDir>b__ad>d__bd.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Squirrel.Utility.<LogIfThrows>d__501.MoveNext()
2017-03-22 19:14:57> Unhandled exception: System.AggregateException: One or more errors occurred. ---> System.IO.PathTooLongException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
at System.IO.PathHelper.GetFullPathName()
at System.IO.Path.LegacyNormalizePath(String path, Boolean fullCheck, Int32 maxPathLength, Boolean expandShortPaths)
at System.IO.Path.NormalizePath(String path, Boolean fullCheck, Int32 maxPathLength, Boolean expandShortPaths)
at System.IO.Path.GetFullPathInternal(String path)
at ICSharpCode.SharpZipLib.Zip.FastZip.ExtractEntry(ZipEntry entry)
at ICSharpCode.SharpZipLib.Zip.FastZip.ExtractZip(Stream inputStream, String targetDirectory, Overwrite overwrite, ConfirmOverwriteDelegate confirmDelegate, String fileFilter, String directoryFilter, Boolean restoreDateTime, Boolean isStreamOwner)
at Squirrel.UpdateManager.ApplyReleasesImpl.<>c__DisplayClassb4.<b__ad>d__bd.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
`

https://atom.io/packages/clang-format

Hi
I have installed the latest release on Windows 8.1 and 10.
Whenever I open Dev for the first time and click compile, it works fine. All subsequent attempts to do any spark-related tasks don't seem to work at all. e.g. clicking compile again has no effect. Clicking "select device" has no effect. etc.

No error messages are shown anywhere (at least not that I can see). If I close Dev and reopen it again, everything seems to work again. Once.

Noted: https://community.particle.io/t/particle-dev-freezes-a-few-minutes-after-you-change-the-theme/16287