Hello Mario,

I've added resetadminpassword to ProGet.Service.exe for the next minor release (4.7.10) - PG-1009

For now, you can reset the password in the database to Admin by setting the Salt_Bytes and Password_Bytes to 0x26CF0B87A338C08CA30F and 0x5868049613BC1ED1E4E3C2E404D8B85684B53263 respectively.

Ok, I noticed that in your log, npm isn't authenticating. Is the anonymous user allowed to access the feed in ProGet?

Hello Marcus,

There was a bug in our HTTP library that caused uploads larger than 2GB to fail or be truncated. It will be fixed for the next version of ProGet, 4.7.10.

Hello Michael,

NPM feeds don't currently support an API key, but you can share a single ProGet user between all of the users who need to upload to the feed to simulate the same thing.

The Publish Packages task group on the NPM feed is all you need to upload a package. If you want to replace an already-uploaded package, you need the Overwrite Package task, which is available on the Administer and Manage Feed task groups by default, but you can create a new task group with just Overwrite Package on the Customize Tasks page (/administration/security/customize-tasks).

Hello Matt,

It looks like the PostgreSQL version of Feeds_SetLastSyncDate was not updated when the MSSQL version was. I've logged this as PG-1006 and it will be fixed in the next version of ProGet.

A vulnerability version range can be:

• the literal string (any)
• empty string (equivalent to (any))
• single
• single, single
• single, single, single
• single, single, single, single
• etc.

A single vulnerability version range can be:

• version
• >version
• >=version
• <version
• <=version
• >version <version
• >=version <version
• >version <=version
• >=version <=version

The format of version is defined by the feed type.

On ProGet 4.7.9:

$ npm install @angular/platform-browser --loglevel verbose
npm info it worked if it ends with ok
npm verb cli [ '/usr/bin/nodejs',
npm verb cli   '/usr/bin/npm',
npm verb cli   'install',
npm verb cli   '@angular/platform-browser',
npm verb cli   '--loglevel',
npm verb cli   'verbose' ]
npm info using npm@3.5.2
npm info using node@v4.2.6
npm verb request uri http://proget/npm/npm-test/@angular%2fplatform-browser
npm verb request always-auth set; sending authorization
npm info attempt registry request try #1 at 2:38:23 PM
npm verb request id 6e455c4d3dbe2135
npm http request GET http://proget/npm/npm-test/@angular%2fplatform-browser
npm http 200 http://proget/npm/npm-test/@angular%2fplatform-browser
npm verb headers { 'cache-control': 'private',
npm verb headers   'content-type': 'application/json; charset=utf-8',
npm verb headers   'content-encoding': 'gzip',
npm verb headers   vary: 'Accept-Encoding',
npm verb headers   server: 'Microsoft-IIS/10.0',
npm verb headers   'x-ua-compatible': 'IE=edge',
npm verb headers   'x-proget-version': '4.7.9.2',
npm verb headers   'x-aspnet-version': '4.0.30319',
npm verb headers   'x-powered-by': 'ASP.NET',
npm verb headers   date: 'Thu, 06 Apr 2017 19:38:15 GMT',
npm verb headers   'content-length': '11462' }
npm verb get saving @angular/platform-browser to /home/ben/.npm/proget/npm/npm-test/_40angular_252fplatform-browser/.cache.json
npm verb makeDirectory /home/ben/.npm creation not in flight; initializing
npm verb cache add spec @angular/platform-browser
npm verb addNamed "latest" is being treated as a dist-tag for @angular/platform-browser
npm info addNameTag [ '@angular/platform-browser', 'latest' ]
npm verb addNameTag registry:http://proget/npm/npm-test/@angular%2fplatform-browser not in flight; fetching
npm verb get http://proget/npm/npm-test/@angular%2fplatform-browser not expired, no request
npm verb addNamed "4.0.1" is a plain semver version for @angular/platform-browser
npm verb addRemoteTarball http://proget/npm/npm-test/@angular/platform-browser/-/platform-browser-4.0.1.tgz not in flight; adding
npm verb addRemoteTarball [ 'http://proget/npm/npm-test/@angular/platform-browser/-/platform-browser-4.0.1.tgz',
npm verb addRemoteTarball   '4b9efbeb2fbb900de188743b988802d3aa2b33ff' ]
npm info retry fetch attempt 1 at 2:38:24 PM
npm info attempt registry request try #1 at 2:38:24 PM
npm http fetch GET http://proget/npm/npm-test/@angular/platform-browser/-/platform-browser-4.0.1.tgz
npm http fetch 200 http://proget/npm/npm-test/@angular/platform-browser/-/platform-browser-4.0.1.tgz
npm verb addTmpTarball /tmp/npm-26991-a64070af/proget/npm/npm-test/_40angular/platform-browser/-/platform-browser-4.0.1.tgz not in flight; adding
npm verb addTmpTarball already have metadata; skipping unpack for @angular/platform-browser@4.0.1
npm verb afterAdd /home/ben/.npm/@angular/platform-browser/4.0.1/package/package.json not in flight; writing
npm verb afterAdd /home/ben/.npm/@angular/platform-browser/4.0.1/package/package.json written
npm verb makeDirectory /home/ben/.npm/_locks creation not in flight; initializing
npm verb lock using /home/ben/.npm/_locks/staging-e45475a342ae353f.lock for /home/ben/npm_test/node_modules/.staging
npm verb unbuild node_modules/.staging/@angular/platform-browser-688e40ec
npm verb gentlyRm don't care about contents; nuking /home/ben/npm_test/node_modules/.staging/@angular/platform-browser-688e40ec
npm verb tar unpack /home/ben/.npm/@angular/platform-browser/4.0.1/package.tgz
npm verb tar unpacking to /home/ben/npm_test/node_modules/.staging/@angular/platform-browser-688e40ec
npm verb gentlyRm don't care about contents; nuking /home/ben/npm_test/node_modules/.staging/@angular/platform-browser-688e40ec
npm verb gentlyRm don't care about contents; nuking /home/ben/npm_test/node_modules/.staging/@angular/platform-browser-688e40ec/node_modules
npm info lifecycle @angular/platform-browser@4.0.1~preinstall: @angular/platform-browser@4.0.1
npm info linkStuff @angular/platform-browser@4.0.1
npm verb linkBins @angular/platform-browser@4.0.1
npm verb linkMans @angular/platform-browser@4.0.1
npm info lifecycle @angular/platform-browser@4.0.1~install: @angular/platform-browser@4.0.1
npm info lifecycle @angular/platform-browser@4.0.1~postinstall: @angular/platform-browser@4.0.1
npm verb unlock done using /home/ben/.npm/_locks/staging-e45475a342ae353f.lock for /home/ben/npm_test/node_modules/.staging
npm_test@1.0.0 /home/ben/npm_test
├── UNMET PEER DEPENDENCY @angular/common@4.0.1
├── UNMET PEER DEPENDENCY @angular/core@4.0.1
└── @angular/platform-browser@4.0.1  extraneous

