particle-iot-archived / particle-dev-app

Particle Dev: a professional, hackable IDE for Particle, based on Github's Atom https://www.particle.io/dev
25 stars 5 forks source link

Particle Dev not showing proper line/file for errors #17

Closed bluerockpr closed 7 years ago

bluerockpr commented 7 years ago

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

suda commented 7 years ago

Hi Marcus, it's possible Particle Dev App automatically updated introducing this bug. Can you share the app that causes this issue?

jmonster commented 7 years ago

Sorry for being a me-too but I've experienced this since issue since I first started using Particle ~2 months ago. There's nothing special about my setup -- so you should be able to recreate it pretty easily? I'm running macOS and storing my project in the default ~/Particle/Projects folder.

In particular, it not only has workspace prefixed but also insists on referring to my files as .ino when I have them saved as .cpp.

bluerockpr commented 7 years ago

Guys,

I am a Particle developer, but I am not sure what your talking about, are you addressing this to the right person?

On Apr 18, 2017, at 8:49 AM, Wojtek Siudzinski notifications@github.com wrote:

Hi Marcus, it's possible Particle Dev App automatically updated introducing this bug. Can you share the app that causes this issue?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/spark/particle-dev-app/issues/17#issuecomment-294888221, or mute the thread https://github.com/notifications/unsubscribe-auth/AaLqx7QVW5M8P1aSDgxJYXZtT-HNp5O0ks5rxNt_gaJpZM4M9Ryk.

bluerockpr commented 7 years ago

Guys,

I am a Particle developer, but I am not sure what your talking about, are you addressing this to the right person?

On May 31, 2017, at 2:41 PM, Johnny Domino notifications@github.com wrote:

Sorry for being a me-too but I've experienced this since issue since I first started using Particle ~2 months ago. There's nothing special about my setup -- so you should be able to recreate it pretty easily? I'm running macOS and storing my project in the default ~/Particle/Projects folder.

In particular, it not only has workspace prefixed but also insists on referring to my files as .ino when I have them saved as .cpp.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/spark/particle-dev-app/issues/17#issuecomment-305326039, or mute the thread https://github.com/notifications/unsubscribe-auth/AaLqxyjm5BAIZQZiNO9gMe17gi8Atb3kks5r_d6ZgaJpZM4M9Ryk.

suda commented 7 years ago

We introduced a patch that removes the /workspace from the paths to the cloud compiler. @bluerockpr / @jmonster are you still experiencing this issue?

bluerockpr commented 7 years ago

Yes, how do I get the patch? Thanks

On Jul 6, 2017, at 11:16 AM, Wojtek Siudzinski notifications@github.com wrote:

We introduced a patch that removes the /workspace from the paths to the cloud compiler. @bluerockpr https://github.com/bluerockpr / @jmonster https://github.com/jmonster are you still experiencing this issue?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/spark/particle-dev-app/issues/17#issuecomment-313477125, or mute the thread https://github.com/notifications/unsubscribe-auth/AaLqxyJGy-Ak4c4d3EZcr4kRqPbrZx_Kks5sLSR9gaJpZM4M9Ryk.

suda commented 7 years ago

The patch was applied server side. It is possible that the current Particle Dev App doesn't enable it yet. We're going to release a new version this sprint which should make it work. I'll keep you posted!

bluerockpr commented 7 years ago

Thank you very much. Appreciated!

Marcus

On Jul 6, 2017, at 11:22 AM, Wojtek Siudzinski notifications@github.com wrote:

The patch was applied server side. It is possible that the current Particle Dev App doesn't enable it yet. We're going to release a new version this sprint which should make it work. I'll keep you posted!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/spark/particle-dev-app/issues/17#issuecomment-313478806, or mute the thread https://github.com/notifications/unsubscribe-auth/AaLqx_5zYepoxFo_JTH-uc9cy4Dw_7jHks5sLSXwgaJpZM4M9Ryk.

suda commented 7 years ago

Hi Marcus! We just released Particle Dev App 1.18.0 ( https://github.com/spark/particle-dev-app/releases/tag/v1.18.0 ) with the patch. Feel free to grab it!