Merged
Conversation
|
🍹 The Update (preview) for dailydotdev/api/prod (at 953cb76) was successful. Resource Changes Name Type Operation
~ vpc-native-private-deployment kubernetes:apps/v1:Deployment update
- vpc-native-api-db-migration-d959c590 kubernetes:batch/v1:Job delete
~ vpc-native-hourly-notification-cron kubernetes:batch/v1:CronJob update
~ vpc-native-generate-search-invites-cron kubernetes:batch/v1:CronJob update
~ vpc-native-clean-zombie-opportunities-cron kubernetes:batch/v1:CronJob update
- vpc-native-api-clickhouse-migration-d959c590 kubernetes:batch/v1:Job delete
~ vpc-native-update-highlighted-views-cron kubernetes:batch/v1:CronJob update
~ vpc-native-personalized-digest-deployment kubernetes:apps/v1:Deployment update
+ vpc-native-api-db-migration-4322cde4 kubernetes:batch/v1:Job create
+ vpc-native-api-clickhouse-migration-4322cde4 kubernetes:batch/v1:Job create
~ vpc-native-temporal-deployment kubernetes:apps/v1:Deployment update
~ vpc-native-update-source-public-threshold-cron kubernetes:batch/v1:CronJob update
~ vpc-native-clean-zombie-users-cron kubernetes:batch/v1:CronJob update
~ vpc-native-post-analytics-history-day-clickhouse-cron kubernetes:batch/v1:CronJob update
~ vpc-native-update-current-streak-cron kubernetes:batch/v1:CronJob update
~ vpc-native-check-analytics-report-cron kubernetes:batch/v1:CronJob update
~ vpc-native-validate-active-users-cron kubernetes:batch/v1:CronJob update
~ vpc-native-ws-deployment kubernetes:apps/v1:Deployment update
~ vpc-native-personalized-digest-cron kubernetes:batch/v1:CronJob update
+ vpc-native-user-profile-updated-sync-cron kubernetes:batch/v1:CronJob create
~ vpc-native-calculate-top-readers-cron kubernetes:batch/v1:CronJob update
~ vpc-native-generic-referral-reminder-cron kubernetes:batch/v1:CronJob update
~ vpc-native-update-views-cron kubernetes:batch/v1:CronJob update
~ vpc-native-post-analytics-clickhouse-cron kubernetes:batch/v1:CronJob update
~ vpc-native-clean-stale-user-transactions-cron kubernetes:batch/v1:CronJob update
~ vpc-native-sync-subscription-with-cio-cron kubernetes:batch/v1:CronJob update
~ vpc-native-update-tag-recommendations-cron kubernetes:batch/v1:CronJob update
~ vpc-native-clean-gifted-plus-cron kubernetes:batch/v1:CronJob update
~ vpc-native-clean-zombie-user-companies-cron kubernetes:batch/v1:CronJob update
~ vpc-native-clean-zombie-images-cron kubernetes:batch/v1:CronJob update
~ vpc-native-bg-deployment kubernetes:apps/v1:Deployment update
~ vpc-native-update-tags-str-cron kubernetes:batch/v1:CronJob update
~ vpc-native-update-trending-cron kubernetes:batch/v1:CronJob update
~ vpc-native-daily-digest-cron kubernetes:batch/v1:CronJob update
~ vpc-native-update-source-tag-view-cron kubernetes:batch/v1:CronJob update
~ vpc-native-deployment kubernetes:apps/v1:Deployment update
|
capJavert
commented
Dec 3, 2025
Comment on lines
+106
to
+111
| @OneToMany( | ||
| 'UserExperienceSkill', | ||
| (skill: UserExperienceSkill) => skill.experience, | ||
| { lazy: true }, | ||
| ) | ||
| skills: Promise<UserExperienceSkill[]>; |
Contributor
Author
There was a problem hiding this comment.
just moved here, skills can technically appear on other entities as well already
capJavert
force-pushed
the
user-profile-updated-publish
branch
from
4c01c88 to
e925527
Compare
capJavert
commented
Dec 3, 2025
| export const userProfileUpdatedSync: Cron = { | ||
| name: 'user-profile-updated-sync', | ||
| handler: async (con) => { | ||
| const timeThreshold = subHours(new Date(), 6); |
Contributor
Author
There was a problem hiding this comment.
We opted for cron because we want to deliver full user experience profile to gondul for easier parsing.
Because of users potentially changing experiences multiple times in a row it would be expensive to compute on every CDC change.
This is why we throttle and just do a once of publish every 6 hours.
Will monitor how it goes in production and adjust schedule/batching if needed. cc: @davidercruz
capJavert
requested review from
AmarTrebinjac,
davidercruz,
omBratteng and
rebelchris
rebelchris
approved these changes
Dec 3, 2025
Contributor
rebelchris
left a comment
rebelchris
left a comment
There was a problem hiding this comment.
We just have to think well with Davide how we can mitigate this, because having to wait 6 hours after CV upload before being able to do the scoring might be long?
Contributor
Author
|
@rebelchris we agreed already on this approach |
Contributor
Author
|
We can also lower, I just want to see how much changes we get throughout the day. I lowered to 3 hours for now. |
Contributor
|
@rebelchris @capJavert let's go with 3 hours and see how it goes. |
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
3 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.
Uh oh!
There was an error while loading. Please reload this page.