-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uncaught Exception "Deno.permissions.querySync is not a function" when using Deno Deploy CLI #10521
Comments
@getsentry-bot Bump |
Hm this sucks. It looks like an upstream issue to me that deno deploy should fix. We don't have the capacity to fix this right now so I'll backlog. Maybe you can work around this with the workaround described here: denoland/deploy_feedback#527 (comment) |
@lforst Sounds good, I'll look into the workaround. I switched back to using the |
From Deno Discord: https://discord.com/channels/684898665143206084/826085979344470037/1209268059173298257
|
Do you know if there is any progress on trying to resolve this one Sentry/Deno side? Is there any way I could help to progress with this one? I encountered the same bug which unfortunately makes Sentry not an option for me to use on Deno projects deployed to Deno Deploy. |
@pawelgrzybek I just realized that we probably don't have to rely on |
Thanks for info and rapid reaction @lforst , looking forward for this one to be merged and released. |
Environment
7.99.0
Steps to Reproduce
import * as Sentry from 'https://deno.land/x/[email protected]/index.mjs';
in any typescript file.deployctl deploy --project=<SOME_PROJECT> ./src/main.ts
This is noted on Deno Deploy Github here as well. denoland/deploy_feedback#527 (comment)
Expected Result
Expected result is that Deno Deploy works without issue.
Deployment works when using Sentry via the npm import:
import * as Sentry from 'npm:@sentry/node'
Actual Result
Deno Deploy fails. Here are the logs from Deno Deploy portal:
EDIT: Still failing on 7.99.0, SDK version updated
The text was updated successfully, but these errors were encountered: