Skip to content
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

Implementing Phoenix-side code to crawl documents using OTA engine #1177

Open
wants to merge 24 commits into
base: master
Choose a base branch
from

Conversation

madoleary
Copy link
Contributor

  • Are you working on the latest release?
  • Have you tested it locally?
  • [->] Please explain your change

This PR would implement the OTA engine for crawling document text on document creation, update, and for individual crawls made on-demand by the user. This addresses issue #1168

It also includes error-handling and removes references to the old crawler system.

Copy link
Member

@michielbdejong michielbdejong left a comment

Choose a reason for hiding this comment

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

LGTM!

package.json Outdated
@@ -2,6 +2,7 @@
"name": "phoenix",
"private": true,
"dependencies": {
"@opentermsarchive/engine": "^1.1.2",
Copy link
Member

Choose a reason for hiding this comment

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

why is this npm package becoming a phoenix dependency?

Copy link
Member

Choose a reason for hiding this comment

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

Hm, it seems to come from a commit from 5 months agp, you should probably run npm remove @opentermsarchive/engine in the repo root and then commit that.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

@michielbdejong
Copy link
Member

michielbdejong commented Sep 26, 2024

Code is working in development but merging this PR to main is still blocked on #1186 since (we think) that would trigger a deploy to production - don't merge this PR until the necessary production environment variables are in place!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants