Skip to content

drop broken function - no replacement for now, so old icals forever exist in storage#145

Merged
DIodide merged 5 commits intomainfrom
fix/ical-exports
Mar 19, 2026
Merged

drop broken function - no replacement for now, so old icals forever exist in storage#145
DIodide merged 5 commits intomainfrom
fix/ical-exports

Conversation

@DIodide
Copy link
Member

@DIodide DIodide commented Feb 26, 2026

No description provided.

@DIodide
Copy link
Member Author

DIodide commented Feb 26, 2026

image

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: dc41ad93c8

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

AFTER DELETE ON public.icals
FOR EACH ROW
EXECUTE PROCEDURE public.handle_ical_deletion(); No newline at end of file
-- Storage file cleanup is handled in application code via the Supabase Storage API.

Choose a reason for hiding this comment

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

P2 Badge Restore deletion path for obsolete calendar objects

Removing the on_ical_deleted trigger leaves no actual cleanup path for old .ics objects even though this comment says cleanup is in application code: the only delete flow in apps/web/src/lib/components/recal/modals/schedule/ExportCal.svelte removes rows from icals (.from("icals").delete()) and then uploads a new random file, with no supabase.storage.from("calendars").remove(...) call. As a result, previously issued public calendar URLs remain accessible indefinitely and users cannot revoke old links by regenerating exports, while storage usage continuously accumulates.

Useful? React with 👍 / 👎.

@DIodide
Copy link
Member Author

DIodide commented Feb 26, 2026

At the very least, calendar exports work (tested), deleting old calendars may or may not work (probably works) but also its probably negligible storage

@DIodide DIodide self-assigned this Feb 26, 2026
DIodide and others added 3 commits February 26, 2026 11:32
…essing for schedules, and add configuration for function timeout and memory size in sst.config.ts.
Enhance refreshCals function with improved error handling, batch processing for schedules, and add configuration for function timeout and memory size in sst.config.ts.
@DIodide
Copy link
Member Author

DIodide commented Mar 19, 2026

this has been pushed to prod for a while now, verified calendars update

@DIodide DIodide merged commit da3f5a6 into main Mar 19, 2026
1 check passed
@DIodide DIodide deleted the fix/ical-exports branch March 19, 2026 15:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant