npm-publish error

gistfile1.txt

0 info it worked if it ends with ok
1 verbose cli [ '/Users/bmc/local/node@v0.10.33/bin/node',
1 verbose cli   '/Users/bmc/local/node/bin/npm',
1 verbose cli   'publish' ]
2 info using npm@1.4.28
3 info using node@v0.10.33
4 verbose publish [ '.' ]
5 verbose cache add [ '.', null ]
6 verbose cache add name=undefined spec="." args=[".",null]
7 verbose parsed url { protocol: null,
7 verbose parsed url   slashes: null,
7 verbose parsed url   auth: null,
7 verbose parsed url   host: null,
7 verbose parsed url   port: null,
7 verbose parsed url   hostname: null,
7 verbose parsed url   hash: null,
7 verbose parsed url   search: null,
7 verbose parsed url   query: null,
7 verbose parsed url   pathname: '.',
7 verbose parsed url   path: '.',
7 verbose parsed url   href: '.' }
8 silly lockFile 3a52ce78- .
9 verbose lock . /Users/bmc/.npm/3a52ce78-.lock
10 verbose tar pack [ '/Users/bmc/.npm/pg/4.1.1/package.tgz', '.' ]
11 verbose tarball /Users/bmc/.npm/pg/4.1.1/package.tgz
12 verbose folder .
13 info prepublish pg@4.1.1
14 silly lockFile 1f1177db-tar tar://.
15 verbose lock tar://. /Users/bmc/.npm/1f1177db-tar.lock
16 silly lockFile f871f6fc-ers-bmc-npm-pg-4-1-1-package-tgz tar:///Users/bmc/.npm/pg/4.1.1/package.tgz
17 verbose lock tar:///Users/bmc/.npm/pg/4.1.1/package.tgz /Users/bmc/.npm/f871f6fc-ers-bmc-npm-pg-4-1-1-package-tgz.lock
18 silly lockFile 1f1177db-tar tar://.
19 silly lockFile 1f1177db-tar tar://.
20 silly lockFile f871f6fc-ers-bmc-npm-pg-4-1-1-package-tgz tar:///Users/bmc/.npm/pg/4.1.1/package.tgz
21 silly lockFile f871f6fc-ers-bmc-npm-pg-4-1-1-package-tgz tar:///Users/bmc/.npm/pg/4.1.1/package.tgz
22 silly lockFile a50ccd7a-Users-bmc-npm-pg-4-1-1-package /Users/bmc/.npm/pg/4.1.1/package
23 verbose lock /Users/bmc/.npm/pg/4.1.1/package /Users/bmc/.npm/a50ccd7a-Users-bmc-npm-pg-4-1-1-package.lock
24 silly lockFile a50ccd7a-Users-bmc-npm-pg-4-1-1-package /Users/bmc/.npm/pg/4.1.1/package
25 silly lockFile a50ccd7a-Users-bmc-npm-pg-4-1-1-package /Users/bmc/.npm/pg/4.1.1/package
26 silly lockFile 3a52ce78- .
27 silly lockFile 3a52ce78- .
28 silly publish { name: 'pg',
28 silly publish   version: '4.1.1',
28 silly publish   description: 'PostgreSQL client - pure javascript & libpq with the same API',
28 silly publish   keywords: [ 'postgres', 'pg', 'libpq', 'postgre', 'database', 'rdbms' ],
28 silly publish   homepage: 'http://github.com/brianc/node-postgres',
28 silly publish   repository:
28 silly publish    { type: 'git',
28 silly publish      url: 'git://github.com/brianc/node-postgres.git' },
28 silly publish   author: { name: 'Brian Carlson', email: 'brian.m.carlson@gmail.com' },
28 silly publish   main: './lib',
28 silly publish   dependencies:
28 silly publish    { 'buffer-writer': '1.0.0',
28 silly publish      'generic-pool': '2.1.1',
28 silly publish      'packet-reader': '0.2.0',
28 silly publish      'pg-connection-string': '0.1.3',
28 silly publish      'pg-types': '1.6.0',
28 silly publish      pgpass: '0.0.3',
28 silly publish      semver: '^4.1.0' },
28 silly publish   devDependencies: { async: '0.9.0', jshint: '2.5.2', 'pg-copy-streams': '0.3.0' },
28 silly publish   minNativeVersion: '1.7.0',
28 silly publish   scripts:
28 silly publish    { changelog: 'npm i github-changes && ./node_modules/.bin/github-changes -o brianc -r node-postgres -d pulls -a -v',
28 silly publish      test: 'make test-all connectionString=postgres://postgres@localhost:5432/postgres' },
28 silly publish   engines: { node: '>= 0.8.0' },
28 silly publish   readme: '#node-postgres\n\n[![Build Status](https://secure.travis-ci.org/brianc/node-postgres.png?branch=master)](http://travis-ci.org/brianc/node-postgres)\n\nPostgreSQL client for node.js.  Pure JavaScript and optional native libpq bindings.\n\n## Install\n\n```sh\n$ npm install pg\n```\n\n\n## Examples\n\n### Client pooling\n\nGenerally you will access the PostgreSQL server through a pool of clients.  A client takes a non-trivial amount of time to establish a new connection. A client also consumes a non-trivial amount of resources on the PostgreSQL server - not something you want to do on every http request. Good news: node-postgres ships with built in client pooling.\n\n```javascript\nvar pg = require(\'pg\');\nvar conString = "postgres://username:password@localhost/database";\n\npg.connect(conString, function(err, client, done) {\n  if(err) {\n    return console.error(\'error fetching client from pool\', err);\n  }\n  client.query(\'SELECT $1::int AS number\', [\'1\'], function(err, result) {\n    //call `done()` to release the client back to the pool\n    done();\n    \n    if(err) {\n      return console.error(\'error running query\', err);\n    }\n    console.log(result.rows[0].number);\n    //output: 1\n  });\n});\n```\n\n[Check this out for the get up and running quickly example](https://github.com/brianc/node-postgres/wiki/Example)\n\n### Client instance\n\nSometimes you may not want to use a pool of connections.  You can easily connect a single client to a postgres instance, run some queries, and disconnect.\n\n```javascript\nvar pg = require(\'pg\');\n\nvar conString = "postgres://username:password@localhost/database";\n\nvar client = new pg.Client(conString);\nclient.connect(function(err) {\n  if(err) {\n    return console.error(\'could not connect to postgres\', err);\n  }\n  client.query(\'SELECT NOW() AS "theTime"\', function(err, result) {\n    if(err) {\n      return console.error(\'error running query\', err);\n    }\n    console.log(result.rows[0].theTime);\n    //output: Tue Jan 15 2013 19:12:47 GMT-600 (CST)\n    client.end();\n  });\n});\n\n```\n\n## [More Documentation](https://github.com/brianc/node-postgres/wiki)\n\n## Native Bindings\n\nTo install the [native bindings](https://github.com/brianc/node-pg-native.git):\n\n```sh\n$ npm install pg pg-native\n```\n\n\nnode-postgres contains a pure JavaScript protocol implementation which is quite fast, but you can optionally use native bindings for a 20-30% increase in parsing speed. Both versions are adequate for production workloads.\n\nTo use the native bindings, first install [pg-native](https://github.com/brianc/node-pg-native.git).  Once pg-native is installed, simply replace `require(\'pg\')` with `require(\'pg\').native`.\n\nnode-postgres abstracts over the pg-native module to provide exactly the same interface as the pure JavaScript version. __No other code changes are required__.  If you find yourself having to change code other than the require statement when switching from `require(\'pg\')` to `require(\'pg\').native` please report an issue.\n\n## Features\n\n* pure JavaScript client and native libpq bindings share _the same api_\n* optional connection pooling\n* extensible js<->postgresql data-type coercion\n* supported PostgreSQL features\n  * parameterized queries\n  * named statements with query plan caching\n  * async notifications with `LISTEN/NOTIFY`\n  * bulk import & export with `COPY TO/COPY FROM`\n\n## Contributing\n\n__We love contributions!__\n\nIf you need help getting the tests running locally or have any questions about the code when working on a patch please feel free to email me or gchat me.\n\nI will __happily__ accept your pull request if it:\n- __has tests__\n- looks reasonable\n- does not break backwards compatibility\n\nInformation about the testing processes is in the [wiki](https://github.com/brianc/node-postgres/wiki/Testing).\n\nOpen source belongs to all of us, and we\'re all invited to participate!\n\n## Support\n\nIf at all possible when you open an issue please provide\n- version of node\n- version of postgres\n- smallest possible snippet of code to reproduce the problem\n\nUsually I\'ll pop the code into the repo as a test.  Hopefully the test fails.  Then I make the test pass.  Then everyone\'s happy!\n\nIf you need help or run into _any_ issues getting node-postgres to work on your system please report a bug or contact me directly.  I am usually available via google-talk at my github account public email address.\n\nI usually tweet about any important status updates or changes to node-postgres on twitter.  \nFollow me [@briancarlson](https://twitter.com/briancarlson) to keep up to date.\n\n\n## Extras\n\nnode-postgres is by design pretty light on abstractions.  These are some handy modules we\'ve been using over the years to complete the picture:\n\n- [brianc/node-pg-native](https://github.com/brianc/node-pg-native) - Simple interface abstraction on top of [libpq](https://github.com/brianc/node-libpq)\n- [brianc/node-pg-query-stream](https://github.com/brianc/node-pg-query-stream) - Query results from node-postgres as a readable (object) stream\n- [brianc/node-pg-cursor](https://github.com/brianc/node-pg-cursor) - Query cursor extension for node-postgres\n- [brianc/node-pg-copy-streams](https://github.com/brianc/node-pg-copy-streams) - COPY FROM / COPY TO for node-postgres. Stream from one database to another, and stuff.\n- [brianc/node-postgres-pure](https://github.com/brianc/node-postgres-pure) - node-postgres without any of the C/C++ stuff\n- [brianc/node-pg-types](https://github.com/brianc/node-pg-types) - Type parsing for node-postgres\n- [Suor/pg-bricks](https://github.com/Suor/pg-bricks) - A higher level wrapper around node-postgres to handle connection settings, sql generation, transactions and ease data access.\n- [grncdr/node-any-db](https://github.com/grncdr/node-any-db) - Thin and less-opinionated database abstraction layer for node.\n- [brianc/node-sql](https://github.com/brianc/node-sql) - SQL generation for node.js\n- [hiddentao/suqel](https://hiddentao.github.io/squel/) - SQL query string builder for Javascript\n- [CSNW/sql-bricks](https://github.com/CSNW/sql-bricks) - Transparent, Schemaless SQL Generation\n- [datalanche/node-pg-format](https://github.com/datalanche/node-pg-format) - Safely and easily create dynamic SQL queries with this Node implementation of [PostgreSQL format()](http://www.postgresql.org/docs/9.3/static/functions-string.html#FUNCTIONS-STRING-FORMAT).\n- [iceddev/pg-transact](https://github.com/iceddev/pg-transact) - A nicer API on node-postgres transactions\n- [sehrope/node-pg-db](https://github.com/sehrope/node-pg-db) - Simpler interface, named parameter support, transaction management and event hooks.\n\n## License\n\nCopyright (c) 2010-2014 Brian Carlson (brian.m.carlson@gmail.com)\n\n Permission is hereby granted, free of charge, to any person obtaining a copy\n of this software and associated documentation files (the "Software"), to deal\n in the Software without restriction, including without limitation the rights\n to use, copy, modify, merge, publish, distribute, sublicense, and/or sell\n copies of the Software, and to permit persons to whom the Software is\n furnished to do so, subject to the following conditions:\n\n The above copyright notice and this permission notice shall be included in\n all copies or substantial portions of the Software.\n\n THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\n IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\n FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\n AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\n LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\n OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN\n THE SOFTWARE.\n',
28 silly publish   readmeFilename: 'README.md',
28 silly publish   gitHead: '243a01ff4f4f5837c5f6a609cf975fbaf3ec6dfa',
28 silly publish   bugs: { url: 'https://github.com/brianc/node-postgres/issues' },
28 silly publish   _id: 'pg@4.1.1',
28 silly publish   _shasum: '98480acfcd3cf6a3f9621ca5d4589415582a5732',
28 silly publish   _from: '.' }
29 verbose request where is /pg
30 verbose request registry https://registry.npmjs.org/
31 verbose request id 23e770dc5b4a1797
32 verbose url raw /pg
33 verbose url resolving [ 'https://registry.npmjs.org/', './pg' ]
34 verbose url resolved https://registry.npmjs.org/pg
35 verbose request where is https://registry.npmjs.org/pg
36 info trying registry request attempt 1 at 13:33:02
37 http PUT https://registry.npmjs.org/pg
38 http 503 https://registry.npmjs.org/pg
39 verbose bad json <?xml version="1.0" encoding="utf-8"?>
39 verbose bad json <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
39 verbose bad json  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
39 verbose bad json <html>
39 verbose bad json   <head>
39 verbose bad json     <title>503 backend read error</title>
39 verbose bad json   </head>
39 verbose bad json   <body>
39 verbose bad json     <h1>Error 503 backend read error</h1>
39 verbose bad json     <p>backend read error</p>
39 verbose bad json     <h3>Guru Mediation:</h3>
39 verbose bad json     <p>Details: cache-jfk1030-JFK 1418495597 4270251624</p>
39 verbose bad json     <hr>
39 verbose bad json     <p>Varnish cache server</p>
39 verbose bad json   </body>
39 verbose bad json </html>
40 error registry error parsing json
41 info retry will retry, error on last attempt: SyntaxError: Unexpected token <
41 info retry
41 info retry <?xml version="1.0" encoding="utf-8"?>
41 info retry <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
41 info retry  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
41 info retry <html>
41 info retry   <head>
41 info retry     <title>503 backend read error</title>
41 info retry   </head>
41 info retry   <body>
41 info retry     <h1>Error 503 backend read error</h1>
41 info retry     <p>backend read error</p>
41 info retry     <h3>Guru Mediation:</h3>
41 info retry     <p>Details: cache-jfk1030-JFK 1418495597 4270251624</p>
41 info retry     <hr>
41 info retry     <p>Varnish cache server</p>
41 info retry   </body>
41 info retry </html>
42 info trying registry request attempt 2 at 13:33:27
43 http PUT https://registry.npmjs.org/pg
44 http 500 https://registry.npmjs.org/pg
45 info retry will retry, error on last attempt: Error: pound_internal_server_error : pg
46 info trying registry request attempt 3 at 13:34:28
47 http PUT https://registry.npmjs.org/pg
48 http 503 https://registry.npmjs.org/pg
49 verbose bad json <?xml version="1.0" encoding="utf-8"?>
49 verbose bad json <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
49 verbose bad json  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
49 verbose bad json <html>
49 verbose bad json   <head>
49 verbose bad json     <title>503 backend read error</title>
49 verbose bad json   </head>
49 verbose bad json   <body>
49 verbose bad json     <h1>Error 503 backend read error</h1>
49 verbose bad json     <p>backend read error</p>
49 verbose bad json     <h3>Guru Mediation:</h3>
49 verbose bad json     <p>Details: cache-atl6224-ATL 1418495684 1281010348</p>
49 verbose bad json     <hr>
49 verbose bad json     <p>Varnish cache server</p>
49 verbose bad json   </body>
49 verbose bad json </html>
50 error registry error parsing json
51 verbose headers { date: 'Sat, 13 Dec 2014 18:34:44 GMT',
51 verbose headers   server: 'Varnish',
51 verbose headers   'retry-after': '0',
51 verbose headers   'content-type': 'text/html; charset=utf-8',
51 verbose headers   'content-length': '448',
51 verbose headers   'accept-ranges': 'bytes',
51 verbose headers   via: '1.1 varnish',
51 verbose headers   'x-served-by': 'cache-atl6224-ATL',
51 verbose headers   'x-cache': 'MISS',
51 verbose headers   'x-cache-hits': '0',
51 verbose headers   'x-timer': 'S1418495668.919581,VS0,VE15344',
51 verbose headers   connection: 'close' }
52 error publish Failed PUT 503
53 error SyntaxError: Unexpected token <
53 error
53 error <?xml version="1.0" encoding="utf-8"?>
53 error <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
53 error  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
53 error <html>
53 error   <head>
53 error     <title>503 backend read error</title>
53 error   </head>
53 error   <body>
53 error     <h1>Error 503 backend read error</h1>
53 error     <p>backend read error</p>
53 error     <h3>Guru Mediation:</h3>
53 error     <p>Details: cache-atl6224-ATL 1418495684 1281010348</p>
53 error     <hr>
53 error     <p>Varnish cache server</p>
53 error   </body>
53 error </html>
53 error
53 error     at Object.parse (native)
53 error     at RegClient.<anonymous> (/Users/bmc/local/node@v0.10.33/lib/node_modules/npm/node_modules/npm-registry-client/lib/request.js:274:23)
53 error     at Request._callback (/Users/bmc/local/node@v0.10.33/lib/node_modules/npm/node_modules/npm-registry-client/lib/request.js:246:65)
53 error     at Request.self.callback (/Users/bmc/local/node@v0.10.33/lib/node_modules/npm/node_modules/request/request.js:236:22)
53 error     at Request.emit (events.js:98:17)
53 error     at Request.<anonymous> (/Users/bmc/local/node@v0.10.33/lib/node_modules/npm/node_modules/request/request.js:1142:14)
53 error     at Request.emit (events.js:117:20)
53 error     at IncomingMessage.<anonymous> (/Users/bmc/local/node@v0.10.33/lib/node_modules/npm/node_modules/request/request.js:1096:12)
53 error     at IncomingMessage.emit (events.js:117:20)
53 error     at _stream_readable.js:943:16
54 error If you need help, you may report this *entire* log,
54 error including the npm and node versions, at:
54 error     <http://github.com/npm/npm/issues>
55 error System Darwin 14.0.0
56 error command "/Users/bmc/local/node@v0.10.33/bin/node" "/Users/bmc/local/node/bin/npm" "publish"
57 error cwd /Users/bmc/src/node-postgres
58 error node -v v0.10.33
59 error npm -v 1.4.28
60 error type unexpected_token
61 verbose exit [ 1, true ]