Code Monkey home page Code Monkey logo

tremendous-ruby's People

Contributors

bpless avatar brianstorti avatar kapilkale avatar nbaum5 avatar raza-kh avatar ricksuggs avatar sevenmaxis avatar walski avatar zhuravel avatar

Stargazers

avatar avatar avatar avatar avatar

Watchers

avatar avatar avatar avatar avatar avatar avatar avatar

Forkers

blueridgelabs talkable datacamp-engineering chadiso juliendefrance waveofphase surprise-hr opensourceame benknowles loldlm1 mfrantz211 alexliedtke ricksuggs curiousalways

tremendous-ruby's Issues

Webhook events enumerated

Hi!

Is there a list of the web hook events sent, and what they mean? On the TestFlight server, I'm only receiving ORDERS.CREATED events. It would be tremendously helpful to get events on rewards delivered, opened/viewed, redeemed, cancelled, etc.

Thanks!

Error parsing response

I'm occasionally getting this error making requests to both production and sandbox:
unexpected token at 'Retry later (JSON::ParserError)

It looks as if the API response is unhandled by this gem. I have retry logic in my implementation, so it would be useful for the gem to surface when your service would like the retry to occur or at least handle the response in a way that isn't a JSON parse error.

Thanks!

[RubyGem] Bump Active Support Dependency

According to this:

GHSA-2p68-f74v-9wc6

we should be using Rails versions

= 5.0.0, <= 5.2.4.2 or
= 6.0.0, <= 6.0.3 | 6.0.3.1

It appears Tremendous is currently only supported with activesupport >= 3.2, <= 5.2.3, even though the gemspec is pointing to 'activesupport', '>= 3.2', '<= 6.0.0.rc1'

JSON parse error in response

Sometimes, Tremendous sends down what appears to be HTML instead of a JSON response. This happens when we try to create an order. There doesn't seem to be any recognizable pattern other than sometimes it just fails. We receive this error:

JSON::ParserError (783: unexpected token at '<!DOCTYPE html>

Unfortunately, this in turn breaks our API handling. I've included a rescue StandardError block around this create! call, but this is not hit and instead the entire process is killed, returning a 500 back to our clients.

This seems similar to #8 but I think perhaps deserves a more fundamental fix is needed.

Please advise, thank you!

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.