Clojurians Log v2

Looking now

Can you provide more details?

love that i experienced an issue and the status page actually reported it

What are you seeing?

https://clojars.statuspage.io/

Oh, DNSimple must be having issues, and it updated our page automatically.

❯ http 

http: error: gaierror: [Errno 8] nodename nor servname provided, or not known
Couldn't resolve the given hostname. Please check the URL and try again.

❯ clj -J-Xmx6g -J"$(llm-repl 6006)"  -M:"$ALIASES":llm-repl
Error building classpath. Failed to read artifact descriptor for com.metabase:athena-jdbc:jar:3.7.0
org.eclipse.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for com.metabase:athena-jdbc:jar:3.7.0
...
Caused by: org.eclipse.aether.transfer.ArtifactTransferException: Could not transfer artifact com.metabase:athena-jdbc:pom:3.7.0 from/to clojars (): 
	at org.eclipse.aether.connector.basic.ArtifactTransportListener.transferFailed(ArtifactTransportListener.java:52)
	at org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run(BasicRepositoryConnector.java:401)
	at org.eclipse.aether.util.concurrency.RunnableErrorForwarder.lambda$wrap$0(RunnableErrorForwarder.java:73)
	at org.eclipse.aether.connector.basic.BasicRepositoryConnector$DirectExecutor.execute(BasicRepositoryConnector.java:669)
	at org.eclipse.aether.connector.basic.BasicRepositoryConnector.get(BasicRepositoryConnector.java:290)
	at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:520)
	at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:408)
	... 26 more
Caused by: java.net.UnknownHostException: 

props that the status page was up to date with the actual issue. I’m used to github’s status page lagging ~30 minutes behind my own experience

I can't get DNSimple's status page to load.

Yeah, they look pretty toast, none of their sites are loading for me

Ah, there is this page: https://dnsimple.statuspage.io/ It shows an issue

> The issue has been identified and a fix is being implemented. nice

So now we wait I guess :(

the past incidents part of the clojars status page isn’t super helpful, while we wait. It includes days of no incidents. Which is nice to not forget it, but doesn’t help you understand the rate of failure

Can you clarify? I'm not quite following.

Or do you mean the format could be better, hiding the good days?

yeah. i wanted to see the past reliability and wasn’t really able to get a sense

I wonder if statuspage has templates for that? I've never looked, we just use the default.

fair enough. just mentioned it since we were waiting on upstream

Thanks! I'll see what we can do.

> Our initial attempts to restore our cluster has failed. We are working on bringing the services up in a fresh cluster. womp

@dpsutton is resolution working for you now? The update from 20 minutes ago was: > We've started restoring backend services. We expect to have services restored shortly!! Our http://uptime.com check was failing to resolve it, but is now.

I checked 5 minutes ago with no success. Just stepped out for lunch so can't check immediately

working for me at a coffee shop