fix: Pipedream retest fixes - #29
Open
daveomri wants to merge 12 commits into
Open
Conversation
* feat: enhance run-actor component to handle fractional numbers and type conversions * fix: tolerate missing schema and coerce numeric run-actor inputs * fix: make no-schema fallback prop optional with empty default * chore: bump run-actor to 0.0.8 * test: add passing unit tests for run-actor schema/number handling * fix: update run-actor to treat apify number as string and remove fractional handling * chore: bump run-actor version to 0.0.4 * chore: remove unecessary test * fix: validate numeric run-actor inputs, reject NaN/blank * fix: distinguish genuine no-schema from real getSchema errors * fix: send no-schema raw input unwrapped; distinguish config errors * chore: lowered the version for run-actor
daveomri
changed the title
* fix: improve crawler type description and options * feat: add url validation in scrape-single-url action * feat: implement url validation method and add tests for scrape-single-url action * chore: update version of scrape-single-url action to 0.0.4 * chore: remove unecesary test file * chore: lowered scrape-single-url version
* feat: update dataset id and limit/offset desc for clarity * feat: bump version to 0.0.7 and refactor dataset item retrieval logic for improved clarity and efficiency * test: add test for get dataset items action to validate pagination and parameter handling * fix: normalize dataset id format in get-dataset-items action * chore: bump version to 0.0.4 for get-dataset-items action * chore: remove unecessary test file * chore: lower get-dataset-items version * chore: remove unecesary comment
* feat: add OUTPUT size-guard helpers * fix: cap sync OUTPUT to step-output limit * fix: cover OUTPUT size-guard helpers * chore: simplify null checker in capOutputRecord function * fix: await async getRecordPublicUrl for recordUrl * chore: update version to 0.0.4 in run-actor component * chore: remove unecessary test file * fix: report capping explicitly from capOutputRecord
* feat: enhance description and annotations for input field for run-task component * fix: typo fix * fix: link fix for get-kvs record * fix: remove runTaskSynchronously method and update version to 0.3.2 * chore: add (MB) to run task memory label * fix: bump up the get-kvs-record version * chore: increase run-task version
* fix: list real Actor builds in Run Actor Build dropdown * fix: resolve Build field by tag or build number * fix: accept build numbers in Run Actor Build field * chore: update version to 0.0.4 in run-actor component * feat: enhance listBuilds method to accept options for sorting and limiting results
* feat: enhance webhook functionality in base component * chore: update version for new-finished-actor-run-instant and new-finish-task-run-instant components to 0.4 * fix: improve webhook deletion handling and update component versions * fix: lower components unnecesary high version
* feat: add memory limit constants and options for Apify platform * feat: enhance run-actor action with memory limits and schema improvements * feat: update run-task action with memory options and version increment * fix: bug fix * chore: increment version numbers for run-actor and run-task actions * feat: add getTask method and refactor memory handling in run-actor and run-task components
* fix: add fallback for when empty recent actors * fix: rename runAsynchronously to waitForFinish and update related descriptions for clarity * chore: update no built message * chore: capitalize Actor mentions * chore: bump up the run actor version * chore: update version to 0.0.4 in run-actor component * chore: update version to 0.0.4 in new-finished-actor-run-instant component * feat: improve ux for actor selection and update version numbers * chore: lower the version bump for new-finished-actor-run-instant * feat: add condition validation and error messaging for actor selection
Member
|
Adding @FilipMasar for context on pipedream as well. |
FilipMasar
approved these changes
Sep 7, 2026
| webhook, | ||
| eventTypes, | ||
| properties, | ||
| ...data |
There was a problem hiding this comment.
actorSource isn't destructured here and has a default (line 41), so data is never empty -line 448 always picks data, and the new properties fallback never runs. For schema-less Actors that means the user's JSON is dropped and the Actor gets { actorSource: "recently-used" } instead. Low impact since most Actors have a schema, but adding actorSource to the destructuring looks like a one-line fix.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pipedream: Retest fixes
Umbrella branch with all nine Pipedream Apify connector fixes from the epic, bundled so the batch can be tested together before landing on
develop.Breaking change
#26 renames the Run Actor prop
Run AsynchronouslytoWait for Finishand inverts the toggle (new default: wait for finish, matching Run Task). Existing workflows keep running on their pinned version, so this only hits users who manually upgrade to the new version, at which point the saved toggle value is lost and falls back to the new default.Versioning
Each touched component and its
apify_oauthtwin is bumped once, collectively, to a single version covering all its fixes here.Testing
Tested together on this branch (
pd publish+ workflow runs). Webhook lifecycle (#28) verified across the four terminal states and delete-then-redeploy re-creation.