1. 29 4月, 2026 7 次提交
  2. 28 4月, 2026 5 次提交
  3. 27 4月, 2026 2 次提交
  4. 24 4月, 2026 1 次提交
  5. 23 4月, 2026 12 次提交
  6. 22 4月, 2026 2 次提交
  7. 21 4月, 2026 5 次提交
  8. 19 4月, 2026 1 次提交
    • Mohamed Aziz Mejri's avatar
      Neon integration (#3178) · 661e1438
      Mohamed Aziz Mejri 提交于
      ### Context for review bots :
      
      1.The agent can execute sql commands directly on production , this is
      fine because they user may choose to start with a simple setup first and
      use the production database directly (in a follow up PR we should give
      the users the ability to sync dev branch to match production branch).The
      user also has the possiblity to revert database changes .
      2.Right now there’s no warning for destructive changes before migration
      , this is fine for now as we're gonna add a follow up PR for this
      3.When linking an existing neon project that doesnt have a developement
      database , we're setting the default branch as the active branch . This
      is fine because the user may prefer to start a simple setup at the
      beginning and work directly on the production database , in addition
      since the project was created outside dyad it may have a developement
      branch named differently so it wouldnt be wise to auto create one here .
      However, in a follow up PR we should allow the user to manually create
      branches and sync dev branch to match production .
      4.neon is only available for next.js now
      5.We dont have enough tests for now, i am gonna add a follow-up PR to
      cover this
      <!-- devin-review-badge-begin -->
      
      ---
      
      <a href="https://app.devin.ai/review/dyad-sh/dyad/pull/3178"
      target="_blank">
        <picture>
      <source media="(prefers-color-scheme: dark)"
      srcset="https://static.devin.ai/assets/gh-open-in-devin-review-dark.svg?v=1">
      <img
      src="https://static.devin.ai/assets/gh-open-in-devin-review-light.svg?v=1"
      alt="Open with Devin">
        </picture>
      </a>
      <!-- devin-review-badge-end -->
      
      ---------
      Co-authored-by: 's avatarClaude Opus 4.6 (1M context) <noreply@anthropic.com>
      661e1438
  9. 16 4月, 2026 1 次提交
  10. 15 4月, 2026 1 次提交
    • Nour Zakhma's avatar
      Feature/pause queue (#3077) · f2265f83
      Nour Zakhma 提交于
      closes #3075 
      Implements pause/resume functionality for the message queue processing
      system, allowing users to pause automatic processing of queued messages
      and selectively resume. Includes session-level persistence via
      sessionStorage.
      
      
      <img width="594" height="694" alt="Capture d&#39;écran 2026-03-26
      045040"
      src="https://github.com/user-attachments/assets/2cf9648f-7be1-466c-971c-e2e96faccd0d"
      />
      
      
      9 comprehensive E2E test cases covering:
      Pause/Resume button visibility
      Pause functionality and message blocking
      Resume processing
      SessionStorage persistence (empty & non-empty cases)
      Multiple pause/resume cycles
      Per-chat isolation
      Visual styling
      f2265f83
  11. 14 4月, 2026 2 次提交
  12. 10 4月, 2026 1 次提交
    • keppo-bot[bot]'s avatar
      [codex] fix binary-safe cloud sandbox sync uploads (#3188) · 26dc0390
      keppo-bot[bot] 提交于
      ## What changed
      - switch the cloud sandbox upload client to a multipart
      manifest-plus-file request instead of JSON `Record<string, string>`
      payloads
      - read synced files as raw bytes for both full and incremental uploads
      while preserving `replaceAll`, `deletedFiles`, and queued incremental
      sync behavior
      - update the fake cloud sandbox server and desktop-side tests to
      validate multipart uploads and binary byte preservation
      
      ## Why
      The previous upload path decoded files as UTF-8 strings before sending
      them to the engine, which corrupted binary assets and broke cloud
      previews for files like images, fonts, and wasm.
      
      ## Impact
      Desktop cloud sandbox syncs now send byte-exact file contents to the
      engine, including incremental syncs.
      
      ## Compatibility
      - depends on the engine multipart upload support in
      dyad-sh/dyad-llm-engine#146
      - the engine PR keeps legacy JSON uploads available for older desktop
      clients, but this desktop change is required for binary-safe uploads
      
      ## Validation
      - `npm test -- src/ipc/utils/cloud_sandbox_provider.test.ts`
      - `npm run ts`
      - `npm run lint`
      - `npm run fmt:check`
      
      <!-- devin-review-badge-begin -->
      
      ---
      
      <a href="https://app.devin.ai/review/dyad-sh/dyad/pull/3188"
      target="_blank">
        <picture>
      <source media="(prefers-color-scheme: dark)"
      srcset="https://static.devin.ai/assets/gh-open-in-devin-review-dark.svg?v=1">
      <img
      src="https://static.devin.ai/assets/gh-open-in-devin-review-light.svg?v=1"
      alt="Open with Devin">
        </picture>
      </a>
      <!-- devin-review-badge-end -->
      Co-authored-by: 's avatarWill Chen <7344640+wwwillchen@users.noreply.github.com>
      26dc0390