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

Bundling Httparty results in ArgumentError: bad argument (expected URI object or URI string) #782

Open
anderson-lee opened this issue Apr 28, 2023 · 1 comment

Comments

@anderson-lee
Copy link

Hi all,

I am trying to make a personal website hosted on github using jekyll and the al-folio template, which uses httparty as one of the required gems. I first running bundle install (which installs all of the required gems correctly), I then run bundle exec jekyll serve, which throws the error /path-to-ruby/httparty/request.rb:87:in `path=': bad argument (expected URI object or URI string) (ArgumentError).

I am using ruby version 3.2.0, jekyll 4.3.2, and httparty 0.21.0. I am on an M1 chip with OSX Ventura 13.3.1. The output for gem env is this:
RubyGems Environment:

  • RUBYGEMS VERSION: 3.4.10
  • RUBY VERSION: 3.2.2 (2023-03-30 patchlevel 53) [arm64-darwin21]
  • INSTALLATION DIRECTORY: /opt/homebrew/lib/ruby/gems/3.2.0
  • USER INSTALLATION DIRECTORY: /Users/andersen/.gem/ruby/3.2.0
  • RUBY EXECUTABLE: /opt/homebrew/opt/ruby/bin/ruby
  • GIT EXECUTABLE: /usr/bin/git
  • EXECUTABLE DIRECTORY: /opt/homebrew/lib/ruby/gems/3.2.0/bin
  • SPEC CACHE DIRECTORY: /Users/andersen/.gem/specs
  • SYSTEM CONFIGURATION DIRECTORY: /opt/homebrew/Cellar/ruby/3.2.2/etc
  • RUBYGEMS PLATFORMS:
    • ruby
    • arm64-darwin-21
  • GEM PATHS:
    • /opt/homebrew/lib/ruby/gems/3.2.0
    • /Users/andersen/.gem/ruby/3.2.0
    • /opt/homebrew/Cellar/ruby/3.2.2/lib/ruby/gems/3.2.0
  • GEM CONFIGURATION:
    • :update_sources => true
    • :verbose => true
    • :backtrace => true
    • :bulk_threshold => 1000
  • REMOTE SOURCES:
  • SHELL PATH:
    • /usr/local/opt/ruby/bin
    • /usr/local/lib/ruby/gems/3.2.2/bin
    • /opt/homebrew/opt/ruby/bin
    • /Users/andersen/opt/anaconda3/bin
    • /Users/andersen/opt/anaconda3/condabin
    • /opt/homebrew/bin
    • /opt/homebrew/sbin
    • /opt/homebrew/bin
    • /opt/homebrew/sbin
    • /opt/local/bin
    • /opt/local/sbin
    • /Library/Frameworks/Python.framework/Versions/3.10/bin
    • /usr/local/bin
    • /System/Cryptexes/App/usr/bin
    • /usr/bin
    • /bin
    • /usr/sbin
    • /sbin
    • /Library/Apple/usr/bin
    • /var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin
    • /var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin
    • /var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin

If you have any suggestions, please let me know. Thanks in advance!

@JonMidhir
Copy link
Contributor

@anderson-lee Looks like a bug in that particular template implementation. There is a workaround though: alshedivat/al-folio#1043

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

No branches or pull requests

3 participants
@JonMidhir @anderson-lee and others