Gastón Fournier b76e66fc1d fix: make sure we have a user in event store (#3072) ... ## About the changes Spotted some issues in logs: ```json { "level":"warn", "message":"Failed to store \"feature-environment-variants-updated\" event: error: insert into \"events\" (\"created_by\", \"data\", \"environment\", \"feature_name\", \"pre_data\", \"project\", \"tags\", \"type\") values (DEFAULT, $1, $2, $3, $4, $5, $6, $7) returning \"id\", \"type\", \"created_by\", \"created_at\", \"data\", \"pre_data\", \"tags\", \"feature_name\", \"project\", \"environment\" - null value in column \"created_by\" violates not-null constraint", "name":"lib/db/event-store.ts" } ``` In all other events we're doing the following: b7fdcd36c0/src/lib/services/segment-service.ts (L80) So this is just mimicking that to quickly release a patch, but I'll look into a safer (type-checked) solution so this problem does not happen again		2023-02-09 11:01:39 +01:00
..
config	feat/enable_batch_metrics_for_all (#3027)	2023-02-01 20:50:17 +01:00
e2e	fix: make sure we have a user in event store (#3072)	2023-02-09 11:01:39 +01:00
examples	fix: found an edge case exporting variants (#2900)	2023-01-13 14:55:57 +01:00
fixtures	Remove timeout from store (#3018)	2023-01-30 12:01:44 +01:00
arbitraries.test.ts	feat(#1873/playground): Return detailed information on feature toggle evaluation (#1839)	2022-08-04 15:41:52 +02:00