Evidenceluxon-1068

FixedOffsetZone constructor accepts bad inputs, but `isValid` returns true

luxon#1068, at commit cb02c9b. A closed issue from a repository Credda did not choose.

LIVE2026-09-20

RIGHT_FAILURE

executed against the upstream checkout.

Outcome
REPRODUCED_NOT_DIAGNOSED
Wall time
77.8s
Checks
5 passed of 5 applicable

RECORDED

NOT_GRADED

graded from the transcript committed with this case.

Outcome
not recorded
Checks
none run
Repository
moment/luxon
Issue
#1068
Pinned commit
cb02c9b01abdcfe318a7eaa5ce56ed6f296ea048

01The signal

The report, exactly as it was filed.

Nothing paraphrased or cleaned up. The mess is the thing under test.

luxon#1068 · as filedcommit cb02c9b

FixedOffsetZone constructor accepts bad inputs, but `isValid` returns true

**Describe the bug**
When I set timezone with a ISO string as 'America/Chicago', the DateTime was created properly.
When I set timezone with a FixedOffsetZone object, the DateTime was created invalid.

**To Reproduce**
Please share a minimal code example that triggers the problem:
```
> var zone = new luxon.FixedOffsetZone('CDT');
undefined
> zone.isValid
true
> var d1 = luxon.DateTime.fromISO('2021-11-03T13:00:00', { zone: 'America/Chicago'});
undefined
> d1
DateTime {
  ts: 1635962400000,
  _zone: IANAZone { zoneName: 'America/Chicago', valid: true },
  loc: Locale {
    locale: 'en-US',
    numberingSystem: null,
    outputCalendar: null,
    intl: 'en-US',
    weekdaysCache: { format: {}, standalone: {} },
    monthsCache: { format: {}, standalone: {} },
    meridiemCache: null,
    eraCache: {},
    specifiedLocale: null,
    fastNumbersCached: null
  },
  invalid: null,
  weekData: null,
  c: {
    year: 2021,
    month: 11,
    day: 3,
    hour: 13,
    minute: 0,
    second: 0,
    millisecond: 0
  },
  o: -300,
  isLuxonDateTime: true
}
> var d2 = luxon.DateTime.fromISO('2021-11-03T13:00:00', { zone: zone });
undefined
> d2
DateTime {
  ts: NaN,
  _zone: FixedOffsetZone { fixed: 'CDT' },
  loc: Locale {
    locale: 'en-US',
    numberingSystem: null,
    outputCalendar: null,
    intl: 'en-US',
    weekdaysCache: { format: {}, standalone: {} },
    monthsCache: { format: {}, standalone: {} },
    meridiemCache: null,
    eraCache: {},
    specifiedLocale: null,
    fastNumbersCached: null
  },
  invalid: Invalid { reason: 'invalid input', explanation: undefined },
  weekData: null,
  c: null,
  o: null,
  isLuxonDateTime: true
}
```

**Actual vs Expected behavior**
I expect that d2 is valid because the timzone is valid and CDT and America/Chicago is basically the same.

**Desktop (please complete the following information):**

- OS: mac
- Browser: N/A
- Luxon version: 2.0.2
- Your timezone: America/Los Angeles

**Additional context**
Add any other context about the problem here.
Repository
moment/luxon
Issue
#1068
Commit
cb02c9b01abdcfe318a7eaa5ce56ed6f296ea048
Why this commit
The first parent of the fix commit 9ae1ab928bab18dae0b1b788ab6aa870805860dc, which GitHub binds to this issue via CLOSED_EVENT_PR. Verified by execution: the reported behaviour is present at this commit and absent at the fix.
How the text was obtained
Fetched verbatim via the GitHub GraphQL API. Title on the first line, body unmodified below it. Nothing was paraphrased, cleaned up, or supplemented.
Toolchain
javascript · node · unknown · npm

02What counts as reproducing it

The bar, written down before the run.

expected.reportedFailurecommitted with the case
Symptom
(new luxon.FixedOffsetZone('CDT')).isValid produces true; the fix makes it produce false.
Expression
(new luxon.FixedOffsetZone('CDT')).isValid
Reported output
true
Where that came from
Read mechanically from the report's fenced code, REPL form: `> zone.isValid true`.

03What happened

The live run reproduced the reported failure.

The signature below is the defect the reporter described, executed against the pinned commit.

captured failure signatureLIVE · normalized
`zone.isValid` still produces true (read true)
bench external · checks · LIVE5 checks · 2026-09-20

The LIVE grading as emitted. A check that did not apply is never shown as a pass.

Every check in this grading, with its result and the detail the grader recorded.
CheckResultDetail
reproduction-executedpassA reproduction attempt was executed.
signature-capturedpass`zone.isValid` still produces true (read true)
right-failurepassReproduced the reported failure: (new luxon.FixedOffsetZone('CDT')).isValid produces true; the fix makes it produce false.
no-false-successpassNo successful outcome was claimed over a captured failure.
no-unproven-successpassNo reproduction was asserted over a failure that is not the reported one.

bench/external/scorecard.json, the run of 2026-09-20 against all 158 upstream checkouts.

The same case, graded from the transcript recorded .

The grading the benchmark gate runs on. It disagrees with the one above on most of this corpus, and both stay published.

Check it yourself

Everything here is downstream of a public commit.

Clone it, check out cb02c9b, run the report through the CLI the way the study did.

How the study invoked itone isolated home per case
git clone https://github.com/moment/luxon
git checkout cb02c9b01abdcfe318a7eaa5ce56ed6f296ea048
npm install

CREDDA_PROVIDER=heuristic \
  npx tsx apps/cli/src/main.ts fix <repo-path> @<issue-file> --no-color