fix(nwis): handle empty peaks response instead of raising KeyError by arpitjain099 · Pull Request #344 · DOI-USGS/dataretrieval-python

arpitjain099 · 2026-07-16T21:03:48Z

Calling nwis.get_discharge_peaks or get_record(service="peaks") for a site with no annual-peak data raises KeyError('peak_dt') instead of returning an empty result.

When peaks has no data, the RDB body is comment lines only, so read_rdb parses it to a column-less empty DataFrame. format_response runs preformat_peaks_response before its own "datetime not in columns" empty-frame check, and that function's first line pops peak_dt, which blows up on the empty frame.

This is the same empty-result behavior that #171 fixed for the other services; peaks slipped through because it gets preformatted first. The fix returns the frame unchanged when peak_dt is absent, so the existing empty-frame path in format_response takes over and callers can check df.empty rather than catching an exception.

Added a regression test in TestReadRdb next to the existing #171 coverage. It fails on main with KeyError('peak_dt') and passes with the change. ruff check and ruff format --check are clean on both touched files.

I work on supply-chain and data-tooling robustness and hit this while looking at the empty-response paths. Happy to adjust if you would rather guard this inside format_response instead.

nwis.get_discharge_peaks / get_record(service="peaks") against a site with no annual-peak data returns a peaks RDB body of comment lines only, which read_rdb parses to a column-less empty DataFrame. format_response runs preformat_peaks_response before its own empty-frame check, and that function's first statement pops "peak_dt", so the empty case raised KeyError('peak_dt') instead of returning an empty frame. This is the same empty-result contract fixed for the other services in issue DOI-USGS#171; peaks was missed because it is preformatted first. Return the frame unchanged when peak_dt is absent so the empty-frame path in format_response handles it and callers can check df.empty. Adds a regression test alongside the existing DOI-USGS#171 coverage. Signed-off-by: Arpit Jain <arpitjain099@gmail.com>

