The cloudup-cli's discuss from automattic

Fix sporadic error

Happens occasionally...

  Error: Offset is out of bounds
      at Object.fs.readSync (fs.js:476:19)
      at sync (/Users/nrajlich/cloudup-cli/node_modules/head/index.js:38:14)
      at module.exports (/Users/nrajlich/cloudup-cli/node_modules/head/index.js:19:10)
      at textual (/Users/nrajlich/cloudup-cli/bin/up:153:13)
      at Socket.files.forEach.ind (/Users/nrajlich/cloudup-cli/bin/up:105:11)
      at Socket.EventEmitter.emit (events.js:117:20)
      at _stream_readable.js:920:16
      at process._tickCallback (node.js:415:13)

Quiting isn't intuitive when interactive

The way to quit the interactive interface isn't clear.

Either adding "q" as shortcut to quit, either explain "ctrl+c" is the way to quit.

stdin with a type flag

git diff master | up -t Diffs -f superagent.diff

update to use api

also giving us a good idea if the level of api I've implemented is sufficient

Consolidation of early bug reports

Might be fixed in @TooTallNate's latest commit, but thought I'd consolidate some of the early feedback

Report 1:

screen shots: https://cloudup.com/couO8FMKRzC

Report 2:

Report 3:

screen shot: https://cloudup.com/cAwyGEFUT6Y

I'll add others as I encounter them...

support dirs

? maybe... could be bad haha, unless we have the recursion limit, we should at least ignore dirs so we dont get EISDIR if you do $ up *

Reject connection if node version < v0.6

per @TooTallNate request

stream operations

low priority

view collections
update
remove

Allow publishing of a new project to "up"?

Hello, if you don't mind I'd like to publish a different unrelated project to "up" in NPM. I already have access to the NPM package but I thought I'd check in, looks as if Cloudup is basically a dead project but let me know if there are any plans to maintain it.

cheers!

500 error when posting

When I'm using up FILE LOCATION I am seeing a 500 bad gateway error:

up /home/Desktop/Screenshot_14-04-2016-15:53:43.png
    Screenshot_14-04-201… : 0%
  Error: 502: <html>
  <head><title>502 Bad Gateway</title></head>
  <body bgcolor="white">
  <center><h1>502 Bad Gateway</h1></center>
  <hr><center>nginx/1.5.13</center>
  </body>
  </html>
   (POST /1/streams)
      at module.exports (/usr/local/lib/node_modules/up/node_modules/cloudup-client/lib/error.js:13:10)
      at /usr/local/lib/node_modules/up/node_modules/cloudup-client/lib/stream.js:335:32
      at Request.callback (/usr/local/lib/node_modules/up/node_modules/superagent/lib/node/index.js:628:30)
      at Request.<anonymous> (/usr/local/lib/node_modules/up/node_modules/superagent/lib/node/index.js:131:10)
      at emitOne (events.js:90:13)
      at Request.emit (events.js:182:7)
      at IncomingMessage.<anonymous> (/usr/local/lib/node_modules/up/node_modules/superagent/lib/node/index.js:773:12)
      at emitNone (events.js:85:20)
      at IncomingMessage.emit (events.js:179:7)
      at endReadableNT (_stream_readable.js:906:12)

Slow response after upload

I tried to upload a file and it has been successfully uploaded and also it returned me the links for the file and the stream url. But, it takes so much time to return exit.

output item specific links

Error: Cannot switch to old mode now.

I get Error: Cannot switch to old mode now. when I try running up.

I tried both installing from npm via npm -g install up and from github. Same result.

OSX 10.8.5, node 0.10.20, all npm packages just upgraded.

when ~/.cloudup.json does not exist, prompt for input

list all streams

not just first 30 or whatever the pagination is at

"c" to copy stream or item link in interactive list

add seen stream listing support

add stream item listing support

$ up streams with --interactive or something might be nice

stream stdin through our app for content-length

to allow for larger stdin items or require --length

Error: EISDIR

From user:

Hi!

Adviced by rauchg I'm sending a bug I just found with the recently released up tool.

I found that when running up * as it's shown on the blog post gif... and there is a sub-directory at the running path, then the process crashes with the following error:

Error: EISDIR, read

And no file us uploaded.

I was guessing that when a sub directory is present, up would zip it into a .tar or .zip file and upload it.

Or at least say that directories cannot be upload but continue uploading the rest of the files.

I'm running [email protected] with [email protected] at a Mac OS X 10.6.8 via native terminal Darwin.

