fix: reject connections if tenant db has low connections available #98
Annotations
1 error and 12 warnings
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
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#L1625
Nested modules could be aliased at the top of the invoking module.
|
Tests:
test/integration/rt_channel_test.exs#L1622
Nested modules could be aliased at the top of the invoking module.
|
Tests:
test/integration/rt_channel_test.exs#L1609
Nested modules could be aliased at the top of the invoking module.
|
Tests:
test/integration/rt_channel_test.exs#L1572
Nested modules could be aliased at the top of the invoking module.
|
Tests:
test/integration/rt_channel_test.exs#L1569
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#L394
Nested modules could be aliased at the top of the invoking module.
|
Tests:
test/integration/rt_channel_test.exs#L1231
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.
|