Last 12 weeks · 0 commits
1 of 6 standards met
Problem description Trying to deploy a project that I've deployed in the past (last time was about 7 months ago) which means that's in deploy classic. I'm trying to look into a bug that's cropped up with the application and don't want to have to figure out moving over to the new deploy dashboard yet. Right now I can do and it works perfectly fine (after some minor syntax updates) but when I do I end up with: error: Uncaught (in promise) APIError: An internal server error occurred. throw new APIError(json.code, json.message, xDenoRay); ^ at API.#requestStream (https://jsr.io/@deno/deployctl/1.13.1/src/utils/api.ts:196:13) at async API.#requestJsonStream (https://jsr.io/@deno/deployctl/1.13.1/src/utils/api.ts:217:20) at async deploy (https://jsr.io/@deno/deployctl/1.13.1/src/subcommands/deploy.ts:322:20) at async default (https://jsr.io/@deno/deployctl/1.13.1/src/subcommands/deploy.ts:166:3) at async https://jsr.io/@deno/deployctl/1.13.1/deployctl.ts:107:5 And cannot for the life of me figure out anyway around this. I also have github linked up for auto deployments though hadn't really ended up using in the past. I tried using that this time as well, and no dice - it just didn't react to the push to the repo at all. Steps to reproduce 1. Run 2. Fails as described above Expected behavior For it to not fail with absolutely no information about how I can fix it. Environment deno 2.6.6 MacOS 15.7.3 deployctl 1.13.1 Possible solution _No response_ Additional context _No response_
Repository: denoland/deploy_feedback. Description: For reporting issues with Deno Deploy Stars: 79, Forks: 4. Homepage: https://deno.com/deploy Open PRs: 0, open issues: 498. Last activity: 2y ago. Community health: 25%. Top contributors: ry, nicolo-ribaudo.
Problem description I started seeing this error everywhere: TypeError: txnproxy call timed out at async doAtomicWriteInPlace (ext:deno_kv/01_db.ts:628:10) at async Kv.delete (ext:deno_kv/01_db.ts:112:20) at async AuthDenoKvRepository.removeAuthToken (file:///src/models/auth/deno-kv-repository.ts:39:5) at async validateAuthTokenAndCreateSession (file:///src/utils/validate-auth-token-and-create-session.ts:27:3) at async AuthController.validateAuthToken (file:///src/controllers/auth.ts:77:21) at async dispatch (file:///node_modules/.deno/hono@4.6.9/node_modules/hono/dist/compose.js:30:17) at async file:///node_modules/.deno/hono@4.6.9/node_modules/hono/dist/validator/validator.js:81:5 at async dispatch (file:///node_modules/.deno/hono@4.6.9/node_modules/hono/dist/compose.js:30:17) at async file:///src/main.ts:148:5 at async dispatch (file:///node_modules/.deno/hono@4.6.9/node_modules/hono/dist/compose.js:30:17) I use DenoKV on Deno Deploy. Previously, everything worked perfectly, and I hasn't changed anything. Steps to reproduce The error happens almost on any request to DenoKV. Expected behavior I expect to not see any timeout error. Environment Deno Deploy Possible solution _No response_ Additional context _No response_
Problem description I am starting to get this in deno deploy. It kills my server. That's the entire error message, and I have no idea what transactionDomainNotFound is about Steps to reproduce Deploy then connect with a websocket Expected behavior To not have the error and crash Environment local host deno 2.5.6 deno deploy ?? Possible solution _No response_ Additional context _No response_
Hello ! 👋 Problem description Deno Deploy can't authenticate NPM with a private package registry/package. Deployment return a 401 error. Context In my Deno project, I added a private registry and private package using the file. For this issue, let's call the private package . The private registry is Github .npmrc file: The env variable is stored in a file. [!note] I tried to replace the env var by the the actual token but the issue is the same. I also tried to add the env variable in the Deno Deploy project settings, but still not working. And I use this command to deploy the project: Error Deno Deploy return this error during deployment : The local command makes me believe that the token and configuration is correct, since is able to install all dependencies, including the private ones. Of course, also works well. Steps to reproduce 1. Create a private package on Github 2. Generate a Github classic token, with permission 3. Create a new folder 4. Run 5. Create a file in a Deno project (see above for .npmrc file example, you can write the token in the file for testing) 6. Run 8. Run You should have a 401 error. Expected behavior I expect Deno Deploy to be able to use the information in the and use the authToken provided. Environment deno 2.2.1 (stable, release, aarch64-apple-darwin) v8 13.4.114.9-rusty typescript 5.7.3 Possible solution _No response_ Additional context _No response_ Please let me know if I'm wrong somewhere or if you need more details !