In my docker container, running asciidoctor -r asciidoctor-plantuml my_doc.adoc gets me asciidoctor: FAILED: 'asciidoctor-plantuml' could not be loaded.
To reproduce the issue:
$ docker run -it -v $WHERE_ADOCS:/documents/ asciidoctor/docker-asciidoctor
77687352778d:/documents# asciidoctor -r asciidoctor-plantuml --trace my_doc.adoc
from <internal:/usr/lib/ruby/3.1.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
from /usr/lib/ruby/gems/3.1.0/gems/asciidoctor-2.0.18/lib/asciidoctor/cli/options.rb:281:in `block in parse!'
from /usr/lib/ruby/gems/3.1.0/gems/asciidoctor-2.0.18/lib/asciidoctor/cli/options.rb:279:in `each'
from /usr/lib/ruby/gems/3.1.0/gems/asciidoctor-2.0.18/lib/asciidoctor/cli/options.rb:279:in `parse!'
from /usr/lib/ruby/gems/3.1.0/gems/asciidoctor-2.0.18/lib/asciidoctor/cli/options.rb:34:in `parse!'
from /usr/lib/ruby/gems/3.1.0/gems/asciidoctor-2.0.18/lib/asciidoctor/cli/invoker.rb:24:in `initialize'
from /usr/lib/ruby/gems/3.1.0/gems/asciidoctor-2.0.18/bin/asciidoctor:13:in `new'
from /usr/lib/ruby/gems/3.1.0/gems/asciidoctor-2.0.18/bin/asciidoctor:13:in `<top (required)>'
from /usr/bin/asciidoctor:25:in `load'
from /usr/bin/asciidoctor:25:in `<main>'```
with the result like above. I've been following this README of plantuml extention for asciidoctor.
Do I need to start the plantuml-server for generating the .html?
11:34 $ docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
plantuml/plantuml-server jetty 92b40d953f4e 3 weeks ago 410MB
asciidoctor/docker-asciidoctor latest dc8b75bfd089 4 weeks ago 685MB
so both images exists in my local. Is there anything I miss?
Any hint is appreciated....
Instead of using asciidoctor-plantuml, asciidoctor-diagram works flawless:
77687352778d:/documents# asciidoctor -r asciidoctor-diagram my_doc.adoc
with the expected my_doc.html with the embedded plantuml being generated.
Related
when i try to create conjure account using the command( I am following conjur quickstart tutorial)
docker-compose exec conjur conjurctl account create myConjurAccount > admin_data
i am getting Cipher error in admin_data file,
when i cat admin_data file
rake aborted!
OpenSSL::Cipher::CipherError:
/var/lib/gems/2.5.0/gems/slosilo-2.1.1/lib/slosilo/symmetric.rb:37:in`final'
/var/lib/gems/2.5.0/gems/slosilo-2.1.1/lib/slosilo/symmetric.rb:37:in `decrypt'
/var/lib/gems/2.5.0/gems/slosilo-2.1.1/lib/slosilo/attr_encrypted.rb:60:in `decrypt'
/var/lib/gems/2.5.0/gems/slosilo-2.1.1/lib/slosilo/attr_encrypted.rb:40:in `block (3 levels) in attr_encrypted'
/var/lib/gems/2.5.0/gems/slosilo-2.1.1/lib/slosilo/adapters/sequel_adapter.rb:32:in `get_key'
/var/lib/gems/2.5.0/gems/slosilo-2.1.1/lib/slosilo/keystore.rb:18:in `get'
/var/lib/gems/2.5.0/gems/slosilo-2.1.1/lib/slosilo/keystore.rb:47:in `[]'
/opt/conjur-server/app/models/account.rb:6:in `find_or_create_accounts_resource'
/opt/conjur-server/lib/tasks/account.rake:15:in `block (2 levels) in <top (required)>'
/var/lib/gems/2.5.0/gems/rake-12.3.2/exe/rake:27:in `<top (required)>'
Tasks: TOP => account:create
(See full trace by running task with --trace)
But sometimes its creating i am not understanding what makes it working in the background. Any help will be appreciated.
and also docker-compose ps showing
bot_app tail -F anything Up
conjur_client sleep infinity Up
conjur_server conjurctl server Up 80/tcp
nginx_proxy nginx -g daemon off; Up 0.0.0.0:8443->443/tcp, 80/tcp
postgres_database docker-entrypoint.sh postgres Up 5432/tcp
openssl openssl req -newkey rsa:20 ... Exit 0
Everytime openssl exiting with 0
I have fixed this issue by removing all stopped containers before running the conjure docker container using docker container prune.
I used to debug test cases in ruby mine for my rails test cases. Some time ago I updated my ruby mine and not sure what happened since then, I am not able to debug my test cases.
Attaching the screenshot of the error below:
What can be done here to rectify this?
Here is the same console output in plain text:
Testing started at 12:53 PM ...
bash -c "/Users/someUSER/.rvm/bin/rvm ruby-2.3.1 do /Users/someUSER/.rvm/rubies/ruby-2.3.1/bin/ruby /Users/someUSER/.rvm/gems/ruby-2.3.1#global/gems/ruby-debug-ide-0.7.0.beta6/bin/rdebug-ide --key-value --disable-int-handler --evaluation-timeout 10 --evaluation-control --time-limit 100 --memory-limit 0 --rubymine-protocol-extensions --port 49496 --host 0.0.0.0 --dispatcher-port 49497 -- /Users/someUSER/.rvm/gems/ruby-2.3.1/bin/rspec /Users/someUSER/RubymineProjects/Proj/spec/controllers/site/some_controller_spec.rb --require teamcity/spec/runner/formatter/teamcity/formatter --format Spec::Runner::Formatter::TeamcityFormatter --example \"Site::SomeController Some POST create new data \""
Fast Debugger (ruby-debug-ide 0.7.0.beta6, debase 0.2.2, file filtering is supported) listens on 0.0.0.0:49496
Uncaught exception: cannot load such file -- rspec/core/formatters/fallback_message_formatter
/Users/someUSER/.rvm/gems/ruby-2.3.1/gems/rspec-core-3.8.0/lib/rspec/core/formatters.rb:132:in `require'
/Users/someUSER/.rvm/gems/ruby-2.3.1/gems/rspec-core-3.8.0/lib/rspec/core/formatters.rb:132:in `setup_default'
/Users/someUSER/.rvm/gems/ruby-2.3.1/gems/rspec-core-3.8.0/lib/rspec/core/reporter.rb:47:in `block in prepare_default'
/Users/someUSER/.rvm/gems/ruby-2.3.1/gems/rspec-core-3.8.0/lib/rspec/core/reporter.rb:228:in `ensure_listeners_ready'
/Users/someUSER/.rvm/gems/ruby-2.3.1/gems/rspec-core-3.8.0/lib/rspec/core/reporter.rb:199:in `notify'
/Users/someUSER/.rvm/gems/ruby-2.3.1/gems/rspec-core-3.8.0/lib/rspec/core/reporter.rb:92:in `message'
/Users/someUSER/.rvm/gems/ruby-2.3.1/gems/rspec-core-3.8.0/lib/rspec/core/reporter.rb:161:in `notify_non_example_exception'
/Users/someUSER/.rvm/gems/ruby-2.3.1/gems/rspec-core-3.8.0/lib/rspec/core/configuration.rb:2037:in `rescue in load_file_handling_errors'
/Users/someUSER/.rvm/gems/ruby-2.3.1/gems/rspec-core-3.8.0/lib/rspec/core/configuration.rb:2034:in `load_file_handling_errors'
/Users/someUSER/.rvm/gems/ruby-2.3.1/gems/rspec-core-3.8.0/lib/rspec/core/configuration.rb:1560:in `block in load_spec_files'
/Users/someUSER/.rvm/gems/ruby-2.3.1/gems/rspec-core-3.8.0/lib/rspec/core/configuration.rb:1558:in `each'
/Users/someUSER/.rvm/gems/ruby-2.3.1/gems/rspec-core-3.8.0/lib/rspec/core/configuration.rb:1558:in `load_spec_files'
/Users/someUSER/.rvm/gems/ruby-2.3.1/gems/rspec-core-3.8.0/lib/rspec/core/runner.rb:98:in `setup'
/Users/someUSER/.rvm/gems/ruby-2.3.1/gems/rspec-core-3.8.0/lib/rspec/core/runner.rb:86:in `run'
/Users/someUSER/.rvm/gems/ruby-2.3.1/gems/rspec-core-3.8.0/lib/rspec/core/runner.rb:71:in `run'
/Users/someUSER/.rvm/gems/ruby-2.3.1/gems/rspec-core-3.8.0/lib/rspec/core/runner.rb:45:in `invoke'
/Users/someUSER/.rvm/gems/ruby-2.3.1/gems/rspec-core-3.8.0/exe/rspec:4:in `<top (required)>'
/Users/someUSER/.rvm/gems/ruby-2.3.1/bin/rspec:23:in `load'
/Users/someUSER/.rvm/gems/ruby-2.3.1/bin/rspec:23:in `<top (required)>'
/Users/someUSER/.rvm/gems/ruby-2.3.1#global/gems/ruby-debug-ide-0.7.0.beta6/bin/rdebug-ide:187:in `<main>'
Process finished with exit code 1
Empty test suite.
I think you are having problems to install the debug gem for RubyMine. I had the same issue and after taking a look at JetBrains web page seems like they are working to fix it on RubyMine 2018.3.3. Meantime, a workaround is to install the gems in a console.
Open the terminal inside RubyMine and run:
gem install debase -v 0.2.3.beta3 --no-document
gem install ruby-debug-ide -v 0.7.0.beta7 --no-document
The beta6 version of the ruby-debug-ide gem that you use is older than rspec 3.8. Maybe upgrading ruby-debug-ide to the latest beta7 version helps (or downgrading rspec to a version older than beta6).
Starting the Ruby thin client works fine in command line:
RAILS_ENV=production bundle exec thin --ssl-disable-verify -C services/private_pub/private_pub_thin.yml start
But starting it as deamon returns a Bad File Descriptor:
user#app:~/app$ RAILS_ENV=production bundle exec thin -d --ssl-disable-verify -C services/private_pub/private_pub_thin.yml start
user#app:~/app$ /opt/rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.12.5/lib/bundler/source/git/git_proxy.rb:149:in ``': Bad file descriptor (Errno::EBADF)
from /opt/rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.12.5/lib/bundler/source/git/git_proxy.rb:149:in `block in git'
from /opt/rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.12.5/lib/bundler/shared_helpers.rb:72:in `call'
from /opt/rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.12.5/lib/bundler/shared_helpers.rb:72:in `with_clean_git_env'
from /opt/rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.12.5/lib/bundler/source/git/git_proxy.rb:149:in `git'
from /opt/rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.12.5/lib/bundler/source/git/git_proxy.rb:83:in `version'
from /opt/rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.12.5/lib/bundler/env.rb:78:in `git_version'
from /opt/rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.12.5/lib/bundler/env.rb:22:in `report'
from /opt/rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.12.5/lib/bundler/friendly_errors.rb:74:in `request_issue_report_for'
from /opt/rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.12.5/lib/bundler/friendly_errors.rb:40:in `log_error'
from /opt/rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.12.5/lib/bundler/friendly_errors.rb:100:in `rescue in with_friendly_errors'
from /opt/rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.12.5/lib/bundler/friendly_errors.rb:98:in `with_friendly_errors'
from /opt/rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.12.5/exe/bundle:19:in `<top (required)>'
from /opt/rbenv/versions/2.2.1/bin/bundle:23:in `load'
from /opt/rbenv/versions/2.2.1/bin/bundle:23:in `<main>'
Any idea? This happened without any code change. There is also nothing already running.
I accidentally ran the command sudo chmod 600 -R / when I meant to do it to sudo chmod 600 -R Documents/some_directory and my macbook pro's file permissions got messed up. I ran sudo chmod 755 -R /directories_that_don't_need_to_be_secure and tried to fix all the permissions. But when I start my Jekyll server jekyll --server --auto I hit a bunch of errors. I made my whole directory readable, writable, and executable. But the error keeps popping up. This is what I get when the jekyll server generates:
Shalin-Shah-Me:shalin shalinvs$ jekyll --server --auto
Configuration from /Users/shalinvs/Documents/Developer/Websites/shalin/_config.yml
/Library/Ruby/Site/1.8/rubygems/custom_require.rb:36:in `gem_original_require': no such file to load -- sass (LoadError)
from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:36:in `require'
from /Users/shalinvs/Documents/Developer/Websites/shalin/_plugins/sass_converter.rb:5
from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:36:in `gem_original_require'
from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:36:in `require'
from /Library/Ruby/Gems/1.8/gems/jekyll-0.12.0/bin/../lib/jekyll/site.rb:78:in `setup'
from /Library/Ruby/Gems/1.8/gems/jekyll-0.12.0/bin/../lib/jekyll/site.rb:77:in `each'
from /Library/Ruby/Gems/1.8/gems/jekyll-0.12.0/bin/../lib/jekyll/site.rb:77:in `setup'
from /Library/Ruby/Gems/1.8/gems/jekyll-0.12.0/bin/../lib/jekyll/site.rb:76:in `each'
from /Library/Ruby/Gems/1.8/gems/jekyll-0.12.0/bin/../lib/jekyll/site.rb:76:in `setup'
from /Library/Ruby/Gems/1.8/gems/jekyll-0.12.0/bin/../lib/jekyll/site.rb:31:in `initialize'
from /Library/Ruby/Gems/1.8/gems/jekyll-0.12.0/bin/jekyll:238:in `new'
from /Library/Ruby/Gems/1.8/gems/jekyll-0.12.0/bin/jekyll:238
from /usr/bin/jekyll:23:in `load'
from /usr/bin/jekyll:23
I have also tried using Disk Utility to repair my permissions but still no luck.
Thanks in advance!
What do you get with this?
gem list sass
Try this:
gem uninstall sass
gem install sass
Then run your jekyll command again.
I accidentally ran the command sudo chmod 600 -R / when I meant to do it to sudo chmod 600 -R Documents/some_directory and my macbook pro's file permissions got messed up. I ran sudo chmod 755 -R /directories_that_don't_need_to_be_secure and tried to fix all the permissions. But when I start my Jekyll server jekyll --server --auto everything is forbidden. I made my whole directory readable, writable, and executable. But the error keeps popping up. This is what I get when the jekyll server generates
Shalin-Shah-Me:shalin shalinvs$ jekyll --server --auto
Configuration from /Users/shalinvs/Documents/Developer/Websites/shalin/_config.yml
/Library/Ruby/Site/1.8/rubygems/custom_require.rb:36:in `gem_original_require': no such file to load -- sass (LoadError)
from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:36:in `require'
from /Users/shalinvs/Documents/Developer/Websites/shalin/_plugins/sass_converter.rb:5
from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:36:in `gem_original_require'
from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:36:in `require'
from /Library/Ruby/Gems/1.8/gems/jekyll-0.12.0/bin/../lib/jekyll/site.rb:78:in `setup'
from /Library/Ruby/Gems/1.8/gems/jekyll-0.12.0/bin/../lib/jekyll/site.rb:77:in `each'
from /Library/Ruby/Gems/1.8/gems/jekyll-0.12.0/bin/../lib/jekyll/site.rb:77:in `setup'
from /Library/Ruby/Gems/1.8/gems/jekyll-0.12.0/bin/../lib/jekyll/site.rb:76:in `each'
from /Library/Ruby/Gems/1.8/gems/jekyll-0.12.0/bin/../lib/jekyll/site.rb:76:in `setup'
from /Library/Ruby/Gems/1.8/gems/jekyll-0.12.0/bin/../lib/jekyll/site.rb:31:in `initialize'
from /Library/Ruby/Gems/1.8/gems/jekyll-0.12.0/bin/jekyll:238:in `new'
from /Library/Ruby/Gems/1.8/gems/jekyll-0.12.0/bin/jekyll:238
from /usr/bin/jekyll:23:in `load'
from /usr/bin/jekyll:23
I have also tried using Disk Utility to repair my permissions but still no luck.
Thanks in advance!
The jekyll command operates on the directory you are currently in. The output in your question shows that you're running it in your home directory. It seems unlikely that that's really where you have your jekyll site stored (especially since it means that jekyll would have to process everything in your home directory each time it runs).
Assuming that you have your jekyll files somewhere else, change to that directory (where you should see the _config.yml and other jekyll files/dirs) and try running the command there.
Disk Utility.app has a Fix Permissions module. Perhaps that would solve it?