fix(file-service): restore share notifications - #253
Open
devin-ai-integration[bot] wants to merge 3 commits into
Open
devin-ai-integration[bot] wants to merge 3 commits into
devin-ai-integration[bot] wants to merge 3 commits into
Conversation
Co-Authored-By: bot_apk <apk@cognition.ai>
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
Co-Authored-By: bot_apk <apk@cognition.ai>
Co-Authored-By: bot_apk <apk@cognition.ai>
This was referenced Aug 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Symptom / blast radius:
file_sharednotification publishes were routed to a nonexistent SNS topic ending in-v2, so shares returned an SNS error and recipients did not receive notifications.Root cause (config/env): the file-service image baked
FILE_SHARE_EVENT_ALWAYS_FAIL=true;EventPublisher::file_sharedtherefore selectedSNS_TOPIC_ARN-v2instead of the configured SNS topic.Fix: remove the enabled image default so deployed file-service instances use the existing off-by-default application configuration and publish shares to
SNS_TOPIC_ARN. Add a regression guard covering modern and legacyENVsyntax, truthy/quoted values, multi-assignment declarations, and backslash continuations. Upload failure and seeded-content settings are unchanged.Verification:
cargo test: 26 passedcargo fmt --checkcargo clippy --all-targets -- -D warningsFILE_SHARE_EVENT_ALWAYS_FAILAnnual Planning 2027.txtreturn 201 and publishfile_sharedtootterworks-events; zero-v2or publish-failure log entriesFollow-up observed: after the successful share, the owner's "People with access" list did not refresh, although recipient access and notification delivery were confirmed. This appears separate from the SNS outage and is not changed here.
Related independent work, left unchanged: #251, #248, #245.
Link to Devin session: https://app.devin.ai/sessions/b9ea2445f63348559338e25689db482f
Devin Review