-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build the start script path correctly on Windows #685
Conversation
@jendib thanks for taking the initiative to fix this. Could you explain why the |
Yes |
@johnnyman727 this is correct, for the same reason as: 50732a7 I'll spend some time today checking for anymore mistakes like this @jendib two things:
|
Signed-off-by: Rick Waldron <waldron.rick@gmail.com>
@jendib and I discussed a strategy for tests, all that remains now:
Once those are complete, and this PR is green, then it's +1 to merge |
Assert that shellScriptPath is not normalized for the local environment.
It's merged and I signed the CLA, thanks @rwaldron ! |
Could somebody make a new relaease containing the change? |
@@ -1035,7 +1035,7 @@ actions.pushScript = function(t, script, opts) { | |||
actions.writeToFile = function(t, entryPoint) { | |||
return new Promise(function(resolve, reject) { | |||
// Path of the script to run a Node project | |||
var shellScriptPath = path.join(Tessel.REMOTE_PUSH_PATH, PUSH_START_SCRIPT_NAME); | |||
var shellScriptPath = Tessel.REMOTE_PUSH_PATH + PUSH_START_SCRIPT_NAME; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You could change this into path.posix.join(...)
instead
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will do, thanks!
Linked to https://forums.tessel.io/t/tessel-2-does-not-start-my-application-with-push/2329/3