This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-03-16
Channels
- # aws-lambda (3)
- # beginners (20)
- # boot (201)
- # cljs-dev (45)
- # cljsrn (9)
- # clojars (19)
- # clojure (141)
- # clojure-china (2)
- # clojure-dev (11)
- # clojure-greece (6)
- # clojure-italy (1)
- # clojure-new-zealand (1)
- # clojure-romania (1)
- # clojure-russia (55)
- # clojure-spec (58)
- # clojure-taiwan (1)
- # clojure-uk (97)
- # clojure-ukraine (40)
- # clojurescript (77)
- # core-async (5)
- # core-typed (1)
- # cursive (35)
- # datomic (9)
- # jobs (2)
- # jobs-rus (25)
- # juxt (8)
- # lein-figwheel (14)
- # luminus (24)
- # mount (16)
- # off-topic (56)
- # om (36)
- # onyx (22)
- # pedestal (3)
- # perun (14)
- # re-frame (111)
- # reagent (5)
- # remote-jobs (6)
- # ring-swagger (3)
- # slack-help (1)
- # specter (17)
- # unrepl (12)
- # untangled (56)
Is there anything specific I'd need to do to set up an HTTP server to emulate clojars?
I could take the easy way, but I want to actually work out whats wrong here 🙂, because I'm mostly a release manager, and the primary dev prefers boot, so I defer to them. Because once I work out the Actual Problem then I can fix the Actual Problem. 🙂
Basically, I just need to be able to see the requests you're seeing natively without having to ferry packets do you directly, that way I can close the loop and see how what I change affects the result.
( mostly because there's no way for me to get between the aether code and push to see what's going on in there or explain why things are getting lost )
Ideally, I'm going to end up wanting to build my own (push) function that turns off all the frills and confusing indirection that is making debugging impossible
the easiest thing to do may be to run a copy of clojars locally, and point at that, maybe
Is there anything special about the http protocol it uses, or is it just a dumb HTTP + Auth + PUT ?
well, I guess its telling that when I overwrite the URL for upload it still does whatever the hell it wants ...
Yeah. Obviously I'd made a mistake in the repo-map assignment somehow, and it decided to ignore my configuration and use its own
said configuration being necessary to store username and password ... probably related to that
Now I have weird bugs because aether doesn't like my repo, and I'm having to dig into its mess of java code 😕
org.sonatype.aether.transfer.NoRepositoryConnectorException: No connector available to access repository hacks () of type default using the available factories FileRepositoryConnectorFactory, WagonRepositoryConnectorFactory
repository: #object[org.sonatype.aether.repository.RemoteRepository 0x275fe372 "hacks (, releases+snapshots)"]
org.sonatype.aether.deployment.DeploymentException: Failed to deploy artifacts/metadata: No connector available to access repository hacks () of type default using the available factories FileRepositoryConnectorFactory, WagonRepositoryConnectorFactory
clojure.lang.ExceptionInfo: Failed to deploy artifacts/metadata: No connector available to access repository hacks () of type default using the available factories FileRepositoryConnectorFactory, WagonRepositoryConnectorFactory