0 Fork 0

mirror of https://github.com/PR0M3TH3AN/bitvid.git synced 2026-10-27 07:52:24 +00:00

Files

T

google-labs-jules[bot]andPR0M3TH3AN f1c83534d6 perf: bound DM subsystem network concurrency & fix CI lint/tests

- Replaced unbounded `Promise.all` with `pMap` and `RELAY_BACKGROUND_CONCURRENCY || 3` in `js/nostr/dmSignalEvents.js` and `js/services/dmNostrService.js` to prevent network saturation.
- Updated `scripts/check-hex.js` to exclude agent artifact directories (`perf/`, `test_logs/`, `context/`, etc.) to prevent lint failures when agents log code snippets or hex codes.
- Increased `maxBuffer` in `scripts/check-hex.js` to 10MB to be robust against large matches.
- Updated `js/services/exploreDataService.js` to trigger immediate data refresh (`refreshWatchHistoryTagCounts` and `refreshTagIdf`) when visibility state changes to visible, fixing a unit test failure.
- Includes daily performance report and context logs.

Co-authored-by: PR0M3TH3AN <[email protected]>

2026-02-18 15:08:13 +00:00

1.2 KiB

Raw Blame History

todo: Investigate why visibility check fails in fixture environment

Found TODOs in tests/visual/moderation.spec.ts related to Playwright test failures in headless mode.

Context

Several tests in tests/visual/moderation.spec.ts have commented-out assertions and interactions due to visibility checks failing or clicks timing out when running in the fixture environment (headless).

TODOs

// TODO: Investigate why visibility check fails in fixture environment (headless)
// TODO: Investigate why click times out in fixture environment (headless)
// TODO: Investigate visibility check failure
// TODO: Investigate click timeout failure

Code Excerpt

    // TODO: Investigate why visibility check fails in fixture environment (headless)
    // await expect(showAnywayButton).toBeVisible();
    await expect(restoreButtonQuery).toHaveCount(0);

    // TODO: Investigate why click times out in fixture environment (headless)
    // await showAnywayButton.click({ force: true });

Suggested Next Step

Investigate the tests/visual/moderation.spec.ts execution in headless mode. It might be related to rendering timing, fixture loading state, or specific CSS properties affecting visibility in the headless renderer.

1.2 KiB Raw Blame History