These are chat archives for reactioncommerce/reaction

15th
Jun 2016
Aaron Judd
@aaronjudd
Jun 15 2016 01:32
@valorloff that’s not actually stopping the order is it? seems like it might be trying to update the order before the user is authenticated (even if it’s an anonymous user). I think that might not be a blocking error.. (but we still should log it and fix).
Valery Orloff
@valorloff
Jun 15 2016 05:36
@aaronjudd this error don't stopping order, which is successfully added to orders collection, anonymous user
Himanshu Aggarwal
@haggarwal90
Jun 15 2016 05:55
Does any body know how to use bootstrap-material-deign with reaction commerse?
Valery Orloff
@valorloff
Jun 15 2016 06:20
@aaronjudd I just did not pay attention, cart don't copied to database successfully, after exit from cart order deleted)
Spencer Norman
@spencern
Jun 15 2016 15:34
Is there a good way to turn off the
04:08:36.906Z WARN Reaction: Failed to get currency exchange rates.
really hard to sort through our log files when we have 100 of those lines to every other line that matters
also would be nice to turn off the
04:49:56.567Z INFO Reaction: create cart: shopId J8Bhq3uTtdgwZx3rz
Jeremy Shimko
@jshimko
Jun 15 2016 15:36
You can change the log level to INFO
Spencer Norman
@spencern
Jun 15 2016 15:36
is that an env variable or a setting?
Jeremy Shimko
@jshimko
Jun 15 2016 15:36
Other than that, no. You’d have to remove the logs from the source.
yes
sorry, no it’s a Meteor.settings thing
Spencer Norman
@spencern
Jun 15 2016 15:37
ok, thanks
Jeremy Shimko
@jshimko
Jun 15 2016 15:37
one sec...
but I also don’t think you want to shut off all warning messages for one message. I think it’s probably more reasonable that we consider making that DEBUG level.
I also find isDebug to be a little unclear. It’s implied that it’s a boolean. I think it should probably be a LOG_LEVEL env var (with an optional Meteor.settings version)
Spencer Norman
@spencern
Jun 15 2016 15:40
agree, I’d like to keep most warning messages
Jeremy Shimko
@jshimko
Jun 15 2016 15:42
In the meantime, you could change this…
https://github.com/reactioncommerce/reaction/blob/175d5015612395fdf18be51c8f5a20776413cf63/packages/reaction-core/server/methods/shop.js#L128
to this…
ReactionCore.Log.debug("Failed to get currency exchange rates.");
Spencer Norman
@spencern
Jun 15 2016 15:43
:+1: and the default log level will mute .debug messages?
Jeremy Shimko
@jshimko
Jun 15 2016 15:43
yep
Spencer Norman
@spencern
Jun 15 2016 15:43
That works for now, thanks!
Jeremy Shimko
@jshimko
Jun 15 2016 15:44
Sure. I’ll fix that in the new modules branch, so it’ll be quieter once you get over to that.
Aaron Judd
@aaronjudd
Jun 15 2016 16:16
@jshimko the naming of isDebug is not great, but the idea was if FALSE, no visible logging, or TRUE defaults to info, or set a level.
Jeremy Shimko
@jshimko
Jun 15 2016 16:16
ah. gotcha
Maybe we can do something like LOG_LEVEL and then another var to hide it from stdout altogether?
Aaron Judd
@aaronjudd
Jun 15 2016 16:18
can’t remember but I think isDebug is leftover from some earlier Meteor settings… I think that used to be a ENV var..
Jeremy Shimko
@jshimko
Jun 15 2016 16:19
The message he’s getting above is a tough one too. I’d hate to change something to debug that you probably want to know about. Maybe we can build an optional throttle into warn messages.
So it only warns once per X amount of time.
(configurable)
Spencer Norman
@spencern
Jun 15 2016 16:22
yeah, I don’t mind the message every once in a while, but it happens along with (created cart) for every single visitor we have, so when something goes wrong (we had an order not process, but go through stripe last night), we have to comb through thousands of lines of log files that are almost exclusively these currency exchange rate or created cart messages to put together the messages that fit. grep helps, but there aren’t IDs on everything
Jeremy Shimko
@jshimko
Jun 15 2016 16:25
That sounds like a good use case for something like Loggly (which bunyan has a plugin for).
https://www.loggly.com/
I use that in Launchdock. I could add those couple of lines to Reaction too and you’d be able to shoot logs over there for easier analysis.
You enable it by adding the Loggly env vars
Spencer Norman
@spencern
Jun 15 2016 16:27
mm, that’d be nice. Thanks
Valery Orloff
@valorloff
Jun 15 2016 16:59
I'm sorry to interrupt)
guys, please, at least hint my a bit, how to skip payment point in order processing? i.e. copyCart to orders without payment? I create static dummy data in generic-payment-form, and Meteor.call("cart/submitPayment, but Error invoking Method 'cart/submitPayment': [An error verifing payment method. Failed to save order.] and Error invoking Method 'cart/submitPayment': Access Denied [403],
any ideas?
Aaron Judd
@aaronjudd
Jun 15 2016 17:08
cart/submitPayment itself doesn’t check permissions, that would be the Cart.update statement, and then permissions would be checked in security.js.
Cart.permit(["insert", "update", "remove"]).ifHasRole({
    role: ["anonymous", "guest"],
    group: Reaction.getShopId()
  }).ifShopIdMatches().ifUserIdMatches().ifSessionIdMatches().allowInClientCode();
that is the only thing that I see that would throw the Access denied error.
Aaron Judd
@aaronjudd
Jun 15 2016 17:14
in hooks/cart.js is where you are getting An error occurred verifing payment method. thrown… when cart/copyCartToOrder fails.
Aaron Judd
@aaronjudd
Jun 15 2016 17:24
more info here: https://docs.reactioncommerce.com/reaction-docs/master/reaction-payments , based on you saying you passed “dummy data” in, I’m going to guess that the hook is failing with some invalid data. Not sure but you might try debugging there, and maybe consider using ReactionCore.MethodHooks.before("cart/submitPayment”) as a method to skip/modify the behavior before that method is triggered.
AusPrinzip
@AusPrinzip
Jun 15 2016 17:42
Hello, downloading mrt:later@1.6.1 for first test, taking longer than expected, any insights?
AusPrinzip
@AusPrinzip
Jun 15 2016 17:49
any help please?
i just run ./reaction after installation it seems to be stucked in the previously mentioned package
Aaron Judd
@aaronjudd
Jun 15 2016 17:52
@AusPrinzip atmosphere packages can sometime be very slow for some people to download. have no suggestions other than retrying/patience. Not something I’ve ever replicated, but plenty have reported downloading issues.
Things will be much better when someday all packages are moved to npm. (I hope)
AusPrinzip
@AusPrinzip
Jun 15 2016 17:54
@aaronjudd ok Thanks
Brent Hoover
@zenweasel
Jun 15 2016 23:31
fwiw, from Southeast Asia, it’s pretty common for downloading of Meteor packages (like when building for a new version) to just stall. I just cancel out and restart and the package will download fine.