feat: Database Broadcast enabled #34
filipecabacoAnnotations
8 errors and 14 warnings
|
Tests:
test/realtime_web/controllers/broadcast_controller_test.exs#L271
test authorization for broadcast user with permission to read all channels and write to them is able to broadcast (RealtimeWeb.BroadcastControllerTest)
|
|
Tests:
test/realtime_web/controllers/broadcast_controller_test.exs#L422
test authorization for broadcast user without permission won't broadcast (RealtimeWeb.BroadcastControllerTest)
|
|
Tests:
test/realtime_web/controllers/broadcast_controller_test.exs#L311
test authorization for broadcast user with permission is also able to broadcast to open channel (RealtimeWeb.BroadcastControllerTest)
|
|
Tests:
test/realtime_web/controllers/broadcast_controller_test.exs#L371
test authorization for broadcast user with permission to write a limited set is only able to broadcast to said set (RealtimeWeb.BroadcastControllerTest)
|
|
Tests:
test/realtime/tenants/connect_test.exs#L29
test lookup_or_start_connection/1 on database disconnect, returns new connection (Realtime.Tenants.ConnectTest)
|
|
Tests:
test/realtime/tenants/connect_test.exs#L205
test lookup_or_start_connection/1 failed broadcast handler and listen recover from failure (Realtime.Tenants.ConnectTest)
|
|
Tests:
test/realtime/database_test.exs#L77
test transaction/1 on checkout error, handles raised exception as an error (Realtime.DatabaseTest)
|
|
Tests
Process completed with exit code 2.
|
|
Tests
Your workflow is using a version of actions/cache that is scheduled for deprecation, actions/cache@v1. Please update your workflow to use either v3 or v4 of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-12-05-notice-of-upcoming-releases-and-breaking-changes-for-github-actions/#actions-cache-v1-v2-and-actions-toolkit-cache-package-closing-down
|
|
Tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
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
|
|
Tests:
test/support/generators.ex#L47
Nested modules could be aliased at the top of the invoking module.
|
|
Tests:
test/integration/rt_channel_test.exs#L1042
Nested modules could be aliased at the top of the invoking module.
|
|
Tests:
test/integration/rt_channel_test.exs#L1005
Nested modules could be aliased at the top of the invoking module.
|
|
Tests:
test/integration/rt_channel_test.exs#L1002
Nested modules could be aliased at the top of the invoking module.
|
|
Tests:
lib/realtime_web/controllers/tenant_controller.ex#L193
Nested modules could be aliased at the top of the invoking module.
|
|
Tests:
test/realtime/tenants/authorization_test.exs#L184
Nested modules could be aliased at the top of the invoking module.
|
|
Tests:
lib/realtime_web/controllers/broadcast_controller.ex#L35
Nested modules could be aliased at the top of the invoking module.
|
|
Tests:
test/realtime_web/controllers/tenant_controller_test.exs#L157
Nested modules could be aliased at the top of the invoking module.
|
|
Tests:
test/realtime_web/controllers/tenant_controller_test.exs#L155
Nested modules could be aliased at the top of the invoking module.
|
|
Tests:
test/realtime_web/controllers/tenant_controller_test.exs#L67
Nested modules could be aliased at the top of the invoking module.
|