-
Notifications
You must be signed in to change notification settings - Fork 28
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
tried to create Proc object without a block #32
Comments
I have the same problem on my Arch Linux. Ruby version info: |
I have the same problem on my Alpine Linux 3.16.3. Ruby version info: ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x86_64-linux-musl] |
Same here. |
I have the same issue too:
|
snowe2010, thank you for updating the version of faraday. I'd like to see if my organization can use this before trying Antora. I'm running Windows 10, I installed Ruby 3.2.2.
My organization also uses self-signed certificates. I'm not sure if simple username/password authentication is enabled or if my organization requires OAUTH. When I ran it, I received this error: I tried integrating to handle self-signed certificates #25, but received this error:
|
I have the same issue on Ubuntu 18.04:
Tools versions:
|
Same problem with |
I have the same issue with the |
Also tested on ruby 3.2.0 (2022-12-25 revision a528908271) [arm64-darwin21] and the same error
|
It works with ruby 2.7.7 So it feels like an issue with Ruby 3 |
C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/faraday-0.9.2/lib/faraday/options.rb:153:in
new': tried to create Proc object without a block (ArgumentError) from C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/faraday-0.9.2/lib/faraday/options.rb:153:in
memoized'from C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/faraday-0.9.2/lib/faraday/options.rb:234:in
<class:ProxyOptions>' from C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/faraday-0.9.2/lib/faraday/options.rb:216:in
module:Faraday'from C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/faraday-0.9.2/lib/faraday/options.rb:1:in
<top (required)>' from <internal:C:/Ruby31-x64/lib/ruby/3.1.0/rubygems/core_ext/kernel_require.rb>:85:in
require'from internal:C:/Ruby31-x64/lib/ruby/3.1.0/rubygems/core_ext/kernel_require.rb:85:in
require' from C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/faraday-0.9.2/lib/faraday.rb:80:in
block in require_libs'from C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/faraday-0.9.2/lib/faraday.rb:79:in
each' from C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/faraday-0.9.2/lib/faraday.rb:79:in
require_libs'from C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/faraday-0.9.2/lib/faraday.rb:240:in
<module:Faraday>' from C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/faraday-0.9.2/lib/faraday.rb:16:in
<top (required)>'from internal:C:/Ruby31-x64/lib/ruby/3.1.0/rubygems/core_ext/kernel_require.rb:85:in
require' from <internal:C:/Ruby31-x64/lib/ruby/3.1.0/rubygems/core_ext/kernel_require.rb>:85:in
require'from C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/asciidoctor-confluence-0.0.2/lib/asciidoctor/confluence.rb:6:in
<top (required)>' from C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/asciidoctor-confluence-0.0.2/lib/asciidoctor/confluence/options.rb:2:in
require_relative'from C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/asciidoctor-confluence-0.0.2/lib/asciidoctor/confluence/options.rb:2:in
<top (required)>' from C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/asciidoctor-confluence-0.0.2/lib/asciidoctor/confluence/invoker.rb:4:in
require_relative'from C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/asciidoctor-confluence-0.0.2/lib/asciidoctor/confluence/invoker.rb:4:in
<top (required)>' from <internal:C:/Ruby31-x64/lib/ruby/3.1.0/rubygems/core_ext/kernel_require.rb>:85:in
require'from internal:C:/Ruby31-x64/lib/ruby/3.1.0/rubygems/core_ext/kernel_require.rb:85:in
require' from C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/asciidoctor-confluence-0.0.2/bin/asciidoctor-confluence:4:in
<top (required)>'from C:/Ruby31-x64/bin/asciidoctor-confluence:32:in
load' from C:/Ruby31-x64/bin/asciidoctor-confluence:32:in
The text was updated successfully, but these errors were encountered: