8000 Rolling importer fixes by mokimo · Pull Request #4413 · adobecom/milo · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Rolling importer fixes #4413

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

Merged
merged 7 commits into from
Jun 19, 2025
Merged

Rolling importer fixes #4413

merged 7 commits into from
Jun 19, 2025

Conversation

mokimo
Copy link
Contributor
@mokimo mokimo commented Jun 16, 2025

Description

Due to network flakiness, a few requests can timeout leading to articles not being successfully imported. We can have some very simplified "retry" logic here, to retry once, which should bring down failures to close to 0. It's manual effort for me to import any straddlers, hopefully can be avoided with this already.

Also added a from-to date for easier tracking of the exact calls we make to the AEM APIs and allowing to set more params locally to simulate a workflow run for debugging purposes.

Test URLs:

Copy link
Contributor
aem-code-sync bot commented Jun 16, 2025
Page Scores Audits Google
📱 /?martech=off PERFORMANCE A11Y SEO BEST PRACTICES SI FCP LCP TBT CLS PSI
🖥️ /?martech=off PERFORMANCE A11Y SEO BEST PRACTICES SI FCP LCP TBT CLS PSI

@@ -0,0 +1,3 @@
export default [
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Compared to localPathsToImport, which actually, when set, would import those specific paths.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it make sense to have these notes as a comment in the file itself, so whoever runs the script knows which to use?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm still not clear about the difference between the two files. I see localPathsToImport is used to read from it, while importingPaths is used to write in it.

Copy link
Contributor Author
@mokimo mokimo Jun 19, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried to add a more elaborate explanation... You're right, localPathsToImport is being read and we only import those articles. Handy for tracking down failures and debugging specific imports.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The now named paths-that-are-being-currently-imported file, just shows whatever is being imported. Based on logs, or local file.
Comes in handy when the logs have certain articles that were 'previewed' but not published, so it avoids any confusion

Copy link
Contributor

This pull request is not passing all required checks. Please see this discussion for information on how to get all checks passing. Inconsistent checks can be manually retried. If a test absolutely can not pass for a good reason, please add a comment with an explanation to the PR.

Copy link
Contributor
@overmyheadandbody overmyheadandbody left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a few notes

@@ -0,0 +1,3 @@
export default [
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it make sense to have these notes as a comment in the file itself, so whoever runs the script knows which to use?

@mokimo mokimo force-pushed the rolling-importer-fixes branch from 2192fb4 to 0586f2e Compare June 19, 2025 12:23
@mokimo mokimo force-pushed the rolling-importer-fixes branch from 36b4b0d to d92a1b0 Compare June 19, 2025 12:27
@mokimo mokimo requested a review from narcis-radu June 19, 2025 12:37
@mokimo mokimo merged commit a615af4 into adobecom:stage Jun 19, 2025
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0