~acdw/bollux#1: Unknown response code: .

This happens with every URI I tried:

$ LC_ALL=C.UTF-8 ./bollux -v gemini://gemini.circumlunar.space/ bollux: bollux_config bollux: Can't load config file '/home/tastytea/.config/bollux/config'. bollux: blastoff gemini://gemini.circumlunar.space/ bollux: request_url gemini.circumlunar.space 1965 gemini://gemini.circumlunar.space/ bollux: handle_response gemini://gemini.circumlunar.space/ bollux: [] bollux: ./bollux: line 38: exit: 100 Unknown response code: .: numeric argument required

-- Get my PGP key with gpg --locate-keys tastytea@tastytea.de or at https://tastytea.de/tastytea.asc.

Status: RESOLVED FIXED
Submitter: tastytea
Assigned to: ~acdw
Submitted: 4 years ago
Updated: 4 years ago
Labels: No labels applied.

tastytea 4 years ago · edit

It seems my mail got processed by markdown, let's try again:

$ LC_ALL=C.UTF-8 ./bollux -v gemini://gemini.circumlunar.space/
bollux: bollux_config
bollux: Can't load config file '/home/tastytea/.config/bollux/config'.
bollux: blastoff gemini://gemini.circumlunar.space/
bollux: request_url gemini.circumlunar.space 1965 gemini://gemini.circumlunar.space/ 
bollux: handle_response gemini://gemini.circumlunar.space/ 
bollux: [] 
bollux: 
./bollux: line 38: exit: 100 Unknown response code: .: numeric argument required

~acdw assigned ~acdw 4 years ago

~acdw 4 years ago

Hey tastytea, could you post the output when run with -v ? I'm thinking it's probably the munge_url function, because that's given me trouble. Turns out URLs are hard.

Thanks for testing!

~acdw 4 years ago

OKAY, so I figured out the problem. Dummy me used the wrong character to separate the server and the port name in the openssl invocation. I get home at 6PM CDT tonight so I can fix it them. I'll mark this resolved at that time.

~acdw 4 years ago

(OH also: I realized you sent me the bollux -v output -- I'm sorry I didn't notice!)

~acdw REPORTED FIXED 4 years ago

Fixed. With the smallest diff ever. Thanks again for bringing it to my attention :)