v.docker.2.2.2
18 Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
 Eric Allam
|
044d38e390 |
Improvement: Auto Execution Yielding (#612)
* Auto-yield run execution to help prevent duplicate task executions * Add auto-yield config to endpoints * Refactor run execution with buffer and limits Introduced constants RUN_CHUNK_EXECUTION_BUFFER and MAX_RUN_CHUNK_EXECUTION_LIMIT. Adjusted PerformRunExecutionV2Service to use the new constants to fine-tune execution timings and buffers. * Add endpoint probing functionality Added new `RESPONSE_TIMEOUT_STATUS_CODES` in `consts.ts` to manage timeout responses. Additional functions `detectResponseIsTimeout(response: Response)` was added in `endpoint.server.ts` to detect if a response was a timeout based on the status codes from `RESPONSE_TIMEOUT_STATUS_CODES`. Update actions to use new endpoint probing endpoint service. This allows for the early probing of endpoints to determine if they're up and running. A new class `ProbeEndpointService` was created in `probeEndpoint.server.ts` which makes HTTP requests to a given endpoint and updates its properties based on the result. Finally, `detectResponseIsTimeout(response)` is used in `performRunExecutionV2.server.ts` for marking the execution as succeeded when facing a timeout. * Refactored probe method in EndpointApi class The probe method of the EndpointApi class has been refactored to remove the error handling part and it now takes a timeout sent from the client directly. The corresponding changes were also made in the ProbeEndpointService and TriggerClient objects to reflect the alterations in the probe method. The error handling related to the timeout has been removed and the responsibility of handling the timeout has been shifted to the client. Thus, the probe method has been greatly simplified. The `probeEndpoint.server.ts` file was also changed to accommodate the change in behavior of the probe result. In the `triggerClient.ts` the timeout for probe is now read from the incoming request object. For backward compatibility, if no timeout is provided in the request, the default value of 15 minutes is used. * Remove performRunExecution v1 enqueue function * Better document limits and add docs on increasing function timeouts * Upgrade webapp docker container to use 18.18.2 * force clients to yield when a run is executing in a gracefully shutting down worker * Renamed task `key` to `cacheKey` and added more task documentation * Index the `@trigger.dev/sdk` version on Endpoints |
||
|
vimode
|
513d0f071d |
fix: broken links in documentation (#602)
* fix: broken links at what is triggerdev docs * fix: broken links for apikey * fix: broken sdk link * fix: broken link in concepts/triggers * fix: broken link for zod guide at concepts/triggers/events * fix: broken links in title for projects * Shouldn't have /docs at the start * Use backgroundFetch path --------- Co-authored-by: Matt Aitken <matt@mattaitken.com> |
||
|
Matt Aitken
|
0558b2c595 |
feat: sveltekit adaptor (#575)
* Feat/svelte kit support (#467) * feat: implemented svelte-kit adapter * feat: implemented the @trigger.dev/svelte package * scaffolded a sveltekit example project with trigger.dev * added the convertToStandardRequest function in the sveltekit package * example sveltekit project with the @trigger.dev/svelte package * doc: added the manual setup guide for sveltekit * updated the web app onboard for sveltekit * formatted the manual setup guide for sveltekit * added a link to webapp sveltekit onboarding * added a wait function to the sveltekit example app job * typo fix * removed comments from the @trigger.dev/svelte - commented out the useEventRunDetails * updated package.json to use internal packages * added a .env.example file * updated the example-svelte-app * updated the svelte-example * updated the onboarding page to reflect requested changes * made the manual setup guide more specific * created a .env.example file for svelte-example * added import aliases * updated the tsconfig and svelte.config file * updated to use uint8Array * added missing paths in the tsconfig --------- Co-authored-by: Matt Aitken <matt@mattaitken.com> * Moved examples to references * Tweaked the SveleteKit manual setup guide * Updated zod, and set the svelte/sveltekit package versions to match other packages * Added the headers to the response from the SvelteKit api/trigger route * Changeset for Svelte and SvelteKit packages * Revert change to rawBody * Remove core from changeset packages * Delete svelte .npmrc file * Build svelte package to build, not build/lib * Made the snapshot instructions easier to copy * Delete the svelte package * Latest lockfile * Updated the SvelteKit docs * Attempt to get Svelte to import the package * Updates for port and host options * Updated lockfile from main * Update neat-feet-wait.md --------- Co-authored-by: Chigala <92148630+Chigala@users.noreply.github.com> |
||
|
Matt Aitken
|
a847b492bc |
NestJS framework suport (from @H4ad) (#574)
* feat: added nestjs package adapter
* Latest lockfile
* Updated Astro setup docs: env import
* Astro docs improvements
* Docs: improved the limitations
* Bumped package versions to 2.1.3
* Updated the Astro docs with SSR notes
* test/368/use vitest instead of jest (#470)
* chore: add vitest dependencies
* refactor: replace jest by vitest
* test: disable broken test
* Update pnpm-lock.yaml
* Update pnpm-lock.yaml
---------
Co-authored-by: Matt Aitken <matt@mattaitken.com>
* Created Temp for pull req, bugreport & feature req
* A few teaks to the templates
* Added instructions for how to do Changeset snapshots
* Redirect people to discord to ask a question
* Documentation Update: Added <github_username> instead of triggerdotdev to avoid confusion while cloning the repository (#477)
* Added a link to the homepage from the side menu (#479)
* Added 2 new named icons
* New side menu link to the homepage
* Updated lock file
* Removed un-used import
* Renamed the examples dir to references (true examples are in another repo and this was confusing)
* Add a references README
* Fixes broken pnpm lock file
* Improve the Astro manual setup guide
* Fixed cal.com link
* Upgrade to the latest remix (pre v2)
* React status hooks (#493)
* Added stripInternal to SDK tsconfig
* Statuses can now be set from a run, and are stored in the database
* Added the key to the returned status
* Made the test job have an extra step and only pass in some of the options
* client.getRunStatuses() and the corresponding endpoint
* client.getRun() now includes status info
* Fixed circular dependency schema
* Translate null to undefined
* Added the react package to the nextjs-reference tsconfig
* Removed unused OpenAI integration from nextjs-reference project
* New hooks for getting the statuses
* Disabled most of the nextjs-reference jobs
* Updated the hooks UI
* Updated the endpoints to deal with null statuses values
* The hook is working, with an example
* Changeset: “You can create statuses in your Jobs that can then be read using React hooks”
* Changeset config is back to the old changelog style
* WIP on new React hooks guide
* Guide docs for the new hooks
* Added the status hooks to the React hooks guide
* Removed the links to the status hooks reference for now
* Re-ordered the hooks
* Fix for an error in the docs
* Set a default of a blank array for the GetRunSchema
* Fixed dependency
* Revert "Upgrade to the latest remix (pre v2)"
This reverts commit
|
||
|
Hemachandar
|
c0aa6633d2 |
chore: update doc title for groups (#539)
* chore: update doc title for groups * update docs for sdk and integrations |
||
|
Eric Allam
|
a42e94c75f |
Add the STAGING environment by default
🚀 Publish Trigger.dev Docker / ʦ TypeScript (push) Has been cancelled
🚀 Publish Trigger.dev Docker / Unit Tests (push) Has been cancelled
🚀 Publish Trigger.dev Docker / e2e Tests (push) Has been cancelled
🚀 Publish Trigger.dev Docker / publish (push) Has been cancelled
|
||
|
Eric Allam
|
c0dfa8048a |
feat: BYO Auth (#491)
* feat: BYO Auth Define client-side auth resolvers to be able to supply custom authentication credentials for integrations before a run is performed - Added new defineAuthResolver - Update all integrations to support the new auth resolvers - Strip internal symbols from .d.ts in integrations and trigger-sdk - Added BYO Auth docs - Update Dynamic Schedule to support associated account IDs - Create external accounts just-in-time - Added Account ID field to test job when there are external auth integrations - Show Account ID on run dashboard - Added new Run error state called “Unresolved auth” * Added changeset * Remove @internal from TriggerIntegration public methods * Add void to the result union * DynamicTriggers now work with the new BYO auth system, and added a bunch of docs and docs changes * Add additional key material for registering dynamic trigger task * Add new define* instance methods to the overview |
||
|
Matt Aitken
|
a68a912d56 | Docs: improved the limitations | ||
|
Chigala
|
1b4db79885 |
Feat/astro support (#466)
* updated the @trigger.dev/astro package to support typescript * set up a example astro project * docs: manual setup of Trigger.dev in an Astro project * doc: updated the manual setup docs for astro * updated the webapp onboarding for astro * cleaned up the example astro project * removed next from dependency 😅 * updated the readme * moved trigger.ts file and job folder to src directory * created a .env.example file * updated tsconfig * updated to use aliases * updated package.json * updated the astro onboarding page * updated the manual installation guide for astro * updated to use alias * added astro as a dev dependency * Remove extra comma I left in * Changed Object.create() to a Record, so we have some type safety * Added the localhost URL to the API in the Astro example * Added the TRIGGER_API_URL to the trigger client in the example * Added the CLI dev dependency to the Astro example * Update the running instructions to be closer to Remix's * Create friendly-carpets-collect.md * Fix bad package name for Astro --------- Co-authored-by: Matt Aitken <matt@mattaitken.com> |
||
|
Chigala
|
b00717748b |
Feat/remix support (#465)
* init remix project * feat: implemented the remix adapter package * updated the remix package to return the action variable * added an example job to the example remix project * fix: Ensure Side Effects Execution in Remix API Routes * updated the readme in @trigger.dev/remix package * doc: added the manual setup guide for remix * updated the webapp onboarding for remix * updated the manual setup guide * added a license to the @trigger.dev/remix package * added a wait function to the example job * added a link to the remix webapp onboarding * Updated the onboarding page For now, we'll only support existing projects. The button that links to the manual installation was just a blank rectangle – added some text to it. * Added the Server API key to the instructions * Remix manual docs Made some things a bit clearer - file paths - exporting the job rather than using a function wrapper - how to run the app and CLI dev command * Export the job * Update api.trigger.ts * Added tsconfig.json paths * Remove next dependency * Package set to 2.1.0 and set dependencies Shouldn't rely on a specific version in main dependencies. In this case we can just have devDependency for @remix/node * Changeset --------- Co-authored-by: Matt Aitken <matt@mattaitken.com> |
||
|
James Ritchie
|
65fa8300ad |
Support for more frameworks (#446)
* Removed next references in the ReadMe * FAQ improvements to update Next.js references * Added a new Frameworks page with logos to link to the quick start guides * Renamed the mdx file so the link works * Added basic platform guides * Introduction doesn’t reference next.js only * Added a note about serverless and restructured the side menu * Added more frameworks pages to the manual install section * Fixed SVG error * Coming soon guides now using snippets so they can be in 2 places while we work on them * Removed redirects * Added a new named icon * increased fireworks particle count slightly * Creating a route for the onboarding and link to access it anytime from the side menu * Moved the onboarding into new components * Updated the routes for the onboarding page * Onboarding is now Setup and the frameworks overview page now links to different framework page in the onboarding side nav * URLs and pages renamed to ‘setup’ * URLs and pages renamed to ‘setup’ * Fixed some old named component imports * WIP on a new less hacked-in background image * Added svg logos for all the frameworks * New paths for the new framework pages * Side menu collapses once you selected a framework * Temporary Nuxt page * New routes for the new frameworks * New ‘framework coming soon’ component - now used in the coming soon framework pages * Moved/removed files * Moved all svg framework logos into a new folder and file * balanced the logo sizes * Framework coming soon pages take a name and url * New express svg logo * New component for a Framework item in the grid * Added information and design for the coming soon frameworks * Change the grid to 1 row if jobs === 0 * Updated the framework coming soon snippet and added it to the relevant pages * Express now 2nd in all lists * Added link to long running server support discussion * New logo to include next.js + supabase quick start * roadmap now links to homepage with page anchor to roadmap section * changelog now links to Github releases page * Removed reference to Next.js * Docs pages with coming soon info all share the same framework snippets * Fixed issue of missing props * Moved the fireworks effect into a separate file to make it easier for adding more framework onboarding pages * Info callouts have a more muted style * Added a callout to the top of the next onboarding to reference Serverless-only support * Moved the callout explaining scheduled triggers not working in dev to the bottom of the test panel This is to resolve eric’s UX ticket: https://github.com/triggerdotdev/trigger.dev/issues/416 * Added groundwork for Nest.js framework * Using framer motion for the menu transition instead of css - now has a slight spring and is snappier * redirect the manual setup page to the new nextjs setup page * Fixed broken docs link * Added a readme.md to next.js package * Capital I for integration * Renamed component: NextDevCommand to RunDevCommand * Made required props non-optional * CLI now points at manual install guides if no Next project detected * Explicitly made supported default to false (it was working but a bit hard to read) * Added links to all github issues for the frameworks coming soon component --------- Co-authored-by: Matt Aitken <matt@mattaitken.com> |
||
|
Matt Aitken
|
8ddd151051 | Re-ordered runTask params in docs, and example Jobs in the app. | ||
|
James Ritchie
|
4fc5de0dac | Fixed console errors | ||
|
Liran Tal
|
e347389b64 |
docs: Update integrations.mdx (#328)
* Update integrations.mdx The first sentence in this paragraph for `### API Keys and Tokens` was missing a word or two and it wasn't entirely clear what did the original author of this docs page intended. I've entered what seems to be the missing context but happy to re-phrase too if another wording makes better sense here. * Made it clear that API keys are provided by you in your code --------- Co-authored-by: Matt Aitken <matt@mattaitken.com> |
||
|
Liran Tal
|
10f92a6124 |
docs: Update runs.mdx (#327)
* docs: Update runs.mdx From what I can tell, it is expected for run functions to return with some sort of payload. Providing an example here as a reference and guideline. * Made it clear returning data is optional and added some more detail below --------- Co-authored-by: Matt Aitken <matt@mattaitken.com> |
||
|
Chigala
|
b884a0ab53 |
doc: added a new documentation for event filters (#300)
* doc: added a new documentation for event filters * removed typos from the event filter doc and formatted it better. * made new changes - moved the eventfilter doc to the guides section - linked the old eventfilter doc to the new one * updated the eventfilter doc based on the requested changes |
||
|
Eric Allam
|
1b7c7520b4 | new Job -> client.defineJob | ||
|
Eric Allam
|
342ab0d471 | Adding docs back into this repo |