Exception: header content contains invalid character '\n' (ArgumentError)

[ghost]

[development] Kemal is ready to lead at http://0.0.0.0:3000

2017-02-16 07:12:32 +0100 304 GET /images/7_of_clubs.png 5.22ms
2017-02-16 07:12:32 +0100 304 GET /images/queen_of_spades.png 95.0µs
2017-02-16 07:12:32 +0100 200 GET /css/style.css 3.45ms
2017-02-16 07:12:32 +0100 304 GET /images/10_of_clubs.png 71.0µs
2017-02-16 07:12:32 +0100 304 GET /images/6_of_hearts.png 50.0µs
2017-02-16 07:12:32 +0100 304 GET /images/4_of_spades.png 50.0µs
2017-02-16 07:12:32 +0100 200 GET /cardgame/b 13.78ms
Exception: header content contains invalid character '\n' (ArgumentError)
0x106744eb2: *CallStack::unwind:Array(Pointer(Void)) at ??
0x106744e51: *CallStack#initialize:Array(Pointer(Void)) at ??
0x106744e28: *CallStack::new:CallStack at ??
0x1066d89d1: *raise<ArgumentError>:NoReturn at ??
0x1067cd497: *HTTP::Headers#check_invalid_header_content<String>:Nil at ??
0x1067cd382: *HTTP::Headers#[]=<HTTP::Headers::Key, Array(String)>:Array(String) at ??
0x1067cd326: *HTTP::Headers#[]=<String, String>:Array(String) at ??
0x1067c73a3: *HTTP::Server::Response#content_type=<String>:Array(String) at ??
0x10673c80b: ~procProc(HTTP::Server::Context, String)@lib/lattice-core/src/lattice-core/application.cr:7 at ??
0x10673c66f: ~procProc(HTTP::Server::Context, String)@lib/kemal/src/kemal/route.cr:11 at ??
0x1068112bb: *Kemal::RouteHandler#process_request<HTTP::Server::Context>:String at ??
0x1068111c9: *Kemal::RouteHandler#call<HTTP::Server::Context>:String at ??
0x10682daa8: *Kemal::WebSocketHandler@HTTP::Handler#call_next<HTTP::Server::Context>:(Bool | File::PReader | HTTP::Server::Context | HTTP::Server::Response | HTTP::Server::Response::Output | IO::FileDescriptor+ | Int32 | String | UInt64 | Nil) at ??
0x10682d532: *Kemal::WebSocketHandler#call<HTTP::Server::Context>:(Bool | File::PReader | HTTP::Server::Context | HTTP::Server::Response | HTTP::Server::Response::Output | IO::FileDescriptor+ | Int32 | String | UInt64 | Nil) at ??
0x106833a07: *Kemal::StaticFileHandler@HTTP::Handler#call_next<HTTP::Server::Context>:(Bool | File::PReader | HTTP::Server::Context | HTTP::Server::Response | HTTP::Server::Response::Output | IO::FileDescriptor+ | Int32 | String | UInt64 | Nil) at ??
0x106832e9b: *Kemal::StaticFileHandler#call<HTTP::Server::Context>:(Bool | File::PReader | HTTP::Server::Context | HTTP::Server::Response | HTTP::Server::Response::Output | IO::FileDescriptor+ | Int32 | String | UInt64 | Nil) at ??
0x1068320ff: *Kemal::CommonExceptionHandler@HTTP::Handler#call_next<HTTP::Server::Context>:(Bool | File::PReader | HTTP::Server::Context | HTTP::Server::Response | HTTP::Server::Response::Output | IO::FileDescriptor+ | Int32 | String | UInt64 | Nil) at ??
0x106831c40: *Kemal::CommonExceptionHandler#call<HTTP::Server::Context>:(Bool | File::PReader | HTTP::Server::Context | HTTP::Server::Response | HTTP::Server::Response::Output | IO::FileDescriptor+ | Int32 | String | UInt64 | Nil) at ??
0x106831226: *Kemal::CommonLogHandler@HTTP::Handler#call_next<HTTP::Server::Context>:(Bool | File::PReader | HTTP::Server::Context | HTTP::Server::Response | HTTP::Server::Response::Output | IO::FileDescriptor+ | Int32 | String | UInt64 | Nil) at ??
0x10682ed3d: *Kemal::CommonLogHandler#call<HTTP::Server::Context>:HTTP::Server::Context at ??
0x106810abe: *Kemal::InitHandler@HTTP::Handler#call_next<HTTP::Server::Context>:(Bool | File::PReader | HTTP::Server::Context | HTTP::Server::Response | HTTP::Server::Response::Output | IO::FileDescriptor+ | Int32 | String | UInt64 | Nil) at ??
0x10681070a: *Kemal::InitHandler#call<HTTP::Server::Context>:(Bool | File::PReader | HTTP::Server::Context | HTTP::Server::Response | HTTP::Server::Response::Output | IO::FileDescriptor+ | Int32 | String | UInt64 | Nil) at ??
0x1068a4329: *HTTP::Server::RequestProcessor#process<(OpenSSL::SSL::Socket::Server | TCPSocket+), (OpenSSL::SSL::Socket::Server | TCPSocket+), IO::FileDescriptor>:Nil at ??
0x1068a3d25: *HTTP::Server::RequestProcessor#process<(OpenSSL::SSL::Socket::Server | TCPSocket+), (OpenSSL::SSL::Socket::Server | TCPSocket+)>:Nil at ??
0x10689eaa6: *HTTP::Server#handle_client<(TCPSocket+ | Nil)>:Nil at ??
0x106742a86: ~procProc(Nil)@/usr/local/Cellar/crystal-lang/0.20.5_2/src/http/server.cr:148 at ??
0x10674f844: *Fiber#run:(IO::FileDescriptor | Nil) at ??
0x1066e81d9: ~proc2Proc(Fiber, (IO::FileDescriptor | Nil))@/usr/local/Cellar/crystal-lang/0.20.5_2/src/fiber.cr:29 at ??

2017-02-16 07:12:32 +0100 500 GET /js/app.js 100.62ms
2017-02-16 07:12:32 +0100 200 GET /images/5_of_hearts.png 1.96ms
2017-02-16 07:12:32 +0100 200 GET /images/6_of_clubs.png 706.0µs
2017-02-16 07:12:32 +0100 200 GET /images/ace_of_spades.png 870.0µs
2017-02-16 07:12:32 +0100 200 GET /images/2_of_hearts.png 494.0µs
subscribe message
#<CardGame::MasterObserver:0x107eeb480>
subscribe message
#<CardGame::CardGame:0x106e90280

No event seems to be emitted when interacting. (Tried on jasonl99/md_live too; got the same error; apparently no event emitted from the client; haven't dug deeper).

[jasonl99]

Thanks...I have a pretty big update coming that really cleans up dom element handling. I hope it clears up some stuff, but the error you're showing is something I haven't seen before, and I don't see any of card_game or lattice_core in that trace. I will definitely see what I can find. Thanks for the report!

[ghost]

Thank you Jason!

On 16 Feb 2017, at 07:52, jasonl99 notifications@github.com wrote:

Thanks...I have a pretty big update coming that really cleans up dom element handling. I hope it clears up some stuff, but the error you're showing is something I haven't seen before, and I don't see any of card_game or lattice_core in that trace. I will definitely see what I can find. Thanks for the report!

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jasonl99/card_game/issues/13#issuecomment-280246970, or mute the thread https://github.com/notifications/unsubscribe-auth/AAnqM5whzGgGsBpMZsk91hjSu0qemXFLks5rc_I4gaJpZM4MCoFj.