@MasseGuillaume I think it is an issue for all oncue projects on bintray, same thing for remotely artifacts. Could someone with credentials please look into this? /cc @timperrett@stew@runarorama
Timothy Perrett
@timperrett
@ahjohannessen hmm - i’ve no idea what would be causing that
the file shows as present
@ahjohannessen are you sure this just doesnt happen in the browser?
it could just be a bintray “feature"
i mean, the actual artifacts do resolve and download
Timothy Perrett
@timperrett
@MasseGuillaume@ahjohannessen bintray did something stupid to our account; i’ve emailed them
Guillaume Massé
@MasseGuillaume
Great let me know when they resolve your issue !
Alex Henning Johannessen
@ahjohannessen
@timperrett
are you sure this just doesnt happen in the browser It also happened on shippable that it could not resolve artifacts
Dan Billings
@danbills
FYI I’m seeing a deadlock on the elastic publisher thread pool, investigating
Dan Billings
@danbills
^ disregard, is upstream of elastic
Timothy Perrett
@timperrett
@ahjohannessen@MasseGuillaume bintray issue is resolved
Alex Henning Johannessen
@ahjohannessen
@timperrett awesome, thanks :+1:
Guillaume Massé
@MasseGuillaume
@timperrett cool thanks !
If you have any special request for the scala index let me know ;-)
this issue caught my attention because there was a lot of failures associated to oncue's Bintray repos
Rob Norris
@tpolecat
hello lads, what do i need to do the simplest kind of single-process instrumentation?
The doc says libraryDependencies += "oncue.funnel" %% "http" % "x.y.z" which doesn't exist.