I wouldn't mind to provide with any extra information you require to debug this.

Salút!

Homebrew complains about `up-config`

I have node/npm installed via homebrew on a Mac as well as up(1).

When I run brew doctor to ensure that things are silky smooth, it complains:

Warning: "config" scripts exist outside your system or Homebrew directories.
`./configure` scripts often look for *-config scripts to determine if
software packages are installed, and what additional flags to use when
compiling and linking.

Having additional scripts in your path can confuse software installed via
Homebrew if the config script overrides a system or Homebrew provided
script of the same name. We found the following "config" scripts:

    /usr/local/share/npm/bin/up-config

Be nice to use a different filename if possible.

output collection asap

add user-agent

up <version> <uname> or similar

Rename ‘up’ to ‘cloudup’ and update install instructions

The npm package name up has been assumed by apex/up, thus cloudup-cli can no longer be installed with npm install -g up. I recommend cloudup-cli be renamed to cloudup so it can be installed with npm install -g cloudup and can be installed in parallel with the new up.

In the meantime, cloudup-cli can be installed by referencing the github repo directly, like this:

npm install -g Automattic/cloudup-cli

display aggregate progress only for items > rows

nicer error reporting

for anticipated errors like 401s etc

Don't clear the screen when uploading stuff

Just move the cursor relative to the number of items being processed, rather than an absolute ANSI goto.

add interactive stream selection for input

maybe, or at least grep on title for things like $ up *.png --stream Victoria etc

FYI - user asking for a more permanent url for mac app

Question from user: @cloudup Is there a more permanent URL for the Mac app, so that it works on Homebrew?

https://twitter.com/hanxue/status/395504472517922817

variable sprintf width

not sure if the node lib supports this or not but hopefully

Error 400

Whenever I try to sign in I get this error:

~ up config

  Cloudup up(1) one-time configuration requires your
  password, however it is transfered via https
  and is not stored locally. Subsequent operations
  use the auth token generated from this process.

  Username: mtello17
  Password: ********

/usr/lib/node_modules/cloudup/bin/up-config:38
      if (err) throw err;
                     ^
Error: 400: {"error":"invalid_grant","error_description":"invalid user credentials"} (POST /oauth/access_token)
    at module.exports (/usr/lib/node_modules/cloudup/node_modules/cloudup-client/lib/error.js:13:10)
    at /usr/lib/node_modules/cloudup/node_modules/cloudup-client/lib/client.js:72:30
    at Request.callback (/usr/lib/node_modules/cloudup/node_modules/cloudup-client/node_modules/superagent/lib/node/index.js:628:30)
    at Request.<anonymous> (/usr/lib/node_modules/cloudup/node_modules/cloudup-client/node_modules/superagent/lib/node/index.js:131:10)
    at Request.EventEmitter.emit (events.js:95:17)
    at IncomingMessage.<anonymous> (/usr/lib/node_modules/cloudup/node_modules/cloudup-client/node_modules/superagent/lib/node/index.js:773:12)
    at IncomingMessage.EventEmitter.emit (events.js:117:20)
    at _stream_readable.js:919:16
    at process._tickCallback (node.js:419:13)

[q@x/0 ~] up Screen\ Shot*.png
    Screen Shot 2017-07-… : 0%
    Screen Shot 2017-07-… : 0%
    Screen Shot 2017-07-… : 0%
                   stream : https://cloudup.com/clNeGiVyxFe
(node:93782) [DEP0013] DeprecationWarning: Calling an asynchronous function without callback is deprecated.
(node:93782) [DEP0013] DeprecationWarning: Calling an asynchronous function without callback is deprecated.
    Screen Shot 2017-07-… : https://cloudup.com/iU3vFBfJ85Ohronous function without callback is deprecated.
    Screen Shot 2017-07-… : https://cloudup.com/iv7ek8HCud3hronous function without callback is deprecated.
    Screen Shot 2017-07-… : https://cloudup.com/iC6aOpZ98phhronous function without callback is deprecated.
(node:93782) [DEP0013] DeprecationWarning: Calling an asynchronous function without callback is deprecated.

add json output

auto-detect stdin

so they don't become blobs, things like:

text
diffs
code snippets

Status?

Is this abandonware? It looks like deprecation warnings are printed on the command-line when I use it now.

automattic / cloudup-cli Goto Github PK

cloudup-cli's Issues

Recommend Projects

Recommend Topics

Recommend Org