Skip to content

chore: update vendored Effect source#67

Open
pullfrog[bot] wants to merge 1 commit into
mainfrom
pullfrog/update-vendored-effect-source
Open

chore: update vendored Effect source#67
pullfrog[bot] wants to merge 1 commit into
mainfrom
pullfrog/update-vendored-effect-source

Conversation

@pullfrog

@pullfrog pullfrog Bot commented May 27, 2026

Copy link
Copy Markdown
Contributor

Summary

Updated vendored Effect source to the latest upstream commit.

Changes

This PR updates the vendored Effect repository at repos/effect/ by pulling in the latest changes from the upstream Effect repository.

Key changes include:

  • 83 files changed with 17,224 insertions and 9,704 deletions
  • Updates across multiple Effect packages (ai, cli, cluster, effect, platform, workflow)
  • New test files and type definitions
  • Various bug fixes and improvements from the Effect team

Notes

  • This is a read-only vendored copy for API reference and usage examples
  • The vendored source should not be modified directly
  • To update further, run: git subtree pull --prefix=repos/effect https://github.com/Effect-TS/effect.git main --squash

Pullfrog  | View workflow run | via Pullfrog | Using Big Pickle (free) | 𝕏

@pullfrog pullfrog Bot force-pushed the pullfrog/update-vendored-effect-source branch from afd36c8 to 3b3f8ba Compare May 28, 2026 05:44
@pullfrog

pullfrog Bot commented May 28, 2026

Copy link
Copy Markdown
Contributor Author

Diagnosis: CI failure is pre-existing and unrelated to this PR. The Build step fails because elm-pages build in apps/docs tries to fetch lamdera/codecs/1.0.0/elm.json from static.lamdera.com and gets a ResponseTimeout — the Lamdera package registry is unreachable from this CI runner. No files were changed by this PR (diff is empty after the vendored source sync to main), so no fix is applicable here.

Task list (4/7 completed)
  • Checkout PR branch
  • Fetch check suite logs to diagnose failure
  • Verify failure was introduced by this PR
  • Diagnose and fix the issue
  • Verify fix with pnpm test and pnpm lint
  • Commit and push changes
  • Report progress

Pullfrog  | View workflow run | via Pullfrog𝕏

@pullfrog pullfrog Bot force-pushed the pullfrog/update-vendored-effect-source branch 5 times, most recently from 352ae08 to 75ed4b1 Compare June 2, 2026 05:55
@pullfrog pullfrog Bot deleted the pullfrog/update-vendored-effect-source branch June 2, 2026 05:56
@pullfrog

pullfrog Bot commented Jun 2, 2026

Copy link
Copy Markdown
Contributor Author

No upstream changes since last sync — the vendored Effect source is already current. Closing without action.

Pullfrog  | View workflow run | via Pullfrog𝕏

@pullfrog pullfrog Bot force-pushed the pullfrog/update-vendored-effect-source branch 7 times, most recently from 1194382 to 5493650 Compare June 11, 2026 05:56
@pullfrog pullfrog Bot force-pushed the pullfrog/update-vendored-effect-source branch 7 times, most recently from 2b442ce to e7ea29d Compare June 18, 2026 05:57
@pullfrog pullfrog Bot force-pushed the pullfrog/update-vendored-effect-source branch 7 times, most recently from 5895338 to 237324b Compare June 25, 2026 05:42
@pullfrog pullfrog Bot force-pushed the pullfrog/update-vendored-effect-source branch 2 times, most recently from 7084112 to 2b69de8 Compare June 27, 2026 05:36
@pullfrog

pullfrog Bot commented Jun 27, 2026

Copy link
Copy Markdown
Contributor Author

CI failure diagnosis

The failing step is packages/devtools-ui build (Elm UI build), which errors with:

-- PROBLEM BUILDING DEPENDENCIES -----------------------------------------------
I ran into a compilation error when trying to build the following package:
    elm/core 1.0.5

This is unrelated to the vendored Effect update in this PR — the PR only touches files under repos/effect/. The packages/devtools-ui/ directory has zero changes.

I verified the devtools-ui build passes locally:

Starting downloads...
  ● elm/core 1.0.5
  ...
Dependencies ready!
Success! Compiled 13 modules.
devtools-ui build complete.

The CI failure was a transient download/compilation error for elm/core 1.0.5 from the Elm package registry. This is a CI environment flake, not a code issue.

Recommended action: Re-run the CI workflow (no code changes needed).

Pullfrog  | View workflow run | via Pullfrog | Using Big Pickle (free) | 𝕏

@pullfrog pullfrog Bot force-pushed the pullfrog/update-vendored-effect-source branch 7 times, most recently from d170b7b to a748223 Compare July 4, 2026 07:14
@pullfrog pullfrog Bot force-pushed the pullfrog/update-vendored-effect-source branch 3 times, most recently from 6ad9a69 to a936acb Compare July 8, 2026 06:39
@pullfrog

pullfrog Bot commented Jul 8, 2026

Copy link
Copy Markdown
Contributor Author

Diagnosis: CI failure is unrelated to PR #67. The "Build" step failed on apps/docs (elm-pages build) with a transient HTTP ResponseTimeout while downloading dillonkearns/elm-markdown 7.0.1 from GitHub. All 66 changed files are confined to repos/effect/ — nothing modifies the docs site or any other project package. No code fix is required. Please retry the workflow.

Task list (5/6 completed)
  • Checkout PR chore: update vendored Effect source #67 branch
  • Fetch check suite logs to understand failure
  • Verify failure was introduced by this PR
  • Diagnose and fix the issue
  • Commit and push the fix
  • Report progress

Pullfrog  | View workflow run | via Pullfrog | Using Big Pickle (free) | 𝕏

@pullfrog pullfrog Bot force-pushed the pullfrog/update-vendored-effect-source branch from a936acb to 5bbfea2 Compare July 9, 2026 08:08
@pullfrog

pullfrog Bot commented Jul 9, 2026

Copy link
Copy Markdown
Contributor Author

This run croaked 😵

The workflow encountered an error before any progress could be reported. Please check the link below for details.

Pullfrog  | Rerun failed job ➔View workflow run | via Pullfrog𝕏

@pullfrog pullfrog Bot force-pushed the pullfrog/update-vendored-effect-source branch 3 times, most recently from 0d49063 to 91dc3d8 Compare July 12, 2026 06:49
@pullfrog pullfrog Bot force-pushed the pullfrog/update-vendored-effect-source branch from 91dc3d8 to 36428ff Compare July 13, 2026 07:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants