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

NullPointerException thrown when listing events #82

Open
jeffreyzupka opened this issue Aug 1, 2014 · 5 comments
Open

NullPointerException thrown when listing events #82

jeffreyzupka opened this issue Aug 1, 2014 · 5 comments
Labels

Comments

@jeffreyzupka
Copy link

The following code is intermittently throwing an NPE from this line when listing events. We are using v1.2 of the client.

for (Event event : new Event.Collection(Event.resource_href + "?type=credit.failed")) {
@mjallday mjallday added the bug label Aug 1, 2014
@remear
Copy link
Contributor

remear commented Aug 1, 2014

I suspect this is due to an API timeout. We'd welcome a pull request to fix it if you have some time.

However, I recommend using a Callback and listing for Events instead of polling /events.

@mjallday
Copy link
Contributor

mjallday commented Aug 1, 2014

this is the endpoint that we're seeing 502s on so I think you're correct @remear.

i've got a fix coming for the timeouts but i agree with @remear the callback method is the better way to resolve this and means not having to wait for a fix which is still a few days away.

@jeffreyzupka let us know if you want a hand understanding how callbacks work. https://docs.balancedpayments.com/1.1/api/callbacks/#create-a-callback

@jeffreyzupka
Copy link
Author

@remear @mjallday Thanks for the response. We already have a task in our backlog to convert to using callbacks, but it's unlikely that it will get started in the next few days. I'll see what I can do about reprioritizing it, though.

@jeffreyzupka
Copy link
Author

@mjallday We haven't seen this issue in 11 days, so I assume a fix has been deployed?

@mjallday
Copy link
Contributor

Hey @jeffreyzupka. Nope, nothing's changed on our end. We're almost complete with the internal migration required to fix the issue but I still see 502 timeouts on that endpoint frequently.

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

No branches or pull requests

3 participants