storj/satellite/orders
Ivan Fraixedes e47b8ed131
storagenode: No FATAL error when unsent orders aren't found (#2801)
* pkg/process: Fatal show complete error information
  Change the general process execution function to not using the sugared
  logger for outputting the full error information.
  Delete some unreachable code because Zap logger Fatal method calls exit
  1 internally.
* storagenode/storagenodedb: Add info to error
  Add more information to an error returned due to some data
  inconsistency.
* storagenode/orders: Don't use sugared logger
  Don't use sugar logger and provide better contextualized error messages
  in settle method.
* storagenode/orders: Add some log fields to error msgs
  Add some relevant log fields to some logged errors of the sender settle
  method.
* satellite/orders: Remove always nil error from debug
  Remove an error which as logged in debug level which was always nil and
  makes the logic that used this variable clear.
* storagenode/orders: Don't return error Archiving unsent
  Don't stop the process which archive unsent orders if some of them
  aren't found the DB because it cause the Storage Node to stop with a
  fatal error.
2019-08-16 16:53:22 +02:00
..
endpoint.go storagenode: No FATAL error when unsent orders aren't found (#2801) 2019-08-16 16:53:22 +02:00
orders_test.go Update satellite settlement endpoint to batch order processing into transactions. (#2762) 2019-08-15 15:05:43 -04:00
serials_test.go interface tests belong to the interface, not the implementation (#1794) 2019-04-23 11:47:16 +03:00
service.go Update satellite settlement endpoint to batch order processing into transactions. (#2762) 2019-08-15 15:05:43 -04:00