CI: journey test asserts WCD cluster's replication default; timeDecay boost test is flaky

Open Beginner friendly
#485 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@dudanogueira is already working on this.

Since Sep 30, 2026.

  • #486 by @dudanogueira — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
88/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
testing-qa

Research direction

Start with test/collections/journey.test.ts and test/collections/query/integration.test.ts, then run the affected collection and query integration tests. Check the journey assertion against the shared WCD cluster default and the boost test's object dates relative to its decay origin. Done means both tests pass consistently across the relevant CI jobs without relying on float-ordering noise.

Written by the indexing model from the issue text.

Description

Two tests are failing CI independently of the code under change (seen on #459, which touches neither file).

1. test/collections/journey.test.ts — "should get the config for the created collection"

Fails on every tests-without-auth job regardless of Weaviate version, because it runs against a shared WCD cluster rather than the version-matrix container. The only real diff:

replication: {
-   asyncEnabled: false,
+   asyncEnabled: true,

The cluster now defaults new collections to asyncEnabled: true. main's last run (2026-09-09) did not hit this, so the cluster's defaults changed since. The test hard-codes a value that is owned by the server's configuration.

2. test/collections/query/integration.test.ts — boost timeDecay

Flaky (failed on 24.x / 1.38 only). All three objects are inserted with createdAt: new Date(Date.now()), while the decay origin is 2024-01-01 with a 35d scale — so every object's decay is ~0 and identical. The boost has no real effect, and expect(boosted).not.toEqual(baseline) only passes when float noise happens to reorder tied results.

Fix
  • Journey: assert asyncEnabled: expect.any(Boolean).
  • Boost: give the objects distinct createdAt dates around the decay origin so timeDecay deterministically reorders them.
Dominant language
TypeScript
Stars
101
Forks
43
Avg merge
7h 31m
Merged PRs (30d)
6

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from weaviate/typescript-client

All issues in weaviate/typescript-client

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.