From: Horacio Sanson <hsanson@gmail.com>
To: Sup developer discussion <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Cannot query Japanese characters
Date: Mon, 2 May 2011 00:35:28 +0900 [thread overview]
Message-ID: <BANLkTim9PigP91LaDQ6UG2_prxncYv1zEA@mail.gmail.com> (raw)
In-Reply-To: <1304052708-sup-4240@masanjin.net>
Installed whistelpig 0.6 but now I get a different error that looks
similar to the turnsole problem. Below the backtrace:
http://localhost:8042/search?q=primo -> /search?q=%7Einbox&start=0&num=20
127.0.0.1 - - [02/May/2011 00:31:58] "GET /favicon.ico HTTP/1.1" 404 447 0.0008
localhost - - [02/May/2011:00:31:58 JST] "GET /favicon.ico HTTP/1.1" 404 447
- -> /favicon.ico
search(body:"会", 0, 20) took 0.0ms
Encoding::CompatibilityError - incompatible character encodings: UTF-8
and ASCII-8BIT:
bin/heliotrope-server:154:in `block in <class:HeliotropeServer>'
/var/lib/gems/1.9.1/gems/sinatra-1.2.5/lib/sinatra/base.rb:1152:in `call'
/var/lib/gems/1.9.1/gems/sinatra-1.2.5/lib/sinatra/base.rb:1152:in
`block in compile!'
/var/lib/gems/1.9.1/gems/sinatra-1.2.5/lib/sinatra/base.rb:724:in
`instance_eval'
/var/lib/gems/1.9.1/gems/sinatra-1.2.5/lib/sinatra/base.rb:724:in `route_eval'
/var/lib/gems/1.9.1/gems/sinatra-1.2.5/lib/sinatra/base.rb:708:in
`block (2 levels) in route!'
/var/lib/gems/1.9.1/gems/sinatra-1.2.5/lib/sinatra/base.rb:758:in
`block in process_route'
/var/lib/gems/1.9.1/gems/sinatra-1.2.5/lib/sinatra/base.rb:755:in `catch'
/var/lib/gems/1.9.1/gems/sinatra-1.2.5/lib/sinatra/base.rb:755:in
`process_route'
/var/lib/gems/1.9.1/gems/sinatra-1.2.5/lib/sinatra/base.rb:707:in
`block in route!'
/var/lib/gems/1.9.1/gems/sinatra-1.2.5/lib/sinatra/base.rb:706:in `each'
/var/lib/gems/1.9.1/gems/sinatra-1.2.5/lib/sinatra/base.rb:706:in `route!'
/var/lib/gems/1.9.1/gems/sinatra-1.2.5/lib/sinatra/base.rb:843:in `dispatch!'
/var/lib/gems/1.9.1/gems/sinatra-1.2.5/lib/sinatra/base.rb:644:in
`block in call!'
/var/lib/gems/1.9.1/gems/sinatra-1.2.5/lib/sinatra/base.rb:808:in
`instance_eval'
/var/lib/gems/1.9.1/gems/sinatra-1.2.5/lib/sinatra/base.rb:808:in
`block in invoke'
/var/lib/gems/1.9.1/gems/sinatra-1.2.5/lib/sinatra/base.rb:808:in `catch'
/var/lib/gems/1.9.1/gems/sinatra-1.2.5/lib/sinatra/base.rb:808:in `invoke'
/var/lib/gems/1.9.1/gems/sinatra-1.2.5/lib/sinatra/base.rb:644:in `call!'
/var/lib/gems/1.9.1/gems/sinatra-1.2.5/lib/sinatra/base.rb:629:in `call'
/var/lib/gems/1.9.1/gems/rack-1.2.2/lib/rack/head.rb:9:in `call'
/var/lib/gems/1.9.1/gems/sinatra-1.2.5/lib/sinatra/showexceptions.rb:21:in
`call'
/var/lib/gems/1.9.1/gems/rack-1.2.2/lib/rack/lint.rb:48:in `_call'
/var/lib/gems/1.9.1/gems/rack-1.2.2/lib/rack/lint.rb:36:in `call'
/var/lib/gems/1.9.1/gems/rack-1.2.2/lib/rack/showexceptions.rb:24:in `call'
/var/lib/gems/1.9.1/gems/rack-1.2.2/lib/rack/commonlogger.rb:18:in `call'
/var/lib/gems/1.9.1/gems/rack-1.2.2/lib/rack/content_length.rb:13:in `call'
/var/lib/gems/1.9.1/gems/rack-1.2.2/lib/rack/handler/webrick.rb:52:in `service'
/usr/lib/ruby/1.9.1/webrick/httpserver.rb:111:in `service'
/usr/lib/ruby/1.9.1/webrick/httpserver.rb:70:in `run'
/usr/lib/ruby/1.9.1/webrick/server.rb:183:in `block in start_thread'
127.0.0.1 - - [02/May/2011 00:32:09] "GET /search?q=%E4%BC%9A
HTTP/1.1" 500 89861 0.0228
localhost - - [02/May/2011:00:32:09 JST] "GET /search?q=%E4%BC%9A
HTTP/1.1" 500 89861
http://localhost:8042/search?q=%7Einbox&start=0&num=20 -> /search?q=%E4%BC%9A
127.0.0.1 - - [02/May/2011 00:32:09] "GET /favicon.ico HTTP/1.1" 404 447 0.0009
localhost - - [02/May/2011:00:32:09 JST] "GET /favicon.ico HTTP/1.1" 404 447
- -> /favicon.ico
regards,
Horacio
On Fri, Apr 29, 2011 at 1:52 PM, William Morgan
<wmorgan-sup@masanjin.net> wrote:
> Reformatted excerpts from William Morgan's message of 2011-04-26:
>> Thanks for the bug report on this one too. It's great to have someone
>> testing this stuff with non-ASCII code. This is a known bug in
>> Whistlepig and I should be releasing a fix soon.
>
> This is fixed in Whistlepig 0.6. Heliotrope should now be fine with
> utf-8 input. I'm still working on this issue in turnsole.
>
> Let me know if you have any more issues!
> --
> William <wmorgan-sup@masanjin.net>
> _______________________________________________
> Sup-devel mailing list
> Sup-devel@rubyforge.org
> http://rubyforge.org/mailman/listinfo/sup-devel
>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2011-05-01 15:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 1:23 Horacio Sanson
2011-04-26 4:49 ` William Morgan
2011-04-29 4:52 ` William Morgan
2011-05-01 15:35 ` Horacio Sanson [this message]
2011-05-01 15:46 ` Horacio Sanson
2011-05-03 14:24 ` Horacio Sanson
2011-05-03 22:26 ` William Morgan
2011-05-04 1:42 ` Horacio Sanson
2011-05-04 2:03 ` Horacio Sanson
2011-05-04 16:56 ` William Morgan
2011-05-06 3:30 ` Horacio Sanson
2011-06-08 5:21 ` William Morgan
2011-06-09 13:48 ` Horacio Sanson
2011-06-09 14:08 ` Horacio Sanson
2011-06-09 22:46 ` William Morgan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BANLkTim9PigP91LaDQ6UG2_prxncYv1zEA@mail.gmail.com \
--to=hsanson@gmail.com \
--cc=sup-devel@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox