Created
June 19, 2018 13:42
-
-
Save rorymckinley/6e198f4849f761939044a6424df130dc to your computer and use it in GitHub Desktop.
backtrace when running script/docker_dev_setup.sh
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<pre>working in 1 processes | |
--> Starting: 'i18n:generate_js' | |
ENOENT: no such file or directory, stat 'symlink_to_node_modules/.bin/nopt' | |
Error extracting JS translations; confirm that `./gems/canvas_i18nliner/bin/i18nliner generate_js` works | |
rake aborted! | |
Parallel::DeadWorker: Parallel::DeadWorker | |
/home/docker/.gem/ruby/2.4.0/gems/parallel-1.12.1/lib/parallel.rb:74:in `rescue in work' | |
/home/docker/.gem/ruby/2.4.0/gems/parallel-1.12.1/lib/parallel.rb:71:in `work' | |
/home/docker/.gem/ruby/2.4.0/gems/parallel-1.12.1/lib/parallel.rb:382:in `block (4 levels) in work_in_processes' | |
/home/docker/.gem/ruby/2.4.0/gems/parallel-1.12.1/lib/parallel.rb:495:in `with_instrumentation' | |
/home/docker/.gem/ruby/2.4.0/gems/parallel-1.12.1/lib/parallel.rb:381:in `block (3 levels) in work_in_processes' | |
/home/docker/.gem/ruby/2.4.0/gems/parallel-1.12.1/lib/parallel.rb:369:in `loop' | |
/home/docker/.gem/ruby/2.4.0/gems/parallel-1.12.1/lib/parallel.rb:369:in `block (2 levels) in work_in_processes' | |
/home/docker/.gem/ruby/2.4.0/gems/parallel-1.12.1/lib/parallel.rb:206:in `block (2 levels) in in_threads' | |
Caused by: | |
EOFError: end of file reached | |
/home/docker/.gem/ruby/2.4.0/gems/activesupport-5.1.6/lib/active_support/core_ext/marshal.rb:4:in `load' | |
/home/docker/.gem/ruby/2.4.0/gems/activesupport-5.1.6/lib/active_support/core_ext/marshal.rb:4:in `load' | |
/usr/src/app/gems/canvas_ext/lib/canvas_ext/marshal.rb:25:in `load' | |
/home/docker/.gem/ruby/2.4.0/gems/parallel-1.12.1/lib/parallel.rb:72:in `work' | |
/home/docker/.gem/ruby/2.4.0/gems/parallel-1.12.1/lib/parallel.rb:382:in `block (4 levels) in work_in_processes' | |
/home/docker/.gem/ruby/2.4.0/gems/parallel-1.12.1/lib/parallel.rb:495:in `with_instrumentation' | |
/home/docker/.gem/ruby/2.4.0/gems/parallel-1.12.1/lib/parallel.rb:381:in `block (3 levels) in work_in_processes' | |
/home/docker/.gem/ruby/2.4.0/gems/parallel-1.12.1/lib/parallel.rb:369:in `loop' | |
/home/docker/.gem/ruby/2.4.0/gems/parallel-1.12.1/lib/parallel.rb:369:in `block (2 levels) in work_in_processes' | |
/home/docker/.gem/ruby/2.4.0/gems/parallel-1.12.1/lib/parallel.rb:206:in `block (2 levels) in in_threads'</pre> |
Thanks for the response! That sounds right. I resolved this similarly by
reducing the number of active record objects in each of my batches so
reducing memory footprint may have been the key.
…On Sat, Sep 14, 2019, 7:03 PM Rory McKinley ***@***.***> wrote:
Hey! I have been wracking my brain, but no, I don't think I ever solved it
- I think I would have created the gist so that I could ask a question in
IRC, but I can't remember ever getting an answer. However, I do know that
canvas wants a *lot* of memory when building the js and the failures that
result from insufficient memory are often not obvious, so I may have
resolved it by upping the memory.
I am sorry that I can't be of more help, but I would love to know if you
ever manage to crack it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://gist.github.com/6e198f4849f761939044a6424df130dc?email_source=notifications&email_token=AAL5OITPAV3PGIH653ND5QLQJTHIBA5CNFSM4IWQTPG2YY3PNVWWK3TUL52HS4DFVNDWS43UINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAFYZC2#gistcomment-3027501>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAL5OIXP2CRD7LLLS5CAFI3QJTHIBANCNFSM4IWQTPGQ>
.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey! I have been wracking my brain, but no, I don't think I ever solved it - I think I would have created the gist so that I could ask a question in IRC, but I can't remember ever getting an answer. However, I do know that canvas wants a lot of memory when building the js and the failures that result from insufficient memory are often not obvious, so I may have resolved it by upping the memory.
I am sorry that I can't be of more help, but I would love to know if you ever manage to crack it.