prepare 5.10.0 release #89
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…igurable-global-datadog Add global tag configuration for datadog exporter
Add smoke tests for debian, centos and docker builds.
Git tag may not be up-to-date until we tag the new release.
…s-nesting-in-metrics-tests [ch20947] Flatten metrics tests
…and-public-metric-views [ch21033] Separate private and public metrics
Fix event exporter views and rename private metric view names
logging.InitLogging needs to be callable externally
Event relay would panic with a default value of 0.
fix event-summarizing logic to preserve tracking status sent by PHP SDK
fix CI publish job by pinning goreleaser version
…icroseconds (#108) * use consistent log format with timestamp at start of line & include microseconds * use correct logger instances for startup info messages * add "main" tag for main logger
support ordinary HTTP proxy via configuration
Since ld-relay doesn't fork and kill the parent process on start, calls to `systemctl start ld-relay` currently hang until the timeout and the unit stays in the activating state. Changing this to `Type=simple` corrects this behavior. [Related docs](https://www.freedesktop.org/software/systemd/man/systemd.service.html#Options) Before: ``` $ systemctl start ld-relay Job for ld-relay.service failed because a timeout was exceeded. See "systemctl status ld-relay.service" and "journalctl -xe" for details. systemctl status ld-relay ● ld-relay.service - LaunchDarkly Relay Proxy Loaded: loaded (/usr/lib/systemd/system/ld-relay.service; enabled; vendor preset: disabled) Drop-In: /etc/systemd/system/ld-relay.service.d └─limits.conf, restart-on-failure.conf Active: activating (start) since Sat 2020-01-11 01:29:26 UTC; 10s ago Control: 27286 (ld-relay) ``` After: ``` $ systemctl start ld-relay $ systemctl status ld-relay ● ld-relay.service - LaunchDarkly Relay Proxy Loaded: loaded (/usr/lib/systemd/system/ld-relay.service; enabled; vendor preset: disabled) Drop-In: /etc/systemd/system/ld-relay.service.d └─limits.conf, restart-on-failure.conf Active: active (running) since Sat 2020-01-11 01:36:09 UTC; 4s ago ```
Fix hang on systemctl start ld-relay
…load update Go SDK to 4.14.1 for event payload ID fix
forward diagnostic events
update to Go SDK 4.14.2
bwoskow-ld
approved these changes
Jan 22, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[5.10.0] - 2020-01-22
Added:
Fixed: