feat(monorepo): [limiter] Incorporates limiter into core services #9
Draft
nanodirijabl wants to merge 60 commits into
Draft
feat(monorepo): [limiter] Incorporates limiter into core services #9nanodirijabl wants to merge 60 commits into
nanodirijabl wants to merge 60 commits into
Conversation
* draft * added format * added backend stuff * added requested changes except batch in range machine * added error sort in handler, add lim_body and its validation * added start time and shard size, implemented shard id generation and time range calculation * fixed xref * fixed format * added unit tests * refactored errors * updated to new proto * added config marshaling * fixed format * added base tests * added exchange tests * fixed linter * added requested changes * updated proto ref
Fix bug calc shard id(same usec); add in config day limit
fix same usec
ED-181: add subtraction behaviour
* added new create method * added party day config
* Switch to valitydev upstreams * valitydev/thrift-erlang@c280ff2 * valitydev/scoper@7f3183d * valitydev/genlib@82c5ff3 * valitydev/erlang-health@5958e2f * valitydev/damsel@1d60b20 * Drop how_are_you
While also involving minimal number of interactions with accounter in order to improve runtime behaviour. * Add annotated testcases for changed exception behavior * Test (kinda) that multirange limits work
As of valitydev/limiter-proto@d390910. Co-authored-by: Артем <WWW_cool@inbox.ru>
* 🔄 Created local '.github/workflows/basic-linters.yml' from remote 'workflows/base/basic-linters.yml' * 🔄 Synced local 'LICENSE' with remote 'LICENSE' * 🔄 Created local '.github/settings.yml' from remote '.github/settings.yml'
* Bump to valitydev/limiter-proto@6723e86. * Introduce _noncurrency_ concept instead of default currency which is kinda misleading. * Rename `lim_p_transfer` → `lim_posting`. * (Minor API break) Respond w/ 0 balance on uninitialized limit ranges.
…#9) * updated limiter proto * added payproc context * fixed linter * bumped proto * added base tests * added payment tool tests * added minor test * fixed dialyzer * fixed
* Bump to valitydev/machinery-erlang@62c3243 * Bump to valitydev/machinegun-proto@347c5c4 * Drop top-level `damsel` dependency * Drop `get_rate` testcase as meaningless * Drop testcases which became duplicate * Support new context type @ config * Delegate context accessors to specific modules * Support rollbacks @ valitydev/limiter-proto@6158184
* added new scopes * added identity and wallet scope tests * switched to proto master * fixed * added multu scope test * added prefix * added commands * finished with new scope ordering system * added requested changes * applied patch
* Adds app configuration flag to disable currency conversion * Revert turnover test suite * Adds testcase for disabled currency conversion * Changes currency_conversion default to disabled * Simplify currency conversion testcases setup
* Adds explicit damsel dependency * Bump dominant docker compose image (sha-e0afa44) * Adds dominant-sourced config unmarshalling * Adds operation `Limiter:GetVersioned/4` * Refactor test suite and add testcase group with dominant-sourced config object use
* Adds new exceptions support for hold operation: `InvalidOperationCurrency`, `OperationContextNotSupported` and `PaymentToolNotSupported`. * Adds testcases for new exceptions
* Bumps limiter-proto
* removed * bumped to valitydev/damsel@c32f50f and valitydev/limiter-proto@e045813
* CP-12: Adds support for 'currency_conversin' config option * Fixes eunit tests * Updates testcases in suites * Fixes struct type in marshaling and temporarily disables codecov report upload * Bumps damsel and limiter-proto * Removes global 'currency_conversion' flag
…context (#29) * CP-4: Adds support for 'sender' and 'receiver' scopes for withdrawal context * Adds tests for sender and receiver scopes * Bumps damsel and limiter_proto
…hone number (#31) * Adds scope support for withdrawal's destination phone number * Implements destination_field limit scope * Adds hold and commit testcases for destination_field scope * Moves field path into hashed value * Adds destination_field support for domain object * Bumps stable deps
* Adds support for prometheus woody metrics * Bumps CI wf * Ignore accidental god-module `lim_turnover_SUITE`
* added liminator * added support of new liminator backend * fixed elvis * wip * finished * bumped limiter proto * fixed * added scopes to limit cfg to test change ctx * Revert "added scopes to limit cfg to test change ctx" This reverts commit 12203c66dc466ffe4eba04dbbd1e895fae49dfd8. * Revert "Revert "added scopes to limit cfg to test change ctx"" This reverts commit 76963bb77a1bd0caf87a8851313cea73f9ea700d. * fixed * fixed * fixed fmt
* TECH-76: Upgrades to Erlang/OTP 27 * Bumps deps
* bumped damsel * fixed * bumped again * bumped compose * removed identity * bumped damsel * bumped * bumped dmt
* Upgrades to dmt v2 * Removes commit test with idenity scope * Updates dmt hostname * Bumps damsel & dmt-v2 * Bumps dmt v2
* Removes obsolete machinery-based limit support * (WIP) Updates dmt and tests w/ `started_at` field * Upgrades damsel, reverts `started_at` field and disables temporary broken test cases * Retires codec modules and moves sole functions into user-modules * Removes comment * Bumps limiter-proto
* Adds WIP on grouped operations by finalization behaviour * Fixes operation wrappers and tests * Reworks limiter's sub operations for conditional finalization * Fixes config marshalling unit test * Adds tests for invertable limit operations * Formats code * Bumps protos * Fixes DRY linter warning * Adds notes about changes grouping
…r-monorepo-intercorporation
nanodirijabl
marked this pull request as draft
July 16, 2026 14:06
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.