I79 clarification announcement fixes #1038

kkarakas · 2025-01-23T06:16:46Z

Description of what the PR does

When there is an announcement WTI does not immediately warn the client.
When WTI asks a clarification, there should be pending status clarification.
Ditto for submitting a problem.

Issue which the PR addresses

Fixes #79

Environment in which the PR was developed (OS,IDE, Java version, etc.)

Windows 11

Precise steps for testing the PR (i.e., how to demonstrate that it works correctly)

Log in to a WTI user. From pc2 judge send an announcement that logged in WTI client would receive. Observe that an pop up appears stating that there was an announcement.
Log in to a WTI user. Ask a clarification. Observe that new pending status clarification appears now.
Log in to a WTI user. Submit a problem. Observe that new pending problem appears now.

kkarakas · 2025-01-23T06:17:42Z

There are a lot of garbage console.log() that I used for debugging, I will delete them. The functionality works though.

kkarakas · 2025-02-04T02:02:15Z

There are a lot of garbage console.log() that I used for debugging, I will delete them. The functionality works though.

removed.

clevengr · 2025-02-08T00:29:27Z

Programs.lnk

Why is this file submitted as part of the PR?

This is a dummy reply.

clevengr · 2025-02-08T00:29:51Z

projects/WTI-API/WebContent/WEB-INF/lib/pc2.jar

Why is this file submitted as part of the PR?

Good question.

clevengr · 2025-02-08T00:33:12Z

projects/WTI-API/src/main/services/ClarificationService.java

+        //This method is used by two (or more?) methods.
+        //Whenever an announcement that this user should receive is made this method is called
+        //Also whenever the team sends a clarification to be answered by the judges.
+        if ( !arg0.isAnswered()) {  //case when the team sends a clarification to be answered.


It would be nice if the default template parameter name ("arg0") was changed to something more meaningful, like "clar" or "clarification".

I am here just following the general structure of the file. If that is the case, every method needs to change as well.

If my answer is satisfactory, I will close this.

Keep in mind this was originally written by students and didn't go through the vigorous review process we do for PC2. I don't thing we have to change all the existing code, but there is no sense in propagating bad practices by putting good code after bad. I think we should change NEW code to be as readable as possible. That is, I would change arg0 to something meaningful, eg. clar or newClar

clevengr · 2025-02-08T00:40:04Z

...ations/components/new-announcement-clarification-alert/new-announcement-alert.component.html

@@ -0,0 +1,9 @@
+<h1 mat-dialog-title>Clarification Announcement Received</h1>


I would suggest the title here be just "Announcement Received", in order to avoid confusion between what's a "clarification" vs. what's an "announcement". (PC2 is, currently, treating "announcements" as "clarifications", but it seems to make more sense from the user's perspective to keep the two notions separate.)

For similar reasons I think it would make sense to rename all of the components which are named like new-announcement-clarification-alert to be just new-announcement-alert. It would simplify the naming and at the same time help maintain the distinction between "announcements" and "clarifications".

The reason I say clarification announcement is to emphasize the fact that announcements are essentially a special form of clarification. The term "announcement clarification" was decided when I was building this feature in pc2. Of course that can be discussed and changed.

clevengr · 2025-02-08T00:41:11Z

...ations/components/new-announcement-clarification-alert/new-announcement-alert.component.scss

If there's no CSS associated with this new component, what is the browser going to use for rendering it?

I think this gets used?

clevengr · 2025-02-08T00:48:54Z

...ications/components/new-announcement-clarification-alert/new-announcement-alert.component.ts

+  templateUrl: './new-announcement-alert.component.html',
+  styleUrls: ['./new-announcement-alert.component.scss']
+})
+export class NewClarificationAnnoucementAlertComponent implements OnInit {


Name of class is misspelled (Annoucement -> Announcement). This should be fixed, and the change propogated throughout the code.

projects/WTI-UI/src/app/modules/core/abstract-services/i-websocket.service.ts

clevengr · 2025-02-08T01:00:32Z

projects/WTI-UI/src/app/modules/core/services/ui-helper.service.ts

@@ -13,12 +14,22 @@ export class UiHelperService {
              private _matSnackBar: MatSnackBar) { }

  incomingClarification(id: string): void {
+	console.log('clarification incoming : Alert will be initiated if alert is enabled.')


I thought you were going to remove console logging?

Same answer as above.

clevengr · 2025-02-08T01:01:29Z

projects/WTI-UI/src/app/modules/core/services/ui-helper.service.ts

    if (this.enableClarificationNotifications) {
      this._dialogService.open(NewClarificationAlertComponent, {
        data: { id }
      });
    }
  }
+
+  incomingClarificationAnnouncement(id: string): void {


I would suggest renaming this to incomingAnnouncement.

We need to decide if we are going to use the term clarification announcement or announcement.

clevengr · 2025-02-08T01:01:44Z

projects/WTI-UI/src/app/modules/core/services/ui-helper.service.ts

    if (this.enableClarificationNotifications) {
      this._dialogService.open(NewClarificationAlertComponent, {
        data: { id }
      });
    }
  }
+
+  incomingClarificationAnnouncement(id: string): void {
+	console.log('Announcement incoming : Alert will be initiated if alert is enabled.')


Remove logging?

clevengr · 2025-02-08T01:03:29Z

projects/WTI-UI/src/app/modules/runs/components/runs-page/runs-page.component.ts

@@ -36,7 +36,9 @@ export class RunsPageComponent implements OnInit, OnDestroy {

    // when runs are updated, trigger a reload
    this._teamService.runsUpdated
-      .pipe(takeUntil(this._unsubscribe))
+      .pipe(
+	delay(300),


Can you at least document/explain in comments why the delay(300) is needed?

Because without delay the refresh happens too quickly and, it misses the new pending clarifications.

clevengr · 2025-02-08T01:04:25Z

...c/app/modules/clarifications/components/clarifications-page/clarifications-page.component.ts

@@ -34,7 +34,9 @@ export class ClarificationsPageComponent implements OnInit, OnDestroy {
    this.loadClars();

    this._contestService.clarificationsUpdated
-      .pipe(takeUntil(this._unsubscribe))
+      .pipe(
+	delay(300),


Can you at least document/explain in comments why the delay(300) is now needed?

clevengr · 2025-02-08T01:08:46Z

...c/app/modules/clarifications/components/clarifications-page/clarifications-page.component.ts

+
+    if (fitlerParams.receipient === 'all') { filtered = filtered.filter(x => x.recipient === 'All'); console.log('receipient is ALl');}
+    if (fitlerParams.receipient === 'team') { filtered = filtered.filter(x => x.recipient !== 'All'); console.log('receipient is a team')}
+    if (fitlerParams.problem) { filtered = filtered.filter(x => x.problem === fitlerParams.problem); console.log('receipient is a problem')}


Two comments about the changes in the above three lines:

I don't think the console logging is necessary any longer; if you agree then I suggest removing it.

These changes conflict with related changes proposed in PR I1030 WTI clar announcement filtering #1041. That's fine; collisions are to be expected when multiple people are working in similar areas of the code. I just note it here so we'll remember that the conflicts will need to be resolved in whichever PR is merged later.

(If you do remove the console logging, then I think these lines will no longer conflict?)

I agree, the console logging should be removed.

clevengr · 2025-02-08T01:10:17Z

projects/WTI-UI/src/app/modules/clarifications/clarifications.module.ts

@@ -5,12 +5,14 @@ import { SharedModule } from '../shared/shared.module';
 import { ReactiveFormsModule } from '@angular/forms';
 import { NewClarificationComponent } from './components/new-clarification/new-clarification.component';
 import { NewClarificationAlertComponent } from './components/new-clarification-alert/new-clarification-alert.component';
+import { NewClarificationAnnoucementAlertComponent } from './components/new-announcement-clarification-alert/new-announcement-alert.component';


Component name is misspelled (Annoucement should be Announcement.)

clevengr · 2025-02-08T01:12:16Z

projects/WTI-UI/src/app/modules/clarifications/clarifications.module.ts


 @NgModule({
  declarations: [
    ClarificationsPageComponent,
    NewClarificationComponent,
-    NewClarificationAlertComponent
+    NewClarificationAlertComponent,
+    NewClarificationAnnoucementAlertComponent


Component name is misspelled. Also, see comments on subsequent files; I think this component should be named simply NewAnnouncementAlertComponent in order to distinguish "Clarifications" from "Announcements". Again, see subsequent comments for further details.

clevengr · 2025-02-08T01:13:36Z

projects/WTI-API/websockets/WebsocketEnums/WebsocketMsgType.java

@@ -1,5 +1,5 @@
 package WebsocketEnums;

 public enum WebsocketMsgType {
-	UNDEFINED, JUDGED, CONTEST_CLOCK, TEST, CLARIFICATION, STANDINGS, CONNECTION_DROPPED
+	UNDEFINED, JUDGED, CONTEST_CLOCK, TEST, CLARIFICATION, CLARIFICATION_ANNOUNCEMENT, STANDINGS, CONNECTION_DROPPED


I suggest CLARIFICATION_ANNOUNCEMENT be renamed to just ANNOUNCEMENT. See additional comments in following files for some explanation of why I think that makes more sense.

clevengr

I have reviewed all the changed files and left comments. I would like to see some of the things I mentioned fixed, but they don't amount to "errors" in the code.

However, when I try to build and run the PR code, I get errors (specifically, building the WTI-UI project for inclusion into the WTI distribution produces main.js and polyfills.js files which are marked as having large numbers of errors). Does package.xml in the PC2 Project produce a build, with no errors in WTI WebContent, for you? (If so, then there is something different about our configurations).

clevengr

I've reviewed file Programs.lnk....

clevengr · 2025-02-21T02:05:15Z

Programs.lnk

This is a dummy reply.

kkarakas · 2025-02-27T05:35:19Z

Think I made it work without delays, will need to test more and resolve the comments above but I'm sleepy so later.

johnbrvc · 2025-03-04T00:34:55Z

...I/src/app/modules/clarifications/components/new-clarification/new-clarification.component.ts

+	      console.error('error submitting new clarification');
+	      console.error(error);
+	    },
+	    complete: () => {


Is this empty routine necessary?

Well this helps people looking at the code know that there is another callback option called complete.

johnbrvc · 2025-03-04T00:36:50Z

...ons/components/new-announcement-clarification-alert/new-announcement-alert.component.spec.ts

+  let fixture: ComponentFixture<NewAnnouncementAlertComponent>;
+
+  beforeEach(async(() => {
+    TestBed.configureTestingModule({


What is TestBed and why do we need it? I know little about the typescript environment, so I have no idea why this is here.

It provides a simulated Angular module environment for testing

Did you add it just for local testing or is it something required for production?

johnbrvc · 2025-03-20T17:44:17Z

...I/src/app/modules/clarifications/components/new-clarification/new-clarification.component.ts

+	    },
+	    error: (error: any) => {
+	      this._uiHelper.alertError('Error submitting clarification!');
+	      console.error('error submitting new clarification');


Are we leaving the console.error? I thought we were removing them, especially since you have an alertError there...

If there is a particular reason if this message is triggered, add why the error came in the message.

johnbrvc · 2025-03-20T17:44:54Z

...ications/components/new-announcement-clarification-alert/new-announcement-alert.component.ts

+        if (clars && clars.length > 0) {
+          const clar = clars.find(x => x.id === clarId);
+          if (!clar) {
+            console.error('Announcement clarification not found! invalid ID passed via websocket');


Are we leaving these console.error messages? Maybe control them by a flag?

If it is supposed to be seen by an user, maybe make the message less technical.

The flag src/constants.ts does not exist in this branch so for now i cannot use the flag. I think this is an important console.log so i'm hessitant on removing it completely.

johnbrvc

Without knowing too much about TS and the interaction between these angular modules, it seems like it's OK to me (other than the couple of minorconsole.errorcalls that I mentioned).
I did test it, and it does work for clars and runs as one would expect it to.

SamanwaySadhu · 2025-03-26T04:37:57Z

projects/WTI-API/src/main/services/ClarificationService.java

+
+	        this.client.sendMessage(builder.toString());
+	        return;
+        }


Add a tab space for each line of code after this line, in this method.

I am not sure what I need to do here. The tabbing seems fine to me.

Usually, the function body should have a tab indentation after the definition line. So, lines 23-26 should have a tab space. Similarly, lines 37-45. The current way does not make it wrong but makes the code more readable.

SamanwaySadhu · 2025-03-26T04:38:25Z

projects/WTI-API/src/main/services/RunsService.java

+                .add("teamId", this.teamId)
+                .build();
+
+        this.client.sendMessage(builder.toString());


Add a tab space for this line.

Which line?

SamanwaySadhu · 2025-03-26T04:38:46Z

projects/WTI-API/src/main/controllers/TeamsController.java

@@ -499,6 +499,7 @@ public Response submitClarification(
 					.entity(new ServerErrorResponseModel(Response.Status.UNAUTHORIZED, "Unauthorized user request"))
 					.type(MediaType.APPLICATION_JSON).build();
 		}
+


Is there a particular reason you added a blank single line in this file?

Looks cool.

SamanwaySadhu · 2025-03-26T04:40:51Z

...ations/components/new-announcement-clarification-alert/new-announcement-alert.component.scss

Why is an empty file added here?

Makes sense.

SamanwaySadhu · 2025-03-26T04:41:50Z

projects/WTI-API/WebContent/WEB-INF/lib/pc2.jar

I don't think changes to the binaries after compilation should be pushed.

Makes sense.

SamanwaySadhu · 2025-03-26T04:45:08Z

...ons/components/new-announcement-clarification-alert/new-announcement-alert.component.spec.ts

+  let fixture: ComponentFixture<NewAnnouncementAlertComponent>;
+
+  beforeEach(async(() => {
+    TestBed.configureTestingModule({


Did you add it just for local testing or is it something required for production?

SamanwaySadhu · 2025-03-26T04:46:45Z

...ications/components/new-announcement-clarification-alert/new-announcement-alert.component.ts

+        if (clars && clars.length > 0) {
+          const clar = clars.find(x => x.id === clarId);
+          if (!clar) {
+            console.error('Announcement clarification not found! invalid ID passed via websocket');


If it is supposed to be seen by an user, maybe make the message less technical.

SamanwaySadhu · 2025-03-26T04:48:41Z

...I/src/app/modules/clarifications/components/new-clarification/new-clarification.component.ts

+	    },
+	    error: (error: any) => {
+	      this._uiHelper.alertError('Error submitting clarification!');
+	      console.error('error submitting new clarification');


If there is a particular reason if this message is triggered, add why the error came in the message.

SamanwaySadhu · 2025-03-26T04:51:29Z

projects/WTI-UI/src/app/modules/runs/components/runs-page/runs-page.component.ts

Why did you remove the filter and simply changed the line for the method arguments?

Well I see your concern for dev and production env however I dont think it is a big deal to have some tests on production since it is not a big project.

Its clearly not being used. I don't see the point of importing functions/methods that are not being used.

SamanwaySadhu · 2025-03-26T04:59:52Z

projects/WTI-API/src/main/controllers/TeamsController.java

This file doesn't have a copyright comment in the beginning. If it makes sense, add it. Similarly, do it for the other files.

Well WTI was made by some student group so pc2 copyright wouldnt apply.

clevengr · 2025-04-23T01:52:55Z

I'm working on reviewing this PR. The first thing I did is clone your pc2v9 repo fork. Then I looked for a branch named to correspond with Issue #79 -- but didn't find one. Finally I found kkarakas:I_-_clarification_announcement_fixes, which appears to be the corresponding branch? (It's missing the issue number in the branch name...) It would be nice if the branch name was changed to match the issue...

kkarakas · 2025-04-24T05:29:39Z

I'm working on reviewing this PR. The first thing I did is clone your pc2v9 repo fork. Then I looked for a branch named to correspond with Issue #79 -- but didn't find one. Finally I found kkarakas:I_-_clarification_announcement_fixes, which appears to be the corresponding branch? (It's missing the issue number in the branch name...) It would be nice if the branch name was changed to match the issue...

When I created the PR I couldnt manage to find the issue so I left to number part blank. Somewhat scared of renaming it. Will github continue to track it?

clevengr · 2025-04-25T04:19:53Z

I just cloned a new copy of the @kkarakas github fork, switched to the I_-_clarification_announcement_fixes branch, and ran the pc2v9/package.xml script as an Ant build (which executes the ArchiveSkipTests target). I am unable to build the project (therefore I'm unable to test it). When I run pc2v9/package.xml I get the following on the console:

...
buildSubProjects:
cleandist:
   [delete] Deleting directory C:\Users\John\git\pc2v9-kutay-github-fork\projects\WTI-API\dist
clean:
   [delete] Deleting directory C:\Users\John\git\pc2v9-kutay-github-fork\projects\WTI-API\bin
   [delete] Deleting directory C:\Users\John\git\pc2v9-kutay-github-fork\projects\WTI-API\build
checkPc2Jar:

BUILD FAILED
C:\Users\John\git\pc2v9-kutay-github-fork\package.xml:161: The following error occurred while executing this line:
C:\Users\John\git\pc2v9-kutay-github-fork\package.xml:182: The following error occurred while executing this line:
C:\Users\John\git\pc2v9-kutay-github-fork\build.xml:261: The following error occurred while executing this line:
C:\Users\John\git\pc2v9-kutay-github-fork\build.xml:269: The following error occurred while executing this line:
C:\Users\John\git\pc2v9-kutay-github-fork\projects\WTI-API\buildWTI.xml:49: C:\Users\John\git\pc2v9-kutay-github-fork\projects\WTI-API\WebContent\WEB-INF\lib\pc2.jar not found.

Is anyone else able to build the project on this branch?

johnbrvc · 2025-04-25T12:21:12Z

I just cloned a new copy of the @kkarakas github fork, switched to the I_-_clarification_announcement_fixes branch, and ran the pc2v9/package.xml script as an Ant build (which executes the ArchiveSkipTests target). I am unable to build the project (therefore I'm unable to test it). When I run pc2v9/package.xml I get the following on the console:

...
buildSubProjects:
cleandist:
   [delete] Deleting directory C:\Users\John\git\pc2v9-kutay-github-fork\projects\WTI-API\dist
clean:
   [delete] Deleting directory C:\Users\John\git\pc2v9-kutay-github-fork\projects\WTI-API\bin
   [delete] Deleting directory C:\Users\John\git\pc2v9-kutay-github-fork\projects\WTI-API\build
checkPc2Jar:

BUILD FAILED
C:\Users\John\git\pc2v9-kutay-github-fork\package.xml:161: The following error occurred while executing this line:
C:\Users\John\git\pc2v9-kutay-github-fork\package.xml:182: The following error occurred while executing this line:
C:\Users\John\git\pc2v9-kutay-github-fork\build.xml:261: The following error occurred while executing this line:
C:\Users\John\git\pc2v9-kutay-github-fork\build.xml:269: The following error occurred while executing this line:
C:\Users\John\git\pc2v9-kutay-github-fork\projects\WTI-API\buildWTI.xml:49: C:\Users\John\git\pc2v9-kutay-github-fork\projects\WTI-API\WebContent\WEB-INF\lib\pc2.jar not found.

Is anyone else able to build the project on this branch?

I did get that issue, and I simply put a the copy of pc2.jar from the "pc2v9/dist" folder in there to try to get it to build.
I think this is because @kkarakas probably removed pc2.jar from the project, which he shouldn't have done. It HAS to be in the lib folder. He should fix this.

After that, I did that I get ANOTHER different error, and I'm not sure why this is:

     [exec] Warning: ▲ [WARNING] Comments in CSS use "/* ... */" instead of "//" [js-comment-in-css]
     [exec]     C:/MyNetProjects/ICPC/kkarakas/pc2v9/projects/WTI-UI/src/app/modules/clarifications/components/new-clarification-alert/new-clarification-alert.component.scss:1:18:
     [exec]       1 │ /******/ (() => { // webpackBootstrap
     [exec]         ╵                   ~~
     [exec] Warning: ▲ [WARNING] Unexpected "(" [css-syntax-error]
     [exec]     C:/MyNetProjects/ICPC/kkarakas/pc2v9/projects/WTI-UI/src/app/modules/clarifications/components/new-clarification-alert/new-clarification-alert.component.scss:1:9:
     [exec]       1 │ /******/ (() => { // webpackBootstrap
     [exec]         ╵          ^
     [exec] Error: Module not found: Error: Can't resolve 'C:/MyNetProjects/ICPC/kkarakas/pc2v9/projects/WTI-UI/src/app/modules/clarifications/components/new-clarification-alert/new-clarification-alert.component.scss?ngResource' in 'C:\MyNetProjects\ICPC\kkarakas\pc2v9\projects\WTI-UI'
     [exec] Error: The loader "C:/MyNetProjects/ICPC/kkarakas/pc2v9/projects/WTI-UI/src/app/modules/clarifications/components/new-clarification-alert/new-clarification-alert.component.scss" didn't return a string.

BUILD FAILED
C:\MyNetProjects\ICPC\kkarakas\pc2v9\build.xml:127: The following error occurred while executing this line:
C:\MyNetProjects\ICPC\kkarakas\pc2v9\build.xml:261: The following error occurred while executing this line:
C:\MyNetProjects\ICPC\kkarakas\pc2v9\build.xml:269: The following error occurred while executing this line:
C:\MyNetProjects\ICPC\kkarakas\pc2v9\projects\WTI-API\buildWTI.xml:150: exec returned: 1

BTW, I am building using "build.xml", and "jarSkipTests"
@kkarakas If you can, please fix these ASAP so we can move this merging process along. Thanks.

kkarakas added 2 commits December 1, 2024 23:09

fixes

91e179f

runs and clars refresh

aecfd76

kkarakas changed the title ~~I clarification announcement fixes~~ I79 clarification announcement fixes Jan 23, 2025

johnbrvc requested review from johnbrvc, troy2914, clevengr and SamanwaySadhu January 23, 2025 13:27

johnbrvc assigned kkarakas Jan 23, 2025

johnbrvc added this to the 9.11.0 milestone Jan 23, 2025

johnbrvc added Comments/Analysis Requested Soliciting comments and feedback from the Team about how to implement issue In PR code review labels Jan 24, 2025

kkarakas added 2 commits February 3, 2025 20:58

prints removed.

2fa5312

Update clarifications-page.component.ts

8c2584e

clevengr reviewed Feb 8, 2025

View reviewed changes

projects/WTI-UI/src/app/modules/core/abstract-services/i-websocket.service.ts Outdated Show resolved Hide resolved

clevengr reviewed Feb 8, 2025

View reviewed changes

clevengr requested changes Feb 8, 2025

View reviewed changes

clevengr reviewed Feb 21, 2025

View reviewed changes

Programs.lnk Outdated

Copy link

Contributor

clevengr Feb 21, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a dummy reply.

removed delays

69e70cd

kkarakas added 4 commits March 2, 2025 13:08

grammar etc

618da7e

Update ClarificationService.java

6af3291

clars

18025f2

Update new-run.component.ts

a9594f4

johnbrvc reviewed Mar 4, 2025

View reviewed changes

kkarakas added 2 commits March 13, 2025 02:41

refreshing added

93ce96e

added for run

ac4963b

johnbrvc reviewed Mar 20, 2025

View reviewed changes

johnbrvc approved these changes Mar 20, 2025

View reviewed changes

kkarakas added 2 commits March 20, 2025 19:12

Update clarifications-page.component.ts

4764765

Update new-clarification.component.ts

7de6311

SamanwaySadhu suggested changes Apr 6, 2025

View reviewed changes

kkarakas closed this Apr 24, 2025

kkarakas reopened this Apr 24, 2025

bruh

71a21fb

		@@ -0,0 +1,9 @@
		<h1 mat-dialog-title>Clarification Announcement Received</h1>

I79 clarification announcement fixes #1038

Are you sure you want to change the base?

I79 clarification announcement fixes #1038

Conversation

kkarakas commented Jan 23, 2025 • edited Loading

Description of what the PR does

Issue which the PR addresses

Environment in which the PR was developed (OS,IDE, Java version, etc.)

Precise steps for testing the PR (i.e., how to demonstrate that it works correctly)

kkarakas commented Jan 23, 2025

kkarakas commented Feb 4, 2025

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

clevengr Feb 8, 2025 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

clevengr left a comment

Choose a reason for hiding this comment

clevengr left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

kkarakas commented Feb 27, 2025

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

johnbrvc left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

kkarakas commented Jan 23, 2025 •

edited

Loading

clevengr Feb 8, 2025 •

edited

Loading

kkarakas commented Apr 24, 2025 •

edited

Loading