search

heroku / s3pository

[DEPRECATED][RETIRED] caching proxy server with s3 backend to speed compiles on heroku
9 stars 0 forks source link

node should not be included in JVM RepositoryGroup #14

Closed ryanbrainard closed 2 years ago

ryanbrainard commented 11 years ago

Currently the node proxy is included in the jvm RepositoryGroup, which means that nodejs.org is being checked for JVM artifacts and creating a lot of logs like this:

2013-11-04T20:50:44.072156+00:00 app[web.6]: WAR [20131104-20:50:44.071] s3pository: nodejs.org error checking source repo nodejs.org for /org/codehaus/plexus/plexus/3.0.1/plexus-3.0.1.pom.sha1 :com.twitter.finagle.WriteException$$anon$1: com.twitter.util.FutureCancelledException: The future was cancelled with Future.cancel

cc: @zeke, @sclasen

sclasen commented 11 years ago

@ryanbrainard Yep you are right, and the all group should probably be renamed to jvm And also to note somewhere that it isnt required that a Repository be placed in a group.

joshwlewis commented 2 years ago

Closing as this service is being retired.