Repository navigation
Conversation
diablo3420
approved these changes
May 7, 2026
danoctua
force-pushed
the
dev
branch
2 times, most recently
from
June 3, 2026 19:47
ea0c2f6 to
213db1d
Compare
…s and use factories for tests
- Update GiftCollection model: replace slug PK with integer id, add options (JSONB) and blockchain_address fields - Update GiftUnique model: replace collection_slug FK with collection_id FK - Update TelegramChatGiftCollection model: replace collection_slug FK with collection_id FK - Create Alembic migration with schema changes, data migration from JSON mapping, and cleanup - Refactor DTOs, services, actions, and API routes to use integer IDs - Update chat eligibility logic (find_relevant_gift_items) to use collection_id - Temporarily disable gift indexer tasks and comment out slug-dependent indexer methods
- Update get_metadata to remove slug filtering and reduce cache TTL to 5 minutes - Migrate whitelisted_gift_collections.txt from slugs to integer IDs - Update indexer actions and tasks to use IDs instead of slugs in get_all calls - Ensure indexer remains disabled with early return in tasks.py
… to solve frontend JS truncation
This reverts commit d2b335a.
Updated the `GiftCollection` query to order results by `title` instead of `id` for consistent sorting.
…_gift_collection settings
Also updates UserAction.refresh_gifts to use sender.send_task and fixes its tests.
…API exceptions This adds an asyncio.sleep(0.250) on close to allow aiohttp SSL transports to cleanly disconnect, preventing SIGKILL from file descriptor leaks. It also ensures 'user not found' exceptions are correctly raised rather than wiping a user's DB gifts.
…sers - Moves batch syncing into IndexerUserGiftAction to share a single BotApiGiftIndexer instance, vastly reducing overhead and event loop thrashing. - Adds UserService.mark_as_blocked() and excludes blocked users from global fetches. - Automatically marks users as blocked when Telegram returns a 'user not found' exception during gift sync.
Avoids unnecessary DB UPDATE queries for gifts that already belong to the user being synced, significantly reducing write load during recurring batch refreshes.
…to enable waiting on refresh to complete
danoctua
added
enhancement
danoctua
marked this pull request as ready for review
September 25, 2026 18:13
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
2 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.
[DON'T MERGE UNTIL FEATURES ARE TESTED ON DEV]
Description
[Please include a summary of the changes made in this pull request. Mention the issue(s) this pull request fixes (if any), and provide a brief context about the problem you're solving.]
Fixes: #[issue number] (if applicable)
Checklist
Before submitting your pull request, please ensure the following:
Changes
[Provide a high-level overview of what changes you made. Mention any new features, bug fixes, or performance improvements. Also, note if there are breaking changes.]
How Has This Been Tested?
[Describe how you tested your changes. Mention the environment (e.g., OS, browser, API version) and tools used to verify the functionality.]
Screenshots (if applicable)
[Provide screenshots or screencasts of your changes where visual updates occurred.]
Additional Notes
[(optional) Leave any extra information, concerns, or comments you would like the reviewers to know.]
Thank you for contributing! 🎉