[receiver/oracledb] Add session, JVM, and OS resource metrics by rluidash · Pull Request #49068 · open-telemetry/opentelemetry-collector-contrib

rluidash · 2026-06-15T09:11:26Z

Description

The Oracle DB receiver scrapes v$sysstat with SELECT * FROM v$sysstat, which returns all system-statistics rows. However, the scraper only processes a subset of those rows in its switch block and silently discards the rest — including the session-activity, in-database JVM, and OS-resource statistics. This change surfaces 8 discarded v$sysstat statistics as 7 new opt-in metrics, giving operators visibility into how much real work sessions perform versus idle waiting, Oracle's embedded JVM (OJVM) call-heap pressure, and OS swap activity as the database process accounts for it.

This change adds 7 new opt-in metrics (disabled by default, stability: development):

oracledb.session.waits — Cumulative number of non-idle waits across sessions. Attribute: oracledb.session.wait.state (non_idle). Covers v$sysstat: non-idle wait count.
oracledb.session.wait.time — Cumulative time, in seconds, sessions spent in non-idle waits. Attribute: oracledb.session.wait.state (non_idle). Covers v$sysstat: non-idle wait time (the raw centisecond value is divided by 100 in the scraper).
oracledb.session.stored_procedure.memory — Memory, in bytes, currently allocated for stored procedures in the session. No attributes. Covers v$sysstat: session stored procedure space.
oracledb.jvm.memory.used — Used size, in bytes, of Oracle's in-database JVM (OJVM) call heap. No attributes. Covers v$sysstat: java call heap used size. Mirrors semconv jvm.memory.used for the embedded OJVM.
oracledb.jvm.memory.committed — Committed (total) size, in bytes, of the OJVM call heap. No attributes. Covers v$sysstat: java call heap total size. Mirrors semconv jvm.memory.committed.
oracledb.jvm.memory.live — Size, in bytes, of live objects in the OJVM call heap. No attributes. Covers v$sysstat: java call heap live size.
oracledb.os.swaps — Number of OS swap operations, as accounted by Oracle. No attributes. Covers v$sysstat: OS Swaps.

Types/units: oracledb.session.waits (Sum int, {wait}), oracledb.session.wait.time (Sum double, s), oracledb.os.swaps (Sum int, {swap}) are cumulative monotonic Sums; oracledb.session.stored_procedure.memory and the three oracledb.jvm.memory.* are Gauges (int, By). The one time metric (oracledb.session.wait.time) converts centiseconds → seconds (÷100), matching the existing oracledb.cpu_time.

Changes since the initial submission (per review + integration testing):

Split the single oracledb.java.heap.usage (with a state attribute) into dedicated oracledb.jvm.memory.used / .committed / .live, aligning leaves with semconv jvm.memory.* while keeping the oracledb. namespace (avoids colliding with real JVM instrumentation and with Oracle SGA/PGA memory).

Renamed oracledb.session.non_idle.* → oracledb.session.waits / oracledb.session.wait.time and added the oracledb.session.wait.state attribute (non_idle) for future extensibility.

Dropped oracledb.process.last_non_idle.time (a raw epoch-seconds gauge with an unclear use case).

