Skip to content
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

unavailable repo.scala-sbt.org (April 7, 2023) #7202

Closed
xuwei-k opened this issue Apr 7, 2023 · 57 comments
Closed

unavailable repo.scala-sbt.org (April 7, 2023) #7202

xuwei-k opened this issue Apr 7, 2023 · 57 comments
Labels
Bug

Comments

@xuwei-k
Copy link
Member

xuwei-k commented Apr 7, 2023

steps

$ curl https://repo.scala-sbt.org/scalasbt/sbt-plugin-releases/com.dwijnand/sbt-dynver/scala_2.12/sbt_1.0/4.1.1/jars/sbt-dynver.jar

or

plugins.sbt

addSbtPlugin("com.dwijnand" % "sbt-dynver" % "4.1.1")

problem

redirect to https://landing.jfrog.com/reactivate-server/scala 😭

<html>
<head><title>302 Found</title></head>
<body>
<center><h1>302 Found</h1></center>
<hr><center>nginx/1.19.6</center>
</body>
</html>

jfrog

expectation

notes
@xuwei-k xuwei-k added the Bug label Apr 7, 2023
This was referenced Apr 7, 2023
Closed
Closed
Merged
@tsuyoshizawa tsuyoshizawa mentioned this issue Apr 7, 2023
Closed
7 tasks
@eed3si9n
Copy link
Member

eed3si9n commented Apr 7, 2023

We're looking into it. Thanks for your patience.

@xuwei-k xuwei-k mentioned this issue Apr 7, 2023
Closed
@WayneWang12

This comment was marked as duplicate.

Sign in to view
@gervaisb

This comment was marked as off-topic.

Sign in to view
@armanbilge armanbilge mentioned this issue Apr 7, 2023
Closed
@mkurz mkurz mentioned this issue Apr 7, 2023
Closed
@fedotxxl

This comment was marked as duplicate.

Sign in to view
@charlescd

This comment was marked as resolved.

Sign in to view
@WayneWang12

This comment was marked as resolved.

Sign in to view
@tgodzik tgodzik mentioned this issue Apr 7, 2023
Merged
@max-leuthaeuser max-leuthaeuser mentioned this issue Apr 7, 2023
Merged
@00subra8

This comment was marked as duplicate.

Sign in to view
@xuwei-k xuwei-k mentioned this issue Apr 7, 2023
Merged
@raboof raboof mentioned this issue Apr 7, 2023
Closed
@SethTisue
Copy link
Member

SethTisue commented Apr 7, 2023 •
edited
Loading

PLEASE READ

You can all safely assume there will be an update here once anything changes.

Please stop asking "any update?" — you are clogging inboxes with pointless noise. Everyone already understands this is a big deal. You're welcome to comment here if you have helpful new information and/or workarounds to share, but otherwise you will simply need to be patient.

@WayneWang12 is correct that this has absolutely nothing to do with the Sonatype outage. They are two entirely separate outages that just happen to be occurring at the same time. As far as we know, the Sonatype outage only affects publishing; Maven Central has continued to serve up existing artifacts just fine. (If it appears otherwise to you, see below at #7202 (comment).)

The problem on this ticket is confined to repo.scala-sbt.org.

It is unfortunate that JFrog is serving up 302 response codes from that domain, instead of 404 or some such. This can lead to cache corruption locally, either on local developer machines or on a privately hosted Artifactory (or any similar software that caches artifacts).

For the past few years, repo.scala-sbt.org has generously been hosted by JFrog for free through their OSS program. For reasons unknown, it suddenly stopped working. Eugene has contacted JFrog to try to find out what happened.

Disclaimer:

It is currently the middle of the night in New Jersey, where Eugene lives, and that's part of why I'm stepping in here with some information. I am not representing any company or organization today; I'm just a guy who tries to help out in this repo, and this week I happen to be a timezone where the sun is currently up.

If you want to come chat and/or commiserate in a more informal environment, there's always the #sbt channel in the Scala Discord.

P.S. I assume you all have seen https://xkcd.com/2347/

@SethTisue
Copy link
Member

SethTisue commented Apr 7, 2023 •
edited
Loading

Workaround for some plugins: try a newer version?

Note that repo.scala-sbt.org hasn't accepted new plugins for several years now. It only has old plugins. So for some plugins, you may be able to resolve the issue immediately by upgrading to a newer version of the plugin, if that newer version is available from Maven Central.

For any plugin whose latest version is still only on the old repo, it would make sense to open a ticket such as sbt/sbt-dynver#239 in the hopes of getting a new version published to Maven Central.

That doesn't help poor benighted people stuck on crufty versions of things, but it's progress regardless towards the long term goal of making the leading edge of the plugin ecosystem more robustly available.

(However, I think repo.scala-sbt.org also serves other things besides plugins...? I'm unclear on that.)

This was referenced Apr 7, 2023
Merged
Merged
@gervaisb

This comment was marked as resolved.

Sign in to view
@SethTisue

This comment was marked as resolved.

Sign in to view
@marcinaylien

This comment was marked as resolved.

Sign in to view
@SethTisue

This comment was marked as resolved.

Sign in to view
@raboof raboof mentioned this issue Apr 7, 2023
Closed
@gervaisb

This comment was marked as resolved.

Sign in to view
@raboof raboof mentioned this issue Apr 7, 2023
Closed
@eed3si9n
Copy link
Member

eed3si9n commented Apr 8, 2023

For the record, I just re-enabled CDN download for sbt-plugin-releases. It might take some time for the content to propagate, but this should make access to JARs faster.

@eed3si9n
Copy link
Member

eed3si9n commented Apr 8, 2023

Actually given the error message

{
  "errors" : [ {
    "status" : 500,
    "message" : "Could not process download request: Artifactory is not configured with CLOUD_FRONT."
  } ]
}

maybe we no longer have access to CDN.

@jrudolph
Copy link
Member

jrudolph commented Apr 8, 2023

We can discuss these options with Scala Center. Taking backups at least would be a good idea. At someone I did have a copy of a backup from Bintray, but since then I've probably deleted that after I pushed the artifacts into Artifactory.

I've still got a backup from bintray from April 2021 lying around, let me know if you need it.

@mkurz
Copy link
Member

mkurz commented Apr 8, 2023

@jrudolph Probably a good idea to not delete that backup anytime soon 😉

@SethTisue SethTisue mentioned this issue Apr 8, 2023
Closed
@milessabin milessabin mentioned this issue Apr 8, 2023
Closed
@fabienfoerster fabienfoerster mentioned this issue Apr 8, 2023
Closed
@muuki88 muuki88 mentioned this issue Apr 8, 2023
Closed
@armanbilge armanbilge mentioned this issue Apr 9, 2023
Closed
This was referenced Apr 10, 2023
Closed
Open
Closed
@SethTisue
Copy link
Member

This can lead to cache corruption locally

for a sample command clearing local cache, see #7211 (comment)

Coursier's cache location is different on different OSes though, as per https://get-coursier.io/docs/cache

@SethTisue SethTisue mentioned this issue Apr 26, 2023
Closed
bushbecky added a commit to bushbecky/VexRiscv that referenced this issue May 9, 2023
@bushbecky
Remove sbt-assembly dependency
1116567 
The plugin is not used in the VexRiscV build and causes issues for users
since repo.scala-sbt.org seems to be down/sunset/?.

See also sbt/sbt#7202

Updating the dependency would also have been an option, but since it's not
used removal is easier.
@SethTisue
Copy link
Member

SethTisue commented May 17, 2023 •
edited
Loading

the Scala Center's blog post about the incident (dated April 20, 2023): https://scala-lang.org/blog/2023/04/20/sbt-plugins-community-repository.html

and an update from a couple days ago with some plans: https://contributors.scala-lang.org/t/roadmap-for-the-sbt-community-repository/6195

This was referenced Jan 25, 2024
Merged
Closed
Merged
Merged
Merged
Merged
Closed
Merged
Closed
Merged
Closed
@ioannakok ioannakok mentioned this issue Jan 30, 2024
Merged
3 tasks
@SethTisue SethTisue mentioned this issue Mar 31, 2024
Closed
@mkurz mkurz mentioned this issue May 8, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests