Overview - Tom-server

ToM-server

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
chore/federated-identity-biome-pass
25b8abd2 chore(federated-identity-service): pass biome lint
by Khaled FER...
Succeeded
chore/db-biome-pass
039f6f94 chore(db): pass biome lint
by Khaled FER...
Failed
chore/config-parser-biome-pass
392189d8 chore(config-parser): pass biome lint
by Khaled FER...
Succeeded
chore/matrix-resolve-biome-pass
38d680f0 chore(matrix-resolve): pass biome lint
by Khaled FER...
Succeeded
chore/utils-biome-pass
f34533ef chore(utils): pass biome lint
by Khaled FER...
Succeeded
chore/tom-server-e2e-biome-pass
3c45c01d chore(tom-server-e2e): pass biome lint
by Khaled FER...
Failed
chore/crypto-biome-pass
4c52d0ac chore(crypto): clear biome lint errors
by Khaled FER...
Succeeded
fix-lint-issues
60167923 fix(common-settings-bridge): clear remaining lint errors in the package Replaces `any` and `(err as any)?.code` with proper `unknown` narrowing in the profile updater and settings repository, bundles `saveSettings` extra parameters into a `SaveSettingsMeta` object to satisfy `useMaxParams`, and swaps `(MockLogger as any).configure` for `Object.assign` in the logger mock. `biome ci` now exits 0 across `packages/common-settings-bridge`.
by Khaled FER...
Succeeded
fix-lint-issues
52da8990 fix(common-settings-bridge): reject non-finite timestamp and version `typeof x === "number"` lets NaN and Infinity through, both of which JSON producers can reach via `1e1000` / `-1e1000`. An Infinity timestamp crashed `new Date(...).toISOString()` inside the info log, escaping the validation try/catch and turning the intended ack-and-drop into a retry-then-DLQ storm. A NaN/-Infinity version silently lost legitimate updates because every comparison in shouldApplyUpdate returns false. Switch both guards to `Number.isFinite` and split the payload-not-object error from UserIdNotProvidedError so the two failure modes are distinguishable in logs.
by Khaled FER...
Succeeded
feat/migrate-rabbitmq-client
86dabfb4 feat(cs-bridge): migrate to @linagora/rabbitmq-client Replaces the in-repo @twake/amqp-connector with @linagora/rabbitmq-client in common-settings-bridge. The new client provisions quorum queues with at-least-once dead-letter routing out of the box, aligning the bridge with the HA topology used by the rest of the fleet. Deletes the @twake/amqp-connector package; common-settings-bridge was its only consumer. - Configurable prefetch, maxRetries, retryDelay - routingKey is optional and defaults to '#' - start() rolls back the open AMQP session if subscribe() fails - stop() always closes the database even if client.close() rejects - Validation errors are acked-and-dropped instead of triggering retry storms Operators must delete the existing classic queue before deploy: the new client asserts it as a quorum queue, which fails PRECONDITION_FAILED against a pre-existing classic queue of the same name.
by Khaled FER...
Succeeded
feat/migrate-rabbitmq-client
75e3b783 feat(cs-bridge): migrate to @linagora/rabbitmq-client Replaces the in-repo @twake/amqp-connector with @linagora/rabbitmq-client in common-settings-bridge. The new client provisions quorum queues with at-least-once dead-letter routing out of the box, aligning the bridge with the HA topology used by the rest of the fleet. Deletes the @twake/amqp-connector package; common-settings-bridge was its only consumer. - Configurable prefetch, maxRetries, retryDelay - routingKey is optional and defaults to '#' - start() rolls back the open AMQP session if subscribe() fails - stop() always closes the database even if client.close() rejects - Validation errors are acked-and-dropped instead of triggering retry storms Operators must delete the existing classic queue before deploy: the new client asserts it as a quorum queue, which fails PRECONDITION_FAILED against a pre-existing classic queue of the same name.
by Khaled FER...
Succeeded
fix/admin-access-token
02d69d3f fix(tom-server/token-service): handle cross-origin redirects in SSO token flow The admin access token acquisition broke because Node.js fetch strips cookies on cross-origin redirects. The SSO chain crosses from the auth provider to Matrix, so the OIDC session cookie never reached Synapse. Split getLoginToken into two explicit fetch calls — auth provider gets only the auth cookie, Matrix callback gets only the session cookies. Validate the callback origin matches the Matrix server before sending session cookies. Also fix cookie serialization: use getSetCookie() and strip attributes so the Cookie header contains clean name=value pairs instead of raw Set-Cookie values with Domain/Path/HttpOnly attributes.
by Khaled FER...
Succeeded
fix/admin-access-token
6f6bf407 fix(tom-server/token-service): handle cross-origin redirects in SSO token flow The admin access token acquisition broke because Node.js fetch strips cookies on cross-origin redirects. The SSO chain crosses from the auth provider to Matrix, so the OIDC session cookie never reached Synapse. Split getLoginToken into two explicit fetch calls — auth provider gets only the auth cookie, Matrix callback gets only the session cookies. Validate the callback origin matches the Matrix server before sending session cookies. Also fix cookie serialization: use getSetCookie() and strip attributes so the Cookie header contains clean name=value pairs instead of raw Set-Cookie values with Domain/Path/HttpOnly attributes.
by Khaled FER...
Succeeded
fix/admin-access-token
a2692c70 fix(tom-server/token-service): validate callback origin and fix test config Validate that the OIDC callback URL points to the expected Matrix server before sending session cookies, preventing cookie leakage to unexpected hosts. Also seed auth_url in test config mock so the getAuthCookie test actually verifies the correct endpoint is called.
by Khaled FER...
Succeeded
fix/admin-access-token
509e3123 fix(tom-server/token-service): handle cross-origin redirects in SSO token flow The admin access token acquisition broke because Node.js fetch strips cookies on cross-origin redirects. The SSO chain crosses from the auth provider to Matrix, so the OIDC session cookie never reached Synapse. Split getLoginToken into two explicit fetch calls — auth provider gets only the auth cookie, Matrix callback gets only the session cookies. Also fix cookie serialization: use getSetCookie() and strip attributes so the Cookie header contains clean name=value pairs instead of raw Set-Cookie values with Domain/Path/HttpOnly attributes.
by Khaled FER...