Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in
U
upgrade-data-crawler-be
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 0
    • Issues 0
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • ThinhNC
  • upgrade-data-crawler-be
  • Merge Requests
  • !15

Merged
Opened Sep 08, 2026 by ThinhNC@ThinhNC
  • Report abuse
Report abuse

feat(be): exempt failed connection & provider quota jobs from daily usage quota

Pull Request Overview: Client Resilience, Quota Waiver Policy & Bilingual Localization

This pull request introduces connection resilience, client-side data handling utilities, an automatic quota exemption policy for connection/provider failures, and complete English/Vietnamese bilingual localization across the platform.


Backend Changes (data-crawler-be)

1. Quota Exemption Policy for Failed Connection & Provider Outages

  • Quota Exemption Logic (crawl-job.repository.ts):
    • Updated countJobsSince to exclude crawl jobs that failed due to connection disruption or provider limitations (e.g., Firecrawl HTTP 402, timeouts, DNS failures) where successPages === 0.
    • Updated sumPagesCrawledByUser to avoid deducting pages from user limits when a job fails without scraping any page.
  • Error Mapping Expansion (error-mapping.helper.ts):
    • Enhanced isConnectionLossError to identify provider credit exhaustion (402, credit), network drops (ECONNRESET, ECONNREFUSED), timeouts, and DNS failures.
  • Test Suite:
    • All Jest unit test suites pass with 100% success rate (39 suites, 430 tests passing).

Check out, review, and merge locally

Step 1. Fetch and check out the branch for this merge request

git fetch origin
git checkout -b feat/resilience-quota-waiver-and-i18n origin/feat/resilience-quota-waiver-and-i18n

Step 2. Review the changes locally

Step 3. Merge the branch and fix any conflicts that come up

git fetch origin
git checkout origin/develop
git merge --no-ff feat/resilience-quota-waiver-and-i18n

Step 4. Push the result of the merge to GitLab

git push origin develop

Note that pushing to GitLab requires write access to this repository.

Tip: You can also checkout merge requests locally by following these guidelines.

  • Discussion 0
  • Commits 1
  • Changes 6
Assignee
No assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
0
Labels
None
Assign labels
  • View project labels
Reference: ThinhNC/upgrade-data-crawler-be!15

Revert this merge request

This will create a new commit in order to revert the existing changes.

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.

Cherry-pick this merge request

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.