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

Explicit assignment execution fails for assignments that have never been built #28

Open
io7m opened this issue Mar 29, 2024 · 2 comments
Assignees
Labels
bug Something isn't working server Issues involving the server

Comments

@io7m
Copy link
Member

io7m commented Mar 29, 2024

Specifically the NPUCommandAssignmentExecute command will call the assignment service directly. The assignment service is not responsible for making sure that the repository associated with the assignment exists or is up-to-date. It might be better for the command to call the scheduling service instead. This makes slightly more conceptual sense... "Schedule this assignment to run right now."

@io7m io7m added bug Something isn't working server Issues involving the server labels Mar 29, 2024
@io7m io7m self-assigned this Mar 29, 2024
@io7m
Copy link
Member Author

io7m commented Mar 30, 2024

Actually, I think that the assignment service should clone a repository if it doesn't exist. It shouldn't attempt to update an existing repository.

The reason is that the assignment service is responsible for creating the various bits of database state that say that an assignment has started executing. We want the clone time and information to be included in the assignment execution logs.

@io7m
Copy link
Member Author

io7m commented Apr 13, 2024

The repository service needs restructuring. It should be rewritten to be as isolated as possible; nothing else should be reading the repository database state. Any other services that need to do things with repositories must make synchronous calls to the repository service.

io7m added a commit that referenced this issue Apr 14, 2024
This restructures the repository service such that it is now the
authority when it comes to updating repositories and writing any
repository-related database state.

Affects: #28
io7m added a commit that referenced this issue Apr 14, 2024
Adjust how branches and tags are calculated, and improve error logging.

Affects: #28
io7m added a commit that referenced this issue Apr 14, 2024
Ensure that directories are created for output files.

Affects: #28
io7m added a commit that referenced this issue Apr 17, 2024
* Classify repository events under their own sealed interface
* Create a single-transaction interface for brevity
* Implement more metrics

Affects: #28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working server Issues involving the server
Projects
None yet
Development

No branches or pull requests

1 participant