Dropped oracledb.process.cpu.time and the cpu.mode attribute. It was sourced from the v$sysstat statistics OS System time used / OS User time used, which are gated by timed_os_statistics (off by default and "very expensive" per Oracle), are never populated on Windows, and cannot be enabled on Amazon RDS. Integration testing on Oracle 19c confirmed both stay 0 even under sustained CPU load (while the existing oracledb.cpu_time advanced normally). The OS CPU split is reliably exposed by V$OSSTAT (USER_TIME/SYS_TIME), a different view that is the domain of separate work ([receiver/oracledb]: Add OS-level metrics from V$OSSTAT #48459) — so it should not be surfaced from these always-zero v$sysstat statistics.

These metrics can be enabled in the collector configuration:

receivers:
  oracledb:
    datasource: "oracle://user:password@host:1521/service"
    metrics:
      oracledb.session.waits:
        enabled: true
      oracledb.session.wait.time:
        enabled: true
      oracledb.session.stored_procedure.memory:
        enabled: true
      oracledb.jvm.memory.used:
        enabled: true
      oracledb.jvm.memory.committed:
        enabled: true
      oracledb.jvm.memory.live:
        enabled: true
      oracledb.os.swaps:
        enabled: true

Link to tracking issue

Fixes #49065

Testing

Unit tests added in scraper_test.go:

TestScraper_ScrapeSessionJVMOSMetrics exercises all 7 new metrics end-to-end through the scraper using the existing fake DB client, asserting one expected value per data point (7 data points per scrape across the 7 metrics).
The shared queryResponses[statsSQL] fixture is extended with 8 new fake v$sysstat rows (one per covered NAME), so TestScraper_Scrape, TestScraper_ScrapeOperationalMetrics, and TestScraper_ScrapeIOPerformanceMetrics continue to pass unchanged.
The test explicitly verifies the centiseconds → seconds conversion: raw 4500 cs from non-idle wait time produces 45.0 s on oracledb.session.wait.time.
Auto-generated tests in internal/metadata/generated_metrics_test.go and generated_config_test.go are regenerated by make generate and cover the new metric configs / metric builders.

Documentation

Auto-generated documentation.md updated with descriptions and metadata for the 7 new metrics and the new oracledb.session.wait.state attribute. internal/metadata/generated_*.go and internal/metadata/testdata/config.yaml regenerated via make generate. internal/metadata/config.schema.yaml was updated for the 7 new metric stanzas, as that file is not produced by make generate.

Authorship

I, a human, wrote this pull request description myself.

Surfaces session non-idle activity, in-database JVM (OJVM) call-heap, and OS CPU/swap statistics already returned by the existing system-statistics query as seven opt-in metrics. No new SQL queries are introduced.

thompson-tomo · 2026-06-15T13:43:48Z

+  oracledb.os.cpu.state:
+    description: Whether the OS CPU time was consumed in system (kernel) or user mode, as accounted by Oracle. Mirrors the semconv system.cpu.state value set.
+    type: string
+    enum: [system, user]


Suggested change

oracledb.os.cpu.state:

description: Whether the OS CPU time was consumed in system (kernel) or user mode, as accounted by Oracle. Mirrors the semconv system.cpu.state value set.

type: string

enum: [system, user]

cpu.mode:

description: The mode of the CPU

type: string

enum: [system, user]

As per https://opentelemetry.io/docs/specs/semconv/registry/attributes/cpu/#cpu-mode

Good call — switched to the semconv cpu.mode attribute and dropped the custom oracledb.os.cpu.state.

thompson-tomo · 2026-06-15T13:45:45Z

+  oracledb.java.heap.state:
+    description: Which portion of the in-database JVM call heap the measurement reports (live, total, or used).
+    type: string
+    enum: [live, total, used]


Suggested change

oracledb.java.heap.state:

description: Which portion of the in-database JVM call heap the measurement reports (live, total, or used).

type: string

enum: [live, total, used]

Removed — it's no longer needed now that the heap metric is split

thompson-tomo · 2026-06-15T13:48:02Z

+  oracledb.java.heap.usage:
+    attributes:
+      - oracledb.java.heap.state
+    description: Size of Oracle's in-database JVM (OJVM) call heap in bytes. Sourced from v$sysstat names java call heap live size (oracledb.java.heap.state=live), java call heap total size (oracledb.java.heap.state=total), and java call heap used size (oracledb.java.heap.state=used).
+    enabled: false
+    stability: development
+    gauge:
+      value_type: int
+      input_type: string
+    unit: By


Let's have dedicated metrics for the states and in fact couldn't we just use https://opentelemetry.io/docs/specs/semconv/runtime/jvm-metrics/#jvm-memory for 2 of them & the third use case?

Split into three dedicated gauges: oracledb.java.heap.used and oracledb.java.heap.committed mirror jvm.memory.used / jvm.memory.committed; oracledb.java.heap.live (live-object size) has no semconv equivalent. I kept the oracledb. namespace rather than emitting bare jvm.memory.* because this is Oracle's embedded OJVM call heap read from v$sysstat, not a standard JVM runtime — emitting jvm.memory.* from the DB receiver would collide with real JVM instrumentation in the same pipeline. Happy to switch to the literal names if you prefer.

Hmmm, i still feel we can be closer aligned in naming even when keeping it under the oracledb namespace.

Options would be:

oracledb.memory.used etc

oracledb.jvm.memory.used etc

I like the first as don't see jvm being necessary in name.

Renamed to oracledb.jvm.memory.used/committed/live to align the leaves with semconv jvm.memory.*. I kept jvm in the path rather than oracledb.memory.* because the latter reads as Oracle's overall memory (SGA/PGA) and would clash with the in-flight SGA work (#48542) — jvm scopes it unambiguously to the embedded OJVM. Happy to drop jvm if you still prefer.

thompson-tomo · 2026-06-15T13:51:39Z

+  oracledb.os.cpu.time:
+    attributes:
+      - oracledb.os.cpu.state
+    description: Cumulative OS CPU time consumed, in seconds (converted from centiseconds), as accounted by Oracle. Sourced from v$sysstat names OS System time used (oracledb.os.cpu.state=system) and OS User time used (oracledb.os.cpu.state=user).
+    enabled: false
+    stability: development
+    sum:
+      aggregation_temporality: cumulative
+      monotonic: true
+      value_type: double
+    unit: s


How does this differ to jvm.cpu.time?

They're unrelated. oracledb.os.cpu.time is OS-level CPU time (kernel + user) consumed by the Oracle server/background processes, as Oracle accounts it in v$sysstat (OS System/User time used, getrusage-derived) — not a JVM's CPU. Even vs system.cpu.time (hostmetrics), this is Oracle's per-instance self-accounting that DBAs correlate with DB workload and that differs from host totals in containers/VMs.

In that case what about process.cpu.time aka https://opentelemetry.io/docs/specs/semconv/system/process-metrics/#metric-processcputime

Renamed to oracledb.process.cpu.time to match semconv process.cpu.time; it keeps the cpu.mode attribute. The description notes it's Oracle's own process accounting from v$sysstat

"Following up on this — I've removed oracledb.process.cpu.time (and the cpu.mode attribute) rather than keep it. It was sourced from the v$sysstat stats OS System time used / OS User time used, which I found during integration testing read 0 on Oracle 19c even under sustained CPU load. They're gated by timed_os_statistics (off by default, documented as 'very expensive'), are never populated on Windows, and can't be enabled on Amazon RDS. The reliable OS-CPU split lives in V$OSSTAT (USER_TIME/SYS_TIME) — a different view that's the domain of #48459 — so it shouldn't be surfaced from these always-zero v$sysstat statistics. PR is now 7 metrics.

thompson-tomo · 2026-06-15T13:56:19Z

+  oracledb.process.last_non_idle.time:
+    description: Epoch time in seconds at which the process was last active (non-idle), as reported by Oracle. Sourced from v$sysstat name process last non-idle time.
+    enabled: false
+    stability: development
+    gauge:
+      value_type: int
+      input_type: string
+    unit: s


Not following on this use case. Wouldn't it be more useful to capture how long it has been idle for? Perhaps even have a status metric to capture if it is idle or active.

Dropped it. The intent was a coarse liveness signal (if the last-non-idle epoch stops advancing, processes are stuck), but you're right a raw epoch gauge is awkward and a useful idle-duration would need now − value math in the scraper, which the project discourages. Removed from this PR.

thompson-tomo · 2026-06-15T14:00:18Z

+  oracledb.session.non_idle.time:
+    description: Cumulative time sessions spent in non-idle waits, in seconds (converted from centiseconds). Sourced from v$sysstat name non-idle wait time.
+    enabled: false
+    stability: development
+    sum:
+      aggregation_temporality: cumulative
+      monotonic: true
+      value_type: double
+    unit: s
+  oracledb.session.non_idle.waits:
+    description: Cumulative number of non-idle waits across sessions. Sourced from v$sysstat name non-idle wait count.
+    enabled: false
+    stability: development
+    sum:
+      aggregation_temporality: cumulative
+      monotonic: true
+      value_type: int
+      input_type: string
+    unit: "{waits}"


Do we really need non_idle in the name couldn't we remove it & for the first metric have a state attribute to indicate non_idle

Renamed to oracledb.session.waits / oracledb.session.wait.time, with 'non-idle' kept in the descriptions. I didn't add a state attribute because v$sysstat only exposes the non-idle counters (no symmetric idle count/time), so it'd be single-valued — but I'm happy to add it for future extensibility if you'd rather.

Let's add it as an attribute for future extensibility and making the definition clear.

Added the oracledb.session.wait.state attribute (value non_idle) to both metrics — documents the non-idle semantics and leaves room for an idle value if Oracle ever exposes that counter.

…sion wait state - Rename java.heap.* to oracledb.jvm.memory.{used,committed,live} - Rename os.cpu.time to oracledb.process.cpu.time (keeps cpu.mode) - Add oracledb.session.wait.state (non_idle) to session waits/wait time

# Conflicts: # receiver/oracledbreceiver/internal/metadata/generated_metrics_test.go

…OS CPU stats are always 0) OS System/User time used require timed_os_statistics (off by default, expensive, unsettable on RDS, absent on Windows) and read 0 even under load on 19c/Linux. DB CPU is already covered by oracledb.cpu_time; host CPU is V$OSSTAT (open-telemetry#48459).

…riptions, simpler tests

…on-jvm-os # Conflicts: # receiver/oracledbreceiver/documentation.md # receiver/oracledbreceiver/internal/metadata/config.schema.yaml # receiver/oracledbreceiver/internal/metadata/generated_config.go # receiver/oracledbreceiver/internal/metadata/generated_config_test.go # receiver/oracledbreceiver/internal/metadata/generated_metrics.go # receiver/oracledbreceiver/internal/metadata/generated_metrics_test.go # receiver/oracledbreceiver/internal/metadata/testdata/config.yaml # receiver/oracledbreceiver/metadata.yaml # receiver/oracledbreceiver/scraper.go # receiver/oracledbreceiver/scraper_test.go

crobert-1 · 2026-07-07T21:36:58Z

+component: receiver/oracledb
+
+# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: Add session, in-database JVM, and OS resource metrics sourced from the existing v$sysstat query.


Suggested change

note: Add session, in-database JVM, and OS resource metrics sourced from the existing v$sysstat query.

note: Add session, in-database JVM, and OS resource metrics

The subtext provides enough context for the end user

crobert-1 · 2026-07-07T21:38:13Z

Please remove all unit references from metric descriptions. It will be clear enough from unit in the generated documentation.

Done — removed all unit references

crobert-1 · 2026-07-07T21:39:21Z

      input_type: string
    unit: "{row}"
+  oracledb.session.stored_procedure.usage:
+    description: Memory in bytes currently allocated for stored procedures in the session.


The description states this is memory, but the name has no memory reference. We should either add memory in the name or clarify.

Agreed — the name didn't convey memory. Renamed to oracledb.session.stored_procedure.memory (Gauge, By) so the metric name itself signals memory.

crobert-1 · 2026-07-07T21:40:35Z

+  oracledb.session.wait.time:
+    attributes:
+      - oracledb.session.wait.state
+    description: Cumulative time sessions spent in non-idle waits, in seconds.


The description should be more generic in case of future updates to the metric to account for other attribute values.

Done — updated the descriptions be generic

crobert-1 · 2026-07-07T21:40:40Z

+  oracledb.session.waits:
+    attributes:
+      - oracledb.session.wait.state
+    description: Cumulative number of non-idle waits across sessions.


The description should be more generic in case of future updates to the metric to account for other attribute values.

crobert-1 · 2026-07-07T21:41:30Z

Groups of strings/variables should be alphabetized

…ons/scraper Rename oracledb.session.stored_procedure.usage to oracledb.session.stored_procedure.memory so the name signals memory; trim the changelog note, remove unit references from descriptions, make the session-wait descriptions attribute-generic, and alphabetize the added constant/gate/case groups in scraper.go

crobert-1 · 2026-07-09T18:50:33Z

File should be updated to have lists in alphabetical order

rluidash · 2026-07-09T21:34:40Z

Hi @thompson-tomo, thanks again for the review here. I'm working toward OpenTelemetry org membership and would like to ask if you'd be willing to sponsor my application. My contribution track is focused on oracledbreceiver and in collector-contrib. Happy to move this to Slack or email — My handle is @rluidash.

…on-jvm-os # Conflicts: # receiver/oracledbreceiver/documentation.md # receiver/oracledbreceiver/internal/metadata/generated_config_test.go # receiver/oracledbreceiver/internal/metadata/generated_metrics.go # receiver/oracledbreceiver/metadata.yaml

crobert-1 · 2026-07-13T17:07:43Z

 				}
+			// Session, JVM & OS resources
+			case javaCallHeapLiveSize:
+				if err := s.mb.RecordOracledbJvmMemoryLiveDataPoint(now, row["VALUE"]); err != nil {


Can we use the file's colValue constant here? (I know we're just using "VALUE" directly earlier, but may as well start using the constant now)

crobert-1 · 2026-07-13T17:09:09Z

@@ -393,6 +401,55 @@ func TestScraper_ScrapeOperationalMetrics(t *testing.T) {
 }

 // scrapeWithConfig starts a scraper over the shared fake responses and returns one scrape.


This comment needs to be moved to be kept above the relevant method.

opentelemetry-pr-dashboard · 2026-07-13T17:18:26Z

This PR has review comments. Review suggestions, whether from maintainers or automated reviewers, aren't always correct or required. Please evaluate each comment on its merits, then make sure each thread has a clear outcome.

For example, link to the commit if you applied a suggestion, explain why it wasn't applied, or ask a follow-up question.

Automation flags a PR for human review once every review thread has a reply or is marked as resolved.

Status across open PRs is visible on the pull request dashboard.

…lacement

…on-jvm-os # Conflicts: # receiver/oracledbreceiver/internal/metadata/generated_config_test.go # receiver/oracledbreceiver/scraper_test.go

songy23

please fix merge conflicts

…on-jvm-os # Conflicts: # receiver/oracledbreceiver/documentation.md # receiver/oracledbreceiver/internal/metadata/config.schema.yaml # receiver/oracledbreceiver/internal/metadata/generated_config.go # receiver/oracledbreceiver/internal/metadata/generated_config_test.go # receiver/oracledbreceiver/internal/metadata/generated_metrics.go # receiver/oracledbreceiver/internal/metadata/generated_metrics_test.go # receiver/oracledbreceiver/internal/metadata/testdata/config.yaml # receiver/oracledbreceiver/metadata.yaml

rluidash · 2026-07-15T21:55:47Z

Done — conflicts resolved.

dmitryax · 2026-07-15T22:51:04Z

@rluidash please rebase once more

…on-jvm-os # Conflicts: # receiver/oracledbreceiver/internal/metadata/config.schema.yaml # receiver/oracledbreceiver/internal/metadata/generated_config_test.go # receiver/oracledbreceiver/metadata.yaml # receiver/oracledbreceiver/scraper.go # receiver/oracledbreceiver/scraper_test.go

otelbot · 2026-07-16T16:45:01Z

Thank you for your contribution @rluidash! 🎉 We would like to hear from you about your experience contributing to OpenTelemetry by taking a few minutes to fill out this survey.

…edbreceiver (open-telemetry#49068) Brings nroracledbreceiver to metric parity with base oracledbreceiver (93 -> 112) by porting the 19 metrics added upstream in open-telemetry#49068 and related commits: JVM call-heap memory (committed/live/used), OS swaps, non-idle session waits/wait-time, session stored-procedure memory, GC current-block time, recovery blocks, SMON posts, transaction lock time, transaction rollbacks, plus the sysmetric-derived cpu/host-cpu usage rates, cursor/PGA cache utilization, transaction response time, single-block read latency, and average active sessions. Adds the oracledb.session.wait.state and oracledb.smon.type attributes and extends oracledb.session.type to [background, foreground]. Wires the new stat names into the existing v$sysstat switch and the sysmetric names into recordSysmetric; no new query required. NR-specific behavior (per-PDB sysmetric/sysstat, SetOracleDbPdb, session-wait db.namespace) is preserved.

[receiver/oracledb] Add session, JVM, and OS resource metrics

92912db

Surfaces session non-idle activity, in-database JVM (OJVM) call-heap, and OS CPU/swap statistics already returned by the existing system-statistics query as seven opt-in metrics. No new SQL queries are introduced.

rluidash force-pushed the feat/oracledb-session-jvm-os branch from c03749c to 92912db Compare June 15, 2026 09:44

thompson-tomo reviewed Jun 15, 2026

View reviewed changes

[receiver/oracledb] Address review feedback on session/JVM/OS metrics

74edbfc

rluidash requested a review from thompson-tomo June 15, 2026 22:14

rluidash added 6 commits June 17, 2026 23:29

Merge upstream/main into feat/oracledb-session-jvm-os

dff3b8e

# Conflicts: # receiver/oracledbreceiver/internal/metadata/generated_metrics_test.go

[receiver/oracledb] Address semconv review: singular units, lean desc…

cd2fb03

…riptions, simpler tests

Trim oracledb session/JVM/OS changelog subtext

aa67916

rluidash marked this pull request as ready for review July 2, 2026 00:04

rluidash requested review from a team, atoulme, crobert-1 and dmitryax as code owners July 2, 2026 00:04

github-actions Bot assigned ChrsMark Jul 2, 2026

github-actions Bot added the receiver/oracledb label Jul 2, 2026

crobert-1 reviewed Jul 7, 2026

View reviewed changes

rluidash requested a review from crobert-1 July 8, 2026 09:16

crobert-1 reviewed Jul 9, 2026

View reviewed changes

Address review: alphabetize scraper and test lists

85fb117

github-actions Bot requested review from XSAM, akshays-19, ebrdarSplunk, splunk-shanu and sv-splunk July 10, 2026 05:49

rluidash requested a review from crobert-1 July 10, 2026 06:58

opentelemetry-pr-dashboard Bot mentioned this pull request Jul 10, 2026

Pull Request Dashboard #49441

Open

crobert-1 reviewed Jul 13, 2026

View reviewed changes

rluidash added 2 commits July 14, 2026 14:04

Address review: use colValue constant, fix scrapeWithConfig comment p…

e4c847c

…lacement

Merge remote-tracking branch 'upstream/main' into feat/oracledb-sessi…

b9dc6be

…on-jvm-os # Conflicts: # receiver/oracledbreceiver/internal/metadata/generated_config_test.go # receiver/oracledbreceiver/scraper_test.go

rluidash requested a review from crobert-1 July 15, 2026 05:29

crobert-1 approved these changes Jul 15, 2026

View reviewed changes

crobert-1 added the ready to merge Code review completed; ready to merge by maintainers label Jul 15, 2026

songy23 reviewed Jul 15, 2026

View reviewed changes

songy23 removed the ready to merge Code review completed; ready to merge by maintainers label Jul 15, 2026

rluidash requested review from crobert-1 and songy23 July 15, 2026 21:56

songy23 merged commit 4a9b938 into open-telemetry:main Jul 16, 2026
133 checks passed

github-actions Bot mentioned this pull request Jul 16, 2026

[receiver/otelarrowreceiver/internal/arrow]: Report for failed tests on main #48669

Open

	note: Add session, in-database JVM, and OS resource metrics sourced from the existing v$sysstat query.
	note: Add session, in-database JVM, and OS resource metrics

		@@ -393,6 +401,55 @@ func TestScraper_ScrapeOperationalMetrics(t *testing.T) {
		}

		// scrapeWithConfig starts a scraper over the shared fake responses and returns one scrape.

Uh oh!

Conversation

rluidash commented Jun 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Link to tracking issue

Testing

Documentation

Authorship

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

rluidash Jun 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

rluidash commented Jul 9, 2026

Uh oh!

rluidash commented Jun 15, 2026 •

edited

Loading

rluidash Jun 15, 2026 •

edited

Loading