Skip to content

Loading…

Exception traces shown on first upload of new artifact #7

Closed
hugoduncan opened this Issue · 3 comments

4 participants

@hugoduncan

The first time an artifact is deployed, the download of existing metadata obviously fails. In this case, an exception is however shown to the user, which is confusing (the deploy however succeeds). This might be just be a case of adjusting the log levels for the messages to DEBUG rather than the current WARN and SEVERE.

@ninjudd

Hey @technomancy, any clues how to fix this? I get error messages from lein all the time when using s3-wagon-private. It seems like it is checking s3 for my dependencies that are on Clojars occasionally.

@technomancy
Owner

Not really; this whole thing got rewritten in 1.1.0 and I haven't looked at the new version at all. TBH it's a bit silly that this project even exists; the upstream projects should just be patched to support private ACLs.

@danielcompton danielcompton added the bug label
@danielcompton
Collaborator

This shouldn't be an issue anymore with the new version 1.2.0 as it uses the official S3 client and is much less noisy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.