Error: incorrect header check
See original GitHub issueHaving a problem compiling a new project using Electron 2.0.9/3.0.0-beta.
Looks like #24 is coming back. Might be a CDN/replication problem (I’m in the US, not China).
$ cmake-js compile --log-level verbose "${MYPROJECT_DEBUG:-'-D'}" -G Ninja --runtime electron --runtime-version="$(grep -oE 'ELECTRON_VERSION=[^
]+' Dockerfile | cut -d= -f2)" -O bin/native --arch x64
grep: brackets ([ ]) not balanced
verb CON Parsing arguments
verb CON options:
verb CON { directory: null,
verb CON debug: false,
verb CON cmakePath: null,
verb CON generator: 'Ninja',
verb CON toolset: undefined,
verb CON target: undefined,
verb CON preferMake: false,
verb CON preferXcode: false,
verb CON preferGnu: false,
verb CON preferClang: false,
verb CON std: null,
verb CON runtime: 'electron',
verb CON runtimeVersion: '',
verb CON arch: 'x64',
verb CON cMakeOptions: {},
verb CON silent: false,
verb CON out: 'bin/native' }
verb CON Running command: compile
verb CFG Looking for application level CMake.js config in '/src/myproject.
verb CFG Application level CMake.js config doesn't exists.
verb CFG Build system options:
verb CFG {"directory":"/src/myproject","debug":false,"cmakePath":null,"generator":"Ninja","preferMake":false,"preferXcode":false,"preferGnu":false,"preferClang":false,"std":null,"runtime":"electron","runtimeVersion":"","arch":"x64","cMakeOptions":{},"silent":false,"out":"bin/native"}
info TOOL Using Ninja generator, as specified from commandline.
info TOOL Using c++11 compiler standard.
verb TOOL Setting default OSX compiler flags.
info DIST Downloading distribution files.
http DIST - https://atom.io/download/atom-shell/v10.10.0/node-v10.10.0.tar.gz
ERR! OMG Error: incorrect header check
ERR! OMG at Zlib.zlibOnError [as onerror] (zlib.js:153:17)
ERR! OMG Error: incorrect header check
ERR! OMG at Zlib.zlibOnError [as onerror] (zlib.js:153:17)
error An unexpected error occurred: "Command failed.
Visiting that link directly redirects to https://gh-contractor-zcbenz.s3.amazonaws.com/atom-shell/dist/v10.10.0/node-v10.10.0.tar.gz
and shows:
<Error>
<Code>NoSuchKey</Code>
<Message>The specified key does not exist.</Message>
<Key>atom-shell/dist/v10.10.0/node-v10.10.0.tar.gz</Key>
<RequestId>06877ADC9BDD20A5</RequestId>
<HostId>Sox5ahfhPoreMhRxZdczLC3LZOtK9/FNAYHUgvjSQtPmAMwpHJolm0NgkVt3KNaYD+0CZZ/SHTE=</HostId>
</Error>
Is this a known issue, or something that has to be fixed on Electron’s side?
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (3 by maintainers)
Top Results From Across the Web
'incorrect header check' parsing gzip response on every call ...
I am seeing the following error on every request but the first to a resource (using 1.7.2). It might be related to #410...
Read more >Incorrect Header Check when using zlib in node.js
1) Collect all the buffers in an array, and in the end event concatentate them using Buffer.concat() . Then call gunzip on the...
Read more >3 while decompressing: incorrect header check - zlib.error
PYTHON : zlib. error : Error -3 while decompressing: incorrect header check [ Gift : Animated Search Engine ...
Read more >Incorrect header check - Questions - Kong Nation
I'm trying to send request throw postman and I'm getting the error incorrect header check, but if I send curl request I get...
Read more >"incorrect header check" using ZLIB Compression
I have written a simple compression program which uses ZLIB 1.1.4 to compress a chunk of data in memory. I am using the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Just ran into this. So it’s necessary to both specify the runtime and runtime version, otherwise the download URL will be wrong. E.g.
--runtime=electron --runtime-version=6.0.2
, while the 6.0.2 is acturally the Electron version, not the Node version Electron used.sounds like this was cmake-js being called with the wrong parameters, do I dont see anything that needs to be done here