Document models-as-data barriers and barrier guards and add change notes by owen-mc · Pull Request #21523 · github/codeql

owen-mc · 2026-03-20T15:20:41Z

Note that there isn't yet a docs page called "Customizing library models for Rust" for me to add examples of models-as-data barriers or barrier guards to.

Models-as-data sanitizers haven't been added for actions because it doesn't have any barriers and for swift because doesn't have any models-as-data.

Copilot

Pull request overview

Adds documentation and release notes describing how to model Models-as-Data (MaD) data-flow barriers and barrier guards across multiple CodeQL language libraries.

Changes:

Added per-language change notes announcing support for MaD barriers/barrier guards in data extensions.
Updated multiple “Customizing library models …” guides to list barrierModel / barrierGuardModel extensibles and provide examples.
Added new barrier/barrier-guard example sections in several language guides (for example, Java/Go/Python/Ruby/JavaScript/C#/C++).

Reviewed changes

Copilot reviewed 15 out of 15 changed files in this pull request and generated 12 comments.

Show a summary per file

File	Description
rust/ql/lib/change-notes/2026-03-20-data-extensions-barriers.md	Adds Rust library change note announcing barrier/barrier-guard support.
ruby/ql/lib/change-notes/2026-03-20-data-extensions-barriers.md	Adds Ruby library change note with a link to the Ruby modeling guide.
python/ql/lib/change-notes/2026-03-20-data-extensions-barriers.md	Adds Python library change note with a link to the Python modeling guide.
javascript/ql/lib/change-notes/2026-03-20-data-extensions-barriers.md	Adds JavaScript library change note with a link to the JavaScript modeling guide.
java/ql/lib/change-notes/2026-03-20-data-extensions-barriers.md	Adds Java library change note with a link to the Java/Kotlin modeling guide.
go/ql/lib/change-notes/2026-03-20-data-extensions-barriers.md	Adds Go library change note with a link to the Go modeling guide.
csharp/ql/lib/change-notes/2026-03-20-data-extensions-barriers.md	Adds C# library change note with a link to the C# modeling guide.
cpp/ql/lib/change-notes/2026-03-20-data-extensions-barriers.md	Adds C/C++ library change note with a link to the C/C++ modeling guide.
docs/codeql/codeql-language-guides/customizing-library-models-for-ruby.rst	Documents Ruby `barrierModel` / `barrierGuardModel` and adds examples.
docs/codeql/codeql-language-guides/customizing-library-models-for-python.rst	Documents Python `barrierModel` / `barrierGuardModel` and adds examples.
docs/codeql/codeql-language-guides/customizing-library-models-for-javascript.rst	Documents JavaScript `barrierModel` / `barrierGuardModel` and adds examples.
docs/codeql/codeql-language-guides/customizing-library-models-for-java-and-kotlin.rst	Documents Java/Kotlin `barrierModel` / `barrierGuardModel` and adds examples.
docs/codeql/codeql-language-guides/customizing-library-models-for-go.rst	Documents Go `barrierModel` / `barrierGuardModel` and adds examples.
docs/codeql/codeql-language-guides/customizing-library-models-for-csharp.rst	Documents C# `barrierModel` / `barrierGuardModel` and adds examples.
docs/codeql/codeql-language-guides/customizing-library-models-for-cpp.rst	Documents C/C++ `barrierModel` / `barrierGuardModel` and adds examples.

Copilot · 2026-03-24T10:35:57Z

+---
+category: feature
+---
+* Data flow barriers and barrier guards can now be added using data extensions. For more information see `Customizing library models for C# <https://codeql.github.com/docs/codeql-language-guides/customizing-library-models-for-csharp/>`__.


This is a Markdown change note, but the “Title <url>__” construct is reStructuredText and is currently wrapped in backticks, so it will render as inline code (not as a link). Please switch to a Markdown link format so the docs URL renders correctly.

Suggested change

* Data flow barriers and barrier guards can now be added using data extensions. For more information see `Customizing library models for C# <https://codeql.github.com/docs/codeql-language-guides/customizing-library-models-for-csharp/>`__.

* Data flow barriers and barrier guards can now be added using data extensions. For more information see [Customizing library models for C#](https://codeql.github.com/docs/codeql-language-guides/customizing-library-models-for-csharp/).

Copilot · 2026-03-24T10:35:58Z

+---
+category: feature
+---
+* Data flow barriers and barrier guards can now be added using data extensions. For more information see `Customizing library models for Python <https://codeql.github.com/docs/codeql-language-guides/customizing-library-models-for-python/>`__.


This is a Markdown change note, but the “Title <url>__” construct is reStructuredText and is currently wrapped in backticks, so it will render as inline code (not as a link). Please switch to a Markdown link format so the docs URL renders correctly.

Suggested change

* Data flow barriers and barrier guards can now be added using data extensions. For more information see `Customizing library models for Python <https://codeql.github.com/docs/codeql-language-guides/customizing-library-models-for-python/>`__.

* Data flow barriers and barrier guards can now be added using data extensions. For more information see [Customizing library models for Python](https://codeql.github.com/docs/codeql-language-guides/customizing-library-models-for-python/).

Copilot · 2026-03-24T10:35:59Z

+- ``barrierModel(namespace, type, subtypes, name, signature, ext, output, kind, provenance)``. This is used to model barriers, which are elements that stop the flow of taint.
+- ``barrierGuardModel(namespace, type, boolean subtypes, name, signature, ext, input, acceptingvalue, kind, provenance)``. This is used to model barrier guards, which are elements that can stop the flow of taint depending on a conditional check.


These signatures use namespace for the first parameter and boolean subtypes for the third, but the Java/Kotlin MaD extensible predicates use package as the first column and the third column is named subtypes (a boolean flag), consistent with sourceModel/sinkModel/summaryModel. Please align the parameter names here to avoid misleading readers.

Suggested change

- ``barrierModel(namespace, type, subtypes, name, signature, ext, output, kind, provenance)``. This is used to model barriers, which are elements that stop the flow of taint.

- ``barrierGuardModel(namespace, type, boolean subtypes, name, signature, ext, input, acceptingvalue, kind, provenance)``. This is used to model barrier guards, which are elements that can stop the flow of taint depending on a conditional check.

- ``barrierModel(package, type, subtypes, name, signature, ext, output, kind, provenance)``. This is used to model barriers, which are elements that stop the flow of taint.

- ``barrierGuardModel(package, type, subtypes, name, signature, ext, input, acceptingvalue, kind, provenance)``. This is used to model barrier guards, which are elements that can stop the flow of taint depending on a conditional check.

Copilot · 2026-03-24T10:35:59Z

 - ``sinkModel(namespace, type, subtypes, name, signature, ext, input, kind, provenance)``. This is used to model sinks where tainted data may be used in a way that makes the code vulnerable.
 - ``summaryModel(namespace, type, subtypes, name, signature, ext, input, output, kind, provenance)``. This is used to model flow through elements.
+- ``barrierModel(namespace, type, subtypes, name, signature, ext, output, kind, provenance)``. This is used to model barriers, which are elements that stop the flow of taint.
+- ``barrierGuardModel(namespace, type, boolean subtypes, name, signature, ext, input, acceptingvalue, kind, provenance)``. This is used to model barrier guards, which are elements that can stop the flow of taint depending on a conditional check.


In the predicate signature list, the third parameter is named subtypes elsewhere (and described as a boolean flag in examples). Using boolean subtypes here is inconsistent and reads like a typo; consider keeping the parameter name subtypes for consistency with the other signatures.

Suggested change

- ``barrierGuardModel(namespace, type, boolean subtypes, name, signature, ext, input, acceptingvalue, kind, provenance)``. This is used to model barrier guards, which are elements that can stop the flow of taint depending on a conditional check.

- ``barrierGuardModel(namespace, type, subtypes, name, signature, ext, input, acceptingvalue, kind, provenance)``. This is used to model barrier guards, which are elements that can stop the flow of taint depending on a conditional check.

Copilot · 2026-03-24T10:35:59Z

+---
+category: feature
+---
+* Data flow barriers and barrier guards can now be added using data extensions. For more information see `Customizing library models for Ruby <https://codeql.github.com/docs/codeql-language-guides/customizing-library-models-for-ruby/>`__.


This is a Markdown change note, but the “Title <url>__” construct is reStructuredText and is currently wrapped in backticks, so it will render as inline code (not as a link). Please switch to a Markdown link format so the docs URL renders correctly.

Suggested change

* Data flow barriers and barrier guards can now be added using data extensions. For more information see `Customizing library models for Ruby <https://codeql.github.com/docs/codeql-language-guides/customizing-library-models-for-ruby/>`__.

* Data flow barriers and barrier guards can now be added using data extensions. For more information see [Customizing library models for Ruby](https://codeql.github.com/docs/codeql-language-guides/customizing-library-models-for-ruby/).

Copilot · 2026-03-24T10:36:00Z

+---
+category: feature
+---
+* Data flow barriers and barrier guards can now be added using data extensions. For more information see `Customizing library models for Java and Kotlin <https://codeql.github.com/docs/codeql-language-guides/customizing-library-models-for-java-and-kotlin/>`__.


This is a Markdown change note, but the “Title <url>__” construct is reStructuredText and is currently wrapped in backticks, so it will render as inline code (not as a link). Please switch to a Markdown link format so the docs URL renders correctly.

Suggested change

* Data flow barriers and barrier guards can now be added using data extensions. For more information see `Customizing library models for Java and Kotlin <https://codeql.github.com/docs/codeql-language-guides/customizing-library-models-for-java-and-kotlin/>`__.

* Data flow barriers and barrier guards can now be added using data extensions. For more information see [Customizing library models for Java and Kotlin](https://codeql.github.com/docs/codeql-language-guides/customizing-library-models-for-java-and-kotlin/).

Copilot · 2026-03-24T10:36:00Z

+---
+category: feature
+---
+* Data flow barriers and barrier guards can now be added using data extensions. For more information see `Customizing library models for Go <https://codeql.github.com/docs/codeql-language-guides/customizing-library-models-for-go/>`__.


This is a Markdown change note, but the “Title <url>__” construct is reStructuredText and is currently wrapped in backticks, so it will render as inline code (not as a link). Please switch to a Markdown link format so the docs URL renders correctly.

Suggested change

* Data flow barriers and barrier guards can now be added using data extensions. For more information see `Customizing library models for Go <https://codeql.github.com/docs/codeql-language-guides/customizing-library-models-for-go/>`__.

* Data flow barriers and barrier guards can now be added using data extensions. For more information see [Customizing library models for Go](https://codeql.github.com/docs/codeql-language-guides/customizing-library-models-for-go/).

aschackmull · 2026-03-31T10:46:36Z

+- The fifth value ``()`` is the method input type signature.
+
+The sixth value should be left empty and is out of scope for this documentation.
+The remaining values are used to define the ``access path``, the ``accepting value``, the ``kind``, and the ``provenance`` (origin) of the barrier guard.


I find it weird that "access path" and "accepting value" are quoted as code, but they contain spaces, so they're not identifiers. Occurs elsewhere as well.

Maybe it's best just to treat these four terms as natural language terms and just not quote them.

It seems to be a convention that column names are quoted this way. It's used in lots of the docs about MaD. I don't think we should change the convention. We could use hyphens instead of spaces in column names.

I've pushed a commit to use hyphens for access-path and accepting-value.

aschackmull

A few comments, otherwise generally LGTM. But I guess we'll want a docs review for this.

yoff

Python 👍 One comment, but not blocking.

yoff · 2026-04-07T11:39:55Z

+  if url_has_allowed_host_and_scheme(url, allowed_hosts=...): # The check guards the use of 'url', so it is safe.
+      redirect(url) # This is safe.
+
+We need to add a tuple ``(type, path, branch, kind)`` to the ``barrierGuardModel`` extensible predicate by updating a data extension file (the extension ID is implicit and auto-assigned).


I think the extension ID has not been mentioned anywhere at this point, is it simply confusing to talk about it here?

Thanks for spotting that. It's definitely confusing. I've removed everything in parentheses in the commit Remove mention of extension ID.

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

owen-mc · 2026-04-14T14:42:36Z

I rebased on main and added two commits to address changes to variable names in #21584, which was merged recently.

coadaflorin · 2026-04-15T10:03:05Z

I'm opening a release so we can post a changelog for this change as it was a big ask from our customers. Can we time this to go public next Tuesday? (We get Tuesdays as the designated day for security releases)

owen-mc · 2026-04-15T13:51:04Z

In some sense this is already public (all the development has been done in the open). I assume you mean merging this doc PR on Tuesday. (Or is there some action needed to update the public docs? I am not sure.) That is fine with me, assuming it gets a doc review by then. (My first request was missed somehow, but it's on their radar now.)

saritai

@owen-mc Looks good overall! Sorry again about the mixup that delayed us reviewing this. We've created an issue to look into why it didn't get added to our review board.

I just noticed a few small formatting things - the main thing was there was a duplicate sentence in most of the examples - it least it felt confusing to me so thought it could be removed. However, if it is there for a reason, feel free to ignore!

saritai · 2026-04-15T14:15:43Z

+       data:
+         - ["", "", False, "is_safe", "", "", "Argument[*0]", "true", "sql-injection", "manual"]
+
+Since we are adding a barrier guard, we need to add a tuple to the ``barrierGuardModel`` extensible predicate.


Suggested change

Since we are adding a barrier guard, we need to add a tuple to the ``barrierGuardModel`` extensible predicate.

This seems a duplicate sentence to me since we already said we are adding a tuple above the code block, but ignore if it is needed!

saritai · 2026-04-15T14:18:31Z

+       data:
+         - ["", "", False, "mysql_real_escape_string", "", "", "Argument[*1]", "sql-injection", "manual"]
+
+Since we are adding a barrier, we need to add a tuple to the ``barrierModel`` extensible predicate.


Suggested change

Since we are adding a barrier, we need to add a tuple to the ``barrierModel`` extensible predicate.

This seems a duplicate sentence to me since we already said we are adding a tuple above the code block, but ignore if it is needed!

saritai · 2026-04-15T14:35:52Z

+      data:
+        - ["my-package", "Member[isValid].Argument[0]", "true", "sql-injection"]
+
+- Since we are adding a barrier guard, we need to add a tuple to the **barrierGuardModel** extensible predicate.


Suggested change

- Since we are adding a barrier guard, we need to add a tuple to the **barrierGuardModel** extensible predicate.

Since we are adding a barrier guard, we need to add a tuple to the **barrierGuardModel** extensible predicate.

Think this can be just a sentence, the unordered list below is each column

saritai · 2026-04-15T14:36:13Z

+      data:
+        - ["global", "Member[encodeURIComponent].ReturnValue", "html-injection"]
+
+- Since we are adding a barrier, we need to add a tuple to the **barrierModel** extensible predicate.


Suggested change

- Since we are adding a barrier, we need to add a tuple to the **barrierModel** extensible predicate.

Since we are adding a barrier, we need to add a tuple to the **barrierModel** extensible predicate.

This can just be a sentence, and everything below is the unordered list of columns

saritai · 2026-04-15T14:39:59Z

+      data:
+        - ["Validator!", "Method[is_safe].Argument[0]", "true", "sql-injection"]
+
+- Since we are adding a barrier guard, we need to add a tuple to the **barrierGuardModel** extensible predicate.


Suggested change

- Since we are adding a barrier guard, we need to add a tuple to the **barrierGuardModel** extensible predicate.

Since we are adding a barrier guard, we need to add a tuple to the **barrierGuardModel** extensible predicate.

saritai · 2026-04-15T14:41:20Z

+         - ["java.io", "File", True, "getName", "()", "", "ReturnValue", "path-injection", "manual"]
+
+
+Since we are adding a new barrier, we need to add a tuple to the ``barrierModel`` extensible predicate.


Suggested change

Since we are adding a new barrier, we need to add a tuple to the ``barrierModel`` extensible predicate.

Duplicate sentence to what is above the code block?

saritai · 2026-04-15T14:41:45Z

+         - ["java.net", "URI", True, "isAbsolute", "()", "", "Argument[this]", "false", "request-forgery", "manual"]
+
+
+Since we are adding a barrier guard, we need to add a tuple to the ``barrierGuardModel`` extensible predicate.


Suggested change

Since we are adding a barrier guard, we need to add a tuple to the ``barrierGuardModel`` extensible predicate.

Duplicate sentence to what is above the code block?

saritai · 2026-04-15T14:42:03Z

+       data:
+         - ["System.Web", "HttpRequest", False, "get_RawUrl", "()", "", "ReturnValue", "url-redirection", "manual"]
+
+Since we are adding a barrier, we need to add a tuple to the ``barrierModel`` extensible predicate.


Suggested change

Since we are adding a barrier, we need to add a tuple to the ``barrierModel`` extensible predicate.

Duplicate sentence to what is above the code block?

saritai · 2026-04-15T14:42:17Z

+       data:
+         - ["System", "Uri", False, "get_IsAbsoluteUri", "()", "", "Argument[this]", "false", "url-redirection", "manual"]
+
+Since we are adding a barrier guard, we need to add a tuple to the ``barrierGuardModel`` extensible predicate.


Suggested change

Since we are adding a barrier guard, we need to add a tuple to the ``barrierGuardModel`` extensible predicate.

Duplicate sentence to what is above the code block?

Co-authored-by: Sarita Iyer <66540150+saritai@users.noreply.github.com>

To avoid copy-paste mistakes and make them more consistent we just use the word "model".

Co-authored-by: Copilot <copilot@github.com>

owen-mc · 2026-04-16T11:37:09Z

Thanks for your review. I agree about the duplication. It is copying a pattern that is already used in the files, so I've fixed it in those other places too. I've also tried to make the guides for the different languages use more consistent wording for introducing examples. And I've gone as far as switching the three that were using bold to use monospace instead.

saritai

@owen-mc This looks great, nice consistency now! 🚀

owen-mc · 2026-04-16T14:39:55Z

@saritai Thanks for re-reviewing. One final question: once this is merged, does the public documentation automatically get updated? If so, how long does it take? (I admit that that was 2 questions...) We want to announce this feature on Tuesday so it would be good to make sure the documentation is updated on that day.

github-actions bot added documentation C# JS C++ Java Python Go Ruby Rust Pull requests that update Rust code labels Mar 20, 2026

owen-mc marked this pull request as ready for review March 24, 2026 10:31

owen-mc requested a review from a team as a code owner March 24, 2026 10:31

Copilot AI review requested due to automatic review settings March 24, 2026 10:31

owen-mc requested review from a team as code owners March 24, 2026 10:31

Copilot started reviewing on behalf of owen-mc March 24, 2026 10:32 View session

owen-mc changed the title ~~Document MaD barriers and barrier guards and add change notes~~ Document models-as-data barriers and barrier guards and add change notes Mar 24, 2026

Copilot AI reviewed Mar 24, 2026

View reviewed changes

owen-mc force-pushed the docs/mad/barriers branch from 3ab2153 to 052b41a Compare March 24, 2026 11:08

owen-mc added the ready-for-doc-review This PR requires and is ready for review from the GitHub docs team. label Mar 26, 2026

aschackmull reviewed Mar 31, 2026

View reviewed changes

Comment thread docs/codeql/codeql-language-guides/customizing-library-models-for-cpp.rst Outdated

aschackmull reviewed Mar 31, 2026

View reviewed changes

Comment thread docs/codeql/codeql-language-guides/customizing-library-models-for-cpp.rst Outdated

aschackmull reviewed Mar 31, 2026

View reviewed changes

owen-mc force-pushed the docs/mad/barriers branch from 9977b1c to 260a1a0 Compare March 31, 2026 14:04

yoff previously approved these changes Apr 7, 2026

View reviewed changes

owen-mc and others added 14 commits April 14, 2026 15:27

(Trivial) Remove trailing spaces in some docs

f02ccd3

(Formatting) Remove erroneous bullet point in ruby docs

ef9136c

List extensible predicates for barriers and barrier guards

05e3073

Update docs for barriers and barrier guards

415330d

Add change notes

c86ba38

Remove incorrect parameter of extensible predicate

a2a0c08

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Correct extensible predicate signatures in docs

6d4e8bf

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Fix link formatting in change notes

8f17b73

"modelling" -> "modeling" in docs

76d165e

Include parameters when quoting extensible predicate name

2ecf086

Use hyphens in column names: "access-path", "accepting-value"

8081d46

Remove mention of extension ID

6321482

Fix docs: "acceptingvalue" -> "acceptingValue"

87f2e21

Fix docs: "branch" -> "acceptingValue"

f79ffe7

owen-mc dismissed yoff’s stale review via f79ffe7 April 14, 2026 14:41

owen-mc force-pushed the docs/mad/barriers branch from 260a1a0 to f79ffe7 Compare April 14, 2026 14:41

saritai previously approved these changes Apr 15, 2026

View reviewed changes

Quote library name in backticks

2c16cb4

Co-authored-by: Sarita Iyer <66540150+saritai@users.noreply.github.com>

owen-mc dismissed saritai’s stale review via 2c16cb4 April 16, 2026 10:30

owen-mc and others added 4 commits April 16, 2026 11:41

Fix mistakes in explanation of override column

5a7b1b9

To avoid copy-paste mistakes and make them more consistent we just use the word "model".

Remove duplication and standardize wording

82d9d46

Co-authored-by: Copilot <copilot@github.com>

Use monospace instead of bold for predicate signatures

69c150d

Use monospace instead of bold for quoted code

73cc54c

saritai approved these changes Apr 16, 2026

View reviewed changes

	* Data flow barriers and barrier guards can now be added using data extensions. For more information see `Customizing library models for C# <https://codeql.github.com/docs/codeql-language-guides/customizing-library-models-for-csharp/>`__.
	* Data flow barriers and barrier guards can now be added using data extensions. For more information see [Customizing library models for C#](https://codeql.github.com/docs/codeql-language-guides/customizing-library-models-for-csharp/).

		- ``barrierModel(namespace, type, subtypes, name, signature, ext, output, kind, provenance)``. This is used to model barriers, which are elements that stop the flow of taint.
		- ``barrierGuardModel(namespace, type, boolean subtypes, name, signature, ext, input, acceptingvalue, kind, provenance)``. This is used to model barrier guards, which are elements that can stop the flow of taint depending on a conditional check.

	- ``barrierGuardModel(namespace, type, boolean subtypes, name, signature, ext, input, acceptingvalue, kind, provenance)``. This is used to model barrier guards, which are elements that can stop the flow of taint depending on a conditional check.
	- ``barrierGuardModel(namespace, type, subtypes, name, signature, ext, input, acceptingvalue, kind, provenance)``. This is used to model barrier guards, which are elements that can stop the flow of taint depending on a conditional check.

	- Since we are adding a barrier guard, we need to add a tuple to the barrierGuardModel extensible predicate.
	Since we are adding a barrier guard, we need to add a tuple to the barrierGuardModel extensible predicate.

	- Since we are adding a barrier, we need to add a tuple to the barrierModel extensible predicate.
	Since we are adding a barrier, we need to add a tuple to the barrierModel extensible predicate.

		- ["java.io", "File", True, "getName", "()", "", "ReturnValue", "path-injection", "manual"]


		Since we are adding a new barrier, we need to add a tuple to the ``barrierModel`` extensible predicate.

		- ["java.net", "URI", True, "isAbsolute", "()", "", "Argument[this]", "false", "request-forgery", "manual"]


		Since we are adding a barrier guard, we need to add a tuple to the ``barrierGuardModel`` extensible predicate.

Conversation

owen-mc commented Mar 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Mar 24, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Copilot AI Mar 24, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 24, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 24, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 24, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 24, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 24, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

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!

aschackmull left a comment

Choose a reason for hiding this comment

Uh oh!

yoff left a comment

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!

owen-mc commented Apr 14, 2026

Uh oh!

coadaflorin commented Apr 15, 2026

Uh oh!

owen-mc commented Apr 15, 2026

Uh oh!

saritai left a comment • 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!

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!

owen-mc commented Mar 20, 2026 •

edited

Loading

saritai left a comment •

edited

Loading

owen-mc commented Apr 16, 2026 •

edited

Loading