Skip to content

Conversation

@miaulalala
Copy link
Collaborator

Since the file source path and user path for resharing users doesn't match, catch the exception and don't generate a notification instead.

Issue might be from #2103, but the exception is also not bubbling up for 32+, so something else must have changed as well.

Fixes #2148

Since the file source path and user path for resharing users doesn't match, catch the exception and don't generate
a notification.

Signed-off-by: Anna Larch <[email protected]>
@cypress
Copy link

cypress bot commented Nov 10, 2025

Activity    Run #3002

Run Properties:  status check passed Passed #3002  •  git commit 002a77526b: [stable31] fix: catch NotFoundException when user is resharer
Project Activity
Branch Review fix/2148/catch-path-exception
Run status status check passed Passed #3002
Run duration 02m 14s
Commit git commit 002a77526b: [stable31] fix: catch NotFoundException when user is resharer
Committer Anna
View all properties for this run ↗︎

Test results
Tests that failed  Failures 0
Tests that were flaky  Flaky 0
Tests that did not run due to a developer annotating a test with .skip  Pending 0
Tests that did not run due to a failure in a mocha hook  Skipped 0
Tests that passed  Passing 10
View all changes introduced in this branch ↗︎

Copy link
Member

@nickvergessen nickvergessen left a comment

Choose a reason for hiding this comment

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

Would a test be possible? 🙊

Copy link
Member

@skjnldsv skjnldsv left a comment

Choose a reason for hiding this comment

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

Btw, it's still feels weirf that we cannot compute the path properly. The end user should still get the notification, no ?

@miaulalala
Copy link
Collaborator Author

Btw, it's still feels weirf that we cannot compute the path properly. The end user should still get the notification, no ?

We don't notify for 32+ either, it just fails more gracefully. I guess we could add a check on the file owner and send them a notification instead, but then we'll have to backport from master.

@miaulalala miaulalala force-pushed the fix/2148/catch-path-exception branch from db41827 to 521d549 Compare November 11, 2025 09:12
@miaulalala miaulalala force-pushed the fix/2148/catch-path-exception branch from 521d549 to ff88d8c Compare November 11, 2025 09:17
@miaulalala miaulalala enabled auto-merge November 11, 2025 09:19
@miaulalala miaulalala merged commit 271a20d into stable31 Nov 11, 2025
51 checks passed
@miaulalala miaulalala deleted the fix/2148/catch-path-exception branch November 11, 2025 09:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants