Add API V2 from DMPonline by gjacob24 · Pull Request #3587 · DMPRoadmap/roadmap

gjacob24 · 2025-11-26T14:57:52Z

PR for issue #3586

This issue branch uses the doorkeeper gem to implement the Authorization Code Grant Flow (ACGF) part of the v2 API.
(The Client Credentials Flow (CCF) part of the v2 API (which is what the org-admins will use) will be implemented separately in a future piece of work.)

Overview:

This PR introduces the initial v2 API implementation, with OAuth 2.0 authentication powered by the Doorkeeper gem. This is a foundation for further v2 API enhancements and ensures secure, standards-based authentication for future integrations.

Key Features:

Integrates Doorkeeper gem for OAuth 2.0 and v2 access token management.
Implements initial v2 API endpoints:
- GET /api/v2/plans
- GET /api/v2/plans/:id
- GET /api/v2/templates
- GET /api/v2/me
- GET /api/v2/heartbeat
  - NOTE: The responses for GET /plans and GET /plans/:id calls serialize plan data according to the RDA DMP Common Standard JSON schema.
Adds optional “complete” flag for GET /plans and GET /plans/:id (Add complete plan flag to V2 API #3595).
Adds test coverage Add v2 API Test Coverage and Address Uncovered Bugs #3589

Notes

hash_application_secrets is enabled. However, when an OAuth application is generated through the Doorkeeper form, the user will not have access to the pre-hashed secret. This limitation will be addressed in a future PR.

For reference, the implementation for exposing the generated secret is available in @portagenetwork/roadmap/pull/1320..

github-actions · 2025-11-26T14:58:54Z

	1 Warning
⚠️	This PR is too big! Consider breaking it down into smaller PRs.

Generated by 🚫 Danger

aaronskiba · 2025-11-26T17:14:31Z

Thank you for this PR.

During today's DMPRoadmap Monthly all-team meeting I mentioned how there are also related DMPTool v2 API test files. Would you like me to add them to this PR?

momo3404 · 2025-11-27T18:14:59Z

I'm seeing a lot of rubocop errors in here. This might be a difference in the configuration of Rubocop between the Roadmap repo and DMP Online. Let me know how you'd want to approach this. If possible, I could start a PR attempting to fix these.

martaribeiro · 2025-11-28T16:34:27Z

Here is the document with the API calls.
API_v2.pdf

Please let us know if needs changing

gjacob24 · 2025-11-28T16:41:19Z

I'm seeing a lot of rubocop errors in here. This might be a difference in the configuration of Rubocop between the Roadmap repo and DMP Online. Let me know how you'd want to approach this. If possible, I could start a PR attempting to fix these.

@momo3404 apologies we missed this. I can do this and push it back next week, if that's ok.

martaribeiro · 2025-11-28T16:47:25Z

These two docs are more for developers support. It might be useful
[Authorization_Code_Grant_Flow.pdf](https://github.com/user-attachments/files/23827
doorkeeper_gem_for_OAuth_2.0_flows.pdf
178/Authorization_Code_Grant_Flow.pdf)

aaronskiba · 2025-11-28T17:02:27Z

These two docs are more for developers support. It might be useful [Authorization_Code_Grant_Flow.pdf](https://github.com/user-attachments/files/23827 doorkeeper_gem_for_OAuth_2.0_flows.pdf 178/Authorization_Code_Grant_Flow.pdf)

Awesome, thank you. Sorry, the links got a little bungled up in the comment. :P
https://github.com/user-attachments/files/23827180/doorkeeper_gem_for_OAuth_2.0_flows.pdf works.
Could you just provide the Authorization_Code_Grant_Flow.pdf link again?

gjacob24 · 2025-12-01T12:27:53Z

These two docs are more for developers support. It might be useful [Authorization_Code_Grant_Flow.pdf](https://github.com/user-attachments/files/23827 doorkeeper_gem_for_OAuth_2.0_flows.pdf 178/Authorization_Code_Grant_Flow.pdf)

Awesome, thank you. Sorry, the links got a little bungled up in the comment. :P https://github.com/user-attachments/files/23827180/doorkeeper_gem_for_OAuth_2.0_flows.pdf works. Could you just provide the Authorization_Code_Grant_Flow.pdf link again?

@aaronskiba Here you go:
Authorization_Code_Grant_Flow.pdf

Let us know if this doesn't work.

aaronskiba · 2025-12-08T19:17:49Z

I'm encountering the following when I test the GET /api/v2/heartbeat endpoint (I can also see that the endpoint is returning a 500 for DMPOnline):

$ curl http://127.0.0.1:3000/api/v2/heartbeat
NoMethodError at /api/v2/heartbeat
==================================

undefined method `name' for nil:NilClass

> To access an interactive console with this error, point your browser to: /__better_errors


app/views/api/v2/_standard_response.json.jbuilder, line 18
----------------------------------------------------------

``` ruby
   13   json.ignore_nil!
   14   
   15   json.server @server
   16   json.source "#{request.method} #{request.path}"
   17   json.time Time.now.to_formatted_s(:iso8601)
>  18   json.client @client.name
   19   json.code response.status
   20   json.message Rack::Utils::HTTP_STATUS_CODES[response.status]
   21   
   22   if response.status == 200
   23

App backtrace

app/views/api/v2/_standard_response.json.jbuilder:18:in `_app_views_api_v___standard_response_json_jbuilder__1455696549825964062_81440'
app/views/api/v2/error.json.jbuilder:3:in `_app_views_api_v__error_json_jbuilder__3591388735008983784_81420'
app/controllers/api/v2/base_api_controller.rb:69:in `handle_internal_server_error'
app/controllers/api/v2/base_api_controller.rb:58:in `handle_exception'

Full backtrace
...

aaronskiba · 2025-12-08T20:50:30Z

+      # Remove `null: false` if you are planning to use grant flows
+      # that doesn't require redirect URI to be used during authorization
+      # like Client Credentials flow or Resource Owner Password.
+      t.text    :redirect_uri, null: false


Since we will be implementing the v2 API Client Credentials Flow in a future piece of work, maybe we should remove null: false on redirect_uri, as the code comment advises.

aaronskiba · 2025-12-10T22:34:39Z

+
+# json.items []
+json.message @payload[:message]
+json.details @payload[:details]


I can see @payload[:message] being assigned within app/controllers/api/v2/base_api_controller.rb. But is @payload[:details] being set anywhere? Maybe it can be removed.

aaronskiba · 2025-12-12T16:14:10Z

+          Plan.joins(:roles)
+              .where(roles: { user_id: @resource_owner.id, active: true })
+              .distinct


It might be even better to reuse the Plan.active(@resource_owner) scope for this query. Note that a bit of refactoring could be performed in that scope to make this more efficient (i.e. don't use includes(:template, :roles))

momo3404 · 2025-12-12T20:36:26Z

Please let me know if I've done something wrong here, but I keep getting 302s when executing the GET command from the Authorization Code Grant Flow.
curl -i -X GET "http://127.0.0.1:3000/oauth/authorize?response_type=code&client_id=[my_client_id]&redirect_uri=[redirect_uri]" HTTP/1.1 302 Found x-frame-options: SAMEORIGIN x-xss-protection: 0 x-content-type-options: nosniff x-permitted-cross-domain-policies: none referrer-policy: strict-origin-when-cross-origin location: http://127.0.0.1:3000/users/sign_in content-type: text/html; charset=utf-8 cache-control: no-cache

But the command still worked, because after calling Doorkeeper::AccessGrant.first I found my authorization which I used for the POST command, and that worked perfectly. So is this a known error, or something I'm missing? I was also signed in when making the request.

gjacob24 · 2025-12-22T16:08:08Z

I'm encountering the following when I test the GET /api/v2/heartbeat endpoint (I can also see that the endpoint is returning a 500 for DMPOnline):

$ curl http://127.0.0.1:3000/api/v2/heartbeat
NoMethodError at /api/v2/heartbeat
==================================

undefined method `name' for nil:NilClass

> To access an interactive console with this error, point your browser to: /__better_errors


app/views/api/v2/_standard_response.json.jbuilder, line 18
----------------------------------------------------------

``` ruby
   13   json.ignore_nil!
   14   
   15   json.server @server
   16   json.source "#{request.method} #{request.path}"
   17   json.time Time.now.to_formatted_s(:iso8601)
>  18   json.client @client.name
   19   json.code response.status
   20   json.message Rack::Utils::HTTP_STATUS_CODES[response.status]
   21   
   22   if response.status == 200
   23

App backtrace

* app/views/api/v2/_standard_response.json.jbuilder:18:in `_app_views_api_v___standard_response_json_jbuilder__1455696549825964062_81440'

* app/views/api/v2/error.json.jbuilder:3:in `_app_views_api_v__error_json_jbuilder__3591388735008983784_81420'

* app/controllers/api/v2/base_api_controller.rb:69:in `handle_internal_server_error'

* app/controllers/api/v2/base_api_controller.rb:58:in `handle_exception'

Full backtrace ...

@aaronskiba this is fixed and should be working now

aaronskiba · 2025-12-22T19:06:14Z

Full backtrace ...

@aaronskiba this is fixed and should be working now

Cool. I can get the 200 via the heartbeat whether I'm signed in or signed in now.

Unfortunately, I think the fix may have introduced other bugs. I am testing the following curl request:

$ curl -H "Authorization: Bearer ${BEARER_TOKEN}"      -H "Accept: application/json"      "http://127.0.0.1:3000/api/v2/plans"

This works and returns the expected JSON response on #3589, which is not up-to-date with these lastest heartbeat changes. However, when I test on this PR, I get the following response:

{
  "source": "GET /api/v2/plans",
  "time": "2025-12-22T12:03:00-07:00",
  "code": 500,
  "message": [
    "There was a problem in the server."
  ]

I also get the following in the rails console:

Processing by Api::V2::PlansController#index as JSON
  Doorkeeper::AccessToken Load (1.3ms)  SELECT "oauth_access_tokens".* FROM "oauth_access_tokens" WHERE "oauth_access_tokens"."token" = $1 LIMIT $2  [["token", "lp5znDvJAOZndbJRWAZ1eeZ_5NR8ZZs_2raswR-YsgQ"], ["LIMIT", 1]]
Exception message: undefined method `include?' for nil:NilClass

        raise Pundit::NotAuthorizedError unless @scopes.include?('read')
                                                       ^^^^^^^^^
  Rendering api/v2/error.json.jbuilder
  Rendered api/v2/_standard_response.json.jbuilder (Duration: 0.7ms | Allocations: 400)
  Rendered api/v2/error.json.jbuilder (Duration: 1.8ms | Allocations: 728)
Completed 500 Internal Server Error in 10ms (Views: 3.8ms | ActiveRecord: 0.9ms | Allocations: 7697)

This must be related to @scopes = doorkeeper_token.scopes.to_a if doorkeeper_token being removed in commit 3645cae

I am also looking at the @application = ApplicationService.application_name change in app/controllers/api/v2/base_api_controller.rb. I like this renaming because it is consistent with app/controllers/api/v1/base_api_controller.rb. However, json.server @server still exists in app/views/api/v2/_standard_response.json.jbuilder. Changing it to json.application @application should fix things and again align with the api/v1 approach.

The assignments to @client and @resource_owner were removed in commit 3645cae. This will need to be addressed as well.

gjacob24 · 2025-12-23T14:21:27Z

Full backtrace ...

@aaronskiba this is fixed and should be working now

Cool. I can get the 200 via the heartbeat whether I'm signed in or signed in now.

Unfortunately, I think the fix may have introduced other bugs. I am testing the following curl request:
$ curl -H "Authorization: Bearer ${BEARER_TOKEN}"      -H "Accept: application/json"      "http://127.0.0.1:3000/api/v2/plans"
This works and returns the expected JSON response on #3589, which is not up-to-date with these lastest heartbeat changes. However, when I test on this PR, I get the following response:
{
  "source": "GET /api/v2/plans",
  "time": "2025-12-22T12:03:00-07:00",
  "code": 500,
  "message": [
    "There was a problem in the server."
  ]
I also get the following in the rails console:
Processing by Api::V2::PlansController#index as JSON
  Doorkeeper::AccessToken Load (1.3ms)  SELECT "oauth_access_tokens".* FROM "oauth_access_tokens" WHERE "oauth_access_tokens"."token" = $1 LIMIT $2  [["token", "lp5znDvJAOZndbJRWAZ1eeZ_5NR8ZZs_2raswR-YsgQ"], ["LIMIT", 1]]
Exception message: undefined method `include?' for nil:NilClass

        raise Pundit::NotAuthorizedError unless @scopes.include?('read')
                                                       ^^^^^^^^^
  Rendering api/v2/error.json.jbuilder
  Rendered api/v2/_standard_response.json.jbuilder (Duration: 0.7ms | Allocations: 400)
  Rendered api/v2/error.json.jbuilder (Duration: 1.8ms | Allocations: 728)
Completed 500 Internal Server Error in 10ms (Views: 3.8ms | ActiveRecord: 0.9ms | Allocations: 7697)
This must be related to @scopes = doorkeeper_token.scopes.to_a if doorkeeper_token being removed in commit 3645cae

I am also looking at the @application = ApplicationService.application_name change in app/controllers/api/v2/base_api_controller.rb. I like this renaming because it is consistent with app/controllers/api/v1/base_api_controller.rb. However, json.server @server still exists in app/views/api/v2/_standard_response.json.jbuilder. Changing it to json.application @application should fix things and again align with the api/v1 approach.

The assignments to @client and @resource_owner were removed in commit 3645cae. This will need to be addressed as well.

Hey @aaronskiba, so sorry about this. I have changed @server to @application, to keep it consistent with V1. I've also put back @scopes and @resource_owner. That was removed unintentionally, so thanks for spotting that. You might still get other errors because we haven't fixed and tested them all, but I think this might be the last change I push before the long break to avoid causing more errors :D

Also, please feel free to commit any changes you feel are necessary (some of which you have already added as comments in this PR).

Co-Authored-By: gjacob24 <97518971+gjacob24@users.noreply.github.com>

Fix crashes when `@client` is nil (e.g., on heartbeat endpoint where doorkeeper_token is not present). - `@client = doorkeeper_token&.application` simplifies `@client` assignment. - Guard log_access and add `@caller` for safe JSON output Align JSON response keys with V1 - server -> application - client -> caller Co-Authored-By: gjacob24 <97518971+gjacob24@users.noreply.github.com> Co-Authored-By: John Pinto <8876215+johnpinto1@users.noreply.github.com>

This test suite was adapted from the v2 API tests in CDLUC3/dmptool. The original request and view specs were copied and then refactored to align with our v2 API. Supporting factories and spec helper files were updated as needed to accommodate the new coverage.

- Add complete flag data to extension in json

- Pre-fetch the answers, questions, and sections as part of the initial plans query (but only when we are in fact fetching all of the questions and answers). - This speeds up the mean request time by 25%

Add complete plan flag to V2 API

More information regarding these Doorkeeper rake tasks can be found at https://doorkeeper.gitbook.io/guides/internals/rake

Generate and apply migration to remove NOT NULL constraint from `oauth_applications.redirect_uri`. This works in conjunction with `allow_blank_redirect_uri true` in `config/initializers/doorkeeper.rb`, allowing us to save `OAuthApplications` with blank `redirect_uri` values for URI-less flows like client_credentials or password grant flows. NOTE: Applications using `authorization_code` (or other flows that require a redirect URI) must still have a non-blank `redirect_uri`. Otherwise, `/oauth/authorize` requests with `response_type=code` will fail. More info is available here: https://github.com/doorkeeper-gem/doorkeeper/wiki/Allow-blank-redirect-URI-for-Applications

- Enable `hash_application_secrets` and `hash_token_secrets` in Doorkeeper initializer for improved security. - This stores application secrets and access tokens as hashes in the database, reducing risk if the database is compromised. - Note: `hash_token_secrets` is incompatible with `reuse_access_token`, so token reuse is now disabled/removed (see warning in Doorkeeper docs). - For more details, see: https://doorkeeper.gitbook.io/guides/security/token-and-application-secrets

Move the "read" scope authorization check to a shared `before_action` in `BaseApiController` - Removes redundant checks from individual actions in `PlansController` and `TemplatesController` - Allows for the safe removal of `@scopes` from `base_response_content`

Prior to this change, `LocaleService.default_locale` was always assigned to `json.language`. - Now we use `plan.owner&.language&.abbreviation` (or `LocaleService.default_locale` as a fallback)

- Updated `it 'includes the :language'` test to reflect changes made in b238c8128e0fefb9ea25cc7528e5be2c499d9318. - Updated `Api::V1` references within spec files with `Api::V2`

NOTE: The prior comment stated the following: # Attach the first data_curation role as the data_contact, otherwise # add the contributor to the contributors array However, the contributor was ALWAYS added to the contributors array

Moved complex query logic from policies to `for_api_v2` scopes in Template and Plan models.

Addresses the following Bullet warning: user: aaron GET /api/v2/templates USE eager loading detected Identifier => [:identifier_scheme] Add to your query: .includes([:identifier_scheme]) Call stack /home/aaron/Documents/GitHub/roadmap/app/presenters/api/v2/org_presenter.rb:9:in `block in affiliation_id' /home/aaron/Documents/GitHub/roadmap/app/presenters/api/v2/org_presenter.rb:9:in `affiliation_id' /home/aaron/Documents/GitHub/roadmap/app/views/api/v2/orgs/_show.json.jbuilder:11:in `block in _app_views_api_v__orgs__show_json_jbuilder__1237609272914133563_48080' /home/aaron/Documents/GitHub/roadmap/app/views/api/v2/orgs/_show.json.jbuilder:10:in `_app_views_api_v__orgs__show_json_jbuilder__1237609272914133563_48080' /home/aaron/Documents/GitHub/roadmap/app/views/api/v2/templates/index.json.jbuilder:16:in `block (3 levels) in _app_views_api_v__templates_index_json_jbuilder___4313931085157922975_47640' /home/aaron/Documents/GitHub/roadmap/app/views/api/v2/templates/index.json.jbuilder:15:in `block (2 levels) in _app_views_api_v__templates_index_json_jbuilder___4313931085157922975_47640' /home/aaron/Documents/GitHub/roadmap/app/views/api/v2/templates/index.json.jbuilder:8:in `block in _app_views_api_v__templates_index_json_jbuilder___4313931085157922975_47640' /home/aaron/Documents/GitHub/roadmap/app/views/api/v2/templates/index.json.jbuilder:5:in `_app_views_api_v__templates_index_json_jbuilder___4313931085157922975_47640' /home/aaron/Documents/GitHub/roadmap/app/controllers/api/v2/templates_controller.rb:13:in `index'

This change further addresses Bullet warnings that were earlier addressed in commit 6ed969b

This change updates `Api::V2::PlansController#show` to use the `.for_api_v2` scope, and applies eager loading of answers (`.includes(answers: { question: :section })`) based on the `complete` param--making the `show` action consistent with `index`. A new `plans_scope` helper DRYs up the controller by centralizing the shared scope and eager loading logic. Since `.for_api_v2` already filters by `.where(roles: { user_id: user_id, active: true })`, only a presence check is now required in the policy.

aaronskiba · 2026-07-15T19:13:59Z

I've approved this PR, but considering I've done a lot of work on it, at least one other approval would be nice. I've set @martaribeiro and @momo3404 as reviewers. Because @gjacob24 put up the PR, I don't think I can set her as a reviewer. However, if she wants to review the additional changes, or even merge it into development, that would be great. Thank you.

momo3404

Everything looks as expected to me!

gjacob24 and others added 2 commits November 19, 2025 15:06

Add API V2 code from DMPonline service

7a2b797

add doorkeeper to routes

63b65c2

aaronskiba reviewed Nov 28, 2025

View reviewed changes

Comment thread app/views/api/v2/datasets/_show.json.jbuilder Outdated

Add rubocop fixes

10380fa

aaronskiba reviewed Dec 8, 2025

View reviewed changes

Comment thread app/controllers/api/v2/templates_controller.rb

aaronskiba reviewed Dec 10, 2025

View reviewed changes

aaronskiba reviewed Dec 11, 2025

View reviewed changes

Comment thread app/controllers/api/v2/base_api_controller.rb Outdated

aaronskiba reviewed Dec 11, 2025

View reviewed changes

Comment thread app/models/oauth_application.rb Outdated

aaronskiba reviewed Dec 12, 2025

View reviewed changes

aaronskiba reviewed Dec 15, 2025

View reviewed changes

Comment thread app/views/api/v2/templates/index.json.jbuilder

gjacob24 requested a review from johnpinto1 December 18, 2025 11:17

This comment was marked as resolved.

Sign in to view

gjacob24 and others added 2 commits January 27, 2026 13:10

Remove DMPonline specific code from doorkeeper initializer

6508633

Co-Authored-By: gjacob24 <97518971+gjacob24@users.noreply.github.com>

aaronskiba force-pushed the api_v2_dmponline branch from 8ae4b5d to a04513b Compare January 27, 2026 20:17

Add v2 API test coverage

3e949be

This test suite was adapted from the v2 API tests in CDLUC3/dmptool. The original request and view specs were copied and then refactored to align with our v2 API. Supporting factories and spec helper files were updated as needed to accommodate the new coverage.

momo3404 and others added 10 commits February 10, 2026 09:49

Add complete plan flag to plans/_show.json.jbuilder

f8c7d42

- Add complete flag data to extension in json

Add question id to returned json

a370249

Optimize complete plan query

6e7ebdc

- Pre-fetch the answers, questions, and sections as part of the initial plans query (but only when we are in fact fetching all of the questions and answers). - This speeds up the mean request time by 25%

Update CHANGELOG.md

465bfca

Merge pull request #3595 from DMPRoadmap/momo/add-complete-flag

cce14fb

Add complete plan flag to V2 API

Add Doorkeeper rake tasks to Rakefile

416d7d3

More information regarding these Doorkeeper rake tasks can be found at https://doorkeeper.gitbook.io/guides/internals/rake

Adapt v2 spec requests to now-hashed tokens

22b9401

aaronskiba marked this pull request as draft March 12, 2026 16:35

aaronskiba added 7 commits March 12, 2026 15:54

Use plan.owner.language for plan.language

5018b89

Prior to this change, `LocaleService.default_locale` was always assigned to `json.language`. - Now we use `plan.owner&.language&.abbreviation` (or `LocaleService.default_locale` as a fallback)

Update plan.language test and V2 references

8337c33

- Updated `it 'includes the :language'` test to reflect changes made in b238c8128e0fefb9ea25cc7528e5be2c499d9318. - Updated `Api::V1` references within spec files with `Api::V2`

refactor: simplify @data_contact assignment

3a7d6a8

NOTE: The prior comment stated the following: # Attach the first data_curation role as the data_contact, otherwise # add the contributor to the contributors array However, the contributor was ALWAYS added to the contributors array

refactor: use for_api_v2 scope for Template & Plan

6a6bf92

Moved complex query logic from policies to `for_api_v2` scopes in Template and Plan models.

Optimise GET api/v2/plans / Fix N+1 queries

c4c75df

This change further addresses Bullet warnings that were earlier addressed in commit 6ed969b

aaronskiba changed the base branch from main to development July 13, 2026 17:52

aaronskiba marked this pull request as ready for review July 14, 2026 22:41

aaronskiba approved these changes Jul 14, 2026

View reviewed changes

This comment was marked as resolved.

Sign in to view

Update CHANGELOG.md

b976366

aaronskiba approved these changes Jul 15, 2026

View reviewed changes

aaronskiba requested review from martaribeiro and momo3404 July 15, 2026 19:12

momo3404 approved these changes Jul 16, 2026

View reviewed changes

aaronskiba merged commit c7167ab into development Jul 16, 2026
9 checks passed

Uh oh!

Conversation

gjacob24 commented Nov 26, 2025 • edited by aaronskiba Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Overview:

Key Features:

Notes

Uh oh!

github-actions Bot commented Nov 26, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

aaronskiba commented Nov 26, 2025

Uh oh!

momo3404 commented Nov 27, 2025

Uh oh!

Uh oh!

martaribeiro commented Nov 28, 2025

Uh oh!

gjacob24 commented Nov 28, 2025

Uh oh!

martaribeiro commented Nov 28, 2025

Uh oh!

aaronskiba commented Nov 28, 2025

Uh oh!

gjacob24 commented Dec 1, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

aaronskiba commented Dec 8, 2025

App backtrace

Uh oh!

aaronskiba Dec 8, 2025 • 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!

Uh oh!

aaronskiba Dec 10, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

aaronskiba Dec 12, 2025

Choose a reason for hiding this comment

Uh oh!

momo3404 commented Dec 12, 2025

Uh oh!

Uh oh!

gjacob24 commented Dec 22, 2025

App backtrace

Uh oh!

aaronskiba commented Dec 22, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

gjacob24 commented Dec 23, 2025

Uh oh!

This comment was marked as resolved.

This comment was marked as resolved.

Uh oh!

aaronskiba commented Jul 15, 2026

Uh oh!

momo3404 left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

gjacob24 commented Nov 26, 2025 •

edited by aaronskiba

Loading

github-actions Bot commented Nov 26, 2025 •

edited

Loading

gjacob24 commented Dec 1, 2025 •

edited

Loading

aaronskiba Dec 8, 2025 •

edited

Loading

aaronskiba commented Dec 22, 2025 •

edited

Loading