Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"geordi commit" fails connecting to Pivotal Tracker #65

Closed
makmic opened this issue Jan 28, 2019 · 3 comments
Closed

"geordi commit" fails connecting to Pivotal Tracker #65

makmic opened this issue Jan 28, 2019 · 3 comments
Assignees

Comments

@makmic
Copy link
Member

makmic commented Jan 28, 2019

Since last week or so, geordi commit does no longer seem to be able connecting to the Pivotal Tracker API.

Backtrace:

Connecting to Pivotal Tracker...
/home/foo/.rbenv/versions/2.3.5/lib/ruby/gems/2.3.0/gems/rest-client-2.0.2/lib/restclient/abstract_response.rb:223:in `exception_with_response': 404 Not Found (RestClient::NotFound)
	from /home/foo/.rbenv/versions/2.3.5/lib/ruby/gems/2.3.0/gems/rest-client-2.0.2/lib/restclient/abstract_response.rb:103:in `return!'
	from /home/foo/.rbenv/versions/2.3.5/lib/ruby/gems/2.3.0/gems/rest-client-2.0.2/lib/restclient/request.rb:809:in `process_result'
	from /home/foo/.rbenv/versions/2.3.5/lib/ruby/gems/2.3.0/gems/rest-client-2.0.2/lib/restclient/request.rb:725:in `block in transmit'
	from /home/foo/.rbenv/versions/2.3.5/lib/ruby/2.3.0/net/http.rb:853:in `start'
	from /home/foo/.rbenv/versions/2.3.5/lib/ruby/gems/2.3.0/gems/rest-client-2.0.2/lib/restclient/request.rb:715:in `transmit'
	from /home/foo/.rbenv/versions/2.3.5/lib/ruby/gems/2.3.0/gems/rest-client-2.0.2/lib/restclient/request.rb:145:in `execute'
	from /home/foo/.rbenv/versions/2.3.5/lib/ruby/gems/2.3.0/gems/rest-client-2.0.2/lib/restclient/request.rb:52:in `execute'
	from /home/foo/.rbenv/versions/2.3.5/lib/ruby/gems/2.3.0/gems/rest-client-2.0.2/lib/restclient/resource.rb:51:in `get'
	from /home/foo/.rbenv/versions/2.3.5/lib/ruby/gems/2.3.0/gems/pivotal-tracker-0.5.13/lib/pivotal-tracker/project.rb:14:in `find'
	from /home/foo/.rbenv/versions/2.3.5/lib/ruby/gems/2.3.0/gems/geordi-1.6.5/lib/geordi/gitpt.rb:107:in `block (2 levels) in load_projects'
	from /home/foo/.rbenv/versions/2.3.5/lib/ruby/gems/2.3.0/gems/geordi-1.6.5/lib/geordi/gitpt.rb:106:in `collect'
	from /home/foo/.rbenv/versions/2.3.5/lib/ruby/gems/2.3.0/gems/geordi-1.6.5/lib/geordi/gitpt.rb:106:in `block in load_projects'
	from /home/foo/.rbenv/versions/2.3.5/lib/ruby/gems/2.3.0/gems/geordi-1.6.5/lib/geordi/gitpt.rb:45:in `loading'
	from /home/foo/.rbenv/versions/2.3.5/lib/ruby/gems/2.3.0/gems/geordi-1.6.5/lib/geordi/gitpt.rb:105:in `load_projects'
	from /home/foo/.rbenv/versions/2.3.5/lib/ruby/gems/2.3.0/gems/geordi-1.6.5/lib/geordi/gitpt.rb:161:in `run'
	from /home/foo/.rbenv/versions/2.3.5/lib/ruby/gems/2.3.0/gems/geordi-1.6.5/lib/geordi/commands/commit.rb:5:in `commit'
	from /home/foo/.rbenv/versions/2.3.5/lib/ruby/gems/2.3.0/gems/thor-0.20.0/lib/thor/command.rb:27:in `run'
	from /home/foo/.rbenv/versions/2.3.5/lib/ruby/gems/2.3.0/gems/thor-0.20.0/lib/thor/invocation.rb:126:in `invoke_command'
	from /home/foo/.rbenv/versions/2.3.5/lib/ruby/gems/2.3.0/gems/thor-0.20.0/lib/thor.rb:387:in `dispatch'
	from /home/foo/.rbenv/versions/2.3.5/lib/ruby/gems/2.3.0/gems/thor-0.20.0/lib/thor/base.rb:466:in `start'
	from /home/foo/.rbenv/versions/2.3.5/lib/ruby/gems/2.3.0/gems/geordi-1.6.5/bin/geordi:10:in `block in <top (required)>'
	from /home/foo/.rbenv/versions/2.3.5/lib/ruby/gems/2.3.0/gems/geordi-1.6.5/lib/geordi/util.rb:13:in `installing_missing_gems'
	from /home/foo/.rbenv/versions/2.3.5/lib/ruby/gems/2.3.0/gems/geordi-1.6.5/bin/geordi:5:in `<top (required)>'
	from /home/foo/.rbenv/versions/2.3.5/bin/geordi:23:in `load'
	from /home/foo/.rbenv/versions/2.3.5/bin/geordi:23:in `<main>'

Thanks for having a look.

@denzelem denzelem self-assigned this Jan 30, 2019
@smith2martin
Copy link

smith2martin commented Feb 7, 2019

FWIW, I'm using the pivotal-tracker-0.5.13 gem directly and have seen the same behavior starting about the same time. Potentially a place to start your investigation. My stack is identical to yours from pivotal-tracker-0.5.13 upwards.

@smith2martin
Copy link

Again FWIW, the below similarly results in a 404. Possible that Tracker made an API change recently that's causing this -- my tracker / github integration broke about the same time and I had to create a github integration on the tracker side to re-enable it.

curl -X GET -H "X-TrackerToken: $TOKEN" "https://www.pivotaltracker.com/n/projects/XYZ

denzelem added a commit that referenced this issue Feb 14, 2019
@denzelem
Copy link
Contributor

denzelem commented Feb 14, 2019

See jsmestad/pivotal-tracker#122: API V3 and V4 are discontinued. The easiest way would be to migrate to https://github.com/dashofcode/tracker_api, but this drops support for Ruby < 2.1 for geordi commit.

denzelem added a commit that referenced this issue Feb 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants