fix: create containers per tenant #151
Triggered via pull request
February 19, 2025 15:36
Status
Failure
Total duration
10m 52s
Artifacts
–
Annotations
10 errors and 2 warnings
Tests:
test/integration/rt_channel_test.exs#L1332
test rate limits max_channels_per_client limit respected (Realtime.Integration.RtChannelTest)
|
Tests:
test/integration/rt_channel_test.exs#L1273
test rate limits max_concurrent_users limit respected (Realtime.Integration.RtChannelTest)
|
Tests:
test/integration/rt_channel_test.exs#L1138
test only private channels user with only private channels enabled will not be able to join public channels (Realtime.Integration.RtChannelTest)
|
Tests:
test/realtime/tenants/janitor_test.exs#L132
test logs error if fails to connect to tenant (Realtime.Tenants.JanitorTest)
|
Tests:
test/realtime_web/channels/realtime_channel/broadcast_handler_test.exs#L76
test call/2 with nil policy and invalid user, is not able to send message (RealtimeWeb.RealtimeChannel.BroadcastHandlerTest)
|
Tests:
test/realtime_web/channels/realtime_channel/broadcast_handler_test.exs#L39
test call/2 with write false policy, user is not able to send message (RealtimeWeb.RealtimeChannel.BroadcastHandlerTest)
|
Tests:
test/realtime/tenants/connect_test.exs#L93
test lookup_or_start_connection/1 if no users are connected to a tenant channel, stop the connection (Realtime.Tenants.ConnectTest)
|
Tests:
test/realtime/tenants/connect_test.exs#L128
test lookup_or_start_connection/1 connection is killed after user leaving (Realtime.Tenants.ConnectTest)
|
Tests:
test/realtime/tenants/connect_test.exs#L62
test lookup_or_start_connection/1 if tenant exists but unable to connect, returns error (Realtime.Tenants.ConnectTest)
|
Tests:
test/realtime/tenants/connect_test.exs#L150
test lookup_or_start_connection/1 handles tenant suspension and unsuspension in a reactive way (Realtime.Tenants.ConnectTest)
|
Tests
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
Tests
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|