fix: Apply RLS rules to Channel controller #721
Annotations
10 errors and 23 warnings
test/realtime/tenants/connect_test.exs#L108
test lookup_or_start_connection/1 handles tenant suspension and unsuspension in a reactive way (Realtime.Tenants.ConnectTest)
|
test/realtime/tenants/connect_test.exs#L72
test lookup_or_start_connection/1 if users are connected to a tenant channel, keep the connection (Realtime.Tenants.ConnectTest)
|
test/realtime/tenants/connect_test.exs#L56
test lookup_or_start_connection/1 if no users are connected to a tenant channel, stop the connection (Realtime.Tenants.ConnectTest)
|
test/realtime/tenants/connect_test.exs#L13
test lookup_or_start_connection/1 if tenant exists and connected, returns the db connection (Realtime.Tenants.ConnectTest)
|
test/realtime/tenants/connect_test.exs#L18
test lookup_or_start_connection/1 on database disconnect, returns new connection (Realtime.Tenants.ConnectTest)
|
test/realtime/tenants/connect_test.exs#L86
test lookup_or_start_connection/1 connection is killed after user leaving (Realtime.Tenants.ConnectTest)
|
test/realtime/repo_test.exs#L166
test one/3 if not found, returns not found error (Realtime.RepoTest)
|
test/realtime/repo_test.exs#L173
test insert/3 inserts a new entry with a given changeset and returns struct (Realtime.RepoTest)
|
test/realtime/repo_test.exs#L192
test del/3 deletes all from query entry (Realtime.RepoTest)
|
test/realtime/repo_test.exs#L197
test del/3 raises error on bad queries (Realtime.RepoTest)
|
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
|
|
|
|
lib/extensions/postgres/adapters/postgres/decoder/decoder.ex#L134
redefining module Realtime.Adapters.Postgres.Decoder.Messages.Relation.Column (current version loaded from _build/dev/lib/realtime/ebin/Elixir.Realtime.Adapters.Postgres.Decoder.Messages.Relation.Column.beam)
|
|
|
|
|
|
lib/extensions/postgres/adapters/postgres/decoder/decoder.ex#L134
redefining module Realtime.Adapters.Postgres.Decoder.Messages.Relation.Column (current version loaded from _build/test/lib/realtime/ebin/Elixir.Realtime.Adapters.Postgres.Decoder.Messages.Relation.Column.beam)
|
test/support/generators.ex#L44
Nested modules could be aliased at the top of the invoking module.
|
lib/realtime/application.ex#L77
Nested modules could be aliased at the top of the invoking module.
|
test/realtime/repo_test.exs#L84
Nested modules could be aliased at the top of the invoking module.
|
test/realtime/repo_test.exs#L75
Nested modules could be aliased at the top of the invoking module.
|
test/realtime/repo_test.exs#L53
Nested modules could be aliased at the top of the invoking module.
|
test/realtime/repo_test.exs#L32
Nested modules could be aliased at the top of the invoking module.
|
test/realtime/cluster_strategy/postgres_test.exs#L9
Nested modules could be aliased at the top of the invoking module.
|
test/integration/rt_channel_test.exs#L93
Numbers larger than 9999 should be written with underscores: 10_000
|
test/realtime/tenants/connect_test.exs#L151
Numbers larger than 9999 should be written with underscores: 10_000
|
test/realtime/cluster_strategy/postgres_test.exs#L27
Numbers larger than 9999 should be written with underscores: 10_000
|
The logs for this run have expired and are no longer available.
Loading