I'm trying to push a chart to my ACR by following the instructions from here.
I'm getting a 404 not found error, And I can't seem to find why this is thrown.
Script:
export HELM_EXPERIMENTAL_OCI=1
echo $(registryPassword) | helm registry login $(registryServerName) -u $(registryLogin) --password-stdin
helm chart save charts/$(projectName) $(registryServerName)/$(imageName):$(imageTag)
helm chart list
helm chart push $(registryServerName)/$(imageName):$(imageTag):v0.3.5
Logs:
Login succeeded
ref: <omitted>.azurecr.io/client-angular:1048:v0.3.5
digest: a0cd7f0f9a47469915a8c8199ecbe00fc4bed094fcf4002d0e602eea2f76473c
size: 1.6 KiB
name: client-angular
version: v0.3.5
v0.3.5: saved
REF NAME VERSION DIGEST SIZE CREATED
<omitted>.azurecr.io/client-angular:1034:v0.3.4 client-angular v0.3.4 396e4d0 1.6 KiB 17 hours
<omitted>.azurecr.io/client-angular:1036:v0.3.4 client-angular v0.3.4 35afa1f 1.6 KiB 2 hours
<omitted>.azurecr.io/client-angular:1040:v0.3.4 client-angular v0.3.4 b3c7d09 1.6 KiB 2 hours
<omitted>.azurecr.io/client-angular:1042:v0.3.5 client-angular v0.3.5 d857c2f 1.6 KiB 2 hours
<omitted>.azurecr.io/client-angular:1044:v0.3.5 client-angular v0.3.5 b3b0b0a 1.6 KiB About an hour
<omitted>.azurecr.io/client-angular:1046:v0.3.5 client-angular v0.3.5 cc2be7a 1.6 KiB 18 minutes
<omitted>.azurecr.io/client-angular:1048:v0.3.5 client-angular v0.3.5 a0cd7f0 1.6 KiB Less than a second
<omitted>.azurecr.io/client-angular:979:v0.3.4 client-angular v0.3.4 52ba3b4 1.6 KiB 10 days
<omitted>.azurecr.io/server:1035:v0.3.4 server v0.3.4 1190dc2 43.1 KiB 17 hours
<omitted>.azurecr.io/server:1037:v0.3.4 server v0.3.4 da1d991 43.1 KiB 2 hours
<omitted>.azurecr.io/server:1045:v0.3.4 server v0.3.4 7bb4611 43.1 KiB About an hour
<omitted>.azurecr.io/server:1047:v0.3.5 server v0.3.5 1cf51bf 43.1 KiB 21 minutes
<omitted>.azurecr.io/server:980:v0.3.4 server v0.3.4 7915917 43.1 KiB 10 days
The push refers to repository [<omitted>.azurecr.io/client-angular:1048]
ref: <omitted>.azurecr.io/client-angular:1048:v0.3.5
digest: a0cd7f0f9a47469915a8c8199ecbe00fc4bed094fcf4002d0e602eea2f76473c
size: 1.6 KiB
name: client-angular
version: v0.3.5
Error: failed commit on ref "manifest-sha256:efeac2a2a1b8b3dc18e4cfc439a765d4c03720aa829756dc94e7b1708d9196bf": unexpected status: 404 Not Found
When looking at the documentation this shoul dbe fine, but still it's complaining.
Anybody got an idea?
As I see, all the steps are right. The problem is in your helm chart. The error shows the manifest no found. You can check if there is something wrong with your chart. For example, some formats wrong. Here is a similar issue that the manifest cannot found.
I faced the same problem and this is how I resolved it.
The name of my helm chart was SampleApp and I renamed it to sampleapp. After that pushing the helm chart to ACR succeeded.
When using helm push to upload a chart an OCI registry, the reference must be prefixed with oci:// and must not contain the basename or tag.
so helm push <file-1.2.3.tgz> oci://myregistry/file
https://helm.sh/docs/topics/registries/
Related
I'm attempting to build a Next.js project on CircleCI using an ARM-based machine (specifically, arm.xlarge) which has 32GB of RAM. However, it seems to very quickly exit with an error about lack of memory. I've tried to increase the memory of the Node process all the way up to that of the machine, but with no luck - I receive the same error.
What's particularly strange is that the GCs have a tiny amount of memory utilization (3.5MB), and that it exits in sub-second time!
This build does work, if I swap out the arm resource type for an x86_64 resource type, and build a Docker image for the x86_64 platform instead. Obviously this doesn't cover my needs, but verifies the build works.
What might cause this very strange behaviour? What else can I do to further debug this issue?
What I've tried
Changing the Node version, ranging from 14 to 18.8.0
Changing the machine resource size
Changing the options of Docker, including adding a --memory flag to the extra-build-args field of the build job
Removing the yarn.lock
Purging the Node cache
Deleting the node_modules folder
Relevant resources:
Here's the trace:
#16 [11/11] RUN NODE_OPTIONS="--max_old_space_size=8192" yarn build
#16 sha256:da0777711cb35943386ef4812f2df1ff4932fb5bee717be330a217104e5240c7
#16 0.178
#16 0.178 <--- Last few GCs --->
#16 0.178
#16 0.178 [1:0x570e320] 100 ms: Mark-sweep 1.2 (3.5) -> 1.2 (3.5) MB, 2.2 / 0.0 ms (average mu = 0.818, current mu = 0.007) allocation failure scavenge might not succeed
#16 0.178 [1:0x570e320] 102 ms: Mark-sweep (reduce) 1.2 (3.5) -> 1.2 (3.5) MB, 2.3 / 0.0 ms (average mu = 0.704, current mu = 0.006) last resort GC in old space requested
#16 0.178 [1:0x570e320] 104 ms: Mark-sweep (reduce) 1.2 (2.5) -> 1.1 (3.5) MB, 2.3 / 0.0 ms (average mu = 0.549, current mu = 0.010) last resort GC in old space requested
#16 0.178
#16 0.178
#16 0.178 <--- JS stacktrace --->
#16 0.178
#16 0.178 FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
#16 ERROR: process "/bin/sh -c NODE_OPTIONS=\"--max_old_space_size=8192\" yarn build" did not complete successfully: exit code: 132
------
> [11/11] RUN NODE_OPTIONS="--max_old_space_size=8192" yarn build:
------
Dockerfile:32
--------------------
31 |
32 | >>> RUN NODE_OPTIONS="--max_old_space_size=8192" yarn build
34 |
--------------------
error: failed to solve: rpc error: code = Unknown desc = process "/bin/sh -c NODE_OPTIONS=\"--max_old_space_size=8192\" CI_BUILD=${CI_BUILD} DEPLOYMENT_VERSION=${DEPLOYMENT_VERSION} yarn build" did not complete successfully: exit code: 132
Here's the relevant parts of the Dockerfile:
FROM node:14.18.0-alpine
WORKDIR /app
RUN apk update
RUN apk add python3
RUN apk add git gnupg jq g++ make py3-pip
COPY package.json yarn.lock ./
RUN yarn
RUN yarn add pm2#5.2.0 --global
COPY . .
RUN NODE_OPTIONS="--max_old_space_size=8192" yarn build
EXPOSE 3001
CMD [ "npx", ... ]
and here's the job from CircleCI config.yml:
build_and_push_image:
machine:
image: ubuntu-2004:202101-01
resource_class: arm.xlarge
steps:
- checkout
- docker/pull:
images: 'node:16.14.2'
- aws-ecr/build-and-push-image:
aws-access-key-id: AWS_ACCESS_KEY_ID
aws-secret-access-key: AWS_SECRET_ACCESS_KEY
aws-cli-version: latest
create-repo: true
skip-when-tags-exist: true
dockerfile: Dockerfile
extra-build-args: >
--build-arg GPG_ENCRYPT_PASSPHRASE
--build-arg BUILD_STAGE
--build-arg CI_BUILD=true
platform: linux/arm64/v7
push-image: true
registry-id: AWS_ACCOUNT_ID
region: $AWS_REGION
repo: $PROJECT_NAME
tag: $version_tag
After a good few hours of debugging with trial and error, I fixed with the following changes to config.yml:
build_and_push_image:
machine:
image: ubuntu-2004:202101-01
resource_class: arm.xlarge
steps:
- checkout
- docker/pull:
images: 'node:16.14.2'
- aws-ecr/build-and-push-image:
aws-access-key-id: AWS_ACCESS_KEY_ID
aws-secret-access-key: AWS_SECRET_ACCESS_KEY
aws-cli-version: latest
create-repo: true
skip-when-tags-exist: true
dockerfile: Dockerfile
extra-build-args: >
--build-arg GPG_ENCRYPT_PASSPHRASE
--build-arg BUILD_STAGE
--build-arg CI_BUILD=true
- platform: linux/arm64/v7
+ platform: linux/arm64
push-image: true
registry-id: AWS_ACCOUNT_ID
region: $AWS_REGION
repo: $PROJECT_NAME
tag: $version_tag
I'm not sure why this works, but here's my best thoughts for others who are blocked by this in the future:
Some miconfiguration of the docker buildx command from the CircleCI orb. I'm also noticing that a lot of people are having problems with Docker image caching using the orb, and maybe there's some issue with the command itself (see https://github.com/CircleCI-Public/aws-ecr-orb/issues/202). It looks something like this:
docker context create builder
# This here is interesting - it is using qemu to emulate for builds
# See https://github.com/tonistiigi/binfmt
docker run --privileged --rm tonistiigi/binfmt --install all
docker --context builder buildx create --use
docker --context builder buildx build \
-f "${PARAM_PATH}"/"${PARAM_DOCKERFILE}" \
${docker_tag_args} \
--platform "${PARAM_PLATFORM}" \
--progress plain \
"$#" \
"${PARAM_PATH}"
https://github.com/docker/buildx/issues/1036 missing qemu dependencies
https://github.com/moby/buildkit/issues/1946#issuecomment-767374876 libseccomp blocking unknown (new) syscalls
Have you checked the versions of OS and Node? The Versions should match. (x64=x64)
I converted my app and deployed follow the instructions here
Error with angular 9 SSR and fire base cloud functions #2369
now in the last step of deploying I get this error
Built at: 04/01/2020 4:18:16 PM
Asset Size Chunks Chunk Names
main.js 3.93 MiB 0 [emitted] [big] main
Entrypoint main [big] = main.js
chunk {0} main.js (main) 7.37 MiB [entry] [rendered]
⚠️ Your Node.js version (13.12.0) does not match the Firebase Functions runtime (10).
Deploying your Angular Universal application...
success.hosting.split is not a function
PS C:\Users\Khaled\Desktop\coupons>
I am trying to deploy a nodejs app I have via
git push heroku master
The build is failing due to timeout and here is the build log
-----> Node.js app detected
-----> Creating runtime environment
NPM_CONFIG_LOGLEVEL=error
NODE_VERBOSE=false
NODE_ENV=production
NODE_MODULES_CACHE=true
-----> Installing binaries
engines.node (package.json): unspecified
engines.npm (package.json): unspecified (use default)
Resolving node version 10.x...
Downloading and installing node 10.15.3...
Using default npm version: 6.4.1
-----> Restoring cache
Cached directories were not restored due to a change in version of node, npm, yarn or stack
Module installation may take longer for this build
-----> Installing dependencies
Installing node modules (package.json + package-lock)
> node-expat#2.3.17 install /tmp/build_c3cb8f26de145fdc95dbb7c74ca4abea/node_modules/node-expat
> node-gyp rebuild
make: Entering directory '/tmp/build_c3cb8f26de145fdc95dbb7c74ca4abea/node_modules/node-expat/build'
CC(target) Release/obj.target/expat/deps/libexpat/lib/xmlparse.o
../deps/libexpat/lib/xmlparse.c: In function ‘gather_time_entropy’:
../deps/libexpat/lib/xmlparse.c:780:7: warning: variable ‘gettimeofday_res’ set but not used [-Wunused-but-set-variable]
int gettimeofday_res;
^
CC(target) Release/obj.target/expat/deps/libexpat/lib/xmltok.o
CC(target) Release/obj.target/expat/deps/libexpat/lib/xmlrole.o
AR(target) Release/obj.target/deps/libexpat/libexpat.a
COPY Release/libexpat.a
CXX(target) Release/obj.target/node_expat/node-expat.o
../node-expat.cc: In static member function ‘static Nan::NAN_METHOD_RETURN_TYPE Parser::Parse(Nan::NAN_METHOD_ARGS_TYPE)’:
../node-expat.cc:103:47: warning: ‘v8::Local<v8::Object> v8::Value::ToObject() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
Local<Object> obj = info[0]->ToObject();
^
In file included from /app/.node-gyp/10.15.3/include/node/node.h:63:0,
from ../node_modules/nan/nan.h:52,
from ../node-expat.cc:1:
/app/.node-gyp/10.15.3/include/node/v8.h:10046:15: note: declared here
Local<Object> Value::ToObject() const {
^
../node-expat.cc: In static member function ‘static Nan::NAN_METHOD_RETURN_TYPE Parser::SetUnknownEncoding(Nan::NAN_METHOD_ARGS_TYPE)’:
../node-expat.cc:470:59: warning: ‘int32_t v8::Value::Int32Value() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
parser->xmlEncodingInfo->map[i] = m->Int32Value();
^
In file included from /app/.node-gyp/10.15.3/include/node/v8.h:26:0,
from /app/.node-gyp/10.15.3/include/node/node.h:63,
from ../node_modules/nan/nan.h:52,
from ../node-expat.cc:1:
/app/.node-gyp/10.15.3/include/node/v8.h:2478:46: note: declared here
V8_DEPRECATED("Use maybe version", int32_t Int32Value() const);
^
/app/.node-gyp/10.15.3/include/node/v8config.h:324:3: note: in definition of macro ‘V8_DEPRECATED’
declarator __attribute__((deprecated(message)))
^
SOLINK_MODULE(target) Release/obj.target/node_expat.node
COPY Release/node_expat.node
make: Leaving directory '/tmp/build_c3cb8f26de145fdc95dbb7c74ca4abea/node_modules/node-expat/build'
> iconv#2.3.1 install /tmp/build_c3cb8f26de145fdc95dbb7c74ca4abea/node_modules/iconv
> node-gyp rebuild
make: Entering directory '/tmp/build_c3cb8f26de145fdc95dbb7c74ca4abea/node_modules/iconv/build'
CXX(target) Release/obj.target/iconv/src/binding.o
CC(target) Release/obj.target/iconv/deps/libiconv/lib/iconv.o
CC(target) Release/obj.target/iconv/support/localcharset.o
SOLINK_MODULE(target) Release/obj.target/iconv.node
COPY Release/iconv.node
make: Leaving directory '/tmp/build_c3cb8f26de145fdc95dbb7c74ca4abea/node_modules/iconv/build'
> execSync#1.0.2 install /tmp/build_c3cb8f26de145fdc95dbb7c74ca4abea/node_modules/execSync
> node install.js
[execsync v1.0.2] Attempting to compile native extensions.
[execSync v1.0.2]
Native code compile failed!!
added 760 packages from 579 contributors and audited 3610 packages in 38.646s
found 111 vulnerabilities (46 low, 49 moderate, 16 high)
run `npm audit fix` to fix them, or `npm audit` for details
-----> Build
Running build
> udemy-nodejs-angular2#1.0.0 build /tmp/build_c3cb8f26de145fdc95dbb7c74ca4abea
> del-cli public/js/app && webpack --config webpack.config.dev.js --progress --profile --watch
0% compiling
Webpack is watching the files…
10% building modules 0/1 modules 1 active ...dc95dbb7c74ca4abea/assets/app/main.ts
[at-loader] Using typescript#2.6.2 from typescript and "tsconfig.json" from /tmp/build_c3cb8f26de145fdc95dbb7c74ca4abea/tsconfig.json.
18812ms building modules
77ms sealing
0ms optimizing
0ms basic module optimization
66ms module optimization
27ms advanced module optimization
0ms basic chunk optimization
0ms chunk optimization
0ms advanced chunk optimization
1ms module and chunk tree optimization
48ms module reviving
6ms module order optimization
9ms module id optimization
10ms chunk reviving
1ms chunk order optimization
45ms chunk id optimization
116ms hashing
1ms module assets processing
1746ms chunk assets processing
6ms additional chunk assets processing
0ms recording
0ms additional asset processing
1ms chunk asset optimization
494ms asset optimization
206ms emitting
Hash: bdcd2d9b22529d57e9ea
Version: webpack 2.7.0
Time: 21715ms
Asset Size Chunks Chunk Names
0.chunk.js 672 kB 0 [emitted] [big]
1.chunk.js 45.2 kB 1 [emitted]
bundle.js 29.8 MB 2 [emitted] [big] app
[0] ./~/#angular/core/esm5/core.js 542 kB {2} [built]
[] -> factory:568ms building:8004ms dependencies:14ms = 8586ms
[4] ./~/tslib/tslib.es6.js 8.03 kB {2} [built]
[] -> factory:1256ms building:1025ms = 2281ms
[46] ./~/#angular/platform-browser/esm5/platform-browser.js 159 kB {2} [built]
[] -> factory:570ms building:4258ms dependencies:5ms = 4833ms
[785] ./~/#angular/platform-browser-dynamic/esm5/platform-browser-dynamic.js 24.9 kB {2} [built]
[] -> factory:96ms building:89ms dependencies:464ms = 649ms
[786] ./assets/app/app.module.ts 4.19 kB {2} [built]
[] -> factory:11ms building:71ms = 82ms
[787] ./assets/app/polyfills.ts 163 bytes {2} [built]
[] -> factory:9ms building:9ms = 18ms
[788] ./~/hammerjs/hammer.js 73.8 kB {2} [built]
[] -> factory:95ms building:643ms = 738ms
[820] ./~/#angular/platform-browser/esm5/animations.js 28 kB {2} [built]
[] -> factory:571ms building:292ms dependencies:499ms = 1362ms
[821] ./assets/app/app.component.ts 1.58 kB {2} [built]
[] -> factory:27ms building:112ms dependencies:431ms = 570ms
[822] ./assets/app/app.routing.ts 3.79 kB {2} [built]
[] -> factory:28ms building:176ms dependencies:12ms = 216ms
[823] ./assets/app/errors/error.component.ts 2.12 kB {2} [built]
[] -> factory:32ms building:343ms dependencies:195ms = 570ms
[825] ./assets/app/header.component.ts 1.53 kB {2} [built]
[] -> factory:28ms building:129ms dependencies:413ms = 570ms
[826] ./assets/app/main.ts 338 bytes {2} [built]
factory:30ms building:7552ms = 7582ms
[830] ./assets/app/messages/message.module.ts 1.78 kB {2} [built]
[] -> factory:34ms building:372ms dependencies:1123ms = 1529ms
[832] ./assets/app/setup/job.module.ts 4.54 kB {2} [built]
[] -> factory:36ms building:471ms dependencies:1277ms = 1784ms
+ 1707 hidden modules
-----> Timed out running buildpack Node.js
! Timed out compiling app (60 minutes)
! See https://devcenter.heroku.com/articles/slug-compiler#time-limit
I see that there is a statement that says Module installation may take longer for this build but unfortunately it is timing out. The frustrating part here is that it used to work and I'm not sure why it isn't now. Is there any way to increase the timeout limit or solve this issue in another way?
This is probably due to the webpack build taking time due to high memory usage. You can try to tweak the memory allowed for the node process by passing NODE_OPTIONS="--max_old_space_size=2560". The default size is 2.5GB and you can try increasing it to a suitable value. Might help!
I created a simple webpack project for a Typescript library : https://github.com/lbar/test-webpackts-issue
On linux, npm run build finishes successfully:
> rimraf dist && webpack --progress --profile
10% 0/1 build modulests-loader: Using typescript#1.8.10 and /tmp/testwebpack/tsconfig.json 8030ms1217ms optimi5ms emit
Hash: 8eac1502f3b7a9a19be2
Version: webpack 1.13.1
Time: 2596ms
Asset Size Chunks Chunk Names
index.js 816 bytes 0 [emitted] index
index.js.map 6.07 kB 0 [emitted] index
/tmp/testwebpack/dist/index.d.ts 31 bytes [emitted]
/tmp/testwebpack/dist/src/info.d.ts 49 bytes [emitted]
+ 2 hidden modules
On Windows, npm run build is blocked during 'emit' phase. The output is :
> rimraf dist && webpack --progress --profile
10% 0/1 build modulests-loader: Using typescript#1.8.10 and C:\tmp\testwebpack\tsconfig.jso
1836ms build modules
3ms seal
7ms optimize
3ms hashing
7ms create chunk assets
79ms additional chunk assets
19ms optimize chunk assets
837ms optimize assets
95% emit
The version of node differs: 6.2.2 on Windows and 4.4.5 on Linux. I don't know if it may be the cause.
Has anyone an idea about the problem? Issue in webpack, ts-loader or typescript?
One more thing, call to tsc is working on both systems.
Thanks for your help
This problem is caused by an issue in ts-loader: https://github.com/TypeStrong/ts-loader/issues/185
A Pull Request is waiting fixes for project core team.
Webpack can use "awesome-typescript-loader" to avoid this issue.
I'm trying to take a script I have that updates my sytstem for me, and have it output it's text to a file, and the screen. This is fairly simple using tee, except my update manager, pacman, outputs the same kind of text like wget. Here's some sample output.
core 107.0 KiB 392K/s 00:00 [################################################################] 100%
extra 1531.8 KiB 719K/s 00:02 [################################################################] 100%
community 2.1 MiB 818K/s 00:03 [################################################################] 100%
When I try to redirect that kind of output to a file using tee, this is the output I get to my screen and file.
:: Synchronizing package databases...
downloading core.db...
downloading extra.db...
downloading community.db...
I understand this is because pacman uses a buffer to output to the screen, but I'm still hoping there's a way I can output the status to the screen and the file, and not just the "downloading xyz...".
Thank you in advance for any help.
Edit:
I have no current updates, but here's some sample output that's very similar of me installing the Opera browser. The lines with the percentages and the pound signs are buffers that update with the progress of the download.
resolving dependencies...
looking for inter-conflicts...
Packages (1): opera-12.16.1860-2
Total Download Size: 10.49 MiB
Total Installed Size: 45.03 MiB
:: Proceed with installation? [Y/n] y
:: Retrieving packages ...
opera-12.16.1860-2-x86_64 13.4 MiB 1151K/s 00:12 [################################################################] 100%
(1/1) checking keys in keyring [################################################################] 100%
(1/1) checking package integrity [################################################################] 100%
(1/1) loading package files [################################################################] 100%
(1/1) checking for file conflicts [################################################################] 100%
(1/1) checking available disk space [################################################################] 100%
(1/1) installing opera [################################################################] 100%
Optional dependencies for opera
gstreamer0.10-base-plugins: HTML5 Video support
gstreamer0.10-good: HTML5 Video support
This is what the above output looks like when redirected through tee.
warning: opera-12.16.1860-2 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...
Packages (1): opera-12.16.1860-2
Total Installed Size: 45.03 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n] y
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
checking available disk space...
reinstalling opera...
As you can see, the download progess isn't shown. Just three periods.
Note sure if I fully understand the question, but I think possibly your script outputs to both stdout and stderr and you want both to be captured to file as well displayed on the terminal. In which case, you could do this by redirecting stderr of your script to stderr, before piping the whole thing to tee:
./myscript.sh 2>&1 | tee output.log
So I think you also want all the output with respect to progress bars, etc. You can use the script command to get this:
script -e -q -c "./myscript.sh" output.log
This works for me with wget:
Terminal output:
ubuntu#ubuntu:~$ script -e -q -c "wget http://stackoverflow.com" output.log
--2014-02-21 20:01:31-- http://stackoverflow.com/
Resolving stackoverflow.com (stackoverflow.com)... 198.252.206.140
Connecting to stackoverflow.com (stackoverflow.com)|198.252.206.140|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 214108 (209K) [text/html]
Saving to: `index.html.5'
100%[======================================>] 214,108 7.59K/s in 38s
Last-modified header invalid -- time-stamp ignored.
2014-02-21 20:02:13 (5.55 KB/s) - `index.html.5' saved [214108/214108]
ubuntu#ubuntu:~$
Contents of output.log:
Script started on Fri 21 Feb 2014 08:01:31 PM PST
--2014-02-21 20:01:31-- http://stackoverflow.com/
Resolving stackoverflow.com (stackoverflow.com)... 198.252.206.140
Connecting to stackoverflow.com (stackoverflow.com)|198.252.206.140|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 214108 (209K) [text/html]
Saving to: `index.html.5'
0% [ ] 0 --.-K/s
1% [ ] 3,367 3.66K/s
2% [> ] 5,863 5.09K/s
3% [> ] 7,111 3.54K/s
5% [> ] 10,855 3.73K/s
### Output omitted - I have a slow connection right now ###
97% [=====================================> ] 209,806 7.84K/s eta 1s
99% [=====================================> ] 212,302 7.44K/s eta 1s
100%[======================================>] 214,108 7.59K/s in 38s
Last-modified header invalid -- time-stamp ignored.
2014-02-21 20:02:13 (5.55 KB/s) - `index.html.5' saved [214108/214108]