NPM registry returning 504 - Gateway Time-out

[PeteLTS]

Hi there,

It appears that https://npm-registry.vive.com/ is down? It's currently returning a 504, which is causing our build pipeline to fail.

Are there any known issues here?

[Dev1234]

Same problem here... It is the most common form of installation nowadays.

Now they do not document that way to install it:

https://developer.vive.com/resources/openxr/unity/tutorials/how-to-install-vive-openxr-plugin/

Maybe it has been removed, but if so, it has not been notified or anything...

At least you can install it with git but it's not ideal:

https://github.com/ViveSoftware/VIVE-OpenXR/tree/master/com.htc.upm.vive.openxr

manifest.json:

"com.htc.upm.vive.openxr": "https://github.com/ViveSoftware/VIVE-OpenXR.git?path=/com.htc.upm.vive.openxr#versions/2.0.0",

There is an attempt to include it in OpenUPM at least to recover that functionality through a third party:

https://github.com/openupm/openupm/pull/4388

[PeteLTS]

It looks like our Unity project is using the com.htc.upm.wave.openxr package - which I can't seem to find on Github, openupm, or anywhere!

Not sure if this package is the same - although, browsing the source on Github, it looks like they're at the very least based on the same codebase if they're not the same.

[Alex_HTC]

@PeteLTSHowdy Pete!  

We had a few changes at a high level:
1) our onboarding flow suggests using the installer that @Dev1234 suggested depending on the package you're using openxr, wave, or legacy openxr pc/aio as described in the instructions linked by dev https://developer.vive.com/resources/openxr/unity/tutorials/how-to-install-vive-openxr-plugin/
2) We combined our openxr pc and AIO packages into one in the openxr 2.x series. And since we're on github, you can check the diffs and releases on the releases page https://github.com/ViveSoftware/VIVE-OpenXR/releases
3) AIO openxr 1.x packages are still available at https://github.com/ViveSoftware/VIVE-OpenXR-AIO

Definitely don't hesitate to reach out with any other questions!

Thanks
Alex
 

[PeteLTS]

Thanks for the response @Alex_HTC

Did I miss some communication on this? It's a little disconcerting that this change was made without any prior warning.

Additionally, can you explain the rationale behind the change to using the installer rather than UPM? What does the installer do that UPM cannot?

Thanks,

Pete

 

[Alex_HTC]

@PeteLTS

I agree that the messaging can be better around this change.

The rationale is a little unclear, but from my understanding there were some external factors outside of our control and relatively sudden.

As Dev pointed out, the difference is really just a different endpoint - using urls that point to github rather than a upm server.

"com.htc.upm.vive.openxr": "https://github.com/ViveSoftware/VIVE-OpenXR.git?path=/com.htc.upm.vive.openxr#versions/2.0.0",

Versus another one

There are features that github offers that artifact repositories do not, and we're excited to engage with our community.

We appreciate your patience and understanding.

-Alex

[Dev1234]

@Alex_HTC the difference is not just the endpoint....

Git method (new):

1. Requires the user to have git installed on his machine and depending on the level of the developer maybe he doesn't even know what git is....
2. You cannot discover new versions automatically, you have to manually go to the git repository and check if there is a new release...
3. You have to put the url in the manifest.json file, so the dependencies you can put in your own packages to "com.htc.upm.vive.openxr" with a specific version, are useless.

Scope Registry method (above):

1. You don't have to have git installed
2. Going to the UI of the package manager the new versions appear if there are any.
3. You can in your own packagees put dependencies to packages like "com.htc.upm.vive.openxr" with specific versions.

[Alex_HTC]

@Dev1234agreed

There are additional positives to the git method (including viewing diffs, less bandwidth for updates, etc) for sure.

Regardless, using the scoped registry is not something we could continue doing any longer, and is not an option going forward.

[VIVE_chengnay]

Hi @PeteLTS,

upm server was down and we got it fixed.

Could you try again? Thanks!