ArgumentError - invalid byte sequence in US-ASCII:
/var/lib/gems/2.3.0/gems/sequenceserver-1.0.9/lib/sequenceserver/sequence.rb:197:in split' /var/lib/gems/2.3.0/gems/sequenceserver-1.0.9/lib/sequenceserver/sequence.rb:197:in block in run’
/var/lib/gems/2.3.0/gems/sequenceserver-1.0.9/lib/sequenceserver/sequence.rb:196:in each_line' /var/lib/gems/2.3.0/gems/sequenceserver-1.0.9/lib/sequenceserver/sequence.rb:196:in each’
/var/lib/gems/2.3.0/gems/sequenceserver-1.0.9/lib/sequenceserver/sequence.rb:196:in map' /var/lib/gems/2.3.0/gems/sequenceserver-1.0.9/lib/sequenceserver/sequence.rb:196:in run’
/var/lib/gems/2.3.0/gems/sequenceserver-1.0.9/lib/sequenceserver/sequence.rb:172:in initialize' /var/lib/gems/2.3.0/gems/sequenceserver-1.0.9/lib/sequenceserver/routes.rb:152:in new’
/var/lib/gems/2.3.0/gems/sequenceserver-1.0.9/lib/sequenceserver/routes.rb:152:in block in <class:Routes>' /var/lib/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb:1611:in call’
/var/lib/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb:1611:in block in compile!' /var/lib/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb:975:in block (3 levels) in route!’
/var/lib/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb:994:in route_eval' /var/lib/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb:975:in block (2 levels) in route!’
/var/lib/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb:1015:in block in process_route' /var/lib/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb:1013:in catch’
/var/lib/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb:1013:in process_route' /var/lib/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb:973:in block in route!’
/var/lib/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb:972:in each' /var/lib/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb:972:in route!’
/var/lib/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb:1085:in block in dispatch!' /var/lib/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb:1067:in block in invoke’
/var/lib/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb:1067:in catch' /var/lib/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb:1067:in invoke’
/var/lib/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb:1082:in dispatch!' /var/lib/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb:907:in block in call!’
/var/lib/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb:1067:in block in invoke' /var/lib/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb:1067:in catch’
/var/lib/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb:1067:in invoke' /var/lib/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb:907:in call!’
/var/lib/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb:895:in call' /var/lib/gems/2.3.0/gems/rack-1.6.5/lib/rack/head.rb:13:in call’
/var/lib/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb:182:in call' /var/lib/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb:2013:in call’
/var/lib/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb:1487:in block in call' /var/lib/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb:1787:in synchronize’
/var/lib/gems/2.3.0/gems/sinatra-1.4.8/lib/sinatra/base.rb:1487:in call' /var/lib/gems/2.3.0/gems/sequenceserver-1.0.9/lib/sequenceserver.rb:92:in call’
/usr/lib/ruby/vendor_ruby/phusion_passenger/rack/thread_handler_extension.rb:97:in process_request' /usr/lib/ruby/vendor_ruby/phusion_passenger/request_handler/thread_handler.rb:152:in accept_and_process_next_request’
/usr/lib/ruby/vendor_ruby/phusion_passenger/request_handler/thread_handler.rb:113:in main_loop' /usr/lib/ruby/vendor_ruby/phusion_passenger/request_handler.rb:416:in block (3 levels) in start_threads’
/usr/lib/ruby/vendor_ruby/phusion_passenger/utils.rb:113:in `block in create_thread_and_abort_on_exception’
Hi,
This happens when there is * or - in the database sequences. If you searched a protein database when you got this error, it’s most likely * indicating translation stop.
It’s a bug in BLAST really. We have a workaround in the version 2.0 beta. But one can argue that there shouldn’t be * or - in database sequences.
Could you please inform maintainers of pristionchus.org about this error and request them to remove * from the affected files. That will resolve the issue.
Priyam