-
-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: return 404 on removePackage #289
Conversation
Codecov Report
@@ Coverage Diff @@
## master #289 +/- ##
=========================================
- Coverage 65.42% 65.33% -0.1%
=========================================
Files 26 26
Lines 1400 1402 +2
Branches 204 202 -2
=========================================
Hits 916 916
- Misses 481 484 +3
+ Partials 3 2 -1
Continue to review full report at Codecov.
|
I'll run some test before merge this, I'll work on this. |
minio is a tool to simulate s3 service on local. Script to start minio server
Verdaccio config section
|
Thanks that is really helpful 🙏 |
Please describe in the commit message and PR title what it does. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think is ok, we have no test running here, so, not 100% confident. But worth to re-visit this. I'd try to enable them again and see what other changes are need it.
Thanks for this.
Try on |
The 404 error is now fixed in my setup (Docker + Digital Oceans's spaces). Thank you everyone! |
Type: bug
Scope: aws-s3-storage
The following has been addressed in the PR:
Description:
Fixed verdaccio/verdaccio/issues/1435,
unpublish -f
failed with s3 storage.When unpublish a package, verdaccio will remove the package.json and all tarballs, then try to remove (source code use word 'unlink') the directory. It is okay in local storage, but not for s3. S3 does not have the directory concept, when remove all objects under a path, the path is gone as well. So try to remove the directory will returns 404 error. Just ignore the 404 error is fine, and will fix the npm client error.