Skip to content

Ability to specify uuid when capturing events #146

Ability to specify uuid when capturing events

Ability to specify uuid when capturing events #146

Re-run triggered August 22, 2024 16:07
Status Success
Total duration 40s
Artifacts

unit-tests.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 2 warnings
Build
buffer (0/1) {identify posthog-go 1.0.0 2009-11-10 23:00:00 +0000 UTC $identify B map[$lib:posthog-go $lib_version:1.0.0] map[email:[email protected]]}
Build
exceeded messages batch limit with batch of 1 messages – flushing
Build
response 200 OK
Build
buffer (0/1) {posthog-go 1.0.0 2009-11-10 23:00:00 +0000 UTC $groupidentify $organization_id:5 map[$group_key:id:5 $group_set:map[] $group_type:organization $lib:posthog-go $lib_version:1.0.0]}
Build
exceeded messages batch limit with batch of 1 messages – flushing
Build
response 200 OK
Build
buffer (0/1) {capture posthog-go 1.0.0 2009-11-10 23:00:00 +0000 UTC 123456 Download map[$lib:posthog-go $lib_version:1.0.0 application:PostHog Go platform:macos version:1.0.0] false}
Build
exceeded messages batch limit with batch of 1 messages – flushing
Build
response 200 OK
Build
buffer (0/1) {alias posthog-go 1.0.0 2009-11-10 23:00:00 +0000 UTC {B A posthog-go 1.0.0} $create_alias}
Build
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/