ic4l
Joined 9 years ago
Joined 9 years ago
FROM mirror.gcr.io/{image_name}
We received failed to resolve source metadata for mirror.gcr.io/
So it looks like these services may not be true mirrors, and just functioning as a library proxy with a cache.If you're image is not cached on one of these then you may be SOL.
Thankfully, AWS provides a docker.io mirror for those who can't wait:
FROM public.ecr.aws/docker/library/{image_name}
In the error logs, the issue was mostly related to the authentication endpoint:▪ https://auth.docker.io → "No server is available to handle this request"
After switching to the AWS mirror, everything built successfully without any issues.
> https://techcrunch.com/2025/06/24/facebook-group-admins-comp...
When using `gpt-4.5-preview` I am getting: > Invalid URL (POST /v1/chat/completions)
Why don’t they just request disclosure of what’s actually stored and allow renaming of the columns? It seems odd that knowing the exact column names would be necessary if the goal is simply to understand what data is being stored and its intended purpose.
What’s the advantage here beyond keeping things lightweight? Feels like this could hit limitations as complexity grows.
I think its related to fingerprinting attacks.
setInterval(() => Array.from(document.querySelectorAll('.main-btn, .upgrade-icon, .press-collect, .press-btn, .collect')).forEach(item => item.click()), 50);
After around level 40 things get very very slow.
Some restore options also do not let you move data to their cloud for direct download, which makes it feel like they do not actually want users to fully download and recover all of their files.