Track expense lhn #41668

Nodebrute · 2024-05-06T11:58:28Z

Details

Fixed Issues

$ #41183
PROPOSAL: #41183 (comment)

Tests

Track an expense
Select any of the actionable whisper options
Confirm that the LHN displays the last visible message instead of 'What would you like to do with this expense?

Verify that no errors appear in the JS console

Offline tests

Track an expense
Go offline
Select any of the actionable whisper options
Confirm that the LHN displays the last visible message instead of 'What would you like to do with this expense?

QA Steps

Track an expense
Go offline
Select any of the actionable whisper options
Confirm that the LHN displays the last visible message instead of 'What would you like to do with this expense?

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Screen.Recording.2024-05-28.at.2.08.34.AM.mov

Android: mWeb Chrome

Screen.Recording.2024-05-28.at.2.14.52.AM.mov

iOS: Native

Screen.Recording.2024-05-27.at.10.58.41.PM.mov

iOS: mWeb Safari

Screen.Recording.2024-05-27.at.11.04.28.PM.mov

MacOS: Chrome / Safari

Screen.Recording.2024-05-06.at.4.25.24.PM.mov

MacOS: Desktop

Screen.Recording.2024-05-27.at.10.35.54.PM.mov

melvin-bot · 2024-05-06T11:58:33Z

@c3024 Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

Nodebrute · 2024-05-06T12:17:34Z

@c3024 We need to address this on the backend too. It works fine in offline mode, but when the open report API is called, the last message text reverts to 'What would you like to do with this expense?

We still have one unhandled case regarding expense deletion. Let's first test this solution, and if everything works fine, we'll decide whether we need to fix that here too.

c3024 · 2024-05-07T07:46:50Z

I see it working fine for all but Do nothing because the expense is moved to another report in those cases.

I found the last message showing as What do you want to do with this expense? when I choose Do nothing for an expense. But it should show the last tracked expense.

I see we only use the lastMessageText from report as fallback here

App/src/libs/OptionsListUtils.ts

Line 625 in 23297de

return lastMessageTextFromReport || (report?.lastMessageText ?? '');

and this here

App/src/libs/ReportActionsUtils.ts

Line 304 in 2d621b7

    
           return actionType !== CONST.IOU.REPORT_ACTION_TYPE.CREATE && actionType !== CONST.IOU.REPORT_ACTION_TYPE.TRACK && !isSentMoneyReportAction(action);

is filtering track actions as well and removing the track action in the sorted report actions to display here

App/src/libs/OptionsListUtils.ts

Line 274 in 23297de

    
           sortedReportActions = ReportActionUtils.getCombinedReportActions(allSortedReportActions[reportID], allSortedReportActions[transactionThreadReportID]);

and only CREATED action is left in the actions and the fallback is taken as last message. Since the backend still sends the whispers also as report actions I think we need not change the lastMessage sent from backend. We should fix the above to include the track action in the actions to display.

c3024 · 2024-05-10T03:18:46Z

@Nodebrute

Please check this. I don't think it needs a backend fix.

Nodebrute · 2024-05-10T05:40:28Z

@c3024 I'm on it. I'll complete it today.

Nodebrute · 2024-05-12T14:18:51Z

@c3024 The issue with the 'do nothing' behavior has been resolved after making this change. However, we're still encountering the same message from the backend when the 'open report' API is called

Screen.Recording.2024-05-12.at.7.10.57.PM.mov

c3024 · 2024-05-13T02:54:49Z

src/libs/ReportActionsUtils.ts

@@ -320,7 +320,7 @@ function getCombinedReportActions(reportActions: ReportAction[], transactionThre
    // Filter out request and send money request actions because we don't want to show any preview actions for one transaction reports
    const filteredReportActions = [...reportActions, ...filteredTransactionThreadReportActions].filter((action) => {
        const actionType = (action as OriginalMessageIOU).originalMessage?.type ?? '';
-        return actionType !== CONST.IOU.REPORT_ACTION_TYPE.CREATE && actionType !== CONST.IOU.REPORT_ACTION_TYPE.TRACK && !isSentMoneyReportAction(action);
+        return actionType !== CONST.IOU.REPORT_ACTION_TYPE.CREATE && !isSentMoneyReportAction(action);


We should not remove it directly.

Removing it breaks shows the report action in transaction report.

reportActionInWorkspaceChat.mp4

We should not filter track actions only in self DMs as far as I see. The following snippet fixes our bug and appears to cause no regressions.

Suggested change

return actionType !== CONST.IOU.REPORT_ACTION_TYPE.CREATE && !isSentMoneyReportAction(action);

const report = allReports?.[action?.reportID ?? ''];

const isSelfDM = report?.chatType === CONST.REPORT.CHAT_TYPE.SELF_DM;

if (isSelfDM) {

return actionType !== CONST.IOU.REPORT_ACTION_TYPE.CREATE && !isSentMoneyReportAction(action);

}

return actionType !== CONST.IOU.REPORT_ACTION_TYPE.CREATE && actionType !== CONST.IOU.REPORT_ACTION_TYPE.TRACK && !isSentMoneyReportAction(action);

c3024 · 2024-05-13T11:30:13Z

@Nodebrute

please fix the lint and ts failures.

Nodebrute · 2024-05-13T13:47:08Z

@c3024 Hey, could you help me solve this TypeScript error? I've tried but haven't had any luck.

c3024 · 2024-05-14T03:04:17Z

src/libs/ReportActionsUtils.ts

+ * Checks whether an action is actionable track expense.
+ *
+ */
+function isActionableTrackExpense(reportAction: OnyxEntry<ReportAction>): boolean {


Suggested change

function isActionableTrackExpense(reportAction: OnyxEntry<ReportAction>): boolean {

function isActionableTrackExpense(reportAction: OnyxEntry<ReportAction>): reportAction is ReportActionBase & OriginalMessageActionableTrackedExpenseWhisper {

We should retain the type predicate so that TS knows the originalMessage is of track whisper when this returns true.

c3024 · 2024-05-14T05:07:47Z

src/libs/ReportActionsUtils.ts

+        const report = allReports?.[action?.reportID ?? ''];
+        const isSelfDM = report?.chatType === CONST.REPORT.CHAT_TYPE.SELF_DM;


Suggested change

const report = allReports?.[action?.reportID ?? ''];

const isSelfDM = report?.chatType === CONST.REPORT.CHAT_TYPE.SELF_DM;

My bad! There is no reportID on action. Could not catch Copilot's shenanigans. I think we better pass the reportID to getCombinedReportActions in OptionsListUtils and add reportID as an optional parameter for getCombinedReportActions.

c3024 · 2024-05-14T05:08:54Z

src/libs/ReportActionsUtils.ts

@@ -320,6 +319,11 @@ function getCombinedReportActions(reportActions: ReportAction[], transactionThre
    // Filter out request and send money request actions because we don't want to show any preview actions for one transaction reports
    const filteredReportActions = [...reportActions, ...filteredTransactionThreadReportActions].filter((action) => {


Suggested change

const filteredReportActions = [...reportActions, ...filteredTransactionThreadReportActions].filter((action) => {

const report = allReports?.[reportID ?? ''];

const isSelfDM = report?.chatType === CONST.REPORT.CHAT_TYPE.SELF_DM;

const filteredReportActions = [...reportActions, ...filteredTransactionThreadReportActions].filter((action) => {

c3024 · 2024-05-14T11:53:36Z

src/libs/ReportActionsUtils.ts

@@ -309,17 +309,22 @@ function shouldIgnoreGap(currentReportAction: ReportAction | undefined, nextRepo
 * Returns a sorted and filtered list of report actions from a report and it's associated child
 * transaction thread report in order to correctly display reportActions from both reports in the one-transaction report view.
 */
-function getCombinedReportActions(reportActions: ReportAction[], transactionThreadReportActions: ReportAction[]): ReportAction[] {
+function getCombinedReportActions(reportActions: ReportAction[], transactionThreadReportActions: ReportAction[], reportID: string): ReportAction[] {


Suggested change

function getCombinedReportActions(reportActions: ReportAction[], transactionThreadReportActions: ReportAction[], reportID: string): ReportAction[] {

function getCombinedReportActions(reportActions: ReportAction[], transactionThreadReportActions: ReportAction[], reportID?: string): ReportAction[] {

c3024 · 2024-05-14T11:54:41Z

src/pages/home/report/ReportActionsView.tsx

@@ -149,7 +149,7 @@ function ReportActionsView({
    // Get a sorted array of reportActions for both the current report and the transaction thread report associated with this report (if there is one)
    // so that we display transaction-level and report-level report actions in order in the one-transaction view
    const combinedReportActions = useMemo(
-        () => ReportActionsUtils.getCombinedReportActions(allReportActions, transactionThreadReportActions),
+        () => ReportActionsUtils.getCombinedReportActions(allReportActions, transactionThreadReportActions,reportID),


Suggested change

() => ReportActionsUtils.getCombinedReportActions(allReportActions, transactionThreadReportActions,reportID),

() => ReportActionsUtils.getCombinedReportActions(allReportActions, transactionThreadReportActions),

src/libs/actions/IOU.ts

@@ -3041,31 +3057,6 @@ const getConvertTrackedExpenseInformation = (
        },
    });

-    // Resolve actionable whisper message
-    optimisticData?.push({


c3024 · 2024-05-24T03:00:32Z

@Nodebrute there are conflicts as well now.

Nodebrute · 2024-05-24T05:23:16Z

@c3024 I'll priorities this and finish it today.

Nodebrute · 2024-05-26T18:13:48Z

@c3024 Hey, I have resolved the conflicts in my code. I have tested it and it still shows the message when the openReport API is called. Can you help me understand what the next steps are to finish this up? Let's get this issue closed.

c3024 · 2024-05-27T01:21:59Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified tests pass on all platforms & I tested again on:
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

trackExpenseAndroid.mp4

Android: mWeb Chrome

trackExpenseAndroidChrome.mp4

iOS: Native

trackExpenseiOS.mp4

iOS: mWeb Safari

trackExpenseiOSSafari.mp4

MacOS: Chrome / Safari

trackExpenseChrome.mp4

MacOS: Desktop

trackExpenseDesktop.mp4

c3024 · 2024-05-27T03:49:36Z

All works well except with a small issue.

Do nothing fails again because this filter

App/src/libs/OptionsListUtils.ts

Lines 299 to 302 in 525ad6f

    
           ReportActionUtils.shouldReportActionBeVisible(reportAction, actionKey) && 
        
           !ReportActionUtils.isWhisperAction(reportAction) && 
        
           reportAction.actionName !== CONST.REPORT.ACTIONS.TYPE.CREATED && 
        
           reportAction.pendingAction !== CONST.RED_BRICK_ROAD_PENDING_ACTION.DELETE,

now does not use shouldReportActionBeVisibleAsLastAction where isResolvedActionTrackExpense change is included.

So, we should change this

App/src/libs/OptionsListUtils.ts

Lines 299 to 302 in 525ad6f

    
           ReportActionUtils.shouldReportActionBeVisible(reportAction, actionKey) && 
        
           !ReportActionUtils.isWhisperAction(reportAction) && 
        
           reportAction.actionName !== CONST.REPORT.ACTIONS.TYPE.CREATED && 
        
           reportAction.pendingAction !== CONST.RED_BRICK_ROAD_PENDING_ACTION.DELETE,

to

ReportActionUtils.shouldReportActionBeVisible(reportAction, actionKey) &&
                    !ReportActionUtils.isWhisperAction(reportAction) &&
                    reportAction.actionName !== CONST.REPORT.ACTIONS.TYPE.CREATED &&
                    reportAction.pendingAction !== CONST.RED_BRICK_ROAD_PENDING_ACTION.DELETE &&
                    !ReportActionUtils.isResolvedActionTrackExpense(reportAction),

c3024 · 2024-05-27T03:50:37Z

@c3024 Hey, I have resolved the conflicts in my code. I have tested it and it still shows the message when the openReport API is called. Can you help me understand what the next steps are to finish this up? Let's get this issue closed.

Yes, this needs a backend fix separately.

c3024 · 2024-05-27T03:51:10Z

@Nodebrute

Please fix this and it is done.

Nodebrute · 2024-05-27T21:18:06Z

@c3024 Hey, I have added videos for all platforms. I have updated the code and it works well. Thank you for your patience.

c3024

LGTM

c3024 · 2024-05-28T09:58:52Z

@thienlnam there is a backend fix required as well because when all track expenses are submitted/categorized (when all track expense whispers are resolved) there are no valid visible report actions and backend sends last message for the report as "What would you like to do with this expense?" even though all the whispers are resolved and expenses are moved to other reports.

I think backend should not send this as last message text when all the track expense whispers are resolved.

thienlnam · 2024-05-28T21:54:15Z

Thanks, I'll create an issue to track that internally

thienlnam · 2024-05-28T21:58:15Z

Is this still a problem? https://github.com/Expensify/App/pull/41668/files#r1600275772

Nodebrute · 2024-05-28T22:13:31Z

@thienlnam No.

cc @c3024

thienlnam

Great, thanks!

OSBotify · 2024-05-28T22:26:18Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

OSBotify · 2024-05-29T09:42:15Z

🚀 Deployed to staging by https://github.com/thienlnam in version: 1.4.77-0 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

OSBotify · 2024-05-30T21:25:04Z

🚀 Deployed to production by https://github.com/puneetlath in version: 1.4.77-11 🚀

platform	result
🤖 android 🤖	failure ❌
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

OSBotify · 2024-05-30T22:37:02Z

🚀 Deployed to production by https://github.com/puneetlath in version: 1.4.77-11 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

Nodebrute added 3 commits May 6, 2024 15:38

hide resolved whisper form lhn

d782a83

move whisper to getDeleteTrackExpenseInformation

67e5c1d

conditionally resolve whisper

704a2d3

Nodebrute requested a review from a team as a code owner May 6, 2024 11:58

melvin-bot bot requested review from c3024 and removed request for a team May 6, 2024 11:58

Nodebrute added 2 commits May 6, 2024 17:18

fix lint errors

7f2f8c8

fix lint

27d2bc1

Nodebrute and others added 2 commits May 12, 2024 18:37

Merge branch 'main' into trackExpenseLHN

0212adc

merge conflict

23fca9f

c3024 reviewed May 13, 2024

View reviewed changes

Nodebrute and others added 2 commits May 13, 2024 14:00

Merge branch 'Expensify:main' into trackExpenseLHN

9d18e70

add self dm check

5e7b53c

Nodebrute and others added 2 commits May 13, 2024 17:40

fix lint and ts errors

6388fc1

Merge branch 'Expensify:main' into trackExpenseLHN

d4f9589

c3024 reviewed May 14, 2024

View reviewed changes

c3024 suggested changes May 14, 2024

View reviewed changes

Nodebrute and others added 4 commits May 14, 2024 11:46

Merge branch 'Expensify:main' into trackExpenseLHN

31ef01b

fix lint errors

9630586

merge main

28ad8b1

fix type errors

0744ef4

c3024 suggested changes May 14, 2024

View reviewed changes

fix lint and cleanup

c574087

c3024 reviewed May 14, 2024

View reviewed changes

Nodebrute and others added 2 commits May 26, 2024 22:47

Merge branch 'main' into trackExpenseLHN

347799f

run prettier

2a19445

Nodebrute and others added 2 commits May 27, 2024 22:00

Merge branch 'Expensify:main' into trackExpenseLHN

8aaf27d

fix reportActionsForDisplay

d12e106

c3024 approved these changes May 28, 2024

View reviewed changes

melvin-bot bot requested a review from thienlnam May 28, 2024 09:55

thienlnam mentioned this pull request May 28, 2024

Prevent lastMessageText to show "What would you like to do with this expense?" when there are no tracked expenses #42727

Closed

thienlnam approved these changes May 28, 2024

View reviewed changes

thienlnam merged commit 1c1e88a into Expensify:main May 28, 2024
18 checks passed

github-actions bot mentioned this pull request May 29, 2024

Deploy Checklist: New Expensify 2024-05-29 #42741

Closed

melvin-bot bot mentioned this pull request May 30, 2024

[HOLD for payment 2024-06-06] CRITICAL: [Actionable Whisper] [$250] After selection an option for a tracked expense, the LHN still shows 'What would you like to do with this expense?' #41183

Closed

6 tasks

Nodebrute deleted the trackExpenseLHN branch September 16, 2024 00:44

	function isActionableTrackExpense(reportAction: OnyxEntry<ReportAction>): boolean {
	function isActionableTrackExpense(reportAction: OnyxEntry<ReportAction>): reportAction is ReportActionBase & OriginalMessageActionableTrackedExpenseWhisper {

		const report = allReports?.[action?.reportID ?? ''];
		const isSelfDM = report?.chatType === CONST.REPORT.CHAT_TYPE.SELF_DM;

		@@ -320,6 +319,11 @@ function getCombinedReportActions(reportActions: ReportAction[], transactionThre
		// Filter out request and send money request actions because we don't want to show any preview actions for one transaction reports
		const filteredReportActions = [...reportActions, ...filteredTransactionThreadReportActions].filter((action) => {

	function getCombinedReportActions(reportActions: ReportAction[], transactionThreadReportActions: ReportAction[], reportID: string): ReportAction[] {
	function getCombinedReportActions(reportActions: ReportAction[], transactionThreadReportActions: ReportAction[], reportID?: string): ReportAction[] {

	() => ReportActionsUtils.getCombinedReportActions(allReportActions, transactionThreadReportActions,reportID),
	() => ReportActionsUtils.getCombinedReportActions(allReportActions, transactionThreadReportActions),

Track expense lhn #41668

Track expense lhn #41668

Conversation

Nodebrute commented May 6, 2024 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented May 6, 2024

Nodebrute commented May 6, 2024

c3024 commented May 7, 2024

c3024 commented May 10, 2024 • edited Loading

Nodebrute commented May 10, 2024

Nodebrute commented May 12, 2024 • edited Loading

c3024 May 13, 2024

Choose a reason for hiding this comment

c3024 commented May 13, 2024

Nodebrute commented May 13, 2024

c3024 May 14, 2024 • edited Loading

Choose a reason for hiding this comment

c3024 May 14, 2024

Choose a reason for hiding this comment

c3024 May 14, 2024

Choose a reason for hiding this comment

c3024 May 14, 2024

Choose a reason for hiding this comment

c3024 May 14, 2024

Choose a reason for hiding this comment

This comment was marked as outdated.

This comment was marked as outdated.

This comment was marked as resolved.

c3024 commented May 24, 2024

Nodebrute commented May 24, 2024

Nodebrute commented May 26, 2024

c3024 commented May 27, 2024 • edited Loading

Reviewer Checklist

Screenshots/Videos

c3024 commented May 27, 2024

c3024 commented May 27, 2024

c3024 commented May 27, 2024 • edited Loading

Nodebrute commented May 27, 2024 • edited Loading

c3024 left a comment

Choose a reason for hiding this comment

c3024 commented May 28, 2024

thienlnam commented May 28, 2024

thienlnam commented May 28, 2024

Nodebrute commented May 28, 2024

thienlnam left a comment

Choose a reason for hiding this comment

OSBotify commented May 28, 2024

OSBotify commented May 29, 2024

OSBotify commented May 30, 2024

OSBotify commented May 30, 2024

Nodebrute commented May 6, 2024 •

edited

Loading

c3024 commented May 10, 2024 •

edited

Loading

Nodebrute commented May 12, 2024 •

edited

Loading

c3024 May 14, 2024 •

edited

Loading

c3024 commented May 27, 2024 •

edited

Loading

c3024 commented May 27, 2024 •

edited

Loading

Nodebrute commented May 27, 2024 •

edited

Loading