Error: Unable to process the following mail with gitlab-ticketing
From time to time, we get an error message from gitlab-ticketing containing a backtrace:
Unable to process the following mail with gitlab-ticketing:
The response is not a valid JSON
/usr/lib/ruby/vendor_ruby/gitlab/request.rb:39:in `rescue in decode'
/usr/lib/ruby/vendor_ruby/gitlab/request.rb:37:in `decode'
/usr/lib/ruby/vendor_ruby/gitlab/request.rb:18:in `parse'
/usr/lib/ruby/vendor_ruby/gitlab/request.rb:12:in `block in <class:Request>'
/usr/lib/ruby/vendor_ruby/httparty/request.rb:391:in `parse_response'
/usr/lib/ruby/vendor_ruby/httparty/request.rb:359:in `block in handle_response'
/usr/lib/ruby/vendor_ruby/httparty/response.rb:25:in `parsed_response'
/usr/lib/ruby/vendor_ruby/gitlab/error.rb:43:in `build_error_message'
/usr/lib/ruby/vendor_ruby/gitlab/error.rb:20:in `initialize'
/usr/lib/ruby/vendor_ruby/gitlab/request.rb:66:in `exception'
/usr/lib/ruby/vendor_ruby/gitlab/request.rb:66:in `raise'
/usr/lib/ruby/vendor_ruby/gitlab/request.rb:66:in `validate'
/usr/lib/ruby/vendor_ruby/gitlab/request.rb:46:in `block (2 levels) in <class:Request>'
/usr/lib/ruby/vendor_ruby/gitlab/client/projects.rb:36:in `project_search'
/var/lib/gems/2.3.0/gems/schleuder-gitlab-ticketing-0.0.1/lib/schleuder-gitlab-ticketing/list.rb:130:in `project'
/var/lib/gems/2.3.0/gems/schleuder-gitlab-ticketing-0.0.1/lib/schleuder-gitlab-ticketing/list.rb:14:in `configured?'
/var/lib/gems/2.3.0/gems/schleuder-gitlab-ticketing-0.0.1/lib/schleuder-gitlab-ticketing/config.rb:19:in `process_list'
/usr/local/lib/schleuder/filters/post_decryption/99_gitlab_ticketing.rb:9:in `gitlab_ticketing'
/usr/lib/ruby/vendor_ruby/schleuder/filters_runner.rb:14:in `block in run'
/usr/lib/ruby/vendor_ruby/schleuder/filters_runner.rb:12:in `map'
/usr/lib/ruby/vendor_ruby/schleuder/filters_runner.rb:12:in `run'
/usr/lib/ruby/vendor_ruby/schleuder/runner.rb:60:in `run_filters'
/usr/lib/ruby/vendor_ruby/schleuder/runner.rb:21:in `run'
/usr/lib/ruby/vendor_ruby/schleuder/cli.rb:35:in `work'
/usr/lib/ruby/vendor_ruby/thor/command.rb:27:in `run'
/usr/lib/ruby/vendor_ruby/thor/invocation.rb:126:in `invoke_command'
/usr/lib/ruby/vendor_ruby/thor.rb:359:in `dispatch'
/usr/lib/ruby/vendor_ruby/thor/base.rb:440:in `start'
/usr/bin/schleuder:13:in `<main>'
This particular mail came from a subscribed list member who doesn't have a corresponding Gitlab account. Not sure whether that's always been the case when we got those error messages in the past (it only happend twice or thrice so far).