You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Interestingly, if I serve the edge function runtime locally (while testing them out), then the module is specific to the docker container that's hosting the edge runtime, and the module label looks like /home/deno/...
Expected result
I would expect my filesystem details to not be present in the module label.
The text was updated successfully, but these errors were encountered:
brettimus
changed the title
🐛 My filestystem details are leaked by the module label when using autometrics-ts with Supabase Edge Functions
🐛 Supabase Edge Functions: My filestystem details are leaked by the module label when using autometrics-ts with Supabase Edge Functions
Jul 25, 2023
brettimus
changed the title
🐛 Supabase Edge Functions: My filestystem details are leaked by the module label when using autometrics-ts with Supabase Edge Functions
🐛 Supabase Edge Functions: My filesystem details are leaked by the module label when using autometrics-ts with Supabase Edge Functions
Feb 24, 2024
Environment information
What happened?
I deployed an edge function with Supabase, and configured autometrics-ts to work with a push gateway.
The module label contained the filesystem path on my local machine to the script containing the edge function.
Interestingly, if I serve the edge function runtime locally (while testing them out), then the module is specific to the docker container that's hosting the edge runtime, and the module label looks like
/home/deno/...
Expected result
I would expect my filesystem details to not be present in the module label.
The text was updated successfully, but these errors were encountered: