8000 cache_s3 outputs misleading 404 message (from aws.s3::head_object) for new keys. · Issue #96 · r-lib/memoise · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

cache_s3 outputs misleading 404 message (from aws.s3::head_object) for new keys. #96

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.

Sign up for GitHub

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

Jump to bottom
Closed
stelsemeyer opened this issue Aug 29, 2019 · 0 comments < 8F50 span data-issue-and-pr-hovercards-enabled>
Closed

cache_s3 outputs misleading 404 message (from aws.s3::head_object) for new keys. #96

stelsemeyer opened this issue Aug 29, 2019 · 0 comments

Comments

@stelsemeyer
Copy link
Contributor
stelsemeyer commented Aug 29, 2019 •
edited
Loading

In cache_s3's cache_has_key uses aws.s3::head_object (ref), which outputs a message Client error: (404) Not Found when the key does not exist yet.
These messages spam the logs/outputs, which can be a bit misleading, as they are somewhat expected behaviour.

It would be nice to suppress this message in some way, for example by implementing a "better" version of aws.s3::head_object or simply using suppressMessages (which seems to be used for the gcs variant).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@stelsemeyer
0