"stack build" failed randomly - haskell

When I used stack build to build a package, it failed randomly during the process of installing dependent packages. Here is an example error message:
While building package statistics-0.13.3.0 using:
/home/work/.stack/setup-exe-cache/x86_64-linux/setup-Simple-Cabal-1.24.0.0-ghc-8.0.1 --builddir=.stack-work/dist/x86_64-linux/Cabal-1.24.0.0 build --ghc-options " -ddump-hi -ddump-to-file"
Process exited with code: ExitFailure (-11)
Logs have been written to: /home/work/server/dev/taiji/.stack-work/logs/statistics-0.13.3.0.log
I said "failed randomly" because this can be fixed by restart stack build. But it will fail on building another package later.
I looked at the dmesg | tail, it says:
[1029507.778048] ghc[16868]: segfault at 7d538d610628 ip 00007f5384094ed0 sp 00007ffceed0bda0 error 4 in libHSrts_thr-ghc8.0.1.so[7f538407a000+63000]
[1029524.911751] ghc[17599]: segfault at 100206005838 ip 00007f1c727de754 sp 00007ffdc160fd58 error 4 in libHSghc-8.0.1-ghc8.0.1.so[7f1c6e4de000+49c9000]
[1029533.035216] ghc[16789]: segfault at 7da273b664f0 ip 00007fa273b35a8e sp 00007ffe2f55d540 error 4 in libHSrts_thr-ghc8.0.1.so[7fa273b1c000+63000]
Any idea?

This turns out to be a memory defect issue.

Related

EclipseCDT will not debug executable: Error creating process

I just installed EclipseCDT 2022-12, created the HelloWorld example app, compiled, but when I debug I get an error. I have both current MSYS2 (MinGW64) and Cygwin64 installed, neither environment works and fails with the same error:
Error in final launch sequence:
Failed to execute MI command:
-exec-run
Error message from debugger back end:
Error creating process /cygdrive/c/Windows/system32/C:/Projects/cc3135/hello/C:/Projects/cc3135/hello/Debug/hello.exe, (error 2).
Failed to execute MI command:
-exec-run
Error message from debugger back end:
Error creating process /cygdrive/c/Windows/system32/C:/Projects/cc3135/hello/C:/Projects/cc3135/hello/Debug/hello.exe, (error 2).
Error creating process /cygdrive/c/Windows/system32/C:/Projects/cc3135/hello/C:/Projects/cc3135/hello/Debug/hello.exe, (error 2).
Any suggestions?
P.S. The hello executable runs fine in cmd.exe and under gdb.

Hybris server startup issue on M1 Mac

Getting intermittent issue for server startup of hybris(1905 version).
--> Wrapper Started as Console
wrapper-macosx-universal-64(12108,0x2001ce600) malloc: Heap corruption detected, free list is damaged at 0x600002104910
*** Incorrect guard value: 105553116300640
wrapper-macosx-universal-64(12108,0x2001ce600) malloc: *** set a breakpoint in malloc_error_break to debug
after getting issue as workaround ,doing ant clean all and some time it work some time it's not working any solution.

Error: Debug Failure. Output generation failed when running formatjs extract

When running formatjs extract this is what we got. From the stack trace it seems that the issue is from formatjs themselves. Feel like I am stuck on what the issue is here.
$ formatjs extract './src/**/*.{js,ts,tsx}' --out-file './src/i18n/messages/messages.json' --extract-from-format-message-call --throws
Error: Debug Failure. Output generation failed
at Object.transpileModule (/Users/.../node_modules/#formatjs/cli/node_modules/typescript/lib/typescript.js:126894:29)
at processFile (/Users/.../node_modules/#formatjs/cli/src/extract.js:104:39)
at /Users/.../node_modules/#formatjs/cli/src/extract.js:163:59
at step (/Users/.../node_modules/#formatjs/cli/src/extract.js:44:23)
at Object.next (/Users/.../node_modules/#formatjs/cli/src/extract.js:25:53)
at fulfilled (/Users/.../node_modules/#formatjs/cli/src/extract.js:16:58)
error Command failed with exit code 1.
You might be processing a file that needs to be ignored using --ignore. Can you upgrade to the latest version and re-run your command? Long added the filename in this commit https://github.com/formatjs/formatjs/commit/ceb0bf8a58c13fe6811bc35191018ee1c431484a
Reference: https://github.com/formatjs/formatjs/issues/2044

Hyperledger Fabric and Node.js creation of environment successfully and getting some error in execution

I am creating network but after that when I'm running the query.js and I am getting this errors:
Fatal error in ../deps/v8/src/api.cc, line 1200
Check failed: !value_obj->IsJSReceiver() || value_obj->IsTemplateInfo().
==== C stack trace ===============================
node(v8::base::debug::StackTrace::StackTrace()+0x16) [0x1598936]
node(V8_Fatal+0xd6) [0x15935c6]
node(v8::Template::Set(v8::Local, v8::Local, v8::PropertyAttribute)+0xf7) [0xa9a447]
/home/ubramanyam/fabric-samples/fabcar/node_modules/grpc/src/node/extension_binary
#Subramanyam , What OS and Node version are you using ?
Can you also confirm if you followed instructions given here
http://hyperledger-fabric.readthedocs.io/en/latest/prereqs.html#node-js-runtime-and-npm

Issue deploying to elastic beanstalk "50npm.sh failed"

I'm having an issue deploying some code to one of my environments.
Creating application version archive "app-aa68e-170213_103330".
Uploading PAS-API/app-aa68e-170213_103330.zip to S3. This may take a while.
Upload Complete.
INFO: Environment update is starting.
INFO: Deploying new version to instance(s).
ERROR: Failed to run npm install. Snapshot logs for more details.
ERROR: [Instance: i-0ee97a5c7bcab8d51] Command failed on instance. Return code: 1 Output: (TRUNCATED)..."/opt/elasticbeanstalk/containerfiles/ebnode.py", line 180, in npm_install
raise e
subprocess.CalledProcessError: Command '['/opt/elasticbeanstalk/node-install/node-v4.4.6-linux-x64/bin/npm', '--production', 'install']' returned non-zero exit status 1.
Hook /opt/elasticbeanstalk/hooks/appdeploy/pre/50npm.sh failed. For more detail, check /var/log/eb-activity.log using console or EB CLI.
INFO: Command execution completed on all instances. Summary: [Successful: 0, Failed: 1].
ERROR: Unsuccessful command execution on instance id(s) 'i-0ee97a5c7bcab8d51'. Aborting the operation.
It seems that the deployment is failing when npm install is running on the server.
When I checked the package.json it seemed some of the deps were added as a tarball instead of a version number, meaning that when it installed and saved it looked like this:
"basic-auth": "https://registry.npmjs.org/basic-auth/-/basic-auth-1.0.4.tgz"
Rather than
"basic-auth": "^1.1.0",
This was failing on npm install on the eb instance, it looks like it works now.
If it was OK before and you didn't change deployment settings, you can reboot the instance and it usually solve the problem.

Resources