-
Notifications
You must be signed in to change notification settings - Fork 419
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(jobs): local runner for enterprise #2212
Conversation
@@ -29,7 +29,7 @@ export function getRunnerId(suffix: string): string { | |||
|
|||
export async function getOrStartRunner(runnerId: string): Promise<Runner> { | |||
const waitForRunner = async function (runner: Runner): Promise<void> { | |||
const timeoutMs = 5000; | |||
const timeoutMs = isEnterprise ? 60000 : 5000; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not sure this is necessary since for remote runner we can assume it is always on (ie: it is not managed by nango)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing some context here, why would we drop the RemoteRunner?
Is it a temporary fix?
https://nangohq.slack.com/archives/C067NRBH1LL/p1716911965222909 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see 👍🏻
context could have been added here for posterity imo
Fair, description updated. |
Describe your changes
Issues with the runner failing health checks for enterprise. Using a a remote runner requires the API call from jobs to the runner stay open for the duration of the sync. This can be problematic as the connection can drop or be terminated for a number of reasons. This piece of [code](https://github.com/NangoHQ/nango/blob/master/packages/jobs/lib/integration.service.ts#L124-L133] should be refactored soon so that this logic is more portable across different cloud providers besides just our own.
Issue ticket number and link
Checklist before requesting a review (skip if just adding/editing APIs & templates)