Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

HttpInputParameters.readTimeOut typed as string — server expects integer (ms)

Open Beginner friendly
  • Is something wrong?
#138 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
91/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
typescript
Domain
api

Research direction

Start at src/open-api/types.ts:156 and compare readTimeOut with the correctly typed connectionTimeOut field at the preceding line. Change the declaration so numeric millisecond values are accepted, then verify the TypeScript checks pass and that the public type matches the server's Integer field.

Written by the indexing model from the issue text.

Description

bug

Summary

HttpInputParameters.readTimeOut is typed as string in src/open-api/types.ts:156.
The server's HttpTask.Input.readTimeOut is Integer (milliseconds). The sibling field
connectionTimeOut is correctly typed as number. The inconsistency is a bug.

Server baseline

Conductor 3.32.0-rc.9

Evidence

Static:

// src/open-api/types.ts:155-156
connectionTimeOut?: number;   // ✓ correct
readTimeOut?: string;         // ✗ should be number

Server:

// http-task/.../HttpTask.java:275
private Integer readTimeOut = 3000;

Live (2026-07-16): Server accepts both readTimeOut: 3000 (integer) and
readTimeOut: "3000" (string) due to Jackson coercion. However, the TypeScript type
is still wrong — passing a number for readTimeOut is a compile-time error with the
current type definition.

Impact

TypeScript users who pass readTimeOut: 5000 (the natural form) get a type error and
must write readTimeOut: "5000" (string), which is semantically confusing and diverges
from connectionTimeOut: 5000 (number).

Proposed fix

// src/open-api/types.ts:156
readTimeOut?: number;   // was: string

Related

Discovered during systematic SDK audit against Conductor OSS 3.32.0-rc.9.

Dominant language
TypeScript
Stars
58
Forks
20
Avg merge
6d 5h
Merged PRs (30d)
3

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

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 conductor-oss/javascript-sdk

All issues in conductor-oss/javascript-sdk

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.