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

Rollbar module broken? #507

Closed
International opened this issue Jul 18, 2019 · 6 comments · Fixed by #513
Closed

Rollbar module broken? #507

International opened this issue Jul 18, 2019 · 6 comments · Fixed by #513

Comments

@International
Copy link
Contributor

What's broken?

Hello, been trying to configure the rollbar module. Nothing gets displayed, and after adding some logs, it looks like the refreshInterval parameter is not being configured.

Shouldn't the last call from widget.Refresh not be to Refresh, but perhaps widget.Render instead?

Thanks

@senorprogrammer
Copy link
Collaborator

Can you paste a copy of your config for Rollbar (redacting any API credentials etc. if necessary). I don't use Rollbar but might be able to help. It's also entirely possible that module is broken.

@International
Copy link
Contributor Author

I just took the default one, and changed the accessToken, projectOwner and projectOwner. If you would like to debug it, you could change this in client.CurrentActiveItems:


func CurrentActiveItems(accessToken, assignedToName string, activeOnly bool) (*ActiveItems, error) {
	items := &ActiveItems{}

	rollbarAPIURL.Host = "api.rollbar.com"
	rollbarAPIURL.Path = "/api/1/items"
	//resp, err := rollbarItemRequest(accessToken, assignedToName, activeOnly)
	//if err != nil {
	//	return items, err
	//}
	//
	//parseJSON(&items, resp.Body)
	items.Results.Items = []Item{
		{Environment: "prod", Title: "show me", },
	}

	return items, nil
}

so that you wouldn't need to do an actual network call. It's how I was debugging also.

Seanstoppable added a commit to Seanstoppable/wtf that referenced this issue Jul 21, 2019
We should be calling Render after a refresh, not calling refresh for an infinite loop
Fixes wtfutil#507
@Seanstoppable
Copy link
Collaborator

You are correct that we should be calling Render rather than having Refresh call itself. I've opened up a PR, but I don't have rollbar myself to test @International

@International
Copy link
Contributor Author

International commented Jul 21, 2019 via email

@senorprogrammer
Copy link
Collaborator

Waiting for verification before closing this issue

@International
Copy link
Contributor Author

I can confirm it works. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

3 participants