Skip to content

AP-783: Add GOBI processing DAG - #96

Open
anarchivist wants to merge 8 commits into
mainfrom
AP-783
Open

AP-783: Add GOBI processing DAG#96
anarchivist wants to merge 8 commits into
mainfrom
AP-783

Conversation

@anarchivist

@anarchivist anarchivist commented Aug 6, 2026

Copy link
Copy Markdown
Member

Migrates the existing GOBI processing script to Airflow using Codex.

@anarchivist
anarchivist force-pushed the AP-783 branch 2 times, most recently from d27119e to 5d8db27 Compare August 11, 2026 21:16
@anarchivist
anarchivist marked this pull request as ready for review August 11, 2026 21:45
@anarchivist anarchivist changed the title AP-783: Add GOBI processing DAG [WIP] AP-783: Add GOBI processing DAG Aug 11, 2026
@anarchivist
anarchivist requested a review from awilfox August 11, 2026 21:57

@davezuckerman davezuckerman left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I'm not versed enough in Python to suggest any potential improvements. As far as the logic goes this looks completely accurate and should do everything the current Gobi script is doing.

@awilfox awilfox left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Not too much to change, but I think it warrants a bit of fine-tuning before merge.

Comment thread mokelumne/dags/process_gobi_orders.py Outdated
Comment thread mokelumne/dags/process_gobi_orders.py Outdated
Comment thread mokelumne/dags/process_gobi_orders.py Outdated
Comment thread mokelumne/dags/process_gobi_orders.py Outdated
Comment thread mokelumne/util/gobi.py Outdated
Comment thread mokelumne/util/gobi.py Outdated
Comment thread mokelumne/util/gobi.py Outdated
Comment thread mokelumne/util/gobi.py Outdated
Comment thread mokelumne/util/gobi.py
final_path,
)
self.skipped_providers.add(provider)
temporary_path.unlink()

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Do we want to remove this if there's already an output, or do we want to keep it for debugging purposes? I'm on the fence; this shouldn't really happen in practice so it's probably fine to leave the file, but we also don't want to fill up the disk with a bunch of temporary nonsense files that don't need to be there if something goes sideways.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

i'm thinking we might want to retain this for debugging. however, i can see that the use of the UUID-based directory here probably means we need to change the temporary path construction to use something along the lines of run_dir() as used in other Dags if we want to support a shared set of cleanup processes. what do you think?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Using something like run_dir makes sense, with a base_dir somewhere inside the GOBI storage path (perhaps the output directory).

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

this has been refactored in 9ac18d3.

anarchivist and others added 6 commits August 12, 2026 16:06
Co-authored-by: Codex GPT-5.6-sol <noreply@openai.com>
Co-authored-by: Codex GPT-5.6-sol <noreply@openai.com>
Co-authored-by: Codex GPT-5.6-sol <noreply@openai.com>
Co-authored-by: Codex GPT-5.6-sol <noreply@openai.com>
anarchivist and others added 2 commits August 13, 2026 10:52
Use run-scoped staging directories on the output filesystem so abandoned files can be attributed and cleaned up without weakening atomic publication.

Co-authored-by: Codex GPT-5.6-sol <noreply@openai.com>
@anarchivist
anarchivist requested a review from awilfox August 13, 2026 21:48

@awilfox awilfox left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

r+ I see no issues, but have not done a local test run yet.

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.

4 participants