Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

i18n: rake gettext:find would fail in certain scenarios #4774

Closed
mzazrivec opened this issue Oct 9, 2015 · 3 comments
Closed

i18n: rake gettext:find would fail in certain scenarios #4774

mzazrivec opened this issue Oct 9, 2015 · 3 comments
Assignees
Labels

Comments

@mzazrivec
Copy link
Contributor

In certain scenarios, for example when config/locales/manageiq.pot file doesn't exist,
gettext:find rake task would fail with the following:

$ bundle exec rake --trace gettext:find
...
** Execute config/locales/manageiq.pot
#<GetText::RubyLexX:0x0056521622efe8>#<GetText::RubyLexX:0x0056521622efe8>** Invoke config/locales/nl (first_time, not_needed)
** Invoke gettext:internal:force (first_time)
** Execute gettext:internal:force
rake aborted!
NoMethodError: undefined method `match' for nil:NilClass
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/task_manager.rb:133:in `block in enhance_with_matching_rule'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/task_manager.rb:132:in `each'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/task_manager.rb:132:in `enhance_with_matching_rule'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/task.rb:234:in `execute'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/task.rb:179:in `block in invoke_with_call_chain'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/monitor.rb:211:in `mon_synchronize'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/task.rb:172:in `invoke_with_call_chain'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/task.rb:201:in `block in invoke_prerequisites'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/task.rb:199:in `each'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/task.rb:199:in `invoke_prerequisites'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/task.rb:178:in `block in invoke_with_call_chain'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/monitor.rb:211:in `mon_synchronize'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/task.rb:172:in `invoke_with_call_chain'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/task.rb:201:in `block in invoke_prerequisites'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/task.rb:199:in `each'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/task.rb:199:in `invoke_prerequisites'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/task.rb:178:in `block in invoke_with_call_chain'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/monitor.rb:211:in `mon_synchronize'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/task.rb:172:in `invoke_with_call_chain'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/task.rb:201:in `block in invoke_prerequisites'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/task.rb:199:in `each'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/task.rb:199:in `invoke_prerequisites'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/task.rb:178:in `block in invoke_with_call_chain'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/monitor.rb:211:in `mon_synchronize'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/task.rb:172:in `invoke_with_call_chain'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/task.rb:201:in `block in invoke_prerequisites'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/task.rb:199:in `each'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/task.rb:199:in `invoke_prerequisites'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/task.rb:178:in `block in invoke_with_call_chain'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/monitor.rb:211:in `mon_synchronize'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/task.rb:172:in `invoke_with_call_chain'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/task.rb:165:in `invoke'
~/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/-1.3.0/lib/gettext_i18n_rails/tasks.rb:59:in `block (2 levels) in <top (required)>'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/task.rb:240:in `call'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/task.rb:240:in `block in execute'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/task.rb:235:in `each'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/task.rb:235:in `execute'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/task.rb:179:in `block in invoke_with_call_chain'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/monitor.rb:211:in `mon_synchronize'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/task.rb:172:in `invoke_with_call_chain'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/task.rb:165:in `invoke'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/application.rb:150:in `invoke_task'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/application.rb:106:in `block (2 levels) in top_level'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/application.rb:106:in `each'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/application.rb:106:in `block in top_level'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/application.rb:115:in `run_with_threads'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/application.rb:100:in `top_level'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/application.rb:78:in `block in run'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/application.rb:176:in `standard_exception_handling'
~/.rbenv/versions/2.2.2/lib/ruby/2.2.0/rake/application.rb:75:in `run'
~/.rbenv/versions/2.2.2/bin/rake:33:in `<main>'
Tasks: TOP => gettext:po:update => gettext:po:nl:update => config/locales/nl/manageiq.po => config/locales/nl/manageiq.edit.po => gettext:internal:force

We need to investigate whether this is a problem on our side or elsewhere and fix it.

@miq-bot
Copy link
Member

miq-bot commented Jul 8, 2017

This issue has been automatically marked as stale because it has not been updated for at least 6 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions!

@miq-bot miq-bot added the stale label Jul 8, 2017
@JPrause
Copy link
Member

JPrause commented Jan 16, 2019

@mzazrivec looks like this issue has been open for some time and is now stale.
If this issue can be closed, can you do so.
Otherwise, if you'd like it to stay open, please remove the stale label.

@JPrause
Copy link
Member

JPrause commented Jan 21, 2019

@miq_bot close_issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants