You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We published version 1.7.0 of the package @ui5/builder. For the next 1.5 hours npm info @ui5/builder@latest --no-cache still returned 1.6.1 as latest.
Basically we are interested in whether this currently "works-as-designed" as part of your load balancing/infrastructure.
npm install @ui5/builder@1.7.0 is working fine right away. However, we have an in-house npm proxy server which, upon proxying a request for a new version of a package, first fetches its metadata. If no metadata for the requested version is found, the package can't be installed from this proxy.
Apparently, the proxy holds this event in a negative cache for another 24 hours. So it is not possible to install the @latest version of the package from the proxy in that timeframe, which even breaks the install of some depending projects that do not use lockfiles.
Now we are wondering whether this proxy is making wrong assumptions on how the package metadata should be used or whether this is something that should normally work from your point of view.
npm v6 is no longer in active development; We will continue to push security releases to v6 at our team's discretion as-per our Support Policy.
If your bug is preproducible on v7, please re-file this issue using our new issue template.
If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo
npm v6 is no longer in active development; We will continue to push security releases to v6 at our team's discretion as-per our Support Policy.
If your bug is preproducible on v7, please re-file this issue using our new issue template.
If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo
What
We published version
1.7.0
of the package@ui5/builder
. For the next 1.5 hoursnpm info @ui5/builder@latest --no-cache
still returned1.6.1
as latest.Basically we are interested in whether this currently "works-as-designed" as part of your load balancing/infrastructure.
npm install @ui5/builder@1.7.0
is working fine right away. However, we have an in-house npm proxy server which, upon proxying a request for a new version of a package, first fetches its metadata. If no metadata for the requested version is found, the package can't be installed from this proxy.Apparently, the proxy holds this event in a negative cache for another 24 hours. So it is not possible to install the
@latest
version of the package from the proxy in that timeframe, which even breaks the install of some depending projects that do not use lockfiles.Now we are wondering whether this proxy is making wrong assumptions on how the package metadata should be used or whether this is something that should normally work from your point of view.
When
2019-11-07 15:58:51 UTC
@ui5/builder/1.7.0
2019-11-07 17:07 UTC
:npm info @ui5/builder@latest --no-cache
2019-11-07 17:34 UTC
:npm info @ui5/builder@latest --no-cache
Where
How
Current Behavior
All commands where executed between 17:10 and 17:30 UTC
npm i @ui5/builder@1.7.0 --verbose --no-cache
Steps to Reproduce
npm info @ui5/builder@latest --no-cache
shortly after publishing a new versionNote: For other packages that we released shortly after, the metadata was up-to-date much quicker (if not right away). Examples:
However, we saw the delay for
@ui5/builder
frequently in past releases.Expected Behavior
npm info @ui5/builder@latest --no-cache
should list version1.7.0
as latest right after publishing itWho
References
The text was updated successfully, but these errors were encountered: