decentraland / lamb2
62%
main: 62%

LAST BUILD BRANCH: 4.13.0
DEFAULT BRANCH: main
Repo Added
Files 81
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

LAST BUILD ON BRANCH 4.13.0
branch: SELECT
CHANGE BRANCH
x

coverage: 62.172% (-20.9%) from 83.077%
28813187564

push

github

web-flow 
chore: migrate @well-known-components/test-helpers and tracer-component to @dcl (#469)

* chore: migrate @well-known-components/test-helpers and tracer-component to @dcl

Swap the two remaining @well-known-components packages for their @dcl
core-components equivalents:

- @well-known-components/test-helpers -> @dcl/test-helpers@^0.2.0. The
  @dcl package declares jest/ts-jest/@types/jest and sinon/@types/sinon
  as peers (the wkc package bundled them), so add them as devDeps; it
  returns jest mocks from stubComponents (port .resolves() ->
  .mockResolvedValue()) and fixes the createLocalFetchCompoment typo
  export to createLocalFetchComponent.
- @well-known-components/tracer-component -> @dcl/tracer-component@^1.0.0.

Build, lint and the full jest suite (561 tests) pass locally.

* test: retry local fetch on transient connection errors

The native fetch (undici) that backs @dcl/test-helpers' createLocalFetchComponent
pools keep-alive connections, unlike the old node-fetch-based helper. Because every
suite reuses the same fixed HTTP_SERVER_PORT and tears its server down in afterAll,
the first request of a suite could land on a stale socket from the previous suite's
closed server and fail intermittently with "fetch failed" / ECONNRESET. Retry such
transient connection errors once so the integration suites are deterministic.

* test: retry transient local-fetch errors with backoff, not just once

The single immediate retry was not enough under CI timing: with all suites
sharing a fixed HTTP_SERVER_PORT, undici's pooled keep-alive socket to a
previous suite's torn-down server is reused and fails with 'other side
closed', and the immediate retry can race the socket eviction. Retry a few
times with a short backoff so undici drops the dead socket and reconnects.
Verified with 3 consecutive full runs (561 tests, 0 connection failures) in
a CI-equivalent environment (no local .env pinning the port).

* test: scope the default `yarn test` to unit tests only; ... (continued)

456 of 962 branches covered (47.4%)

Branch coverage included in aggregate %.

1 of 1 new or added line in 1 file covered. (100.0%)

429 existing lines in 29 files now uncovered.

1605 of 2353 relevant lines covered (68.21%)

10.51 hits per line

Relevant lines Covered
2353 RELEVANT LINES 1605 COVERED LINES
10.51 HITS PER LINE
Source Files on main

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
28813187564 4.13.0 chore: migrate @well-known-components/test-helpers and tracer-component to @dcl (#469) * chore: migrate @well-known-components/test-helpers and tracer-component to @dcl Swap the two remaining @well-known-components packages for their @dcl core-c... push web-flow github
62.17
28469095931 main chore: migrate @well-known-components/test-helpers and tracer-component to @dcl (#469) * chore: migrate @well-known-components/test-helpers and tracer-component to @dcl Swap the two remaining @well-known-components packages for their @dcl core-c... push web-flow github
62.17
28384761852 chore/migrate-test-helpers-tracer-to-dcl test: scope the default `yarn test` to unit tests only; split out integration The shared Dockerfile.alpine and platform-actions apps-build.yml both run `yarn test`, which lamb2 had defined as the WHOLE suite (testMatch '**/*.spec.ts'). After migr... Pull #469 LautaroPetaccio github
62.17
28384029156 chore/migrate-test-helpers-tracer-to-dcl test: retry transient local-fetch errors with backoff, not just once The single immediate retry was not enough under CI timing: with all suites sharing a fixed HTTP_SERVER_PORT, undici's pooled keep-alive socket to a previous suite's torn-down se... Pull #469 LautaroPetaccio github
83.08
28123678469 main fix: cancel undrained response bodies and bump @dcl core-components/core-libs deps (#468) * fix: cancel undrained response bodies and bump @dcl core-components/core-libs deps Cancel HTTP response bodies on non-OK paths that previously discarded ... push web-flow github
83.08
28121213976 fix/response-body-leaks-and-dcl-bump Merge branch 'main' into fix/response-body-leaks-and-dcl-bump Updates the stale branch so CI runs on Node 24 (.nvmrc + build.yml from main), which satisfies @dcl/crypto@3.7.0's "node >=22" engine requirement — the branch's Node 18 CI was failing ... Pull #468 LautaroPetaccio github
83.08
27975355725 main chore: bump core-components and core-libs dependencies to latest (#467) * chore: bump core-components and core-libs dependencies to latest Update the @dcl core-components and core-libs packages to their latest published versions: core-component... push web-flow github
83.19
27975217741 chore/bump-core-components-and-core-libs chore: bump @dcl/schemas to latest (^16.2.0 -> ^26.5.0) Bring lamb2's direct @dcl/schemas dependency up to the current major. The types lamb2 uses (Avatar/Emote/Wearable/Entity/categories/Outfit/...) are unchanged across the bump, so src builds a... Pull #467 LautaroPetaccio github
83.19
27973920243 chore/bump-core-components-and-core-libs chore: bump @types/node to 24 to match the node 24 runtime Now that CI and the production image run on Node 24 (.nvmrc + apps-build node-version + node:24-alpine), align the type definitions: @types/node ^18.11.18 -> ^24.13.2. Build, lint and the... Pull #467 LautaroPetaccio github
83.19
27973480522 chore/bump-core-components-and-core-libs ci: run build workflow on node 24 and pin via .nvmrc The latest @dcl/crypto (3.7.0) and @dcl/urn-resolver (3.6.1) declare engines.node ">=22", so the build workflow (which defaulted to Node 18.x via the shared apps-build reusable workflow) failed... Pull #467 LautaroPetaccio github
83.19
See All Builds (308)