npm WARN @angular/platform-browser@4.0.1 requires a peer of @angular/core@4.0.1 but none was installed.
npm WARN @angular/platform-browser@4.0.1 requires a peer of @angular/common@4.0.1 but none was installed.
npm WARN npm_test@1.0.0 No description
npm WARN npm_test@1.0.0 No repository field.
npm verb exit [ 0, true ]
npm info ok 

Are you getting something different?

Version 1.1.0 of the upack command line tool is now available from http://inedo.com/support/documentation/proget/reference/upack. The chocolatey version has been submitted and will be available once it's approved.

There's a bug we haven't been able to figure out where the Linux version of ProGet doesn't respond to requests for URLs with colons in them.

NUnit 5.1.2 has been released now, so you can update it from inside BuildMaster at any time.

Hello Patrick,

Yes, this is a bug in the NUnit BuildMaster plugin. It will be fixed in the next release of the plugin, 5.1.2.

I haven't been able to figure out the solution or what part of the code is choking, but the problem is that there's a colon in the URL.

For example, going to http://proget/%3A also hangs forever for the Linux version of ProGet.

I've logged this as PG-769.

Correct. Output variables don't need to be specially declared.

However, the next version of the Windows plugin for BuildMaster and Otter will add support for [ref] parameters as output variables in the editor.

It looks like this was fixed back in November as [PG-646] but the updated EXE was never published with the update.

I'll see if I can get that done.

I'm on ProGet Version 4.7.8 (Build 4) (locally hosted, not on EC2) and I'm able to upload universal packages to an S3-backed feed using the upack.exe tool with both the latest published release of the Amazon plugin and a debug build from source code.

Can you still reproduce the error on the latest version of ProGet?

You have the order of the output parameter reversed. It goes PowerShellVariableName => OtterScriptVariableName, so it should be hashlist => %items.

MaxResponseLength was missing a ScriptAlias. It'll be fixed in the next release.

The latest version of Windows.bmx is 5.6.3, which doesn't include the fix:

https://github.com/Inedo/inedox-windows/compare/BuildMaster-5.6.3.1...master

I'll see if I can get someone to publish it.

Hmm, if you rebooted the host, that's probably not it.

Hmm, I just tried it locally and Docker gives a very different error message for my hypothesis:

docker: Error response from daemon: driver failed programming external connectivity on endpoint proget (559abf94e7064e2fa65b27ebf9c334b517927912b0eb73763a0875c6c060d4a7): Error starting userland proxy: listen tcp 0.0.0.0:8081: bind: address already in use.

Is it possible something is still holding one end of a connection open to port 8081 on the host?