1.8.1

Just a few error patches I made while watching our tests run.

Release Notes

• [fix] occasional log of circular objects that have toObj() function
• [fix] make sure .userreal is included on manual service responder construction
• [fix] perform checks for socket existing before trying to access
• [wip] eslint changes

Test Status

No specific tests created to cover these changes. These were "random" errors or glitches I observed while watching our e2e tests run.

1.8.0

These additions are related to making it easier to debug our failed e2e tests. This default handler allows us to print out the specific versions of our services that are running.

Release Notes

• [wip] add a default versionCheck handler
• [wip] eslint changes
• [wip] include jobID on error responses
• [wip] prevent json parse attempts on default healthCheck responses

1.7.7

#65

Release Notes

• Handle errors with cote socket connections

1.7.6

Release Notes

• Prevent JSON.stringify() errors when parsing BigInt values

1.7.5

digi-serve/global-hr-update#107

Release Notes

• Check string type and send data.

1.7.4

#60
digi-serve/ab_service_definition_manager#64

Release Notes

• Replace bfj.stringify() with JSON.stringify() in a worker_thread
• Add a worker service

1.7.3

Release Notes

• Add the stringResult option.
• digi-serve/ab_service_api_sails#113

1.7.2

Release Notes

• fix converting the open telemetry span attribute to sentry

1.7.1

Release Notes

• fix error when using the default telemetry

1.7.0

Implements #55

• To get better Sentry data have each service initializes Sentry. This will help us capture uncaught errors, and provide better context for notify() errors.

Release Notes

• add sentry integration
  • services can init sentry through ab-utils (with common default config options)
  • nofity() now sends to sentry directly rather than through log_manager
  • performance tracking in sentry for each service's handlers

Example of how services would use it: digi-serve/ab_service_log_manager#34