Skip to content

fix: remove stray merge-conflict marker in assets resources#2

Closed
mxatmx wants to merge 1 commit into
mainfrom
fix/stray-conflict-marker
Closed

fix: remove stray merge-conflict marker in assets resources#2
mxatmx wants to merge 1 commit into
mainfrom
fix/stray-conflict-marker

Conversation

@mxatmx

@mxatmx mxatmx commented Jun 13, 2026

Copy link
Copy Markdown
Owner

A lone <<<<<<< HEAD marker was committed on main in zou/app/blueprints/assets/resources.py (in the AssetsAndTasksResource POST handler). It has no matching =======/>>>>>>>, and a single stray marker line is a SyntaxError that breaks import of the module — and therefore the whole app fails to start.

This removes just that one line; the surrounding code was already correct (it is the intended body = validation.validate_request_body(NewAssetSchema) branch).

Verified: python -m py_compile passes and the file is free of conflict markers.

A lone '<<<<<<< HEAD' line was left in the AssetsAndTasksResource POST
handler, which broke import of the module (and the whole app). Remove it;
the surrounding code was already correct.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@mxatmx

mxatmx commented Jun 13, 2026

Copy link
Copy Markdown
Owner Author

Superseded by #1, which includes this stray-marker removal (plus the test_assignment.py cleanup and the OIDC feature). Closing as already merged via #1.

@mxatmx mxatmx closed this Jun 13, 2026
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.

1 participant