full360

Not sure if we have the time for that

or if it’ll complicate things. An alternative can be to define different versions of the same card definition and send those whenever is necessary: A first version without the bonusPoints/previousAmount with a date range that ends the moment the next version (the one containing the bonusPoints and/or the previousAmount) should be sent to the users. We can do that instead of adding stuff on the delivery process that could complicate it.

+ if (response.response.getStatus != ClientResponse.

SUCCESS

[INFO] BUILD

SUCCESS

not sure if this has some special requisites

or cosiderations associated.

[INFO] BUILD

SUCCESS

not sure if the :cookie: are “only” aged

or turned in :hankey:

not sure if @vianel (who is in charge of the API on our side) has some consideration

or what is the size of the column in VoltDB: As VoltDB is in memory we tend to be conservative with sizing, despite we never had problems with the footprint.

[INFO] BUILD

SUCCESS

not sure if it's a whitelisting issue

or we're just using a bad token

not sure if it's a whitelisting issue

or maybe a token thing

not sure if events are going to be handled through websockets as well, or if that’ll be delegated to the native app,

or if we will continue using the current endpoints...

not sure if incremental

or different for something like 4 weeks.

voltdb_tests_1 | [INFO] BUILD

SUCCESS

not sure if that was about the position of the AUD input

or if it was something that should happen when the container is resized

not sure if we should ask Paul via email

or if you can help us out there :joy:… It’s about the format, content and encryption of those csv files we’ll be generating