The empty-peaks test parsed with _read_rdb, which already runs format_response(service=None); the real get_discharge_peaks path uses the raw read_rdb parser followed by format_response(service="peaks"). Switch to read_rdb so the test exercises the actual call path without the redundant format pass. Signed-off-by: thodson-usgs <thodson@usgs.gov> Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Conflict was in tests/nwis_test.py, where main added TestGetRecordDispatch directly after the class this branch appends to; both sides kept. read_rdb has since moved to the dataretrieval.rdb leaf, so the test imports it from there rather than through the nwis adapter, and passes _NWIS_RDB_DTYPES to mirror what get_discharge_peaks now does. Retarget the test docstring at the defect that is actually reachable. get_discharge_peaks does not raise KeyError: every empty peaks response the live service returns starts "No sites/data", which _querying turns into NoSitesError before format_response is reached. The real gap is that format_response and preformat_peaks_response are public API and crash on a column-less frame, where every other service yields an empty one (issue DOI-USGS#171). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

thodson-usgs · 2026-08-26T21:25:32Z

Thanks for this — the fix is right and I've merged current main into the branch and pushed. Net change is still just the 7-line guard plus one regression test.

One correction to the premise, because I couldn't reproduce the headline symptom and I'd rather the test docstring not enshrine a repro that doesn't hold.

get_discharge_peaks doesn't actually raise KeyError. Every genuinely empty peaks response the live service returns is the legacy sentinel body, which _querying converts to NoSitesError before format_response is reached. I probed six cases against nwis.waterdata.usgs.gov/nwis/peaks:

case	body
streamgage, empty future window	`No sites/data found…` → `NoSitesError`
groundwater-only site	`No sites/data found…` → `NoSitesError`
nonexistent site	`No sites/data found…` → `NoSitesError`
streamgage, pre-record window	HTML error page → `ValueError` from `read_rdb`
`stateCd=HI`, narrow window	651 KB of data (peaks ignores the date filter)
control, site with peaks	normal RDB

So the getter path is already guarded.

The defect is real anyway, one level down. format_response and preformat_peaks_response are both public, documented API (automodule :members:), and on current main:

read_rdb(comment_only_rdb) -> (0, 0) empty frame
format_response(df, service="peaks") -> KeyError: 'peak_dt'
format_response(df, service=None)    -> OK, empty frame

That asymmetry is exactly what issue #171 established shouldn't happen, and peaks is the one arm that still violates it — because preformat_peaks_response runs before the "datetime" not in df.columns check. So the guard belongs where you put it. I've reworded the test docstring to describe that path rather than the getter.

This also sits inside ADR 0005, which permits "compatibility, security, and correctness fixes only" on the deprecated nwis facade — a correctness fix, no new capability.

What I changed while resolving:

read_rdb has since moved to the dataretrieval.rdb leaf, so the test imports it from there rather than through the nwis adapter, and passes _NWIS_RDB_DTYPES to mirror what get_discharge_peaks now does.
Trimmed the inline comment to the constraint; the history lives in the commit message.
Conflict was TestGetRecordDispatch landing right where this branch appends; both sides kept.

Verified: the new test fails with KeyError: 'peak_dt' without the guard and passes with it; 1130 tests pass; mypy --strict, ruff, Xenon, complexipy and import-linter all clean.

One thing I deliberately left alone: there are now two different empty-result behaviors for NWIS — NoSitesError when the body starts with the sentinel, an empty frame when the RDB is comment-only. That predates this PR and isn't its job to reconcile, but it's worth a follow-up issue.

Review follow-ups on the empty-peaks guard. The guard fired on any frame missing peak_dt, including a non-empty one from a truncated or altered RDB header. Such a frame is malformed rather than empty, and was being returned silently without its datetime index where it used to raise. Require df.empty too, and pin it with a test. Correct the regression test's docstring, which said the empty responses get_discharge_peaks sees are caught earlier as NoSitesError. That check fires only on a body starting "No sites/data" -- what the live service happens to send today -- so a comment-only RDB does reach the guarded line. As written the docstring read as "this guard is unreachable", inviting its deletion. Widen the test class docstring to cover both arms it now holds, document the pass-through in preformat_peaks_response's public docstring, and add the NEWS entry this behavior change warrants. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

thodson-usgs · 2026-08-26T21:40:23Z

Ran a review pass over the branch and pushed the follow-ups. No functional bug in the fix itself; these are contract and documentation issues.

The guard was broader than intended. if "peak_dt" not in df.columns also fired on a non-empty frame missing that column — a truncated or altered RDB header. That frame is malformed rather than empty, and was being returned silently without its datetime index where it previously raised. Now if df.empty and "peak_dt" not in df.columns, with a test pinning that a malformed non-empty frame still raises.

I had overstated the NoSitesError guard in the test docstring I wrote on the last push. I said the empty responses get_discharge_peaks sees are caught earlier as NoSitesError — but that check fires only on a body starting No sites/data, which is what the live service happens to send today. A comment-only RDB does reach the guarded line. As written the docstring read as "this guard is unreachable", which invites someone deleting it. Reworded.

Also: widened the test class docstring so it still describes its contents, documented the pass-through in preformat_peaks_response's public docstring, and added the NEWS entry this behavior change warrants.

Verified: 1131 tests pass; mypy --strict, ruff, Xenon, complexipy and import-linter all clean.

One thing I deliberately left out: a mocked test driving get_discharge_peaks end-to-end. It would pass, but it pins a response shape the live service doesn't produce — I probed six empty cases and every one returns the No sites/data sentinel. The unit-level test covers the path callers actually reach.

Separate follow-up, not folded in here: rdb.read_rdb has the same empty-result hole one step earlier — read_rdb("# //Output-Format: RDB\n#\n\n") raises pandas.errors.EmptyDataError rather than returning an empty frame, because header_idx lands on the blank line. Confirmed, but it lives in the shared rdb leaf, so it belongs in its own change rather than growing this one.

arpitjain099 · 2026-09-02T11:11:40Z

@thodson-usgs Your narrowing is right. df.empty and "peak_dt" not in df.columns is the correct guard. Mine fired on a malformed non-empty frame as well and would have handed it back silently without its datetime index.

On the conflicts: I resolved them locally and the branch comes out empty against main. #395 already carries the guard and an equivalent malformed-frame test, and merging this as-is would revert the censored-peaks work. It restores df.pop("peak_dt") and the dropna(subset=["datetime"]) that #395 removed, and drops the three peaks tests. So I'd close this as superseded unless you want it open for something.

Happy to take the rdb.read_rdb follow-up you flagged. read_rdb("# //Output-Format: RDB\n#\n\n") raising EmptyDataError because header_idx lands on the blank line is the same hole one layer down, and it is self-contained enough for its own change. I'll open an issue for it first unless you'd rather go straight to a patch.

Main absorbed this PR's empty-peaks guard via DOI-USGS#395 (censored peaks), so the code and NEWS conflicts resolve to upstream wholesale — keeping this branch's version of preformat_peaks_response would have reverted DOI-USGS#395's keep-censored- peaks behavior (it popped peak_dt and dropped NaT rows). The branch's remaining net contribution is the malformed-frame regression test; its duplicate empty-peaks test (now redundant with main's) and the _NWIS_RDB_DTYPES import it needed are dropped. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JAEQqs7XzQHGQQi2KakuXD

thodson-usgs · 2026-09-02T13:26:36Z

@arpitjain099 , the bot found #395 while reviewing your PR, but I merged out of order and it clobbered your fix. Sorry about that. I trimmed this PR to a regression test rather than closing it. Thanks for finding the bug!

The merge resolved that file with ``git checkout --ours``, which takes the whole ours-side blob rather than the one conflicted region, so everything main brought to the file was reverted: - ``TestReadRdb::test_malformed_peaks_frame_still_raises``, the regression test from DOI-USGS#344 -- the suite went 1154 -> 1153 and nothing flagged it, since a missing test cannot fail. - 36 lines of copy edits from DOI-USGS#417 and DOI-USGS#418, the passes that replaced figurative wording with literal ("has no opinion about it" -> "does not record it", "borrowing" -> "importing"). Redone as a three-way merge of the file with only the conflicted region resolved by hand. That region is main's copy edit of ``test_named_replacement_exists_in_waterdata``, a test this branch had already replaced with the stronger ``test_named_replacement_resolves`` (ARG001: the old one never read its ``name`` parameter). The replacement stands, with main's edits carried into its docstring -- the "Tripwire:" prefix and the contraction dropped, matching the pass that removed the only other instance of each in ``tests/``.

#398) * fix(waterdata): write downloaded ratings as UTF-8 `get_ratings(..., file_path=...)` wrote each rating with `open(..., "w")` and no encoding, so the bytes on disk depended on the writing machine's locale rather than on what the service sent. On a non-UTF-8 locale an unrepresentable character raises `UnicodeEncodeError`, which is a `ValueError`, which `_download_all`'s per-feature handler downgrades to a `SkippedRatingWarning` -- so the rating disappears from the returned dict rather than failing loudly, which is the opposite of what the function's own docstring promises. `newline=""` disables the translation that would otherwise rewrite the RDB's line endings on Windows. The regression test asserts the saved file equals the response body byte for byte, using a character absent from cp1252, so it fails on the Windows leg without the fix and cannot fail on Linux or macOS. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01T6MVcko4gh68LieGWxUnrR * fix(waterdata): move the ratings write off the event loop The same `open()` was a blocking call inside `async def _fetch_rating`, which runs dozens-concurrent under a fan-out drive -- so every rating write stalled every other in-flight download for its duration. The write is now a three-line `_write_rating` dispatched through `anyio.to_thread.run_sync`. Nothing in the suite would have caught this: the tests await mocked transports, so a stalled loop still passes. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01T6MVcko4gh68LieGWxUnrR * fix(nwis): stop setting the index on the caller's frame in place `format_response` set the index with `inplace=True` on the frame it was handed while already returning a new object -- and already left the caller's frame untouched on the `peaks` and GeoDataFrame paths, so the in-place branch was the odd one out. Callers using the return value, which is the only documented use, see no difference. `pandas` is also phasing `inplace=` out. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01T6MVcko4gh68LieGWxUnrR * fix(nwis): warn for the get_record options whose services are defunct `get_record`'s `wide_format`, `datetime_index` and `state` have read nothing since `qwdata`, `gwlevels` and `water_use` were retired -- their only readers went with those branches -- but all three stayed in the signature and in the published docstring. `get_record(sites=..., state="OH")` therefore reads as a state filter while doing nothing at all. Verified against the tree before `491eb5c3` ("remove usage of qwdata"), where `get_record` passed `wide_format` and `datetime_index` to `get_qwdata`, `datetime_index` to `get_gwlevels`, and `state` to `get_water_use` -- the four readers (`if wide_format:`, two `if datetime_index is True:`, and `if state is not None:`) that went with those functions. Nothing in the package reads any of the three today. They now advise through `_deprecation.warn_deprecated`, naming a live replacement each, and are still accepted and still ignored. Naming one at its declared default is silent: the caller is asking for exactly what the dead default already gave them, so only a value the option cannot honour is worth a warning. A test pins that, and with it the agreement between the table's "unset" value and `get_record`'s declared default that the distinction rests on. They are not raised on and not deleted: - A defunct *service* cannot return the data asked for; `get_record( service="dv", wide_format=False)` returns exactly the right data, and only the knob is dead. Raising would retire a documented parameter of a Production/Stable getter ~20 months before `REMOVALS["nwis"]` with no warned release in between. - Deleting `state` from the signature would let it fall through `**kwargs` to `query_waterservices` and onto the wire as a parameter NWIS does not define. Confirmed against the live code path: an unknown *string* kwarg reaches the query string, while an unknown *bool* is dropped, because `to_str` returns `None` for a non-iterable scalar. So the argument for keeping the parameter holds for `state` alone. A call naming all three emits four `DeprecationWarning`s: one from `@_deprecated` plus one per option. They are not duplicates -- each names a distinct subject and a distinct replacement -- but `_warn_defunct_record_options` raises through `warn_deprecated` directly and so does not pass through `_deprecated`'s re-entrancy guard. The count is pinned by a test, as is the attribution the hand-counted `stacklevel=4` encodes. The replacement tripwire is now derived from the deprecation tables themselves rather than from a hand-kept list, and checks the keywords a message names as well as the function. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01T6MVcko4gh68LieGWxUnrR * lint(ruff): fix what the checks in the next commit found Everything the newly selected rules reported that is not a bug in its own right, kept apart from the config change so the config commit is only config: - `D100`: `dataretrieval.codes` and `dataretrieval.waterdata.types` are rendered by `automodule ... :members:`, so a missing module docstring ships to the docs site as a bare signature. `setup.py` and `docs/source/conf.py` get one-liners. - `ARG001`: `_display_api_key` and `_display_progress` never read `adapter`; it is there because the display registry calls every renderer with the same signature, so the name is prefixed rather than removed. - `RUF100`: four `# noqa: BLE001` directives sat on handlers that re-raise and never needed one. Four more carried their reason after a dash or in parentheses -- ruff reads the rest of the line as the directive's description and would delete a co-located `# pylint: disable=` with it -- so they are respelled with a second `#`. - `PLW1514`: the test helpers that read fixture files now name an encoding. - `PD002`: `_parse_parameter_record` returns the renamed frame rather than renaming in place; the frame is local, so nothing outside changes. - `PD003`: `isnull` -> `isna`. - `DTZ007`: `ogc/dates.py`'s `_parse_datetime` is correct by design -- `_DATETIME_FORMATS` deliberately carries both the `%z` and the bare forms, and the docstring promises tz-awareness only for an input that carried an offset. It takes a directive naming the reason rather than a "fix". Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01T6MVcko4gh68LieGWxUnrR * lint(ruff): select the checks no other gate covers, and pin the linter Config only; the findings are fixed in the commits before this one. ## The rules - `PLW1514` -- mypy does not model encodings, and a locale-dependent write misbehaves only on the Windows leg, so a green Linux run proves nothing. Found the silent rating loss. - `ARG001` -- notices when retiring a legacy getter strands a documented keyword. Found the three inert `get_record` options. - `ASYNC` -- the suite awaits mocked transports, so a stalled event loop still passes. Found the blocking ratings write. - `D100`-`D104` -- `automodule ... :members:` renders a docstring-less public symbol as a bare signature. - `RUF100` -- nothing was watching the suppressions. Six `# noqa: BLE001` directives sat in the tree suppressing a rule nobody had selected. - `BLE001` -- a blind `except Exception` skips ADR 0004's transient-versus- fatal judgement. Already half-adopted, via those six directives. - `PD`, `DTZ` -- `inplace=` is on pandas' way out, in a pandas library; a naive `datetime` in a library about time series. - `C4` `LOG` `G` `T20` `FA` `NPY` -- free ratchets at today's setting. The suppression budget goes down, not up: four directives removed, one added. ## The flow - The version was pinned in three places and honoured in none: the pre-commit rev, CI and the `test` extra all said 0.16.1, while the machine that wrote this had 0.16.5 on `$PATH` and 0.15.12 in its venv -- `ruff format --check` disagreed by 28 files between them. It now lives in two: a `[lint]` extra that CI installs the way the `[metrics]` job already installs its own, and the `ruff-pre-commit` rev. The `test` extra reuses `dataretrieval[lint]`, as it already reuses `dataretrieval[type-check]`. - Pinned at 0.16.5, the current release. - `preview = true` enabled 52 rules to get one. `explicit-preview-rules` keeps the rest off: that count was 50 at 0.16.1 and is 52 at 0.16.5, four patch releases apart, and each would have arrived as a CI failure nobody selected. - `E501` was selected redundantly (already inside `E`) under a comment naming a `line-length` setting that did not exist. The value is now set explicitly, where it visibly governs both the checker and the formatter. Unrelated but found the same way: the mypy `anyio` override is dropped. Its rationale was a 3.9 target that a `match` statement would fail to parse, and `python_version` has been 3.10 since 1.2.0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01T6MVcko4gh68LieGWxUnrR * docs(news): record the two ratings fixes The `nwis.get_record` option deprecations and the `format_response` change are not called out: `nwis` is deprecated itself, and the entry covers interface changes and bug fixes to active modules. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01T6MVcko4gh68LieGWxUnrR * perf(nwis): keep the caller's frame without duplicating it Dropping `inplace=` from `format_response`'s `set_index` stopped the function from mutating its argument, but it also made the function copy the data. pandas resolves a non-inplace `set_index` to `self.copy(deep=None)`, and `BlockManager.copy` turns `deep=None` into a full deep copy whenever copy-on-write is off -- the default for all of pandas 2.x, which is what a Python 3.10 install gets, since pandas 3.0 requires 3.11. A shallow copy carries the same guarantee: the index lands on our frame and the columns stay shared. `set_index` then runs inplace on that copy, which is what the `noqa` records. The rest of the gap is `_localize_datetime_index`. `DataFrame.tz_localize` relabels one axis by duplicating every column, a copy main paid too. Retagging the index alone is equivalent -- asserted frame-equal against the old call on both the multi-index and single-index branches -- and costs nothing. Peak RSS for one call, measured in a fresh process on pandas 2.2.3: main inplace dropped here 2M rows, 1 site 108.0 123.3 46.2 MiB 2M rows, 8 sites 250.0 394.6 318.3 MiB 1M rows, 20 cols, 8 sites 389.2 456.6 288.7 MiB The narrow multi-site frame stays above main. Building a two-level MultiIndex while the source columns stay materialized is the price of leaving the caller's frame intact; only mutating the argument avoids it. The other two shapes fall below main because the tz_localize copy is gone. CPU improves alongside: 355 -> 319 ms on pandas 2.2.3 and 227 -> 215 ms on 3.0.5, for 2M rows across 8 sites. pandas 3.0.5 memory is unchanged throughout -- copy-on-write already made both copies shallow, which is why the suite cannot see any of this: CI runs 3.13 and 3.14. So the test asserts the property that does hold everywhere -- the argument keeps its columns and its index -- which fails against the in-place version on both branches. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QVhHGSDkVxWzeUMmHn6oAT * fix(nwis): stop the peaks path writing into the caller's frame A review of the previous commit found that the invariant its test states is broader than what the code delivers. `preformat_peaks_response` derives `datetime` from `peak_dt` with a plain assignment, so `format_response(df, service="peaks")` still added a column to the frame it was handed: the shallow copy the previous commit introduced sits downstream of that call. `preformat_peaks_response` is public in its own right, so a caller reaches the mutation without going through `format_response` at all. It now derives the column on its own frame, and the test class covers the peaks arm alongside the plain ones. That also settles a claim in e773171, which said the function already left the caller's frame untouched on the peaks and GeoDataFrame paths. It held for GeoDataFrame only. It holds for both now. `_localize_datetime_index` loses its frame wrapper. Its one caller hands it a frame it has just shallow-copied, so the second copy -- and the identity guard that existed to avoid it -- protected a caller that no longer exists. As `_localized_datetime_index` it takes an index and returns one, and the caller assigns. Frame-equal to the previous form on pandas 2.2.3 and 3.0.5 across single-site, multi-site, already-aware and no-datetime frames; peak RSS is unchanged at 46.2 / 317.3 / 288.6 MiB on the three shapes the previous commit measured. The `datetime_index` entry told a caller to reach for `waterdata.get_continuous` or `get_daily` "which index by datetime". Neither does: no getter under `waterdata/` sets an index, and the suite pins `time` as an ordinary column. The recommendation is right, the reason given for it was not. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QVhHGSDkVxWzeUMmHn6oAT * fix(merge): restore what main brought to tests/nwis_test.py The merge resolved that file with ``git checkout --ours``, which takes the whole ours-side blob rather than the one conflicted region, so everything main brought to the file was reverted: - ``TestReadRdb::test_malformed_peaks_frame_still_raises``, the regression test from #344 -- the suite went 1154 -> 1153 and nothing flagged it, since a missing test cannot fail. - 36 lines of copy edits from #417 and #418, the passes that replaced figurative wording with literal ("has no opinion about it" -> "does not record it", "borrowing" -> "importing"). Redone as a three-way merge of the file with only the conflicted region resolved by hand. That region is main's copy edit of ``test_named_replacement_exists_in_waterdata``, a test this branch had already replaced with the stronger ``test_named_replacement_resolves`` (ARG001: the old one never read its ``name`` parameter). The replacement stands, with main's edits carried into its docstring -- the "Tripwire:" prefix and the contraction dropped, matching the pass that removed the only other instance of each in ``tests/``. * docs: clarify deprecation guidance and review terminology --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>

arpitjain099 and others added 3 commits July 17, 2026 06:03

thodson-usgs mentioned this pull request Aug 26, 2026

fix(nwis): keep censored peaks instead of dropping or dating them #395

Merged

thodson-usgs added the bug Something isn't working label Aug 27, 2026

thodson-usgs requested a review from ehinman August 27, 2026 13:35

thodson-usgs merged commit b146c0e into DOI-USGS:main Sep 2, 2026
11 checks passed

Navigation Menu

fix(nwis): handle empty peaks response instead of raising KeyError - #344

fix(nwis): handle empty peaks response instead of raising KeyError#344
thodson-usgs merged 5 commits into
DOI-USGS:mainfrom
arpitjain099:chore/nwis-empty-peaks

arpitjain099 commented Jul 16, 2026

Uh oh!

thodson-usgs commented Aug 26, 2026

Uh oh!

thodson-usgs commented Aug 26, 2026

Uh oh!

arpitjain099 commented Sep 2, 2026

Uh oh!

thodson-usgs commented Sep 2, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

arpitjain099 commented Jul 16, 2026

Uh oh!

thodson-usgs commented Aug 26, 2026

Uh oh!

thodson-usgs commented Aug 26, 2026

Uh oh!

arpitjain099 commented Sep 2, 2026

Uh oh!

thodson-usgs commented Sep 2, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants