denoland / denoland/deploy_feedback

[Bug]: Unable to use Deno.openKv()::enqueue() for production deploys

Open
#773 10 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
79
Forks
5
PR merge metrics
No merged PRs in 30d

Description

### Problem description

I just deployed an application on the free tier that utilizes the `enqueue()` function of Deno KV. Similar to this code:

```typescript
const db = await Deno.openKv()
db.enqueue({ some: "data" })
```

This works completely fine in my local dev environment, but when I push to Deno Deploy (and deploy to production!) I get the following message in the logs:

![image](https://github.com/user-attachments/assets/7ff265c1-112c-4496-b2bb-3e3d97ee68d1)

### Steps to reproduce

1. Create application utilizing `enqueue()` and `listenQueue()` of `Deno.openKv()`
2. Deploy to production on Deno Deploy free tier using `deployctl deploy`
3. Promote deployment to production deploy
4. Trigger `enqueue()` by interacting with the app

### Expected behavior

Messages that are enqueued for the production app should not be dropped

### Environment

- Deno Deploy (gcp-europe-west3)
- deployctl 1.13.0

### Possible solution

_No response_

### Additional context

_No response_

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.