Gulp getUpstream throws error

[newswim]

Greetings! Following some instructions I received from @splendido; trying gulp getUpstream --tag v2.4.3 the following error occurs:

[15:12:33] Using gulpfile ~/Documents/dev/test_cases/jspdf-core-wrapper/gulpfile.js
[15:12:33] Starting 'getUpstream'...
[15:12:33] Finished 'getUpstream' after 3.67 ms
cloning https://github.com/MrRio/jsPDF.git
[15:12:38] Submodule 'libs/Blob.js' (https://github.com/eligrey/Blob.js.git) registered for path 'libs/Blob.js'
Submodule 'libs/FileSaver.js' (https://github.com/eligrey/FileSaver.js.git) registered for path 'libs/FileSaver.js'
Submodule 'libs/adler32cs.js' (https://github.com/chick307/adler32cs.js.git) registered for path 'libs/adler32cs.js'
Submodule path 'libs/Blob.js': checked out 'b0141af46b608e03942fd5feb6b961dfb6f8018c'
Submodule path 'libs/FileSaver.js': checked out 'babc6d9d8fc60e667ddeafb7a7d3b844ce761ab5'
Submodule path 'libs/adler32cs.js': checked out 'c6576b4ed91b4216973bf85d8478a49970934515'
 Cloning into 'upstream'...
Cloning into 'libs/Blob.js'...
Cloning into 'libs/FileSaver.js'...
Cloning into 'libs/adler32cs.js'...

checking out v2.4.3
/Users/dm/Documents/dev/test_cases/jspdf-core-wrapper/gulpfile.js:28
        if (err) throw err;
                       ^
Error: Command failed: /bin/sh -c git checkout   'v2.4.3'
error: pathspec 'v2.4.3' did not match any file(s) known to git.

    at ChildProcess.exithandler (child_process.js:751:12)
    at ChildProcess.emit (events.js:110:17)
    at maybeClose (child_process.js:1015:16)
    at Socket.<anonymous> (child_process.js:1183:11)
    at Socket.emit (events.js:107:17)
    at Pipe.close (net.js:485:12)

Do I need to specify a different tag?

[splendido]

error: pathspec 'v2.4.3' did not match any file(s) known to git. means v2.4.3 is not recognized as a tag or anything else...

Lets have a look at the releases page and pick a valid name.
I'm sorry I used an invalid name, but I guess it was just to give an example...

[newswim]

Thanks Luca!

Fetching v1.0.272 worked, as did gulp updateVersion and updateRelease 👍,
however, running gulp test throws the following error:

gulp test
[15:41:00] Using gulpfile ~/Documents/dev/test_cases/my_fork_jspdf-core-wrapper/jspdf-core-wrapper/gulpfile.js
[15:41:00] Starting 'test'...
[15:41:00] Starting 'setuptests'...
[15:41:00] Finished 'test' after 8.41 ms
[gulp] Downloading https://raw.github.com/arunoda/travis-ci-meteor-packages/master/start_test.js... Done
[gulp] Downloading https://raw.github.com/arunoda/travis-ci-meteor-packages/master/phantom_runner.js... Done
[15:41:02] Finished 'setuptests' after 1.54 s
[15:41:02] Starting 'runtests'...
[15:41:02] Finished 'runtests' after 5.22 ms
I20150821-15:41:08.563(-5)? test-in-console listening
starting testing...
events.js:85
      throw er; // Unhandled 'error' event
            ^
Error: spawn phantomjs ENOENT

my linter caught a few errors in start_test.js (line 31 and 40).

Had I permission to meteor publish the package, I believe it would work -- great job! Can't stress enough how important I think this service will be.

[splendido]

do you have phantomjs installed on your system?
You need a system-wide installation because the one you might have installed with npm is not enough.

[splendido]

@chip are you fine with publishing this new version?

Edit: it seems that the published version is already at v1.1.135! Lets have a look on Atmosphere

[splendido]

@newswim can you please confirm we're already at the newest version?

[newswim]

@splendido -- yes no need to publish yet, looks like there will be an upcoming refactor soon though. Good test for autopublish.

Another strange error after installing phantomjs -->

Daniels-MBP:jspdf-core-wrapper dm$ gulp test
[18:52:43] Using gulpfile ~/Documents/dev/test_cases/my_fork_jspdf-core-wrapper/jspdf-core-wrapper/gulpfile.js
[18:52:43] Starting 'test'...
[18:52:43] Starting 'setuptests'...
[18:52:43] Finished 'test' after 8.15 ms
[gulp] Downloading https://raw.github.com/arunoda/travis-ci-meteor-packages/master/start_test.js... Done
[gulp] Downloading https://raw.github.com/arunoda/travis-ci-meteor-packages/master/phantom_runner.js... Done
[18:52:44] Finished 'setuptests' after 983 ms
[18:52:44] Starting 'runtests'...
[18:52:44] Finished 'runtests' after 5.29 ms
Can't listen on port 10015. Perhaps another Meteor is running?

Running two copies of Meteor in the same application directory
will not work. If something else is using port 10015, you can
specify an alternative port with --port <port>.
starting testing...
meteor exited with code 254

[newswim]

note: no other instance of Meteor is running.

.. I think there may be a problem within start_test.js.